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

Existing device MEG5113-0300/MEG5165-0000 has new endpoint id #5561

Closed
Moony83 opened this issue Jan 4, 2021 · 3 comments
Closed

Existing device MEG5113-0300/MEG5165-0000 has new endpoint id #5561

Moony83 opened this issue Jan 4, 2021 · 3 comments
Labels
problem Something isn't working

Comments

@Moony83
Copy link

Moony83 commented Jan 4, 2021

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"

@Moony83 Moony83 added the problem Something isn't working label Jan 4, 2021
@Koenkk
Copy link
Owner

Koenkk commented Jan 5, 2021

Does const endpoint1 = device.getEndpoint(1) || device.getEndpoint(21); fix it?

@Moony83
Copy link
Author

Moony83 commented Jan 5, 2021

Actually i was a bit wrong there, it seems like Endpoint 5 is the one to go. At least partly.
I managed to integrate with const endpoint1 = device.getEndpoint(1) || device.getEndpoint(5);

The device(s) now show up correctly on MQTT and report their linkstate and position.
However, the logfile still notes a couple of "no converter" lines:
https://pastebin.com/JEB0eiaJ

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Jan 5, 2021
@Koenkk
Copy link
Owner

Koenkk commented Jan 5, 2021

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants