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

[gaetanb76]

Yesterday afternoon I wanted to stop the mini PC running Gladys so I could plug it into another outlet.

I stopped the containers one by one.

I stopped Gladys.

I shut down the mini PC with the command shutdown -h now.

[pierre-gilles]

Hi @gaetanb76,

First, you’re making extra work for yourself by stopping the containers one by one, it’s overkill

If you want to move your mini-PC, the simplest thing is to just press the mini-PC’s « power » button, wait for it to be off, then unplug it:

When you press the « power » button, here’s what happens:

1. You press the button
2. The OS triggers a clean shutdown (systemd)
3. systemd:
   • stops services in order
   • stops the Docker service
4. Docker
   • sends a SIGTERM to each container
   • waits for the grace timeout (default 10 seconds)
   • sends a SIGKILL only if the container doesn’t respond
5. The system powers off

So all your containers are therefore fully stopped cleanly.

Now, about your problem: when you started zwave-js-ui, did you start the container with a « restart=always » property?

Is your MQTT broker also set to « restart=always »?

Do you have any errors in the Gladys logs?

[gaetanb76]

Yes,

I kept thinking it was a Raspberry Pi, like the one I had before, what a dummy

Indeed, a simple press of the button does the trick, thanks @pierre-gilles

@pierre-gilles

Now, for your problem, when you launched zwave-js-ui, did you start the container with a « restart=always » property?

I didn’t start zwave-js-ui, it launches at Gladys startup

@pierre-gilles

Is your MQTT broker also set to « restart=always »?

Same for it.

Today there was a power outage that lasted 8 hours and Z-Wave is working normally.

I’ll investigate

[pierre-gilles]

Ok, if you ever have logs to share when Gladys restarts, that will give us some information