node-red-contrib-knx-ultimate: KNX not working properly anymore after update from 3.2.10 -> 3.2.11
Hello Super-Giovanni, thanks for maintaining this wonderful node driving my SmartHome since ~5years!
Describe the bug I regularly update my Node-RED nodes. Yesterday from knx-ultimate version 3.2.5 -> 3.2.11. After a restart of the Raspberry PI I noticed that KNX communication is not working propery anymore.
Most obvious malfunctions:
- Values are not read from KNX bus after startup (“Read from KNX bus”)
- Sending new values (e.g. for light bulbs) to KNX does not work anymore.
From the logs I can see that the cron-plus node reports several “System Time Change Detected”. I had this already in the past when running for example a heavy database query which blocks the nodejs loop for too long time. Then after ~30sec a serious KNX error happens and the node does a reconnect
Oct 14 20:28:44 rpi0 Node-RED[1518]: 14 Oct 20:28:44 - [info] [cronplus:0:00 ] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application
Oct 14 20:28:44 rpi0 Node-RED[1518]: 14 Oct 20:28:44 - [info] [cronplus:Morning AutoOpen Trigger] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application
Oct 14 20:28:44 rpi0 Node-RED[1518]: 14 Oct 20:28:44 - [info] [cronplus:12:00:] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application
Oct 14 20:28:44 rpi0 Node-RED[1518]: 14 Oct 20:28:44 - [info] [cronplus:7:00] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application
Oct 14 20:28:44 rpi0 Node-RED[1518]: 14 Oct 20:28:44 - [info] [cronplus:goldenHour + 20m] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application
Oct 14 20:29:37 rpi0 Node-RED[1518]: 10/14/2024, 8:29:37 PM [KNXEngine] [ERROR] Error: Invalid Connection ID
Oct 14 20:29:37 rpi0 Node-RED[1518]: at KNXClient.processInboundMessage (/home/pi/.node-red/node_modules/knxultimate/src/KNXClient.ts:1618:9)
Oct 14 20:29:37 rpi0 Node-RED[1518]: at Socket.emit (node:events:519:28)
Oct 14 20:29:37 rpi0 Node-RED[1518]: at UDP.onMessage (node:dgram:946:8)
Oct 14 20:29:37 rpi0 Node-RED[1518]: 10/14/2024, 8:29:37 PM [knxUltimate-config <knx.homelab>] [ERROR] received KNXClientEvents.error: Invalid Connection ID
Oct 14 20:29:37 rpi0 Node-RED[1518]: 10/14/2024, 8:29:37 PM [knxUltimate-config <knx.homelab>] [ERROR] Disconnected by: Invalid Connection ID
Oct 14 20:29:38 rpi0 Node-RED[1518]: 10/14/2024, 8:29:38 PM [KNXEngine] [ERROR] Sending KNX packet: Send UDP Catch error: Not running object seqCounter:
Oct 14 20:29:38 rpi0 Node-RED[1518]: 10/14/2024, 8:29:38 PM [KNXEngine] [ERROR] Error: Not running
Oct 14 20:29:38 rpi0 Node-RED[1518]: at healthCheck (node:dgram:924:11)
Oct 14 20:29:38 rpi0 Node-RED[1518]: at Socket.send (node:dgram:651:3)
Oct 14 20:29:38 rpi0 Node-RED[1518]: at KNXClient.processKnxPacketQueueItem (/home/pi/.node-red/node_modules/knxultimate/src/KNXClient.ts:501:40)
Oct 14 20:29:38 rpi0 Node-RED[1518]: at KNXClient.handleKNXQueue (/home/pi/.node-red/node_modules/knxultimate/src/KNXClient.ts:561:16)
Oct 14 20:29:38 rpi0 Node-RED[1518]: at runNextTicks (node:internal/process/task_queues:60:5)
Oct 14 20:29:38 rpi0 Node-RED[1518]: at processTimers (node:internal/timers:516:9)
Oct 14 20:29:38 rpi0 Node-RED[1518]: 10/14/2024, 8:29:38 PM [knxUltimate-config <knx.homelab>] [ERROR] received KNXClientEvents.error: Not running
Oct 14 20:29:38 rpi0 Node-RED[1518]: 10/14/2024, 8:29:38 PM [knxUltimate-config <knx.homelab>] [ERROR] Disconnected by: Not running
Oct 14 20:29:44 rpi0 Node-RED[1518]: 10/14/2024, 8:29:44 PM [KNXEngine] [ERROR] KNXClient: into async closeSocket(): Error: Not running
Oct 14 20:29:44 rpi0 Node-RED[1518]: at healthCheck (node:dgram:924:11)
Oct 14 20:29:44 rpi0 Node-RED[1518]: at Socket.close (node:dgram:749:3)
Oct 14 20:29:44 rpi0 Node-RED[1518]: at /home/pi/.node-red/node_modules/knxultimate/src/KNXClient.ts:1130:41
Oct 14 20:29:44 rpi0 Node-RED[1518]: at new Promise (<anonymous>)
Oct 14 20:29:44 rpi0 Node-RED[1518]: at KNXClient.closeSocket (/home/pi/.node-red/node_modules/knxultimate/src/KNXClient.ts:1116:10)
Oct 14 20:29:44 rpi0 Node-RED[1518]: at knxUltimateConfigNode.node.initKNXConnection (/home/pi/.node-red/node_modules/node-red-contrib-knx-ultimate/nodes/knxUltimate-config.js:618:38)
Oct 14 20:29:44 rpi0 Node-RED[1518]: at KNXClient.Disconnect (/home/pi/.node-red/node_modules/knxultimate/src/KNXClient.ts:1165:15)
With version 3.2.10 or before I don’t get such errors. Downgrading the knx-ultimate 3.2.10 resolves these errors completely.
After ~4-5min of Node-RED runtime these System Time Change Detected error are actually stopping and the systems seems to recover. The “Read from KNX bus” gets the values from the bus and also sending values to the bus works again.
To Reproduce
- Install node-red-contrib-knx-ultimate from version 3.2.10 -> Everything works as expected
- Update to node-red-contrib-knx-ultimate to version 3.2.11
- Restart Node-RED
- “Read from KNX bus” or send to KNX bus works does not work anymore
Expected behavior “Read from KNX bus” and send to KNX network works.
Screenshots only the logs above might be helpful.
Knx-Ultimate Version node-red-contrib-knx-ultimate version 3.2.11
Are you running node-red behind homematic, docker or anything similar? Node-Red running alone on a Raspberry Pi 4 with the following software versions:
[info] Node-RED version: v4.0.5
[info] Node.js version: v20.18.0
[info] Linux 6.6.51+rpt-rpi-v8 arm64 LE
Additional context Issue also reproducible with node-red-contrib-knx-ultimate 3.2.12. I am working with knxd and TUL stick.
Please let me know if I anyhow can help you analyzing this issue.
Maybe related to #387 also reporting issues with update to 3.2.11.
Thanks! Sebastian
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19 (13 by maintainers)
Please revert back. Tomorrow i’ll take a deep look into the 3.2.11. Usually, a step install is not required.