Closed BugRoger closed 3 years ago
It seems to be related to the group read: timeout
s. Interessting enough the addresses that time out aren't even used by any accessory.
Does HKKNX by chance read the whole middle group, like 1/2/*? Possibly a race condition for addresses that don't respond to read? The addresses it tries to read here aren't connected and won't respond ever.
I'll try to clean up, so that all adresses related to Homekit respond. Though I'm using a scheme where I just copy/paste per Room which leaves me with many spare/empty/"for future reference" GAs. So, this is an annoying task :/
I found a workaround. First, I actually made it that all GAs respond on the read request. That didn't help. A google search hinted that "sequence number one less than expected" is either a problem with an SAP BAPI call or the KNX IP Gateway is responding out of sequence. 😄
Disabling the KNX Gateway auto-detection and setting it to another IP Gateway fixed it. MDT IP Router is throwing this error. The gateway in the Elabnet Timerwolf works without a problem.
My HKKNX process is dying every once in a while. I managed to catch the following panic.
I usually notice since my devices show up as "No Response" in Homekit. Checking the GUI gives me a "System unavailable". After a while it stabilises again.
There's a similar error in the logs that might be related but doesn't cause a panic:
Any pointer's what's happening?