Gladys slowdowns

Configuration
1

Hello hello!

I haven’t been back to Gladys since the update, and I can’t say if this is due to the update because according to the changelog, there’s no apparent reason.

This morning, Gladys is completely laggy, taking between 30 seconds and 2 minutes to display a page and before I can click somewhere else. I think this is due to excessive log verbosity. All messages from all my devices log errors handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic and handleNewMessage.js:54 (MqttHandler.handleNewMessage) TypeError: Cannot read properties of null (reading 'external_id'):

Logs 
2025-04-22T06:16:48+0200 <warn>handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:Arduino01_Building:Centre Equitherapy/feature/mqtt:Arduino01_Building:Average Voltage:Centre Equitherapy/state
2025-04-22T06:16:48+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-04-22T06:16:50+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:shellypro3em-2cbcbba663cc/feature/mqtt:active_power_general_power_supply_L1/state
2025-04-22T06:16:50+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-04-22T06:16:50+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:shellypro3em-2cbcbba663cc/feature/mqtt:apparent_power_general_power_supply_L1/state
2025-04-22T06:16:50+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-04-22T06:16:50+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:shellypro3em-2cbcbba663cc/feature/mqtt:active_power_general_power_supply_L2/state
2025-04-22T06:16:50+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 processTicksAndRejections (node:internal/process/task_queues:85:11)
2025-04-22T06:16:50+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:shellypro3em-2cbcbba663cc/feature/mqtt:apparent_power_general_power_supply_L2/state
2025-04-22T06:16:50+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 processTicksAndRejections (node:internal/process/task_queues:85:11)
2025-04-22T06:16:50+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:shellypro3em-2cbcbba663cc/feature/mqtt:puissance_active_alimentation_generale_L3/state
2025-04-22T06:16:50+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 processTicksAndRejections (node:internal/process/task_queues:85:11)
2025-04-22T06:16:50+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:shellypro3em-2cbcbba663cc/feature/mqtt:puissance_apparente_alimentation_generale_L3/state
2025-04-22T06:16:50+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 processTicksAndRejections (node:internal/process/task_queues:85:11)
2025-04-22T06:16:50+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:shellypro3em-2cbcbba663cc/feature/mqtt:puissance_active_alimentation_generale_TOTALE/state
2025-04-22T06:16:50+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 processTicksAndRejections (node:internal/process/task_queues:85:11)
2025-04-22T06:16:50+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic gladys/master/device/mqtt:shellypro3em-2cbcbba663cc/feature/mqtt:puissance_apparente_alimentation_generale_TOTALE/state
2025-04-22T06:16:50+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 processTicksAndRejections (node:internal/process/task_queues:85:11)
2025-04-22T06:16:51+0200 <warn> handleNewMessage.js:53 (MqttHandler.handleNewMessage) Unable to handle new MQTT message in topic tele/tasmota_F19068/STATE

et vue mon installation mqtt, it’s non-stop.
Yet when I manage to display the curves, the data is indeed present!!

2

Hi @Terdious,

I don’t think that’s related to the update.

You must have a script or a Node-RED flow that is flooding MQTT with messages and on the Gladys side it can’t find a match with an existing device

3

No, precisely that’s the problem, it affects all MQTT topics of the MQTT and TASMOTA integrations. But as I said, the data is still being recorded correctly.

No issues on the scripts and Node-RED side, the messages are indeed being sent every 10s / 30s / or 60s. Nothing has changed on that side.

I’ll take a look on my end. No more slowdowns at the moment, but errors are still present in the logs for no apparent reason since all the data is being recorded correctly!