ZWaveJSUI : Websocket integration instead of mqtt discovery

[barry44]

Hello

I'm using zwavejsui since a few months, and it works great
I just post for a case in zwavejsui with a device that don't work as expected https://github.com/zwave-js/zwave-js-ui ... 1926986563

In the end of the case, they tell that the mqtt discovery is not the good way to work, and even open a case in openhab to have websocket intergration
https://github.com/openhab/openhab-core/issues/4080

Here is Z-Wave JS official integration #16374

Is it possible to add this websocket discovery in domoticz ? Is it possible to take this enhancement ?

Thank you

[waltervl]

The advantage of MQTT Auto Discovery is that multiple projects use the same protocol. So Domoticz developers only have to program one protocol and all supporting platforms like Zwave-JS-UI, Zigbee2MQTT, ESPHome, ecowitt2mqtt, EsPurna, IOTLink, MiFlora MQTT Daemon, OpenMQTTGateway, Teleinfo MQTT, Wyzesense2MQTT, Arduino HAMqttDevice, EMS-bus-Gateway etc can be used in Domoticz.

Writing a specific Websocket integration for ZwaveJSUI would mean a lot of work that cannot be reused for other projects.

[gizmocuz]

Did you follow this guide?:

https://www.domoticz.com/wiki/MQTT_AD_Report_Problems

[akamming]

hmmm... it is a bit worrying that in that thread the ZWAVEJSUI developer yesterday mentioned he is going to drop MQTT AD support in the future...

i did a lot of work migrating to ZWAVE JS with MQTT AD. hope i don't have to remigrate to another solution

[barry44]

The advantage of MQTT Auto Discovery is that multiple projects use the same protocol. So Domoticz developers only have to program one protocol and all supporting platforms like Zwave-JS-UI, Zigbee2MQTT, ESPHome, ecowitt2mqtt, EsPurna, IOTLink, MiFlora MQTT Daemon, OpenMQTTGateway, Teleinfo MQTT, Wyzesense2MQTT, Arduino HAMqttDevice, EMS-bus-Gateway etc can be used in Domoticz.

Writing a specific Websocket integration for ZwaveJSUI would mean a lot of work that cannot be reused for other projects.

Indeed, I agree, but I just forward the message. ZWaveJSUi main developper explained that he wanted to stop MQTT Discovery.

Did you follow this guide?:

https://www.domoticz.com/wiki/MQTT_AD_Report_Problems

Yes, I follow the guide. By following the guide, I've seen that the discovery values send by zwavejsui for command topic were wrong. I open a ZWaveJSUI bug report. It was due to a change in a recent ZWaveJSUI version. They have just reverted it in today. It's now OK.

But in the bug report, ZWaveJSUI guys explained me that MQTT discovery will be (or is already) deprecated. So I relay the message

hmmm... it is a bit worrying that in that thread the ZWAVEJSUI developer yesterday mentioned he is going to drop MQTT AD support in the future...

i did a lot of work migrating to ZWAVE JS with MQTT AD. hope i don't have to remigrate to another solution

Same as you. I hope too

[gizmocuz]

This was mentioned already quite some time ago, but it's still here (luckily!)
But since you are using docker compose with zwavejs-ui, you can checkout a specific version of it.
Even make a backup.
Remember the development of OpenZWave had been stopped years ago but is still working.

[akamming]

Because i was a bit worried i send a message to the zwave-js-ui developer stating i am happy with mqtt support and hope he will continue to support for a long time.

Reaction was:

anyway yeah no worries about MQTT AD, I know many are using it I just want to ensure users have the best experience using ZwaveJS

So he recommends ha systems like domoticz to migrate to websocket API, cause apparently better experience. But doesn't seem like support will be dropped soon...

BTW: I am wondering what that better experience is: moving to ZWAVE JS UI with MQTT AD was quite a hassle, but my ZWAVE network became much more stable and responsive. So this already works much better than openzwave