executed:

sudo snap refresh --channel=stable zwave-js-ui

Was on edge previously. Now it is working for me on current beta

having same issue.

Think i solved it.

Replace the mosquitto.conf with the default mosquitto.conf.dpkg-dist and added
"listener 1883" and "allow_anonymous true" again to the conf file.

Now the errors are gone.

Solved it based on checks done via this thread:
https://www.domoticz.com/forum/viewtopic.php?t=39565

yes. And i have access to this gui.

Note: i am on stable release. Was on beta but then zwave was no longer working. Quickly reverted to stable.
In parallel now getting the zwave-js-ui and mqtt working....

Keep getting errors in Domoticz on MQTT.

2023-08-14 22:44:20.567 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:45:03.751 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:45:33.827 ...

Found it under swithes/utility. Seems to work.

it is working again. Repeated some snap related commands. But not sure it is stable.

What i noticed is that i cannot find the replace device button.

Tried the docker method yesterday but did not get far with that.

Managed to get things started up using ZWave-JS-UI.

Had access to my pi-ip:8091.

Managed to give all (seem identical id's) a name in the interface.

Did a reboot a now this access via port 8091 is no longer working.

followed the method by Andrehj
https://www.domoticz.com/forum/viewtopic.php?p ...

having same errors sporadically. Edited the generic_device.lua as advised. Will follow the thread.

Quite quick solution:
https://api.honeywell.com/oauth2/authorize?response_type=code&client_id=[[YOURAPIKEY]]&redirect_uri=none
will give you a new Code.

Due to this changing response code the latest curl command needs to be adapted and rerun with this new code.

The base64 code you generated before ...

After some issues updating to newer (beta) release the Honeywell API interface has stopped (again).

Is there an easy way to get this working again without eg doing the whole definition of user/secret/64code bla bla again.

Why does it stop actually assume all keys at a point in time are valid and ...

Any way to restore previous zwave config. Only domoticz.db restore from the backups isn't the full scope.