Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with npm-knx #162

Closed
Luehrsen opened this issue Apr 22, 2020 · 3 comments
Closed

Issues with npm-knx #162

Luehrsen opened this issue Apr 22, 2020 · 3 comments
Labels

Comments

@Luehrsen
Copy link
Contributor

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.

@snowdd1
Copy link
Owner

snowdd1 commented May 1, 2020

You are right. Will change that to force "knxconnection": "knxjs" for pure knx js to use.

@snowdd1
Copy link
Owner

snowdd1 commented May 1, 2020

fixed with daec87f

@snowdd1
Copy link
Owner

snowdd1 commented May 1, 2020

... in version 0.3.24 in npm.

@snowdd1 snowdd1 closed this as completed May 1, 2020
@snowdd1 snowdd1 added the bug label May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants