Notice to Docker + ARM Users (RPi 3/4/5 and others)

[toggledbits]

Looks like this is the result of a change introduced in ZWaveJS version 12.12.0 (see change #6958 linked there).

Let's see if we can deal with this the easy way first. I've updated the device definition data. You can download it (ZIP archive zwavejs_data.zip) from the Reactor download server and put the ZIP archive into your config directory (do not unzip it); restart Reactor. Let's see if that brings tilt_sensor back.

[Snowman]

@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

[Snowman]

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

Have you opened and closed the door since updating? Because it's a notification sensor, Reactor won't have the right values until it gets notifications from the device.

[Snowman]

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]

The Z-Wave JS UI doesn't show notifications here, only states. All of those are states. Notifications are class number 113.

At this point, I'll need to see logs for what happens when you open and close this thing. Here's what you need to do:

1. In your ZWaveJSController config in reactor.yaml, add the following line:

        config:  # don't add this line, included for indenting reference only
          monitor_nodes: [24]  # add this line
   

2. Restart Reactor.

3. Open and close the door two or three times.

4. Remove or comment out the line you added in step 1 and restart Reactor again.

5. Post the logs/zwavejs_24_monitor.json file to the URL I am going to DM to you in chat.

[Snowman]

@toggledbits I now have the requested log file.

[toggledbits]

OK. Pull the zwavejs_data.zip update file from the server and put it into your config directory. The stop Reactor (not restart), clear out storage/entities/zwavejs, and start Reactor again.

[Snowman]

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

Perfect. Thanks for sending the log. Don't forget to remove or comment out the monitor_nodes line if you haven't already... it will consume disk space to exhaustion if you don't disable it.

Edit: the issue, by the way, was the new device data had handling dependent on which version of Z-Wave JS was running, because the device is reported differently on earlier versions (as you pointed out earlier), but the test in the new data file was broken. Easy fix.