Need help with custom MQTT error messages

mutmut · January 21, 2025, 4:39pm

Hello,
while looking at the docker logs (via Portainer), I have lots of messages every second like this :

2025-01-21T17:22:44+0100 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-01-21T17:22:44+0100 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":520,"humanName":"[Maison][xxxxxx][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-01-21T17:22:44+0100 <warn> handleDeviceCustomTopicMessage.js:27 (MqttHandler.handleDeviceCustomTopicMessage) TypeError: Cannot read properties of null (reading 'external_id')
    at MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:21:103)
    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:1541:12)
    at MqttClient._handlePacket (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:529:12)
    at work (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:430:12)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:444:5)
    at doWrite (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:390:139)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:381:5)
    at Writable.write (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:302: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)
2025-01-21T17:22:44+0100 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-01-21T17:22:44+0100 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":520,"humanName":"[Maison][xxxxxx][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-01-21T17:22:44+0100 <warn> handleDeviceCustomTopicMessage.js:27 (MqttHandler.handleDeviceCustomTopicMessage) TypeError: Cannot read properties of null (reading 'external_id')
    at MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:21:103)
    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:1541:12)
    at MqttClient._handlePacket (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:529:12)
    at work (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:430:12)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:444:5)
    at doWrite (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:390:139)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:381:5)
    at Writable.write (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:302: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)

My Gladys MQTT retrieves the value of PAPP, which is pushed by Jeedom as soon as there is a change.

Can someone tell me if this is serious or not, if I made a mistake, and if there is anything to do?
(knowing that I correctly retrieve the PAPP value and that I display it on my dashboard with the MQTT Topic to publish)
Thanks in advance

Terdious · January 21, 2025, 7:50pm

Hi @mutmut,

If I’m not mistaken, it’s because you have other properties in your JSON that aren’t used, so it’s looking for features that would have those properties but doesn’t find any. It only finds the feature that uses the ‹ value › property.

I think so ^^

So normally nothing serious, it just produces logs. If everything works for you, it’s good. If you don’t use this topic/MQTT message anywhere else, you can remove the properties so you shouldn’t see them anymore.

pierre-gilles · January 22, 2025, 8:00am

I don’t think so @Terdious!

The error comes from here:

github.com/GladysAssistant/Gladys

server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js

master


      
          * @example
          * handleDeviceCustomTopicMessage('custom_topic', '{"data": 12}', 'ea841937-74e5-401a-8b08-c546d9a322b5', 'data');
          */
          function handleDeviceCustomTopicMessage(topic, message, deviceFeatureId, objectPath) {
           logger.debug(`New value on custom topic ${topic} for device_feature = ${deviceFeatureId}`);
           try {
             const deviceFeature = this.gladys.stateManager.get('deviceFeatureById', deviceFeatureId);
             if (!deviceFeature) {
               logger.warn(`handleDeviceCustomTopicMessage: Device feature ${deviceFeatureId} not found`);
               return;
             }
             // If objectPath is not null, it's supposed to be a JSON
             if (objectPath) {
               const state = get(JSON.parse(message), objectPath);
               this.gladys.event.emit(EVENTS.DEVICE.NEW_STATE, {
                 device_feature_external_id: deviceFeature.external_id,
                 state,
               });
             } else {
               // else, it's supposed to be a normal string, send it raw
               this.gladys.event.emit(EVENTS.DEVICE.NEW_STATE, {

@mutmut Do you have other places where you’ve defined this same custom MQTT topic?

Terdious · January 22, 2025, 8:14am

Hello !!

Indeed it’s not in the way I was saying:

2025-01-22T09:10:51+0100 \u003cwarn\u003e handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic tele/tasmota_CEE4B0/STATE
2025-01-22T09:10:51+0100 \u003cwarn\u003e 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 (\u003canonymous\u003e)
    at MqttHandler.handleNewMessage (/src/server/services/mqtt/lib/handleNewMessage.js:39:26)
    at MqttClient.\u003canonymous\u003e (/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:1541:12)
    at MqttClient._handlePacket (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:529:12)
    at work (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:430:12)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:444:5)
    at doWrite (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:390:139)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:381:5)
    at Writable.write (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:302: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)

I have the same errors on my side for lots of devices like ‹ tasmota_CEE4B0 ›. I’ll investigate to get the exact answer, but it seemed to me to be related to the topic or the message all this time ^^ Because likewise I have all the values that are integrated into Gladys!!

I won’t be able to investigate before Sunday though!!

mutmut · January 22, 2025, 10:19am

I use PAPP twice on my dashboard and nowhere else.

pierre-gilles · January 23, 2025, 7:30am

I was referring more to the MQTT integration side — did you have multiple devices to which you attached that same custom topic?

mutmut · January 23, 2025, 10:21am

Are we talking about the custom MQTT topic?

If so, then it is only used once.
And for your info, this one is the first on my device, which has 10 custom topics in total.

As I recall, I had to create several topics using the same custom MQTT topic but fetching a different message and notably by putting humanName and name instead of value. However, I deleted them, but I saw a post saying there could be « ghost » topics — that might be my problem.

mutmut · January 23, 2025, 10:32am

If I continue with my thoughts and especially my initial tests.

When I create a feature and then realize it doesn’t have the right information inside (like Unité for example) :

I then create a second feature and put exactly the same information as the first into it and save.
The result is that the second feature replaces the first (which saves me from having to delete and then find the new feature at the end). I hope that’s clear enough.

I don’t know whether that’s normal behavior or not, but it’s super convenient

mutmut · January 23, 2025, 11:04am

C’est encore moi
Je viens de redémarrer mon docker Gladys car il ne me récupérai plus les topics personnalisés depuis ce matin ou hier soir, aucune idée.
Une fois redémarré, j’ai les logs suivants :

2025-01-23T11:46:55+0100 <info> scene.dailyUpdate.js:58 () Sunrise today is at 8:42 today, in your timezone = Europe/Paris
2025-01-23T11:46:55+0100 <info> scene.dailyUpdate.js:59 () Sunset today is at 17:55 today, in your timezone = Europe/Paris
2025-01-23T11:46:55+0100 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2025-01-23T11:46:55+0100 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 6 hours.
2025-01-23T11:46:55+0100 <info> scene.dailyUpdate.js:58 () Sunrise today is at 8:11 today, in your timezone = Europe/Paris
2025-01-23T11:46:55+0100 <info> scene.dailyUpdate.js:59 () Sunset today is at 17:13 today, in your timezone = Europe/Paris
2025-01-23T11:46:55+0100 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2025-01-23T11:46:55+0100 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 5 hours.
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/517
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/578
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/578
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/579
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/517
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/436
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/578
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/518
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/518
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/578
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/516
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/517
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/518
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/516
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/578
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/578
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/578
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/885
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/889
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/887
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/888
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/886
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic jeedom/cmd/event/890
2025-01-23T11:46:55+0100 <info> listenToCustomMqttTopicIfNeeded.js:32 () Subscribing to MQTT topic zigbee2mqtt/prise_02
2025-01-23T11:46:55+0100 <info> device.migrateFromSQLiteToDuckDb.js:36 (DeviceManager.migrateFromSQLiteToDuckDb) DuckDB : Already migrated from SQLite. Not migrating.
2025-01-23T11:46:55+0100 <info> index.js:64 (Server.<anonymous>) Server listening on port 8420
2025-01-23T11:47:02+0100 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-01-23T11:47:02+0100 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":"23/01/2025 11:47","humanName":"[Maison][ecocompteur][Dernier refresh]","unite":"","name":"Dernier refresh","type":"info","subtype":"string"}
2025-01-23T11:47:02+0100 <warn> handleDeviceCustomTopicMessage.js:27 (MqttHandler.handleDeviceCustomTopicMessage) TypeError: Cannot read properties of null (reading 'external_id')
    at MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:21:103)
    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:1541:12)
    at MqttClient._handlePacket (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:529:12)
    at work (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:430:12)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:444:5)
    at doWrite (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:390:139)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:381:5)
    at Writable.write (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:302: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)
2025-01-23T11:47:05+0100 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-01-23T11:47:05+0100 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":520,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-01-23T11:47:05+0100 <warn> handleDeviceCustomTopicMessage.js:27 (MqttHandler.handleDeviceCustomTopicMessage) TypeError: Cannot read properties of null (reading 'external_id')
    at MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:21:103)
    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:1541:12)
    at MqttClient._handlePacket (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:529:12)
    at work (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:430:12)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:444:5)
    at doWrite (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:390:139)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:381:5)
    at Writable.write (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:302: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)
2025-01-23T11:47:05+0100 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-01-23T11:47:05+0100 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":520,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-01-23T11:47:05+0100 <warn> handleDeviceCustomTopicMessage.js:27 (MqttHandler.handleDeviceCustomTopicMessage) TypeError: Cannot read properties of null (reading 'external_id')
    at MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:21:103)
    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:1541:12)
    at MqttClient._handlePacket (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:529:12)
    at work (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:430:12)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:444:5)
    at doWrite (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:390:139)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:381:5)
    at Writable.write (/src/server/services/mqtt/node_modules/readable-stream/lib/_stream_writable.js:302: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)

De ce que je vois :

j’ai 2 évaluations de sunrise/sunset au démarrage : bizarre ?
on dirait que je subscribe plusieurs fois aux mêmes topics personnalisés (alors je ne n’en ai qu’un seul à la fois dans mes fonctionnalités)
un topic personnalisé a une erreur mais je n’utilise pas du tout celui-là (« Dernier Refresh »). Par contre j’ai peut-être créée (puis supprimé) une fonctionnalité Texte pour récupérer la value de ce topic qui est du texte (test non concluant).

image1288×866 215 KB

pierre-gilles · January 24, 2025, 8:19am

Indeed!

That’s not normal behavior Rather a bug

No that’s normal, you must have 2 houses in Gladys, right? The sunrise/sunset is calculated at each house’s location (normal, it’s not the same everywhere)

Ok, there must be an issue on that point. We need to be able to reproduce it.

I think @Terdious is already able to reproduce your first crash; I think we’ll know more after he has investigated.

We don’t handle text types But that can be changed → feature request (there might already be one)

mutmut · January 24, 2025, 3:27pm

thanks to the bug then, I love it

Exactly, I added a second location which is to the west and I’m in the east.

I’ll take care of it because I’d like to retrieve texts.

Thanks for your feedback and your analysis @pierre-gilles !

Topic		Replies	Views
Les Scènes - Rex Développement	6	654	May 5, 2020
Problème zigbee2mqtt depuis quelques jours Configuration	37	735	June 1, 2023
Actions ne se chargent pas dans une grande scène Configuration	35	1211	May 16, 2022
Bugs avec la discussion Configuration	42	1529	January 7, 2021
Reflexion autour de l'API MQTT Développement	17	2933	May 4, 2020

Need help with custom MQTT error messages

Related topics