ZWave JS UI integration down

Hello,

I use Z-Wave for my heating.

Last week there was a power outage and I no longer had access to the heating controls via my Octan Remote or via the interface.
By going to Configuration \u003e Save configuration, it started working again

This morning, Gladys was updated. A Telegram message told me about the new version v4.63.1 at 11:05.
No action possible on the heating this morning.
I retried the procedure, but it didn’t succeed.

I go to the Z-Wave JS UI interface but it’s not accessible: The connection failed.
I connect to the machine that runs Gladys with WinSCP.
I go to the Z-WAVE logs (/var/lib/gladysassistant/zwave/zwave-js-ui/store/logs)
and I open the file zwavejs_2025-10-07.log

Everything seems OK, until 11:04.

2025-10-07 11:04:35.612 SERIAL « 0x01090004000b03250300dc                                            (11 bytes)
2025-10-07 11:04:35.613 SERIAL » [ACK]                                                                   (0x06)
2025-10-07 11:04:35.613 CNTRLR   [Node 011] [~] [Binary Switch] currentValue: false =\u003e false       [Endpoint 0]
2025-10-07 11:04:35.615 DRIVER « [Node 011] [REQ] [ApplicationCommand]
                                 └─[BinarySwitchCCReport]
                                     current value: false
2025-10-07 11:04:35.665 SERIAL « 0x01090004000b03250300dc                                            (11 bytes)
2025-10-07 11:04:35.665 SERIAL » [ACK]                                                                   (0x06)
2025-10-07 11:04:35.666 CNTRLR   [Node 011] [~] [Binary Switch] currentValue: false =\u003e false       [Endpoint 0]
2025-10-07 11:04:35.668 DRIVER « [Node 011] [REQ] [ApplicationCommand]
                                 └─[BinarySwitchCCReport]
                                     current value: false
2025-10-07 11:04:35.763 SERIAL « 0x01090004000b03200100db                                            (11 bytes)
2025-10-07 11:04:35.764 SERIAL » [ACK]                                                                   (0x06)
2025-10-07 11:04:35.764 DRIVER « [Node 011] [REQ] [ApplicationCommand]
                                 └─[BasicCCSet]
                                     target value: 0
2025-10-07 11:04:35.765 CNTRLR   [Node 011] treating BasicCC::Set as a report
2025-10-07 11:04:35.765 CNTRLR   [Node 011] [~] [Basic] currentValue: 0 =\u003e 0                       [Endpoint 0]
2025-10-07 11:04:35.818 SERIAL « 0x01090004000b03200100db                                            (11 bytes)
2025-10-07 11:04:35.819 SERIAL » [ACK]                                                                   (0x06)
2025-10-07 11:04:35.820 DRIVER « [Node 011] [REQ] [ApplicationCommand]
                                 └─[BasicCCSet]
                                     target value: 0
2025-10-07 11:04:35.820 CNTRLR   [Node 011] treating BasicCC::Set as a report
2025-10-07 11:04:35.821 CNTRLR   [Node 011] [~] [Basic] currentValue: 0 =\u003e 0                       [Endpoint 0]
2025-10-07 11:04:37.348 DRIVER   destroying driver instance...
2025-10-07 11:04:37.363 DRIVER   driver instance destroyed

docker ps returns

4a82e1ccb2c9   zwavejs/zwave-js-ui:latest     \"node server/bin/www\"    4 hours ago     Restarting (1) 44 seconds ago                                                 zwave-js-ui

This is what Dozzle shows me :

Hi @gaetanb76,

Looking at the Z-WaveJS UI repo, you can see there was an issue with their latest update:

But apparently the issue has been fixed since, so if you update Z-WaveJS UI it will be resolved :slight_smile:

You can use Watchtower to update the container:

docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock \
    containrrr/watchtower \
    --run-once --include-restarting
2 Likes

Thanks @pierre-gilles,

It’s working perfectly!
Script launched
A backup of the configuration in the Z-Wave JS UI integration
And everything’s running smoothly.

Great!

1 Like