Z-wave device stopped updating, now won't discover

For devices supporting the Auto Discovery feature. Like ZWaveJS2MQTT, Zigbee2MQTT.

Moderator: leecollings

Post Reply
jefft
Posts: 75
Joined: Monday 23 January 2017 23:30
Target OS: Linux
Domoticz version: 2023.1
Location: UK
Contact:

Z-wave device stopped updating, now won't discover

Post by jefft »

Strange things happening... I noticed that one of my z-wave sensors, a Fibaro universal binary, hadn't updated any values in domoticz for 2 days. I forced a refresh in the zwavejs console, restarted the system, still nothing.

Deleted the domoticz devices for that node completely and forced rediscovery; only some of the node's devices have been discovered. Whatever I do, I can't seem to get the important ones - the sensors - to show up.

The domoticz log shows that it received the auto-discovery messages for the relevant devices:

Code: Select all

2022-07-17 10:46:46.186  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_scene_state_sceneid (unique_id: zwavejs2mqtt_0xc7625338_9-43-0-sceneId)
2022-07-17 10:46:46.288  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_scene_state_dimmingduration (unique_id: zwavejs2mqtt_0xc7625338_9-43-0-dimmingDuration)
2022-07-17 10:46:46.389  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_any_1 (unique_id: zwavejs2mqtt_0xc7625338_9-48-1-Any)
2022-07-17 10:46:46.490  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_any_2 (unique_id: zwavejs2mqtt_0xc7625338_9-48-2-Any)
2022-07-17 10:46:46.592  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_temperature_air_3 (unique_id: zwavejs2mqtt_0xc7625338_9-49-3-Air_temperature)
2022-07-17 10:46:46.693  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_gas_carbon_dioxide_3 (unique_id: zwavejs2mqtt_0xc7625338_9-49-3-Carbon_dioxide_CO_level)
2022-07-17 10:46:46.794  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_humidity_air_3 (unique_id: zwavejs2mqtt_0xc7625338_9-49-3-Humidity)
2022-07-17 10:46:46.895  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_temperature_air_4 (unique_id: zwavejs2mqtt_0xc7625338_9-49-4-Air_temperature)
2022-07-17 10:46:46.996  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_temperature_air_5 (unique_id: zwavejs2mqtt_0xc7625338_9-49-5-Air_temperature)
2022-07-17 10:46:47.097  Status: MQTT - zwavejs2mqtt: discovered: Vent sensor/Vent sensor_temperature_air_6 (unique_id: zwavejs2mqtt_0xc7625338_9-49-6-Air_temperature)
... yet only the root device and -1, -2 have entries in the domoticz devices list.

There are no records in the DeviceStatus table with those -3, -4, -5, -6 IDs, only the root and -1, -2.

Does anyone have an idea what I need to do to fix this? What could make domoticz report that it has discovered the device, but not create a device record for it; is there another list of discovered devices where there might be a stale record, perhaps?

These things are the temperature sensors on my ventilation system, so I'd very much like them working before it hits 40C tomorrow ;-)

Thanks!
Domoticz, Z-Stick Gen.5, zzh Zigbee, rxftrx433XL on Ubuntu 22.04, HP 290 G1.
Node Red, MQTT, 80+ Z-wave, ESP8266 & Shelly, handful of Zigbee bulbs. EMS-ESP gateway for Bosch boiler. Controlicz, until it dies :-(
User avatar
gizmocuz
Posts: 2350
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Top of the world
Contact:

Re: Z-wave device stopped updating, now won't discover

Post by gizmocuz »

Is it showing (and updating) correctly in the zwavejs2mqtt web interface ? Maybe you have to check the node groups ?
Quality outlives Quantity!
jefft
Posts: 75
Joined: Monday 23 January 2017 23:30
Target OS: Linux
Domoticz version: 2023.1
Location: UK
Contact:

Re: Z-wave device stopped updating, now won't discover

Post by jefft »

Yes, zwavejs console is fine. The node has the controller in both lifeline and another group.
What's odd, is that domoticz reports discovering the z-wave child devices but does not create domoticz devices to match. Feels like an issue between discovery and creation within domoticz. What happens between those two steps that could cause the devices not to be created?
Domoticz, Z-Stick Gen.5, zzh Zigbee, rxftrx433XL on Ubuntu 22.04, HP 290 G1.
Node Red, MQTT, 80+ Z-wave, ESP8266 & Shelly, handful of Zigbee bulbs. EMS-ESP gateway for Bosch boiler. Controlicz, until it dies :-(
jefft
Posts: 75
Joined: Monday 23 January 2017 23:30
Target OS: Linux
Domoticz version: 2023.1
Location: UK
Contact:

Re: Z-wave device stopped updating, now won't discover

Post by jefft »

@gizmocuz, it looks like this might be an issue with the MQTT topics.

zwjs2mqtt is publishing this device as 'zwave/9/49/4/Air_temperature', but I see messages for some devices as 'zwave/nodeID_101/...' and also the name, 'zwave/Node_name/...'.

I spotted that 'use node name' was set on in the zwjs console, so I tried switching that off. It didn't cause domoticz to create the devices, but it did stop most of my switches and plugs working!

Which MQTT topic format does domoticz want, and do you know how I can get zwjs2mqtt to send every node in the same format?

I'm puzzled; given the different topics that the messages can come in with, how does domoticz map them onto its devices? For example, one of my plugs has the ID 'zwavejs2mqtt_0xc7625338_111-37-0-currentValue' in domoticz, but the message sent to switch it on/off has the topic 'zwave/Kitchen_water_heater/111/37/0/targetValue' and its actual node name in the zwjs console is 'TKB Plug X'... how is the mapping between those IDs and names done?

Thanks!
Domoticz, Z-Stick Gen.5, zzh Zigbee, rxftrx433XL on Ubuntu 22.04, HP 290 G1.
Node Red, MQTT, 80+ Z-wave, ESP8266 & Shelly, handful of Zigbee bulbs. EMS-ESP gateway for Bosch boiler. Controlicz, until it dies :-(
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest