Besoin d'aide sur des messages d'erreur MQTT personnalisé

mutmut · Janvier 21, 2025, 4:39

Hello,
en regardant les logs docker (via portainer), j’ai plein de messages toutes les secondes comme ceci :

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)

Mon MQTT Gladys récupère la value de PAPP, qui elle est poussée par jeedom dès qu’il y a un changement.

Quelqu’un peut me dire si c’est grave ou pas, si je me suis trompé, et si il y a quelque chose à faire ?
(sachant que je récupère bien la valeur PAPP et que je l’affiche bien sur mon dashboard avec le Topic MQTT pour publier)
Merci d’avance

Terdious · Janvier 21, 2025, 7:50

Salut @mutmut ,

Si je ne dis pas de betise, c est parce que tu as d’autres propriétés dans ton json qui ne sont pas utilisées, donc il recherche des features qui auraient ces propriétés mais n’en trouve pas. Il ne trouve que la feature qui utilise la propriété ‹ value ›.

Je pense hein ^^

Donc normalement rien de grave, ca fait juste du log. Si tout fonctionne pour toi, c’est good. Si tu ne l’utilise nulle part d’autre ce topic/message mqtt, tu peux supprimer les propriétés pour ne plus les avoir normalement.

pierre-gilles · Janvier 22, 2025, 8:00

Je ne pense pas @Terdious !

L’erreur vient de là:

github.com

GladysAssistant/Gladys/blob/master/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js#L21


      
          * @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}`);
           // If objectPath is not null, it's supposed to be a JSON
           if (objectPath) {
             try {
               const state = get(JSON.parse(message), objectPath);
               this.gladys.event.emit(EVENTS.DEVICE.NEW_STATE, {
                 device_feature_external_id: this.gladys.stateManager.get('deviceFeatureById', deviceFeatureId).external_id,
                 state,
               });
             } catch (e) {
               logger.warn(`Fail to parse message from custom MQTT topic.`);
               logger.warn(message);
               logger.warn(e);
             }
           } else {
             // else, it's supposed to be a normal string, send it raw
             this.gladys.event.emit(EVENTS.DEVICE.NEW_STATE, {

@mutmut Tu as d’autres endroits où tu as défini ce même topic MQTT personnalisés ?

Terdious · Janvier 22, 2025, 8:14

Hello !!

En effet ce n’est pas dans le sens que je le disais :

2025-01-22T09:10:51+0100 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic tele/tasmota_CEE4B0/STATE
2025-01-22T09:10:51+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: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)

J’ai les memes erreurs de mon côté pour plein d’appareils comme ‹ tasmota_CEE4B0 ›. Je vais investigué pour avoir l’exact réponse, mais ça me paraissait être en lien avec le topic ou le message depuis tout ce temps ^^ Parce que idem j’ai bien toutes les valeurs qui sont intégrées dans Gladys !!

Je ne pourrais pas investiguer avant dimanche par contre !!

mutmut · Janvier 22, 2025, 10:19

J’utilise 2 fois PAPP sur mon dashboard et rien autre part.

pierre-gilles · Janvier 23, 2025, 7:30

Je parlais plus côté intégration MQTT, est-ce que tu avais plusieurs appareils auquel tu as rattaché ce même topic personnalisé ?

mutmut · Janvier 23, 2025, 10:21

On parle bien du Topic MQTT personnalisé ?

Si oui alors il n’est utilisé qu’une seule fois.
Et pour info celui-ci est le premier dans mon appareil qui en compte 10 personnalisés en tout.

Dans mon souvenir, j’ai dû créer plusieurs topics avec le même mqtt personnalisé mais en allant chercher un autre message et notamment en mettant humanName et name à la place de value. Par contre je les ai supprimé mais j’ai vu un post où il pouvait y avoir des « ghost » de topic, c’est peut-être ça mon problème.

mutmut · Janvier 23, 2025, 10:32

Si je continue dans mes réflexions et surtout mes tests du début.

Lorsque je crée une fonctionnalité et que je m’aperçois ensuite qu’elle n’a pas les bonnes infos à l’intérieur (comme Unité par exemple) :

alors je crée une seconde fonctionnalité et j’y mets exactement les mêmes infos que la première et je sauvegarde.
Le résultat est que la seconde fonctionnalité remplace la première (ce qui m’évite de faire un supprimer et de retrouver la nouvelle fonctionnalité à la fin). J’espère que c’est assez clair.

Je ne sais pas si c’est un comportement normal ou pas par contre, mais c’est super pratique

mutmut · Janvier 23, 2025, 11:04

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 · Janvier 24, 2025, 8:19

Effectivement !

Ce n’est pas un comportement normal Plutôt un bug

Non c’est normal, tu dois avoir 2 maisons dans Gladys non ? Le sunrise/sunset est calculé à la localisation de chaque maison (normal, il n’est pas le même partout)

Ok, il doit y avoir un souci sur ce point. Faudrait qu’on arrive à reproduire.

Je crois que @Terdious arrive déjà à reproduire ton premier crash, je pense qu’on on en saura plus après qu’il ait investigué.

On ne gère pas les types texte Mais ça peut se changer → demande de fonctionnalité (il y en a peut-être déjà une)

mutmut · Janvier 24, 2025, 3:27

merci le bug alors, je l’adore

exact, j’ai mis un second emplacement qui est à l’ouest et moi je suis à l’est.

Je m’en occupe car j’aimerais bien récupérer des textes.

Merci pour ton retour et ton analyse @pierre-gilles !