Page 1 of 1
zwavejsui -> Domoticz issue
Posted: Monday 16 January 2023 16:15
by mancide
Hi,
Since saterday 14/01/2023 15:50, I have an issue with a Fibaro universal binary sensor.
The Fibaro universal binary sensor has 3 DS18B20 temp probes connected.
Normal path:
DS18B20 > fibaro universal binary sensor > Aeotec zwave stick > zwavejsui > mosquitto > Domoticz.
However, I no longer see temperature updates in Domoticz.
using MQTT Explorer I see updates from all 3 temp probes.
It seems like Domoticz is refusing all updates for my device with ID==25.
I deleted the device for 1 of the 3 temp probes hoping it would be rediscovered but this is not happening.
Can somebody help out here?
PS: Temperatures for another Fibaro uninversal binary sensor are still being displayed...
Re: zwavejsui -> Domoticz issue
Posted: Monday 16 January 2023 19:15
by ksacca
Hi,
Not sure how this could happen for only one device, but you never know.
If domoticz didn't load the configuration message for autodiscovery, it will not update the device when a state update is received.
To force zwavejsui to resend the configuration messages, I believe it's sufficient to just go the settings in zwavejsui and click the save button.
If this works, you should also enable "retained discovery" under the home assistant menu. When you restart domoticz or the mqtt hardware in domoticz, the autodiscovery messages will immediately be loaded as they are stored on your broker and sent when you connect.
Otherwise, after a restart of domoticz, you have to resend the configuration manually as explained above.
When you enable this option, the downside is that when you delete a device from zwavejsui, it might still be discovered in domoticz.
If that's the case, you can delete the message using MQTT Explorer (see
https://www.domoticz.com/wiki/Zwave-JS-UI).
Re: zwavejsui -> Domoticz issue
Posted: Tuesday 17 January 2023 9:52
by mancide
Hi,
I tried the save. I see the Fibaro universal binary sensor being discovered.
Code: Select all
2023-01-17 09:18:50.237 Status: MQTT auto discovery: discovered: vijver temp box/vijver temp box_any_1 (unique_id: zwave-js-ui_0xf46f2a31_25-48-1-Any)
2023-01-17 09:18:50.340 Status: MQTT auto discovery: discovered: vijver temp box/vijver temp box_any_2 (unique_id: zwave-js-ui_0xf46f2a31_25-48-2-Any)
2023-01-17 09:18:50.443 Status: MQTT auto discovery: discovered: vijver temp box/vijver temp box_temperature_air_3 (unique_id: zwave-js-ui_0xf46f2a31_25-49-3-Air_temperature)
2023-01-17 09:18:50.544 Status: MQTT auto discovery: discovered: vijver temp box/vijver temp box_temperature_air_4 (unique_id: zwave-js-ui_0xf46f2a31_25-49-4-Air_temperature)
2023-01-17 09:18:50.646 Status: MQTT auto discovery: discovered: vijver temp box/vijver temp box_temperature_air_5 (unique_id: zwave-js-ui_0xf46f2a31_25-49-5-Air_temperature)
but I still don't get to see any temperature value updates...
I do see them in MQTT explorer:
{
"time": 1673945225977,
"time": 1673945435983,
"value": 1.93,
"nodeName": "vijver temp box",
"nodeLocation": "vijver"
}
Re: zwavejsui -> Domoticz issue
Posted: Tuesday 17 January 2023 10:59
by mancide
I removed the comments on 1 print() line in 1 of my events scripts and it started working again
very, very strange...
It's like my event script was eating all device updates before domoticz could do anything with it...