The new built fixed the issue. Thanks for the fast response. Much appreciated.

I 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

@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

@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

@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

@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.

@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:40040

DuckDuckGo 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:44

Firefox 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:58

Chrome 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)
``

@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")

@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

@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

@toggledbits I now have the requested log file.

I 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

@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.0

Vestibule 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=null

tilt_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=null

tilt_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=null

tilt_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

@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.0

battery_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

@toggledbits It never crossed my mind to use HTTP. I'll give it a try.

Referencing 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
endif

Setting 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_delay

Thanks in advance

@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

@toggledbits I just noticed that the tilt_sensor.state = false now and no longer can be used in my rule. I have to use door_sensor.state instead.

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.3

battery_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

@toggledbits Got it. Will show all attributes next time. Thanks

@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: 0xd5ed4cd5

PS 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