-
Notifications
You must be signed in to change notification settings - Fork 13
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
Issue connecting the window sensor: Cannot read property 'modelId' of undefined #6
Comments
I checked with mosquitt_sub what the incoming message looked like.
Strangely, |
I think I've cracked it: this version of the magnetic contact sensor was not in the supported devices list. Perhaps there could be a fuzzy matching heuristic where only the first two parts of the |
I've created a pull request to add this device. It might be nice to create more expressive error messages when this is the issue, so the user knows what to do. |
Yeah, I think we should add a proper error message for unsupported devices. Will definitely look into this |
How do you feel about the fuzzy matching? Could that work? Or will that only lead to issues? I don't know if the convention that Xiaomi/other companies use is in any way predictable. E.g. that the string after the second dot is just a version upgrade without a fundamentally change to how things work. Then again, this case already hinted that version 2 of the magnetic contact sensor works differently. |
I have managed to install the add-on manually, I think. The Zigbee2mqtt software is running in a terminal window, and when I press the button on the Aqara window sensor for 3 seconds I can see some messages scroll by. It seems Zigbee2MQTT is working.
The add-on also show some activity at the same time: it crashes.
The text was updated successfully, but these errors were encountered: