Problem beim Abrufen eines TEXT-Werts

[mutmut]

Hallo Team,
nach dem PR von @pierre-gilles hier habe ich versucht, einen Textwert abzurufen, aber bei mir klappt es nicht
Hier sind meine Parameter:

Ich glaube, ich mache etwas falsch, aber ich komme nicht weiter.

[pierre-gilles]

Hallo @mutmut

Nutzt du Zigbee2mqtt mit einem benutzerdefinierten MQTT-Broker oder hast du Zigbee2mqtt automatisch mit Gladys gestartet?

Falls du es automatisch mit Gladys gestartet hast, dann ist das, was du beobachtest, normal. Gladys verwendet einen separaten MQTT-Broker, der ein anderer ist.

[mutmut]

Ich habe Custom für z2m und mqtt, verwaltet aber keines davon über Gladys.

[pierre-gilles]

Du verwendest also denselben Broker Mosquitto?

[mutmut]

ja, es ist derselbe.

[mutmut]

Ich habe es gerade mit einem frischen Gladys getestet, das auf meinen produktiven Mosquitto zeigt und … es funktioniert, wie es sollte, und sogar sehr gut.
Also habe ich ein Problem mit meiner produktiven Gladys-Instanz

[mutmut]

Hier sind einige Infos/Logs, die ich gesammelt habe, falls sie helfen können, mir zu helfen.
Ich habe ein benutzerdefiniertes Thema (Funktionsart Text) auf meiner Produktionsinstanz erstellt:

Das Thema wird tatsächlich überwacht, ich sehe es in Debug:

Aber nichts wird auf dem Dashboard angezeigt:

Und hier ist ein Log-Ausschnitt, in dem dieses Thema (2025-05-14T21:55:03) zu sehen ist:

2025-05-14T21:54:35+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:35+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:37+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:37+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:39+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:39+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:41+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-05-14T21:54:41+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":610,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-05-14T21:54:41+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:41+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-05-14T21:54:41+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":610,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-05-14T21:54:41+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:41+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic jeedom/cmd/event/517
2025-05-14T21:54:41+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:41+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:41+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:43+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:43+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:44+0200 <info> netatmo.loadDevices.js:155 (NetatmoHandler.loadDevices) Netatmo devices not supported : 0
2025-05-14T21:54:45+0200 <info> lan-manager.scan.js:19 (LANManager.scan) LANManager starts scanning devices...
2025-05-14T21:54:46+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic jeedom/cmd/event/886
2025-05-14T21:54:46+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:46+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-05-14T21:54:46+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":600,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-05-14T21:54:46+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:46+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fehlgeschlagen beim Parsen der Nachricht vom benutzerdefinierten MQTT-Topic.
2025-05-14T21:54:46+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":600,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-05-14T21:54:46+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:46+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic jeedom/cmd/event/517
2025-05-14T21:54:46+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:49+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:49+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:50+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:50+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:51+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic jeedom/cmd/event/886
2025-05-14T21:54:51+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:51+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fail to parse message from custom MQTT topic.
2025-05-14T21:54:51+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":610,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-05-14T21:54:51+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:51+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fehlgeschlagen beim Parsen der Nachricht vom benutzerdefinierten MQTT-Topic.
2025-05-14T21:54:51+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":610,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-05-14T21:54:51+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:51+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic jeedom/cmd/event/517
2025-05-14T21:54:51+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:54:52+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:52+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:55+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:54:55+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
    at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    at EventEmitter.emit (node:events:518:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
    at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:54:56+0200 <info> lan-manager.scan.js:66 (NmapScan.onSuccess) LANManager discovers 28 devices
2025-05-14T21:54:56+0200 <info> lan-manager.stop.js:12 (LANManager.stop) LANManager stops scanning devices
2025-05-14T21:55:02+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic jeedom/cmd/event/886
2025-05-14T21:55:02+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:55:02+0200 <error> index.js:15 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed not found
      at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
      at EventEmitter.emit (node:events:518:28)
      at Event.emit (/src/server/lib/event/index.js:18:16)
      at Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
}
2025-05-14T21:55:02+0200 <error> index.js:16 (process.<anonymous>) NotFoundError: DeviceFeature zwavejs-ui:25:0:meter:value:electric_w_consumed nicht gefunden
    bei DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:18:11)
    bei EventEmitter.emit (node:events:518:28)
    bei Event.emit (/src/server/lib/event/index.js:18:16)
    bei Promise.map.concurrency (/src/server/services/zwavejs-ui/lib/zwaveJSUI.onNodeValueUpdated.js:53:11)
2025-05-14T21:55:03+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fehlgeschlagene Parsung der Nachricht vom benutzerdefinierten MQTT-Topic.
2025-05-14T21:55:03+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":"14/05/2025 21:55","humanName":"[Maison][ecocompteur][Dernier refresh]","unite":"","name":"Dernier refresh","type":"info","subtype":"string"}
2025-05-14T21:55:03+0200 <warn> handleDeviceCustomTopicMessage.js:27 (MqttHandler.handleDeviceCustomTopicMessage) TypeError: Eigenschaft 'external_id' von null gelesen
    bei MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:21:103)
    bei /src/server/services/mqtt/lib/handleNewMessage.js:41:12
    bei Array.forEach (<anonymous>)
    bei MqttHandler.handleNewMessage (/src/server/services/mqtt/lib/handleNewMessage.js:39:26)
    bei MqttClient.<anonymous> (/src/server/services/mqtt/lib/connect.js:85:10)
    bei MqttClient.emit (node:events:518:28)
    bei handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    bei handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    bei work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    bei Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    bei writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    bei _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    bei Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    bei Socket.ondata (node:internal/streams/readable:1009:22)
    bei Socket.emit (node:events:518:28)
    bei addChunk (node:internal/streams/readable:561:12)
    bei readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    bei Socket.Readable.push (node:internal/streams/readable:392:5)
    bei TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:55:03+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Neue MQTT-Nachricht im Topic jeedom/cmd/event/436 konnte nicht verarbeitet werden
2025-05-14T21:55:03+0200 <warn> handleNewMessage.js:54 (MqttHandler.handleNewMessage) TypeError: Eigenschaft 'external_id' von null gelesen
    bei MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:32:101)
    bei /src/server/services/mqtt/lib/handleNewMessage.js:41:12
    bei Array.forEach (<anonymous>)
    bei MqttHandler.handleNewMessage (/src/server/services/mqtt/lib/handleNewMessage.js:39:26)
    bei MqttClient.<anonymous> (/src/server/services/mqtt/lib/connect.js:85:10)
    bei MqttClient.emit (node:events:518:28)
    bei handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    bei handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    bei work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    bei Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    bei writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    bei _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    bei Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    bei Socket.ondata (node:internal/streams/readable:1009:22)
    bei Socket.emit (node:events:518:28)
    bei addChunk (node:internal/streams/readable:561:12)
    bei readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    bei Socket.Readable.push (node:internal/streams/readable:392:5)
    bei TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:55:07+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fehlgeschlagene Parsung der Nachricht vom benutzerdefinierten MQTT-Topic.
2025-05-14T21:55:07+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":640,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-05-14T21:55:07+0200 <warn> handleDeviceCustomTopicMessage.js:27 (MqttHandler.handleDeviceCustomTopicMessage) TypeError: Eigenschaft 'external_id' von null gelesen
    bei MqttHandler.handleDeviceCustomTopicMessage (/src/server/services/mqtt/lib/handler/handleDeviceCustomTopicMessage.js:21:103)
    bei /src/server/services/mqtt/lib/handleNewMessage.js:41:12
    bei Array.forEach (<anonymous>)
    bei MqttHandler.handleNewMessage (/src/server/services/mqtt/lib/handleNewMessage.js:39:26)
    bei MqttClient.<anonymous> (/src/server/services/mqtt/lib/connect.js:85:10)
    bei MqttClient.emit (node:events:518:28)
    bei handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    bei handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    bei work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    bei Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    bei writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    bei _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    bei Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    bei Socket.ondata (node:internal/streams/readable:1009:22)
    bei Socket.emit (node:events:518:28)
    bei addChunk (node:internal/streams/readable:561:12)
    bei readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    bei Socket.Readable.push (node:internal/streams/readable:392:5)
    bei TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:55:07+0200 <warn> handleDeviceCustomTopicMessage.js:25 (MqttHandler.handleDeviceCustomTopicMessage) Fehlgeschlagene Parsung der Nachricht vom benutzerdefinierten MQTT-Topic.
2025-05-14T21:55:07+0200 <warn> handleDeviceCustomTopicMessage.js:26 (MqttHandler.handleDeviceCustomTopicMessage) {"value":640,"humanName":"[Maison][042375084120][PAPP]","unite":"VA","name":"PAPP","type":"info","subtype":"numeric"}
2025-05-14T21:55:07+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-14T21:55:07+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic jeedom/cmd/event/517
2025-05-14T21:55:07+0200 <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:85:10)
    at MqttClient.emit (node:events:518:28)
    at handlePublish (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/src/server/services/mqtt/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:779:17)
    at Writable.writable._write (/src/server/services/mqtt/node_modules/mqtt/src/lib/client.ts:803:4)
    at writeOrBuffer (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/src/server/services/mqtt/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)

Vielen Dank im Voraus für die Hilfe.

[mutmut]

Also verstehe ich gar nichts mehr, denn ich habe ein benutzerdefiniertes Thema, das funktioniert… Und das ist eines, das ich vor mehreren Monaten erstellt habe, also lange bevor diese Version 4.58 herauskam!

Allerdings habe ich keine Logs, weil sich das nur um 22 Uhr und 6 Uhr (HC und HP) ändert und ich weiß nicht, wie ich sie wiederfinden kann.

