Ok, now I'm really confused. As part of my attempt to update reactor, the docker container obviously got restarted - and now the rule is working as expected, with only the change condition. I have no idea why the change in behavior, but at least it is now working as you guys expected.
I
ibrewster
@ibrewster
@toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.
I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.
I see these errors on the following browsers:
Safari 16.6.1 on macOS Big Sur Safari 18.1.1 on MacOS Sonoma DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma Firefox 133.0.3 on macOS Big Sur Chrome 131.0.6778 on macOS Big SurHere are the errors
Safari while creating/updating an expression
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29 reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32 @http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40 dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040DuckDuckGo while clicking on status
http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44 asyncFunctionResume@[native code] saveGridLayout@[native code] dispatchEvent@[native code] _triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30 _triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31 makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30 addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24 placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44Firefox while updating a rule
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39 forEach@[native code] @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58Chrome while creating/updating an expression
TypeError: Cannot read properties of undefined (reading 'getEditor') at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86) at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54) at http://192.168.0.13:8111/client/MessageBus.js:98:44 at Array.forEach (<anonymous>) at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54) at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44) at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15) at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18) ``Build 24343 has fully HTTP actions, so cool things could be created (see docs). I've recently changed a couple of cams because better definition and I've found tha Reolink has a couple of cams that have spotlights. While the spotlights are driven by motion (so the cam could record in color), I wanted to drive them directly, so in case of any "security" event, like alarm on, door open, etc, I could use the lights to have a better video and make - you know - light.
So, if you want to use HTTP actions in VirtualController, just go to config, entities under your VirtualEntityController section in reactor.yaml, and add this:
- id: cams_retro_spotlights name: "Retro Cam - Spotlights" template: Binary Switch # update the status at interval http_request: interval: 900 # 15m url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo" method: "POST" force_json: true headers: "Content-Type": "application/json" "Accept": "application/json" body: '[{"cmd": "GetWhiteLed", "action": 0 , "param": { "channel": 0 }}]' capabilities: power_switch: attributes: state: expr: "isnull( response ) ? null : response[0]?.value?.WhiteLed?.state == 1" default: false actions: "on": http_request: url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo" method: "POST" force_json: true headers: "Content-Type": "application/json" "Accept": "application/json" body: '[{"cmd": "SetWhiteLed", "param": { "WhiteLed": {"bright" : 100, "channel": 0, "mode": 1, "state": 1}}}]' target: state expr: "isnull( response ) ? null: response[0]?.value?.rspCode == '200'" "off": http_request: url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo" method: "POST" force_json: true headers: "Content-Type": "application/json" "Accept": "application/json" body: '[{"cmd": "SetWhiteLed", "param": { "WhiteLed": {"bright" : 100, "channel": 0, "mode": 1, "state": 0}}}]' target: state expr: "isnull( response ) ? null : response[0]?.value?.rspCode == '200' ? false : null"Reolink has API where you have to post a JSON and the response will give you a JSON (in theory). It's not really JSON, so force_json: true will do the trick for you. I'm lefting this as an example of cool things you could do with the new capabilites added/documented in 24343. HTH.
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi
Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.
I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.
I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?
I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.
But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?
So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.
This is how I installed nodejs as whilst logged in as root
ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png
Thanks in advance.
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.As the title says, here's my OpenAI Controller for Reactor:
OpenAI Controller per Reactor. Contribute to dbochicchio/reactor-openai development by creating an account on GitHub.
It supports both OpenAI and Azure OpenAI endpoints. You'll need keys/endpoints, according to each service.
The controller supports multiple models, and each one could be mapped as an entity.
It's quite easy to use, and responses can be stored in variables, for easy access. Or sent to another action (Text To Speech, another endpoint, etc).
9013ae50-fd68-42a2-87c3-97479132e465-image.png
80a88eec-7c89-464a-8196-690b4b72d044-image.png
Have fun with LLM into your scenes!
I've switched to a virtual entity with both power_switch and string_sensor capabilities to represent the current holiday.
The power switch is used to indicate if it's a public holiday (so, no school/work), while the string sensor is a string with the actual holiday (Easter, Christmas, Halloween, etc - we don't have thanksgiving), mostly to drive lights.
I build it with some static dates (mostly birthdays/anniversaries) and then the dynamics ones are taken from webcal.guru. My lights/scenes are linked to events this way and it's easier to manage it in the long run: just a bunch of group action in the reaction driving the lights. This part is outside Reactor for me (because, legacy), but it's not difficult to completly drive it off a virtual sensor or a custom controller.
I don't know how people are doing this, but I'm lefting a note for the ones looking for a working solution.
In Home Assistant I have an integration that if I add entities to it, I will get the following error in MSR as certain entity values I'm using in expressions are null for a moment. This is more or less cosmetic issue and happens very rarely as I rarely modify that integration on the hass side.
Screenshot 2024-11-28 at 22.20.41.png
And the expression is
Screenshot 2024-11-28 at 22.38.19.png
Could I "wrap" hass-entity shown above somewhat differently to prevent this error from happening? Using build 24302.
Hello
I am trying to set up Multi System Reactor to automate routines across multiple smart home devices & platforms (e.g., Home Assistant, SmartThings, and Hubitat). While I have successfully linked the systems; I am facing issues with:
-Delays in triggering actions on secondary devices.
-Inconsistent execution of complex logic conditions.
-Synchronization of states between devices when one system updates.
Is there a recommended way to optimize performance & confirm seamless state sharing across systems?
I have checked https://smarthome.community/category/22/multi-system-reactor-msbi guide for reference but still need advice.
Any tips on debugging or log analysis to pinpoint where the issue arises would also be appreciated.
Thank you !
Hello AK
Have been writing about the openLuup email server as I was tinkering with it the other day. One minor problem: it looks like the domain part of the email address eg ...@openLuup.local is case sensitive in openLuup.
Looking round the net, it suggests that the local part is case sensitive but the domain part is not meant to be. To keep things so they are more likely to work, it's suggested the email address should be totally case insensitive regardless. Refer to rfc2821 page 13 or search on the word "sensitive". Suffice to say I was using mail@openluup.local rather than mail@openLuup.local, so it didn't work for me.
Next challenge was that the file saved in /etc/cmh-ludl/mail has "Content-Transfer-Encoding: base64" so the body of the email was encoded:
Received: from ((openLuup.smtp) [ip_address_1] by (openLuup.smtp v18.4.12) [ip_address_2]; Tue, 26 Nov 2024 14:21:22 +1000 From: "dali@switchboard" <dali@switchboard> To: "mail@openLuup.local" <mail@openLuup.local> Subject: Warning form R2E. MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: base64 QXV0byBXYXJuaW5nOiBDb2xkIHN0YXJ0IGV2ZW50The above base 64 text translates to "Auto Warning: Cold start event".
Is it your preference to leave the saved files in the raw mode or would you consider translating the base64 text in the openLuup code base?
On a side note, does the reception of an email by openLuup generate some sort of trigger that can be watched. In the case above; the email represents the restoration of power after a power outage. I would like to know about that by the email triggering a "Telegram" notification on my mobile.
I see that the images@openLuup.local images@openLuup.local can be associated with I_openLuupCamera1.xml, which spawns a movement detector child. Anything similar for the other email addresses?
I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
@toggledbits Since I have upgraded ZWaveJSController to 24293 from 24257 I am seeing entries related to registering action set_volume, but action is not defined by the capability 143 every time I restart Reactor.
The Siren seems to be doing what it is supposed to do. The volume levels are fine. Should I worry about it?
Reactor version 24302
ZWaveJSController version 24293
Z-Wave JS UI version 9.27.4
zwave-js version 14.3.4
I have an oven that I need to manage the temperature of, keeping it in the neighborhood of 600° C (1100° F). I have not been able to find a Zigbee-enabled solution to measure temps that high. Does anyone know if such a thing exists? If not, any ideas for how to roll a custom solution that I could integrate into a Sonoff ihost controller? I have no trouble finding high temperature probes, but none of them interface with my automation stack.
Hi All
Hopefully this place looks like a helpful forum as I’m quite new to all this!
I’ve had a few devices all working separately /through their proprietary apps but we’re just finishing off a large house extension and this has added to the list.
I’d ideally like to be able to view/switch a number of different devices on one screen/head end but have no idea where to start.
The devices we have/will have shortly are as follows;
Zigbee Smart Sockets
Zigbee smart switches (for lights)
Heatmiser Neo Underfloor Heating (this runs from a Samsung ASHP but that part is automatic)
Samsung VRF air conditioning (currently using Smart Things App)
Hive (2xLTHW heating circuits in the existing house and Hot Water)
Ring (doorbell!)
Hik Vision PoE CCTV
We have lots of appliances (Neff N70) which we can control remotely but not too fussed about controlling those at the
Moment)
Any help/recommendations would be appreciated!
Thanks
Adrian
After a major hassle got z-way running on my ubuntu 16 VM with a USB pasthough UZB1 stick including license and connected to Vera...
I see:
I also see:
0d6e8c78-c8cd-4307-9474-23e0d6a55094-image.png
But how do I update that?
e09ffa19-a31d-4a03-8983-01228bc5478f-image.png
I have a legacy home automation set-up running on Windows XP. the computer and software have now died.
I have written a very nice Excel VBA program to replace the software and it can run on any modern Windows system.
My only remaining problem is to output the correct signal to a USB port to trigger the wireless switches.
Has anybody done a similar exercise. Please help.
The locksmith is trying to persuade me to purchase the BE-TECH K35 touchscreen lock with both Wi-Fi and Bluetooth, claiming it's better than the Yale Assure Lock 2. What are your thoughts on this? Which one would you recommend?
Here is the link to the Chinese brand BE-TECH: BE-TECH Smart Deadbolt K3S.
The other smart lock I am considering is the Schlage Encode Plus.
Thank you!
Posts
-
Run rule on dimmer change? -
Run rule on dimmer change?Reactor latest-23302-b7def56a; docker on Ubuntu 20.04; With Vera Plus and Ezlo Plus controllers
Nope, the delay reset box is empty (nor have I tried to make any modifications in that section of the rule).
Although now that you mention it, it does seem odd, since while the rule remains set, if I toggle the rule open in the Rule Set list, the condition is evaluating to false, which (I would think) should reset the rule...right?
I have updated reactor recently, but let me try again in case 23302-b7def56a isn't the latest, and has a bug here...
EDIT: Nope, doesn't appear there are any updates available
-
Run rule on dimmer change?@tunnus said in Run rule on dimmer change?:
If you only have a single trigger with changes -operator, the rule is immediately reset after the change
That is not the behavior I am seeing. Sorry!
-
Run rule on dimmer change?@toggledbits said in Run rule on dimmer change?:
Please show your work (post screen shots of your rules).
As I mentioned, I tried to do so, but the forum gives me errors. Specifically, it will show the image as uploading, get to 100%, pause, drop back to 60% (or so), give me a message stating "Looks like your connection to SmartHome Community was lost, please wait while we try to reconnect", the progress goes up to 100% again, and then I get an error stating "Something went wrong while parsing server response", and the image is not uploaded, leaving me with something like this:
So as far as I can tell, no screen shot posting is possible.
Perhaps walking through the steps of what happens will help?
The rule is set up with a single Trigger:Entity Attribue -- Inovelli 2-in-1 (the switch) -- dimming.level -- changes -- from <blank> to <blank>A local expression is set up with the following code that gets the current dimming.level value:
SwitchLevel = getEntity( "ezlo>device_65655fb712a3b714bdbcb935" ).attributes.dimming.levelAnd a Set Reaction to set the LR Fan Light to the same level:
Entity Action -- LR Fan Light -- dimming.set -- ${{SwitchLevel}}- We start with the switch at 0 (off), and the rule is reset as expected
- We then set the switch to some other value (say, 50% or .5)
2a. The rule is now set, and the Set Reaction runs as expected.
2b. The rule remains set at this point - only going back to a dimming level of 0 will reset it. - We then set the switch to another value, say 75% or .75
3a. Since the rule is already in a set state, the Set Reaction does not run again, meaning the LR Fan light does not change dimming level
Adding in the rule of the LR Fan Light level <> SwitchLevel allows the rule to drop back to a reset state after setting the LR Fan Light Level, thereby allowing it to run again the next time the switch level changes.
-
Run rule on dimmer change?Ahhhh, I think I finally got it! If I add a second condition of device.dimming.level <> switch.dimming.level, then the rule is set whenever the switch changes, and quickly reset once the device is set to the same level, allowing the next change in switch level to properly trigger the rule again.
Only took me two days and a forum post to figure that one out...
-
Run rule on dimmer change?That is correct, yes - and it works when going from 0-->any. After that, however, the condition evaluates to true, the rule is set, and so further changes do not trigger it again, as per the documentation (once true it remains true and the rule is not run again until it evaluates to false, i.e. 0)
-
Run rule on dimmer change?Reactor latest-23302-b7def56a; docker on Ubuntu 20.04; With Vera Plus and Ezlo Plus controllers
I'm trying to tie the dimmer level of a dimmer switch to the dimmer level of a dimmable device (fan canopy light controller). In the triggers section of the rule I can select "dimming.level changes" as the condition, and I can get said dimming level in an expression that I then use to set the dimming.set attribute of the dimming device in the Set Reaction section, but this only works when going from 0--><some value>. When going from <some value> --> <some other value> or <some value>-->0, this does not work, because the rule is already set (it went true with the first change, and hasn't gone false yet - this is expected behavior as per the documentation)
I can fix the <some value>-->0 issue by setting the Reset Reaction, but how can I get the rule to run - and set the entity dimming level - every time the switch value changes?
(I tired to upload a screen shot of what I have, but I just kept getting errors)
-
EzloControler access credentials timeout?Reactor version: latest-22343-ef2b8f75
OS: Ubuntu 22.04.1 LTS, AMD EPYC 7262
Reactor installed vis Docker (docker-compose to be exact), version 20.10.12, build 20.10.12-0ubuntu4
Hub involved: Ezlo Plus Firmware 2.0.33.2116.2 Advanced Scenes 1.56Yes, much better - things seem to be working now. I'd attach a log (as you mentioned there were warnings about setting undefined, among other things), but apparently I can't do that yet, so I'll stand by for directions on the data collection.
Thanks for your help.
-
EzloControler access credentials timeout?AMD EPYC 7262
-
EzloControler access credentials timeout?Reactor version: latest-22337-1a0a685f
OS: Ubuntu 22.04.1 LTS
Reactor installed vis Docker (docker-compose to be exact), version 20.10.12, build 20.10.12-0ubuntu4
Hub involved: Ezlo Plus Firmware 2.0.33.2116.2 Advanced Scenes 1.56 -
EzloControler access credentials timeout?So perhaps the network timeout errors were some sort of temporary ban on my IP due to repeated logins? Just a thought, may not make any sense.
-
EzloControler access credentials timeout?Checking the log again this morning, I now have a different error - apparently whatever was causing the network timeout was resolved, but now I'm getting this (after a restart of reactor):
[latest-22337]2022-12-09T14:29:41.939Z <EzloController:INFO> EzloController#ezlo successful local connection (authenticated) to "90000478" [latest-22337]2022-12-09T14:29:41.940Z <EzloController:INFO> EzloController#ezlo starting hub inventory [latest-22337]2022-12-09T14:29:41.980Z <EzloController:INFO> EzloController#ezlo hub "90000478" is h2.1 (undefined) firmware "2.0.33.2116.2" [latest-22337]2022-12-09T14:29:41.980Z <System:WARN> System#ezlo>system attempt by caller to set attribute value to undefined [latest-22337]2022-12-09T14:29:41.980Z <System:CRIT> Error: traceback [-] Error: traceback at System.setAttribute (/opt/reactor/server/lib/Entity.js:454:152) at EzloController._process_hub_info (/opt/reactor/server/lib/EzloController.js:1516:768) at /opt/reactor/server/lib/EzloController.js:1354:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.138Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f5199de12a3b716d5ba2969: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] [latest-22337]2022-12-09T14:29:42.138Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.139Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f5199de12a3b716d5ba296c: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] [latest-22337]2022-12-09T14:29:42.139Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.141Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f5199de12a3b716d5ba296e: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] [latest-22337]2022-12-09T14:29:42.141Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.142Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f5199de12a3b716d5ba2970: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] [latest-22337]2022-12-09T14:29:42.142Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.143Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f63e44712a3b715b80ffcd2: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] [latest-22337]2022-12-09T14:29:42.143Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.146Z <EzloController:ERR> EzloController#ezlo error creating entity SecuritySensor#ezlo>device_618063af12a3b712364c7dc8: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-] [latest-22337]2022-12-09T14:29:42.146Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.148Z <EzloController:ERR> EzloController#ezlo error creating entity ValueSensor#ezlo>device_618063af12a3b712364c7dcf: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-] [latest-22337]2022-12-09T14:29:42.149Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.150Z <EzloController:ERR> EzloController#ezlo error creating entity ValueSensor#ezlo>device_618063af12a3b712364c7dd1: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-] [latest-22337]2022-12-09T14:29:42.150Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.153Z <EzloController:ERR> EzloController#ezlo error creating entity ValueSensor#ezlo>device_618063af12a3b712364c7dd3: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-] [latest-22337]2022-12-09T14:29:42.154Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.155Z <EzloController:ERR> EzloController#ezlo error creating entity Light#ezlo>device_6182b52012a3b7121fd6594b: [ReferenceError] Capability sys_group not extended (ezlo>room_5fed146312a3b716fad9f58d [-] [latest-22337]2022-12-09T14:29:42.155Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5fed146312a3b716fad9f58d [-] ReferenceError: Capability sys_group not extended (ezlo>room_5fed146312a3b716fad9f58d at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.157Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_618ff90912a3b7122edeaccd: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] [latest-22337]2022-12-09T14:29:42.157Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-] ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.158Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_61901ff112a3b71209e73282: [ReferenceError] Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a [-] [latest-22337]2022-12-09T14:29:42.159Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a [-] ReferenceError: Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.160Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_6190203012a3b71209e73286: [ReferenceError] Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a [-] [latest-22337]2022-12-09T14:29:42.160Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a [-] ReferenceError: Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19) at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39) at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31) at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227) at /opt/reactor/server/lib/EzloController.js:1612:61 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.161Z <EzloController:ERR> [TypeError] Cannot read properties of undefined (reading 'switch') [-] failed to process devices: [undefined2] [latest-22337]2022-12-09T14:29:42.161Z <EzloController:CRIT> TypeError: Cannot read properties of undefined (reading 'switch') [-] TypeError: Cannot read properties of undefined (reading 'switch') at EzloController._match_criterion (/opt/reactor/server/lib/EzloController.js:1119:84) at EzloController._map_device (/opt/reactor/server/lib/EzloController.js:1171:48) at /opt/reactor/server/lib/EzloController.js:1592:58 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.162Z <EzloController:ERR> EzloController#ezlo failed to complete inventory: [TypeError] Cannot read properties of undefined (reading 'switch') [-] [latest-22337]2022-12-09T14:29:42.162Z <EzloController:CRIT> TypeError: Cannot read properties of undefined (reading 'switch') [-] TypeError: Cannot read properties of undefined (reading 'switch') at EzloController._match_criterion (/opt/reactor/server/lib/EzloController.js:1119:84) at EzloController._map_device (/opt/reactor/server/lib/EzloController.js:1171:48) at /opt/reactor/server/lib/EzloController.js:1592:58 at Array.forEach (<anonymous>) at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226) at /opt/reactor/server/lib/EzloController.js:1413:48 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22337]2022-12-09T14:29:42.172Z <EzloController:NOTICE> EzloController#ezlo connection closed: 1002 [latest-22337]2022-12-09T14:29:42.173Z <EzloController:INFO> EzloController#ezlo will retry in 5000ms; this was attempt 1 -
EzloControler access credentials timeout?Yes, I set up a user specifically for reactor to use, with a username of reactor. Also, as I mentioned, when I originally set this up a while ago, it did work - only recently has it stopped working. Of course, if the user/password WAS wrong, (or something changed so it wouldn't work any more) I would expect a different error than "network timeout"
-
EzloControler access credentials timeout?I have Multi-System reactor set to with both my Vera Plus and Ezlo Plus - and up to a while ago, both were working. Recently, however, I noticed that it didn't seem to be communicating with my Ezlo Plus correctly. Looking at the logs, I see this:
[latest-22337]2022-12-09T03:44:49.980Z <EzloController:INFO> EzloController#ezlo: connecting to hub "90XXXXXX" [latest-22337]2022-12-09T03:44:49.980Z <EzloController:ERR> EzloController#ezlo: failed to get access credentials: [FetchError] network timeout at: https://vera-us-oem-autha11.mios.com/autha/auth/username/reactor?SHA1Password=<long_string>c&PK_Oem=1&TokenVersion=2 [-] [latest-22337]2022-12-09T03:44:49.980Z <EzloController:INFO> EzloController#ezlo will retry in 75000ms; this was attempt 17So apparently it is getting a timeout when trying to connect to vera to authorize? How can I fix this, or does it simply not work any more?