Ok thanks, I’ll post the items this evening.
1 Like
You might be using Firefox; if so, try doing the operation in Chrome or Opera (there is a recurring problem with on-the-fly autocomplete of fields in Firefox)
1 Like
@cce66, thank you very much, it worked immediately in Chromium!
1 Like
I’m taking advantage of @Prof_Techno’s message to also raise the issue… I was supposed to deal with it a while ago, but I kept forgetting every time.
For info @pierre-gilles, the MQTT service not reconnecting problem has been happening at my place since… forever ^^ and has never stopped!
To recontextualize, I have 2 installations at home (well actually 3 ^^ but one doesn’t update automatically ^^):
-
Gladys light is installed on a Pi 4 (Raspberry Pi 4) in the living room, it has the same devices and features as the primary Gladys but doesn’t store any history and doesn’t trigger scenes.
It just manages zigbee2mqtt in the house.
Its IP is ‹ xx.5.xx.51 ›.
During Gladys updates it reconnects without issues to the MQTT broker which is on another Pi 4 (Raspberry Pi 4) at address ‹ xx.5.xx.51 ›.
It used to be my primary Gladys and couldn’t reconnect to MQTT until I removed its scenes and value histories. -
The primary Gladys located in the IT office is installed on a Beelink mini PC (the cream of the crop ^^) and manages value histories and scenes.
It is connected to Gladys light to retrieve zigbee2mqtt info (and is awaiting a second service to manage the building’s Zigbee ^^)
Its IP is ‹ xx.5.xx.227 ›.
During Gladys updates it never reconnects to the MQTT broker which is on another Pi 4 (Raspberry Pi 4) at address ‹ xx.5.xx.51 ›. I have to reconnect it manually.
This point is very important to me because at 5:30 AM Gladys is supposed to start the hay purifier for the horses. And inevitably with every update that happens during the night the command is never sent and I get… you know what ^^
I was planning to take the time to look into it because I think it’s a reconnection timeout issue… simply clicking on the connection the next morning reconnects without issue so …
@Terdious Which version of the MQTT broker are you using?
Could it be that, by any chance, the updates of Gladys and mosquitto occur at the same time, which would cause Gladys to never manage to connect to Mosquitto on first startup, and thus never reconnect to it (because it was never connected)? I confirm that reconnection works very well, but what if the initial connection isn’t possible?
Keep us posted on your investigations! I can help if needed, provided I have enough data. For now, it seems I’ve never been able to reproduce these bugs, unfortunately
Mon serveur mosquitto n’est surtout pas en mise à jour automatique. Voici sa version au cas où :
Mais comme je le disais, aucun souci avec mon autre Gladys.
Information supplémentaire :
Si je suis en dev et que je prend ma base prod en base dev, j’ai exactement le même souci … ^^
Exemple :
Logs :
2024-11-05T14:49:31+0100 <info> index.js:45 (shutdown) SIGTERM received.
2024-11-05T14:49:31+0100 <info> index.js:51 (shutdown) Closing database connections.
2024-11-05T14:49:31+0100 <info> index.js:37 (closeDuckDB) DuckDB closed.
2024-11-05T14:49:31+0100 <info> index.js:27 (closeSQLite) SQLite closed.
2024-11-05T14:49:38+0100 <info> index.js:96 (Object.duckDbCreateTableIfNotExist) DuckDB - Creating database table if not exist
2024-11-05T14:49:38+0100 <info> job.purge.js:17 (Job.purge) Deleting all background jobs created before = Tue Oct 29 2024 14:49:38 GMT+0100 (Central European Standard Time)
2024-11-05T14:49:40+0100 <info> service.startAll.js:30 () Service xiaomi was manually stopped, so it is ignored at startup
2024-11-05T14:49:40+0100 <info> service.startAll.js:30 () Service ewelink was manually stopped, so it is ignored at startup
2024-11-05T14:49:40+0100 <info> service.startAll.js:30 () Service tp-link was manually stopped, so it is ignored at startup
2024-11-05T14:49:40+0100 <info> service.startAll.js:30 () Service example was manually stopped, so it is ignored at startup
2024-11-05T14:49:40+0100 <info> index.js:14 (Object.start) starting Alexa service
2024-11-05T14:49:40+0100 <info> index.js:20 (Object.start) Starting Open Weather service
2024-11-05T14:49:40+0100 <info> index.js:25 (Object.start) Starting EDF Tempo service
2024-11-05T14:49:40+0100 <info> index.js:18 (Object.start) Starting GoogleCast service
2024-11-05T14:49:40+0100 <info> index.js:16 (Object.start) Starting Z-Wave JS UI service
2024-11-05T14:49:40+0100 <info> service.start.js:40 (Service.start) Service zwavejs-ui is not configured, so it was not started.
2024-11-05T14:49:40+0100 <info> index.js:17 (Object.start) Starting Sonos service
2024-11-05T14:49:40+0100 <info> index.js:17 (Object.start) Starting Netatmo service 2f061381-b138-428a-abfb-dfb1af216ec2
2024-11-05T14:49:40+0100 <info> service.start.js:40 (Service.start) Service netatmo is not configured, so it was not started.
2024-11-05T14:49:40+0100 <info> checkForContainerUpdates.js:13 (NodeRedManager.checkForContainerUpdates) Node-RED: Checking for current installed versions and required updates...
2024-11-05T14:49:40+0100 <info> checkForContainerUpdates.js:17 (NodeRedManager.checkForContainerUpdates) Node-RED: update #2 of the container required...
2024-11-05T14:49:40+0100 <info> checkForContainerUpdates.js:34 (NodeRedManager.checkForContainerUpdates) Node-RED: update #2 of the container done
2024-11-05T14:49:40+0100 <info> installContainer.js:48 (NodeRedManager.installContainer) Nodered: is being installed as Docker container...
2024-11-05T14:49:40+0100 <info> installContainer.js:49 (NodeRedManager.installContainer) Pulling nodered/node-red:3.1 image...
2024-11-05T14:49:41+0100 <info> installContainer.js:53 (NodeRedManager.installContainer) Nodered: Preparing environment...
2024-11-05T14:49:41+0100 <info> configureContainer.js:16 (NodeRedManager.configureContainer) Node-RED: Docker container is being configured...
2024-11-05T14:49:41+0100 <info> configureContainer.js:34 (NodeRedManager.configureContainer) Node-RED: configuration file already exists.
2024-11-05T14:49:41+0100 <info> installContainer.js:56 (NodeRedManager.installContainer) Creation of container...
2024-11-05T14:49:41+0100 <info> installContainer.js:66 (NodeRedManager.installContainer) Node-RED: successfully installed and configured as Docker container
2024-11-05T14:49:41+0100 <info> configureContainer.js:16 (NodeRedManager.configureContainer) Node-RED: Docker container is being configured...
2024-11-05T14:49:41+0100 <info> configureContainer.js:34 (NodeRedManager.configureContainer) Node-RED: configuration file already exists.
2024-11-05T14:49:41+0100 <info> installContainer.js:89 (NodeRedManager.installContainer) Node-RED: container is (re)starting...
2024-11-05T14:49:46+0100 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
[...]
2024-11-05T14:49:47+0100 <info> installContainer.js:95 (NodeRedManager.installContainer) Node-RED: container successfully started
2024-11-05T14:49:47+0100 <info> index.js:27 (Object.start) Starting MELCloud service bca6a945-1d67-494a-9abc-eef17f023afa
2024-11-05T14:49:47+0100 <info> service.start.js:40 (Service.start) Service melcloud is not configured, so it was not started.
2024-11-05T14:49:47+0100 <info> index.js:17 (Object.start) Starting Tuya service 2ae251ee-8619-4310-9c71-f0542d7a99b7
2024-11-05T14:49:47+0100 <info> service.start.js:40 (Service.start) Service tuya is not configured, so it was not started.
2024-11-05T14:49:47+0100 <info> index.js:16 (Object.start) Starting Nextcloud Talk service
2024-11-05T14:49:47+0100 <info> service.start.js:40 (Service.start) Service nextcloud-talk is not configured, so it was not started.
2024-11-05T14:49:47+0100 <info> index.js:17 (Object.start) Starting LAN Manager service
2024-11-05T14:49:47+0100 <info> lan-manager.initPresenceScanner.js:18 (LANManager.initPresenceScanner) LANManager configuration: starting presence scanner
2024-11-05T14:49:47+0100 <info> index.js:16 (Object.start) starting Broadlink service
2024-11-05T14:49:47+0100 <info> index.js:18 (Object.start) Starting HomeKit service
2024-11-05T14:49:48+0100 <info> index.js:14 (Object.start) starting GoogleActions service
2024-11-05T14:49:48+0100 <info> init.js:56 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle not attached
2024-11-05T14:49:48+0100 <info> connect.js:25 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://10.5.0.51:1884 MQTT broker...
2024-11-05T14:49:48+0100 <info> connect.js:35 (MqttClient.<anonymous>) Connected to MQTT container mqtt://10.5.0.51:1884
2024-11-05T14:49:48+0100 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2024-11-05T14:49:48+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
2024-11-05T14:49:48+0100 <info> index.js:15 (Object.start) Starting Tasmota service
2024-11-05T14:49:48+0100 <info> index.js:13 (Object.start) Starting usb service
2024-11-05T14:49:48+0100 <info> index.js:19 (Object.start) Starting Telegram service
2024-11-05T14:49:48+0100 <info> index.js:17 (Object.start) Starting RTSP service
2024-11-05T14:49:48+0100 <info> index.js:18 (Object.start) Starting Philips Hue service
Connexion au service
2024-11-05T14:49:48+0100 <info> index.js:16 (Object.start) Starting MQTT service
2024-11-05T14:49:48+0100 <info> updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes...
2024-11-05T14:49:48+0100 <info> updateContainer.js:41 (MqttHandler.updateContainer) MQTT: no container update required
2024-11-05T14:49:48+0100 <info> connect.js:38 (MqttClient.<anonymous>) Connected to MQTT server mqtt://10.5.0.50:1883
2024-11-05T14:49:48+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic stat/+/+
2024-11-05T14:49:48+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic tele/+/+
2024-11-05T14:49:48+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic gladys/master/#
2024-11-05T14:49:48+0100 <info> index.js:15 (Object.start) Starting enedis service
2024-11-05T14:49:49+0100 <info> index.js:88 (Object.start) Starting CalDAV service
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:58 () Sunrise today is at 7:55 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:59 () Sunset today is at 17:31 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 3 hours.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:58 () Sunrise today is at 7:55 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:59 () Sunset today is at 17:31 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 3 hours.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:58 () Sunrise today is at 7:55 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:59 () Sunset today is at 17:31 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 3 hours.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:58 () Sunrise today is at 7:55 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:59 () Sunset today is at 17:31 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 3 hours.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:58 () Sunrise today is at 7:55 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:59 () Sunset today is at 17:31 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 3 hours.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:58 () Sunrise today is at 7:30 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:59 () Sunset today is at 17:38 today, in your timezone = Europe/Paris
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2024-11-05T14:49:49+0100 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 3 hours.
Souscription aux topics MQTT au lancement + messages Tasmota
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic gladys/master/device/mqtt:light-ambiance-piscine/feature/mqtt:light-ambiance-piscine
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic gladys/master/device/mqtt:light-ambiance-piscine/feature/mqtt:light-ambiance-piscine
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic tarifs-total-energie
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic tarifs-total-energie
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic consos-vince
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic consos-vince
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic consos-vince
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic consos-vince
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic consos-vince
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic consos-vince
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic consos-vince
2024-11-05T14:49:49+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic consos-vince
2024-11-05T14:49:49+0100 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic stat/tasmota_C4BA91/STATUS11
2024-11-05T14:49:49+0100 <warn> handleNewMessage.js:54 (MqttHandler.handleNewMessage) TypeError: Cannot read properties of null (reading 'external_id')
at MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:32:101)
at /src/server/services/mqtt/lib/handleNewMessage.js:41:12
at Array.forEach (<anonymous>)
at MqttHandler.handleNewMessage (/src/server/services/mqtt/lib/handleNewMessage.js:39:26)
at MqttClient.<anonymous> (/src/server/services/mqtt/lib/connect.js:68:10)
at MqttClient.emit (node:events:517:28)
at MqttClient._handlePublish (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:1257:12)
at MqttClient._handlePacket (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:401:12)
at work (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:312:12)
at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:325:5)
at doWrite (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:417:5)
at Writable.write (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:334:11)
at Socket.ondata (node:internal/streams/readable:809:22)
at Socket.emit (node:events:517:28)
at addChunk (node:internal/streams/readable:368:12)
at readableAddChunk (node:internal/streams/readable:341:9)
at Socket.Readable.push (node:internal/streams/readable:278:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
2024-11-05T14:49:49+0100 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic stat/Tasmota_POWR2-1/STATUS11
2024-11-05T14:49:49+0100 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic stat/tasmota_C4E883/STATUS11
2024-11-05T14:49:49+0100 <warn> handleNewMessage.js:54 (MqttHandler.handleNewMessage) TypeError: Cannot read properties of null (reading 'external_id')
at MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:32:101)
at /src/server/services/mqtt/lib/handleNewMessage.js:41:12
at Array.forEach (<anonymous>)
at MqttHandler.handleNewMessage (/src/server/services/mqtt/lib/handleNewMessage.js:39:26)
at MqttClient.<anonymous> (/src/server/services/mqtt/lib/connect.js:68:10)
at MqttClient.emit (node:events:517:28)
at MqttClient._handlePublish (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:1257:12)
at MqttClient._handlePacket (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:401:12)
at work (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:312:12)
at processTicksAndRejections (node:internal/process/task_queues:77:11)
2024-11-05T14:49:49+0100 <warn> connect.js:50 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: write ECONNRESET
2024-11-05T14:49:49+0100 <info> device.migrateFromSQLiteToDuckDb.js:36 (DeviceManager.migrateFromSQLiteToDuckDb) DuckDB : Already migrated from SQLite. Not migrating.
2024-11-05T14:49:49+0100 <info> index.js:64 (Server.<anonymous>) Server listening on port 82
2024-11-05T14:49:50+0100 <info> index.js:917 (Socket.<anonymous>) Gladys Gateway: connected in websockets
2024-11-05T14:50:04+0100 <info> enedis.sync.js:23 (recursiveBatchCall) Enedis: Syncing 02351085339470 after 1841-09-18
Comme tu le vois dans la 2ème et dans la 4ème partie, la connexion se fait bien au redémarrage mais je n’ai même pas le temps de la voir. Je reçois quelques messages puis je me retrouve déconnecté. Pas de message complémentaire côté Gladys, par contre côté broker mosquitto :
2024-11-05 16:06:17.%f: New client connected from xx.5.xx.227:56192 as gladys-main-instance-471473 (p2, c1, k60, u'mqtt').
2024-11-05 16:06:18.%f: Client gladys-main-instance-471473 disconnected due to malformed packet.
Mais si je me reconnecte via Gladys, aucun soucis …
PS : Oh et dans le doute j’ai mis à jour mosquitto pour être sûr :
Ok, super interesting investigation, @Terdious
The most interesting message is here:
disconnected due to malformed packet.
Two possibilities:
- A mosquitto bug
- A bug in the JavaScript package « mqtt » that we use in Gladys
First, you updated to 2.0.11, whereas in Gladys we normally use 2.0.15 (Code: Gladys/server/services/mqtt/docker/eclipse-mosquitto-container.json at master · GladysAssistant/Gladys · GitHub)
The latest version of eclipse-mosquitto is 2.0.20 but we had issues with 2.0.16, so it’s worth testing whether those issues have been resolved.
So the first lead is to investigate the different versions of eclipse-mosquitto to see if the problem comes from there
2nd option: update MQTT.js
The MQTT.js library (GitHub - mqttjs/MQTT.js: The MQTT client for Node.js and the browser) that we use in the integration is at 4.0.0 in Gladys, and the latest version is 5.10.1.
Knowing that 5.0 is a complete rewrite in TypeScript, it’s possible the library has changed a lot since then and fixes historical bugs:
So upgrading could be another avenue
1 Like
Thank you very much for your additional input @pierre-gilles.
I’ve had this issue for years so nothing urgent!! What I propose is to run the tests with the solutions you mentioned as soon as I can get back to development. I’m the best-placed person to reproduce the problem at will ^^
I just absolutely have to finish insulating before the cold weather.
EDIT (for the record): No issues with the other connections
1 Like
I don’t know if this will help (not analyzed ^^):
1 Like
@Terdious to fuel the debate here, I noticed we don’t have the issue on the Zigbee2mqtt integration for this case!
And surprise, we’re using the version the version 4.2.6 on the Zigbee2mqtt side :
Vs 4.0.0 on the MQTT integration side :
I can try updating to 4.2.6 if you want, it takes 2 minutes since it’s not a breaking change
Besides, the other big difference is that on the Zigbee2mqtt side we run a pinned mosquitto container, so no updates :
"Image": "eclipse-mosquitto:2.
1 Like
Thanks for keeping this going.
Whatever you think! If it’s not a breaking change, then indeed it won’t hurt ^^
If you’d prefer to wait for me to run a test on my side to verify that it resolves, since there’s no one else, that’s no problem at all!! ^^
On second thought I’m not sure it’s useful — I reread all the release notes from 4.0.0 to 4.2.6 and I didn’t see anything that might concern us.
I think the Zigbee2mqtt integration is not affected because the mosquitto container is based on a fixed image.
Ok, but it’s the same on my side. I never update ^^ except the last time to test!! (Or I didn’t understand ^^)
And as I told you, I have the problem on my heavy installation but not on the other one…
1 Like
Ok, always up for more tests on your side then 
I never managed to reproduce it, so I’m having trouble helping, I admit!
1 Like
Yes, I guessed!! ^^ No worries (sorry I couldn’t test earlier)
I’ll keep you posted when I’ve been able to run more tests… it’s coming:
[details=« Off-topic: progress of the work »]
Only the strips, the underlay and the laying of the vinyl floor remain
1 Like
1 Like
Stopped again on December 13 at 6:00 PM
Time of the power outage that lasted 3 hours.
Maybe the broker doesn’t restart when Gladys starts…
I just saw that it’s the same thing with Z-Wave JS UI :
After clicking Save configuration :
This is a big problem because my water heater no longer works in off-peak/peak mode if it trips.
I’m going to remove the contactor I installed to be sure of having hot water.
Yesterday, water was at 40°C.
Same for the ground-floor heating. The fireplace
1 Like