[pierre-gilles]

@mutmut könntest du Gladys neu starten (docker restart gladys) und die Start-Logs von Gladys überprüfen?

Vielleicht hast du ein benutzerdefiniertes MQTT-Topic, das Probleme verursacht und das Laden der anderen Topics verhindert. Wir hatten schon mal ein ähnliches Problem in der Vergangenheit!

Mach dir keine Sorgen, wir finden das schon

[mutmut]

@pierre-gilles ich habe dir gerade meine Startprotokolle geschickt. Ich persönlich habe Schwierigkeiten, die Details zu interpretieren, aber soweit ich sehe, habe ich mehrere Zeilen mit Abonnements für identische benutzerdefinierte Themen, aber ich habe jedes Mal nur eines.
Das Einzige, was zu Duplikaten führen könnte, wären Tests, die ich durchgeführt habe, indem ich Funktionen mit benutzerdefinierten Themen erstellt und gelöscht habe.
Und es scheint zu bedeuten, dass diese gelöschten Funktionen immer noch existieren, aber als Geister (laut meiner Analyse).

[mutmut]

eigentlich glaube ich, dass ich seit diesem Jahresauftakt-Thema (und meinem verstärkten Einstieg bei Gladys) ein noch nicht gelöstes Problem habe: Besoin d'aide sur des messages d'erreur MQTT personnalisé - #10 par pierre-gilles

[pierre-gilles]

Danke für dein Feedback @mutmut

Auf den ersten Blick scheint ein Problem mit einem der Geräte die anderen daran zu hindern, zu hören.

Ein guter erster Schritt wäre, die Listener voneinander zu isolieren, um zu verhindern, dass ein Absturz die anderen daran hindert, zu funktionieren. Und natürlich mehr Logs hinzufügen, um besser zu verstehen, was mit denen passiert, die Probleme haben.

Wenn du einverstanden bist, kannst du mir auch deine Datenbank privat schicken. Das würde mir helfen, die Situation schneller zu analysieren

Ich arbeite morgen an Gladys, ich werde mir notieren, mir das dann anzusehen!

[pierre-gilles]

Vielen Dank für deine Datenbank @mutmut, ich habe genau gesehen, was nicht stimmte

Wenn eine Funktion mit einem benutzerdefinierten Thema gelöscht wird, wird die Funktion zwar gelöscht… aber nicht das benutzerdefinierte Thema, das für immer in Gladys bleibt und die Fehler verursacht, die du gesehen hast.

Ich arbeite an einem Fix!

[pierre-gilles]

In diesem PR korrigiert:

MQTT: Fix bug where custom listener params weren’t cleaned up after feature deletion (#2305)

Das geht in die nächste Version von Gladys

[mutmut]

also ich glaube, ich schlage mich nicht zu schlecht in der Systemverständnis aber nicht im reinen Entwickeln
Danke für deine Analyse!

[mutmut]

Hallo,
ich weiß nicht, ob ich etwas übersehen habe, aber ich kann eine MQTT-Textvariable, die über Gladys erstellt wurde (und nicht von einem benutzerdefinierten Topic), nicht abrufen.

Hier ist mein Szenario:

• ich hole eine Textvariable von einer HTTP-Anfrage
  
  
  
  
• ich sende sie in eine MQTT-Textfunktion
  
  
• sie wird im Dashboard angezeigt
  
  
• es ist unmöglich, den letzten Zustand dieser TEXT-Variablen abzurufen
  
  
  
  
  
  
  
  

Hinweis: Wenn dieses Thema in einen neuen Beitrag verschoben werden muss, zögern Sie nicht, die Moderatoren zu kontaktieren.

[pierre-gilles]

@mutmut

Ich weiß nicht, ob ich etwas übersehen habe, aber ich kann keine über Gladys erstellte MQTT-Textvariable abrufen (und nicht von einem benutzerdefinierten Topic).

Ich würde mich freuen, wenn du einen Feature-Request erstellst, denn das ist aktuell mit der Aktion „Letzten Zustand abrufen“ nicht möglich, da diese keine Textfunktionen unterstützt

[mutmut]

et voilà : [Amélioration] Récupérer le dernier état de type TEXT

[pierre-gilles]

@mutmut ich schließe dieses Thema, da alles gut zu sein scheint

Zögere nicht, ein anderes Thema zu erstellen, wenn du weitere Fragen hast!

Gladys Assistant 4.59: Thermostat Aqara W100, Matter, Szenen!

Salut à tous Une nouvelle version de Gladys est disponible Prise en charge des boutons du Thermostat Aqara W100 via Zigbee2MQTT Aqara a récemment sorti un nouveau thermostat connecté, le Aqara W100, compatible Zigbee, Thread et Matter. [aqara-capteur-de-temperature-et-d-humidite-zigbee-30-et-thread-aqara-climate-sensor-w100] @bjm est en train de le tester et m’a fait des retours sur des boutons qui n’étaient pas encore pris en charge par Gladys,…