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

Buderus KM100 can't connect #41

Open
scholli113 opened this issue Sep 7, 2022 · 5 comments
Open

Buderus KM100 can't connect #41

scholli113 opened this issue Sep 7, 2022 · 5 comments

Comments

@scholli113
Copy link

HI,

I have a Buderus KM100, as I understand Nefit would be the protocol that should work but what ever I try I can't seem to looking. I tried Variations for logging in.

I tried like this

"accessories": [
{
"accessory": "NefitEasy",
"name": "thermostaat",
"options": {
"serialNumber": "XXX XXX XXX",
"accessKey": "XXX-XXX-XXX-XXX",
"password": "Bosch ID PW also tried Device PW"
}
}
],

I tried like this

"accessories": [
{
"accessory": "NefitEasy",
"name": "thermostaat",
"options": {
"serialNumber": "XXXXXXXXX",
"accessKey": "XXXXXXXXXXXX",
"password": "Bosch ID PW also tried Device PW"
}
}
],

Would be great If somebody can give me some ideas what to do here

@robertklep
Copy link
Owner

Which error are you receiving, specifically? I can't remember if the KM100 uses the same protocol as the Easy.

@scholli113
Copy link
Author

I get this message

Error: Unhandled error. ('XMPP authentication failure')
at new NodeError (node:internal/errors:372:5)
at Client.emit (node:events:516:17)
at Client._handleAuthState (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/node-xmpp-client/lib/Client.js:295:10)
at Client._handleStanza (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/node-xmpp-client/lib/Client.js:233:12)
at Client.onStanza (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/node-xmpp-client/lib/Client.js:221:8)
at Connection.emit (node:events:527:28)
at Connection.onStanza (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/node-xmpp-core/lib/Connection.js:377:10)
at StreamParser. (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/node-xmpp-core/lib/Connection.js:231:10)
at StreamParser.emit (node:events:527:28)
at SaxLtx. (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/@xmpp/streamparser/index.js:69:14)
at SaxLtx.emit (node:events:527:28)
at SaxLtx._handleTagOpening (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/ltx/lib/parsers/ltx.js:40:12)
at SaxLtx.write (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/ltx/lib/parsers/ltx.js:159:18)
at StreamParser.write (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/@xmpp/streamparser/index.js:134:17)
at Connection.onData (/usr/local/lib/node_modules/homebridge-nefit-easy/node_modules/node-xmpp-core/lib/Connection.js:310:17)
at TLSSocket.emit (node:events:539:35)

@scholli113
Copy link
Author

scholli113 commented Sep 7, 2022

Its hard for me to understand how the set serial, Accesskey, and password

Or if KM100 is supported at all

@robertklep
Copy link
Owner

robertklep commented Sep 7, 2022

XMPP authentication relies on the serial number and access key, not the password.

For Nefit, the serial number consists of 9 digits and the access key of 16 characters (without any hyphens, -, in between), and is also case-sensitive (so a lower case "a" is not considered to be the same as an upper case "A").

Both values can be found on the packaging of the device, and/or on the device itself.

I also don't know if the KM100 is supported, at least by the Nefit Easy driver. There's also a more generic module, bosch-xmpp which (I believe) does support it, but there's no HomeBridge support for it.

@scholli113
Copy link
Author

Okay I guess it doesn't to I get this correct for bosch-xmpp I would need to setup home assistant which I then can connect to HomeKit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants