-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Existing device MEG5113-0300/MEG5165-0000 has new endpoint id #5561
Comments
Does |
Actually i was a bit wrong there, it seems like Endpoint 5 is the one to go. At least partly. The device(s) now show up correctly on MQTT and report their linkstate and position. |
Thanks, fixed the code. These no converter messages are normal (it just indicates these won't be converter to MQTT, because these messages are not interesting). Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html) |
While adding a couple of Merten wiser Shutter controls, herdsman ran into a Type Error: "TypeError: Cannot read property 'bind' of undefined".
When examining the paring process with herdsman on debug, it seems that the endpoint id is 21 instead of 1.
(See https://pastebin.com/pdUMskcp)
devices.js has this model currently configured with "const endpoint1 = device.getEndpoint(1);"
I suggest mending devices.js and including a potential endpoint id of "21"
The text was updated successfully, but these errors were encountered: