The new built fixed the issue. Thanks for the fast response. Much appreciated.
S
Snowman
@Snowman
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks.
Any chance of a 'bulk delete' option?
No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices
Cheers
C
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.
Just for the record, in case anyone is following, I'm really rather impressed.
I have installed one of these:
https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
That's connected (physically) to the VM running on my Synology, with a 2m USB extension.
The same host also runs Openluup, Mosquito, HA Bridge.
Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions.
Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor
I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA.
https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title
The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so...
https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title
Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt.
And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one).
A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....)
Commended to the house. Thanks for everyone that got me on the right lines.
C
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO:
Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1.
Then, configure these endpoints as needed:
On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on
Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off
Dim:
For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent}
For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent}
Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b}
Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier.
This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa!
If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Good evening all,
For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time.
Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed.
Thanks.
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations.
Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction?
Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for.
I guess it's something of an edge case so no huge issue.
TIA!
C
I'm sure this has been asked, and answered, but damned if I can figure it out
Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage.
Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts.
After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!)
What I would like is for the 3 minute delay until the lights go off to start from the latest door open event.
That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity.
I've tried 'hacking' with a virtual switch, but can't seem to stop the delay.
Any pointers?
TIA
C
Hello oh great ones.
After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi
Can connect to the front end and everything
Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this:
[Unit]
Description=zigbee2mqtt
After=network.target
[Service]
Environment=NODE_ENV=production
Type=notify
ExecStart=/usr/local/bin/node index.js
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
WatchdogSec=10s
Restart=always
RestartSec=10s
User=pi
[Install]
WantedBy=multi-user.target
Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using.
Running manually pnpm start
in /opt/zigbee2mqtt works fine
However:
catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service
Job for zigbee2mqtt.service failed because the control process exited with error code.
See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details.
Which I have
catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago
Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER)
Main PID: 3093 (code=exited, status=217/USER)
and
-- A start job for unit zigbee2mqtt.service has begun execution.
--
-- The job identifier is 17477.
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process
-- Subject: Process /usr/local/bin/node could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /usr/local/bin/node could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zigbee2mqtt.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 217.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'.
Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt.
-- Subject: A start job for unit zigbee2mqtt.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zigbee2mqtt.service has finished with a failure.
Which strikes me as very odd.
Any blindingly obvious things I'm missing?
TIA!
C
Obviously a quiet forum, but perhaps it's time
I'm looking at rolling Zigbee into my system, in large part for the Aqara FP300 presence sensors which seem to finally provide a solution to if the wasp is actually in the box.
My current set up is as follows:
One Debian VM on Synology NAS running:
Z-wave Server
Open Luup
Multi system reactor
HA bridge
Mosquito MQQT broker
This machine has a UZB Z-wave stick connected via the USB port on the NAS
Another HAOS VM on the same NAS running HAOS
I've got some older Z-wave stuff that I keep around until it fails.
I have some Tuya stuff integrated in HA
My thought was to get either a SMLIGHT SLZB-06M
or an Aqara Hub M2
Integrate them via Zigbee2MQQT (running on the Debian machine) and then expose them in HA so I can continue to automate in MSR.
Thoughts on which of those devices wold be preferable long term. Both are POE capable which is good. It also appears I could add a USB dongle to the NAS and expose it to the HAOS machine.
Any thoughts from the assembled experts here? TIA
C
Another question to the hive mind. Prompted by the fact that I lost yet another z-wave device over the weekend due to a power issue. It looks like z-way server is reporting another device failed (although it's working fine) and message queue is far too long IMHO. Also the failed device has been removed in the expert interface, but still there in the 'normal' one. Sigh.
Currently I have z-wave, Tuya, thinking about Zigbee.... Does anyone use one single protocol for everything? Right now I'm feeling that as the z-wave stuff dies, I'm just gonna replace it with something else....
C
Not really Smart Home stuff, but going to ask as we have smart people...
Bear with me on this one. Asking here because of the font of knowledge!
For many eek years I have had a Virgin V6 box and a Raspberry Pi running Kodi connected to my TV through a cheap *** HDMI switch. It all worked beautifully but the absolutely critical thing was that the TV remote passed the signals back to the Pi to allow remote control of Kodi.
Couple of changes of late:
Installed a soundbar on the TV using the ARC (audio return channel). That then turns the soundbar on and off when the TV turns on and off and the TV volume control controls the soundbar volume direct.
Everything continues to work
Upgraded the software of the Tivo box to Virgin 360. This is literally software only. You get sent a snacky new Bluetooth remote hit 'upgrade' on the screen and off it goes.
Now, things are not playing well. Typically when I turn on to watch Kodi the soundbar comes on (as it should) but the TV either puts out sound through its own speakers and the soundbar, or just the soundbar. It's not possible to control the volume of the soundbar through the TV. Also it's not longer possible to control Kodi using the TV remote.
If I turn the TV360 box off, i.e. power it down, before turning on to watch Kodi, everything is fine.
This makes little to no sense to me. My assumption is that the cheap *** HDMI switch is getting something from the TV360 connection that it didn't used to get when the software was Tivo and that's screwing up the HDMI communications. I'm upgrading the switch to something a little less chap, but wondered if anyone could validate my theory at all?
TIA
C
Posts
-
Cannot delete Global Expressions -
Cannot delete Global ExpressionsI am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.
I have not created a global expression for some times and just noticed this while doing some clean-up.
I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.
Here's what the log shows.
[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }Reactor latest-25067-62e21a2d
Docker on Synology NAS -
Button.Since Revisited@toggledbits In the MSR documentation, under Standard Capabilities, I noticed that the
button.since attribute was deprecated as of version 22256 and the metadata is the preferred way to access the last-modified time of an attribute.Am I reading this right? Should I stop using it in my rules?
Thanks
-
[SOLVED]Hass websocket falsely reporting ready on boot??@toggledbits I have a similar issue but I do not have a wait_all_controllers: true in my engine subsection.
I just add it I suppose ? Thanks
This is what I have under engine.
engine: # enabled - whether or not the rules engine runs. Change only when directed. enabled: true # # startup_wait - Time to wait for all controllers to come ready. Reactor often starts faster # than most hubs, so this pause allows Reactor to wait for a tunable time. The # Engine is not started until all controllers are ready or this timeout # expires. See https://smarthome.community/topic/700/start-up startup_wait: 600000 # milliseconds, default 60000 (one minute) # # allow_shell_action - The "Shell Command" reaction action comes with some security risks, so # by default it is disabled. To enable it, set this value true. # allow_shell_action: true # allow_shell_action_substitution: true # # shell_action_timeout - The "Shell Command" action will allow the running command to run for # up to this many milliseconds before it terminates it (to prevent run- # away processes). The default is 30000 (milliseconds, 30 seconds). #shell_action_timeout: 30000 # # monitored_entities - if you can't figure out what is changing an entity, # (not the data, but the physical device, like a light # that is being turned on or off at an unexpected time), # you can add it to this list and the logs will post # a message whenever an action is performed on the # device (no log level changes are needed, the message # is unconditional). # monitored_entities: # - vera>device_XXX -
Reactor-Editor / Reactor-ui-Status Errors@toggledbits Below, the error and a screenshot while creating a new Global Expression, named "test". Hoping this helps answer your questions.
As soon as I am done typing "test" and clicking in the field to add my formula, the error pops-up and will continue popping-up three times by the time it saved the changes. The error will also pop-up when I delete the expression and will pop-up a second time by the time it saved the changes.
It did not happen on the first use of the tab/function. It took a few tries before I could re-produce the error. It does resolve itself after a page refresh.
@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:40040
-
Reactor-Editor / Reactor-ui-Status Errors@toggledbits These errors are on the UI. Not from the logs. They are not preventing me from doing any work.
For example, I'll go to Expressions, click the Add Expression, and when I click the Save Changes button, that is when these errors pop-up.
Same goes with creating or updating a rule.
I'll post a screenshot next time I see one.
I'll try the Clear local storage suggestion and will let you know.
-
Reactor-Editor / Reactor-ui-Status Errors@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 Sur
Here 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) `` -
ZWaveJSController - Warning/Error Traceback - Registering action set volume for Aeotec Siren 6 (ZW164)@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[latest-24302]2024-11-22T02:10:32.852Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 0 (entity "143-0") [latest-24302]2024-11-22T02:10:32.854Z <Entity:WARN> Entity#zwavejs>143-1 registering action set_volume, but action is not defined by the capability [latest-24302]2024-11-22T02:10:32.855Z <Entity:CRIT> Error: Traceback [-] Error: Traceback at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112) at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84) at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38) at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [latest-24302]2024-11-22T02:10:32.859Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 1 (entity "143-1") [latest-24302]2024-11-22T02:10:32.860Z <Entity:WARN> Entity#zwavejs>143-2 registering action set_volume, but action is not defined by the capability [latest-24302]2024-11-22T02:10:32.861Z <Entity:CRIT> Error: Traceback [-] Error: Traceback at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112) at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84) at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38) at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [latest-24302]2024-11-22T02:10:32.864Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 2 (entity "143-2") [latest-24302]2024-11-22T02:10:32.866Z <Entity:WARN> Entity#zwavejs>143-3 registering action set_volume, but action is not defined by the capability [latest-24302]2024-11-22T02:10:32.866Z <Entity:CRIT> Error: Traceback [-] Error: Traceback at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112) at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84) at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38) at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [latest-24302]2024-11-22T02:10:32.870Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 3 (entity "143-3") [latest-24302]2024-11-22T02:10:32.871Z <Entity:WARN> Entity#zwavejs>143-4 registering action set_volume, but action is not defined by the capability [latest-24302]2024-11-22T02:10:32.872Z <Entity:CRIT> Error: Traceback [-] Error: Traceback at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112) at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84) at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38) at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [latest-24302]2024-11-22T02:10:32.876Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 4 (entity "143-4") [latest-24302]2024-11-22T02:10:32.878Z <Entity:WARN> Entity#zwavejs>143-5 registering action set_volume, but action is not defined by the capability [latest-24302]2024-11-22T02:10:32.878Z <Entity:CRIT> Error: Traceback [-] Error: Traceback at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112) at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84) at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38) at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [latest-24302]2024-11-22T02:10:32.881Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 5 (entity "143-5") [latest-24302]2024-11-22T02:10:32.883Z <Entity:WARN> Entity#zwavejs>143-6 registering action set_volume, but action is not defined by the capability [latest-24302]2024-11-22T02:10:32.884Z <Entity:CRIT> Error: Traceback [-] Error: Traceback at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112) at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84) at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38) at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [latest-24302]2024-11-22T02:10:32.887Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 6 (entity "143-6") [latest-24302]2024-11-22T02:10:32.888Z <Entity:WARN> Entity#zwavejs>143-7 registering action set_volume, but action is not defined by the capability [latest-24302]2024-11-22T02:10:32.889Z <Entity:CRIT> Error: Traceback [-] Error: Traceback at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112) at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84) at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38) at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [latest-24302]2024-11-22T02:10:32.892Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 7 (entity "143-7") [latest-24302]2024-11-22T02:10:32.893Z <Entity:WARN> Entity#zwavejs>143-8 registering action set_volume, but action is not defined by the capability [latest-24302]2024-11-22T02:10:32.894Z <Entity:CRIT> Error: Traceback [-] Error: Traceback at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112) at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84) at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38) at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [latest-24302]2024-11-22T02:10:32.896Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 8 (entity "143-8") -
Unusual zwavejs entity naming convention@toggledbits It appears the ZIP file you provided me with to fix the TILT-ZWAVE2.5-ECO tilt_sensor.state issue also fixed this topic. I do not see the unusual entity names. Thanks
-
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL@toggledbits The ZIP file fixed the issue. The tilt_sensor.state working as expected. Thanks
door_sensor.state=true tamper.state=true tilt_sensor.state=true -
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL@toggledbits I now have the requested log file.
-
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULLI did open and close the garage door after updating Reactor. More than once. I even removed the battery to see if it would make a difference.
I am looking at the Notification values under ZWaveJS UI ans can see that the Window/door state do toggle between TRUE/FALSE when the door opens and closes. Nothing unusual here.
Looking at Binary Sensor values, I am seing this though. Makes sense?
When the garage door Opens
When the garage door Closes
-
Unusual zwavejs entity naming convention@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=null
Tilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=nulltilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nulltilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=nulltilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null
-
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL@toggledbits I appears the tilt_sensor.state = false is back again after I upgraded both Reactor and ZWaveJSController to version 24257. It was working fine with ZWaveJSController version 24242.
I can certainly stop using this entity and use the door_sensor.state instead.
I did check the latest changes for zwave-js 13.2.0 and did not see any thing that may have been introduced causing this.
I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0battery_maintenance.charging=0 battery_maintenance.rechargeable=0 battery_maintenance.replace=false battery_maintenance.state="normal" battery_power.level=1 battery_power.since=null door_sensor.state=true tamper.state=true tilt_sensor.state=false x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":48,"metadata.ccSpecific.sensorType":255},"capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":113,"metadata.ccSpecific.notificationType":6},"capabilities":{"tilt_sensor":{"attributes":{"state":{"expr":"value === 22"}}}}}],"manufacturerId":330,"productType":4,"productId":3} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=100 x_zwave_values.Binary_Sensor_Any=false x_zwave_values.Binary_Sensor_Door_Window=true x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0 x_zwave_values.Configuration_Send_Reports=0 x_zwave_values.Manufacturer_Specific_manufacturerId=330 x_zwave_values.Manufacturer_Specific_productId=3 x_zwave_values.Manufacturer_Specific_productType=4 x_zwave_values.Notification_Access_Control_Door_state=22 x_zwave_values.Notification_Access_Control_Door_state_simple=22 x_zwave_values.Notification_Home_Security_Cover_status=3 x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0 x_zwave_values.Notification_UNKNOWN_0x46=23 x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Version_firmwareVersions=["10.1"] x_zwave_values.Version_hardwareVersion=2 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=14400 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="24256:1:24192:1" zwave_device.is_beaming=true zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1726513928400 zwave_device.manufacturer_info=[330,4,3] zwave_device.max_data_rate=100000 zwave_device.node_id=24 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[4,"10.1"] zwave_device.wakeup_interval=14400 -
How to reference a local expression inside a Shell Command@toggledbits It never crossed my mind to use HTTP. I'll give it a try.
-
How to reference a local expression inside a Shell CommandReferencing an expression inside a reaction is in the form of ${{ expression }}. When referenced inside my shell command to set the watering delay duration for my Rachio sprinkler system, it just does not work.
If I enter "86400" instead of referencing the expression lWateringDelayDuration, it works. Either I am doing something wrong or referencing an expression inside a shell command is not supported.
Reactor version: 24212
Local Expression
lWateringDelayDuration =WDD = getEntity( "hass>input_number_h_watering_delay_duration" ).attributes.value_sensor.value, if WDD == 0 then 0 elif WDD == 1 then 86400 elif WDD == 2 then 172800 elif WDD == 3 then 259200 elif WDD == 4 then 345600 endifSetting Reaction using Shell command
curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer xxxxxxxxxx -d '{ "id" : "xxxxxxxxxx", "duration" : ${{ lWateringDelayDuration}} }' https://api.rach.io/1/public/device/rain_delayThanks in advance
-
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL@toggledbits That fixed it. Thank you sir.
battery_maintenance.charging=null
battery_maintenance.rechargeable=false
battery_maintenance.replace=false
battery_maintenance.state="normal"
battery_power.level=1
battery_power.since=1720778246637
door_sensor.state=true
power_source.source=null
tamper.state=true
tilt_sensor.state=true -
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL@toggledbits I just noticed that the
tilt_sensor.state = falsenow and no longer can be used in my rule. I have to usedoor_sensor.stateinstead.I cannot tell when the issue started and not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 24190
ZWaveJSController version 23326
Z-Wave JS UI version 9.14.5
zwave-js version 12.12.3battery_maintenance.charging=null
battery_maintenance.rechargeable=false
battery_maintenance.replace=false
battery_maintenance.state=null
battery_power.level=1
battery_power.since=1720636775292
door_sensor.state=true
power_source.source=null
tamper.state=true
tilt_sensor.state=false
x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":48,"metadata.ccSpecific.sensorType":255},"capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3}
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Binary_Sensor_Any=false
x_zwave_values.Binary_Sensor_Door_Window=true
x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0
x_zwave_values.Configuration_Send_Reports=0
x_zwave_values.Manufacturer_Specific_manufacturerId=330
x_zwave_values.Manufacturer_Specific_productId=3
x_zwave_values.Manufacturer_Specific_productType=4
x_zwave_values.Notification_Access_Control_Door_state=22
x_zwave_values.Notification_Access_Control_Door_state_simple=22
x_zwave_values.Notification_Home_Security_Cover_status=3
x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0
x_zwave_values.Notification_UNKNOWN_0x46=23
x_zwave_values.Notification_alarmLevel=0
x_zwave_values.Notification_alarmType=0
x_zwave_values.Version_firmwareVersions=["10.1"]
x_zwave_values.Version_hardwareVersion=2
x_zwave_values.Version_libraryType=6
x_zwave_values.Version_protocolVersion="4.5"
x_zwave_values.Wake_Up_controllerNodeId=1
x_zwave_values.Wake_Up_wakeUpInterval=14400
zwave_device.capabilities=[48,112,113,114,128,132,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Notification Sensor"
zwave_device.impl_sig="23326:1:23318:2"
zwave_device.is_beaming=false
zwave_device.is_listening=false
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.last_wakeup=1720636775220
zwave_device.manufacturer_info=[330,4,3]
zwave_device.max_data_rate=null
zwave_device.node_id=24
zwave_device.specific_class="Notification Sensor"
zwave_device.status=1
zwave_device.status_text="asleep"
zwave_device.version_info=[null,"10.1"]
zwave_device.wakeup_interval=14400 -
Smart plugs showing battery maintenance capability@toggledbits Got it. Will show all attributes next time. Thanks
-
Smart plugs showing battery maintenance capability@toggledbits Any reasons that might escape me why there are battery_maintenance attributes for the Zooz (ZEN04), Aeotec (ZWA023) and Dome (DMOF1) smart plugs (and probably other smart plugs)?
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes in question in hopes it can help.
Thanks in advance.
Reactor: 23344
ZWaveJSController: 9.6.0.ec8995c
zwave-js: 12.4.1
home id: 3589098709
home hex: 0xd5ed4cd5PS I could copy all attributes but there are too many to be listed in this thread.
Attributes
battery_maintenance.charging=null battery_maintenance.rechargeable=false battery_maintenance.replace=false battery_maintenance.state=null