search

ekarak / knx

KNXnet/IP protocol implementation for Node(>=6.x)
MIT License
9 stars 4 forks source link

empty internal fsm queue due to inbound_DISCONNECT_REQUEST #7

Open pesi- opened 3 months ago

pesi- commented 3 months ago

Hi! I get an "empty internal fsm queue due to inbound_DISCONNECT_REQUEST" info message every 10 minutes. It is only an info message i know, but at the very same moment i get oflline. The "offline"-state holds on for 9 minutes. Then i get the (re)"connected" event. After 1 minute i get the above info again and i'am offline again. When i restart my node-server it works for approx. 2 to 3 hours normally. Then the above described behavior starts. At the beginning not so often. See screenshot.

image

Any ideas?

I start the connection with "forceTunneling=true". connection = new knx.Connection({ ipAddr: config.settings.routerIp, ipPort: config.settings.port, interface: config.settings.interface, physAddr: config.settings.physAddress, forceTunneling: true }); My Gateway is a Zennio KNX-IP-Router https://www.zennio.com/de/produkt/ip-router

THX in advance!

pesi- commented 3 months ago

Additional information with loglevel trace: for each "conn.write" i get an "[debug] 2024-07-23 05:52:54.026 *** deferring outbound_TUNNELING_REQUEST until transition sendDatagram => idle"

I also tried to deactivate "forceTunneling" with no effect. THX.