@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

Thank you both @togglebits and @Andr. I got it now.

@togglebits Thanks for the recommendation. I do have to ask though.

I am by no means an expert so how am I supposed to know this? The documentation does not mention anything about this. And based on your recommendation, I will have to review all my rules/logics using this device.

Thanks in advance.

If I understand you correcltly, I had the same issue when I first setup this device. Here's what I did to ensure the button state gets reset after a button is pressed two times in my case.

I am using the ZwaveJS controller provided by @togglebit.

Triggers

Controller Scene 001.button.state (primary) == double

Set Reaction

Controller Scene 001.button.release

The "button.release" action ensures the button state resets.

Give it a try.

That did the trick. Thanks again.

@togglebits I have another one for you.

HASS controller shows hvac_control.state="heating, cooling or idle".

ZWaveJSController controller shows hvac_control.state="heat, cool, or idle"

I believe hvac_control.state="heating, cooling or idle" should be what the ZWaveJSController should show.

"heat", "cool" or "off" are values assigned to the hvac_control.mode attribute.

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 of the thermostat in hopes it can help.

Thanks in advance.

Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3

battery_power.level=0.95
battery_power.since=1700301347874
humidity_sensor.units="%"
humidity_sensor.value=40
hvac_blower_unit.filter_change=null
hvac_blower_unit.mode="low"
hvac_blower_unit.state=true
hvac_control.mode="heat"
hvac_control.state="heat"
hvac_cooling_unit.setpoint=23.5
hvac_cooling_unit.state=false
hvac_cooling_unit.units="°C"
hvac_heating_unit.setpoint=20.5
hvac_heating_unit.state=false
hvac_heating_unit.units="°C"
power_source.source=null
temperature_sensor.units="°C"
temperature_sensor.value=20.5
x_debug.dt={"entity_class":"Thermostat","match":"deviceClass.generic.key=8","capabilities":["hvac_control"],"primary_attribute":"hvac_control.state","description":"T6 Pro Z-Wave Programmable Thermostat","model":"TH6320ZW","default_name":"Honeywell T6 Pro Thermostat","values":[{"valueId":"113:Power Management:Mains status","capabilities":{"power_source":{"attributes":{"source":{"expr":"([ 'unknown', 'unknown', 'dc', 'ac' ])[value ?# 0] ?? 'unknown'","update_only":true}}}}}],"manufacturerId":57,"productType":17,"productId":8}
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=95
x_zwave_values.Configuration_Adaptive_Intelligent_Recovery=1
x_zwave_values.Configuration_Air_Filter_1_Reminder=0
x_zwave_values.Configuration_Air_Filter_2_Reminder=0
x_zwave_values.Configuration_Air_Filters=1
x_zwave_values.Configuration_Auto_Changeover=0
x_zwave_values.Configuration_Auto_Differential=0
x_zwave_values.Configuration_Aux_Heat_Cycle_Rate=9
x_zwave_values.Configuration_Aux_Heat_Outdoor_Lockout=0
x_zwave_values.Configuration_Auxiliary_Emergency_Control=0
x_zwave_values.Configuration_Auxiliary_Heat_Droop=0
x_zwave_values.Configuration_Auxiliary_Heat_Type=0
x_zwave_values.Configuration_Balance_Point=0
x_zwave_values.Configuration_Clock_Format=1
x_zwave_values.Configuration_Compressor_Protection=5
x_zwave_values.Configuration_Cool_Stage_1_Cycle_Rate=3
x_zwave_values.Configuration_Cool_Stage_2_Cycle_Rate=3
x_zwave_values.Configuration_Cool_Stages=1
x_zwave_values.Configuration_Daylight_Saving=1
x_zwave_values.Configuration_Dehumidification_Filter_Reminder=0
x_zwave_values.Configuration_Emergency_Heat_Cycle_Rate=9
x_zwave_values.Configuration_Emergency_Heat_Type=0
x_zwave_values.Configuration_Equipment_Type=2
x_zwave_values.Configuration_Fossil_Kit_Control=0
x_zwave_values.Configuration_Heat_Stage_1_Cycle_Rate=3
x_zwave_values.Configuration_Heat_Stage_2_Cycle_Rate=3
x_zwave_values.Configuration_Heat_Stages=1
x_zwave_values.Configuration_High_Cool_Stage_Finish=0
x_zwave_values.Configuration_High_Heat_Stage_Finish=0
x_zwave_values.Configuration_Humidification_Pad_Reminder=0
x_zwave_values.Configuration_Idle_Brightness=0
x_zwave_values.Configuration_Maximum_Heat_Temperature=75
x_zwave_values.Configuration_Minimum_Cool_Temperature=66
x_zwave_values.Configuration_Outdoor_Temperature_Sensor=0
x_zwave_values.Configuration_Reversing_Valve=0
x_zwave_values.Configuration_Schedule_Type=2
x_zwave_values.Configuration_Temperature_Offset=0
x_zwave_values.Configuration_Temperature_Scale=1
x_zwave_values.Configuration_UV_Bulb_1_Reminder=0
x_zwave_values.Configuration_UV_Bulb_2_Reminder=0
x_zwave_values.Configuration_UV_Devices=0
x_zwave_values.Configuration_Up_Stage_Timer_Aux_Heat=0
x_zwave_values.Configuration_Ventilation_Filter_Reminder=0
x_zwave_values.Manufacturer_Specific_manufacturerId=57
x_zwave_values.Manufacturer_Specific_productId=8
x_zwave_values.Manufacturer_Specific_productType=17
x_zwave_values.Multilevel_Sensor_Air_temperature=20.5
x_zwave_values.Multilevel_Sensor_Humidity=40
x_zwave_values.Notification_Power_Management_Mains_status=3
x_zwave_values.Notification_alarmLevel=0
x_zwave_values.Notification_alarmType=0
x_zwave_values.Thermostat_Fan_Mode_mode=1
x_zwave_values.Thermostat_Fan_Mode_off=false
x_zwave_values.Thermostat_Fan_State_state=1
x_zwave_values.Thermostat_Mode_manufacturerData=null
x_zwave_values.Thermostat_Mode_mode=1
x_zwave_values.Thermostat_Operating_State_state=0
x_zwave_values.Thermostat_Setpoint_setpoint_1=20.5
x_zwave_values.Thermostat_Setpoint_setpoint_11=18
x_zwave_values.Thermostat_Setpoint_setpoint_12=26
x_zwave_values.Thermostat_Setpoint_setpoint_2=23.5
x_zwave_values.Version_firmwareVersions=["1.3","1.4"]
x_zwave_values.Version_hardwareVersion=1
x_zwave_values.Version_libraryType=6
x_zwave_values.Version_protocolVersion="4.61"
zwave_device.capabilities=[49,64,66,67,68,69,112,113,114,128,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Thermostat"
zwave_device.impl_sig="23318:1:22315:1"
zwave_device.is_beaming=false
zwave_device.is_listening=true
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.manufacturer_info=[57,17,8]
zwave_device.max_data_rate=null
zwave_device.node_id=16
zwave_device.specific_class="General Thermostat V2"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"1.3"]

Working now. I no longer see binary_sensor.state for the tilt sensor which was erratic at times showing the garage door was open while it was actually closed. I can now use the tilt_sensor.state (primary) = true/false

Thanks again. Much appreciated.

@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.

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 of the tilt sensor in hopes it can help.

Thanks in advance.

Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3

battery_power.level=0.99
battery_power.since=1699401727360
binary_sensor.state=false
tamper.state=true
tilt_sensor.state=null
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":{}}}}}],"manufacturerId":330,"productType":4,"productId":3}
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=99
x_zwave_values.Binary_Sensor_Any=false
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=23
x_zwave_values.Notification_Access_Control_Door_state_simple=23
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="23305:1:22057:1"
zwave_device.is_beaming=false
zwave_device.is_listening=false
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.last_wakeup=1699563172708
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

@togglebits Just want to make sure you did see my response three days ago. The zip file did the trick.