Dear All
At the moment I have an issue to not anymore be able to start up NoderRed. I therefore checked the nodered logs and found a lot of entries like the following - which might not be the reasons NodeRed is not starting right now but I guess still not good. What is wrongly configreud between KNX and the nodes in noderred ?
....
[warn] 3/9/2024, 2:57:26 PM.682 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 66. Delay handling queue.
[warn] 3/9/2024, 2:57:26 PM.733 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 66. Delay handling queue.
[warn] 3/9/2024, 2:57:26 PM.782 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 66. Delay handling queue.
[error] 3/9/2024, 2:57:26 PM.810 KNXUltimate-KNXEngine: KNXClient: _setTimerWaitingForACK: RequestTimeoutError seqCounter:66, DestAddr:3/1/88, AckRequested:0, timed out waiting telegram acknowledge by 10.0.0.20 no ACK received. Retransmit datagram with seqNumber 66 from 1.1.0 to 3/1/88
[warn] 3/9/2024, 2:57:30 PM.61 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 104. Delay handling queue.
[warn] 3/9/2024, 2:57:30 PM.822 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 111. Delay handling queue.
....
Thanks for any thoughts on this.
BR Schnabu
At the moment I have an issue to not anymore be able to start up NoderRed. I therefore checked the nodered logs and found a lot of entries like the following - which might not be the reasons NodeRed is not starting right now but I guess still not good. What is wrongly configreud between KNX and the nodes in noderred ?
....
[warn] 3/9/2024, 2:57:26 PM.682 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 66. Delay handling queue.
[warn] 3/9/2024, 2:57:26 PM.733 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 66. Delay handling queue.
[warn] 3/9/2024, 2:57:26 PM.782 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 66. Delay handling queue.
[error] 3/9/2024, 2:57:26 PM.810 KNXUltimate-KNXEngine: KNXClient: _setTimerWaitingForACK: RequestTimeoutError seqCounter:66, DestAddr:3/1/88, AckRequested:0, timed out waiting telegram acknowledge by 10.0.0.20 no ACK received. Retransmit datagram with seqNumber 66 from 1.1.0 to 3/1/88
[warn] 3/9/2024, 2:57:30 PM.61 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 104. Delay handling queue.
[warn] 3/9/2024, 2:57:30 PM.822 knxUltimate-config: handleTelegramQueue: the KNXEngine is busy or is waiting for a telegram ACK with seqNumner 111. Delay handling queue.
....
Thanks for any thoughts on this.
BR Schnabu
Kommentar