On the current master branch and due to the excellent work by Paul, the existing implementations based on knxd WILL break. Existing users will have to update the knx_config.json and add "knxd: true" to the root of the json.
This might lead to increased support issues. You might want to leave the default case as is and make the new way the optin way.
I noticed that because the communication from knx to hk broke. No messages from the bus arrived in homebridge-knx. The other way around was fine. Means: I was able to switch lights from HK, but when I switched lights in KNX, the updated state was not reflected in HK.
Now this one was hard to figure out. 😄
On the current master branch and due to the excellent work by Paul, the existing implementations based on knxd WILL break. Existing users will have to update the knx_config.json and add "knxd: true" to the root of the json.
This might lead to increased support issues. You might want to leave the default case as is and make the new way the optin way.
I noticed that because the communication from knx to hk broke. No messages from the bus arrived in homebridge-knx. The other way around was fine. Means: I was able to switch lights from HK, but when I switched lights in KNX, the updated state was not reflected in HK.