ZWaveJSUI MQTT broker disconnected

[gaetanb76]

Hello,
the day before yesterday I tried to set my heating to Eco with the remote control but it didn’t work.
I went into the configuration interface and everything was OK.
I clicked on Save configuration
Everything started working again.

I was too lazy to post another message here because I had already had the problem, which had been resolved.

This morning, 17°C on the ground floor…
Same, I clicked on Save configuration and it works again.

Here’s what I have:

In the logs, I can’t go back far enough to reach the container creation.

I stopped the zwave-js-ui container and restarted it, but it was still not working.
I stopped the gladys container and restarted it, but it was still not working.
I rebooted the mini PC, it’s down; by clicking on Save configuration it works again
The ZWaveJSUI logs after restart (filtered with zwave):

Link to the full log file

[pierre-gilles]

Hi @gaetanb76

This is not an MQTT disconnection issue; the problem is that Z-WaveJS UI responded to the device discovery with an object that does not match what Gladys expects.

The affected code is:

Apparently the « data » does not contain a result.

From what I can see, there was a major update of Z-WaveJS UI two weeks ago:

(Releases · zwave-js/zwave-js-ui · GitHub)

By any chance, has your Z-WaveJS UI instance not been automatically updated to this version?

I can’t access the ZWaveJS UI site which is down right now, so I can’t see what API changes are in this new version; I’ll try again later.

@Sescandell Did you notice the same thing on your side?

[Sescandell]

Hello,

This seems to continue to work for me despite an update to version 10:

.

I could take a look at the logs above this week

[gaetanb76]

Hi to you two,
Here’s the version I have:
zwave-js-ui: 10.1.3.bcd59a0
zwave-js: 15.0.3