-
-
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
Updating bindings for devices with a '/' in the name doesn't work. #2250
Comments
Anyway, still having issues with a E1743 I borrowed from a friend for testing. Even if the source and target do not have a '/' in the name, I am unable to bind it. It also doesn't even log that it received the mqtt topic :s |
Fixed in latest dev. Multiple For the E1743 I think you first need to unbind it from group 99 or 0, and maybe it can even be bound to a group and not directly to a device (not sure though). Closing this as the OP issue has been fixed. |
I'll see if I can borrow the E1743 again at some point to see if I can unbind it from the group... I tried unbinding it from the coordinator with no success either. For a group... do I just send it the group_id ? |
yes |
nvm, somehow a non printable char snuk in :| |
https://github.com/Koenkk/zigbee2mqtt/blob/master/lib/extension/deviceBind.js#L24
First issue seems to be the mqtt subscription, as it currently accepts + or +/+ wild cards so it will match a device or device/endpoint, if the device name has a '/' it, it will no longer work.
Not sure we can get this to work though, as there is also getIDAndPostfix which strips of the last chunk as the endpoint name (I think).There seems to be a regex in dev.if this is indeed causing a lot of issues, it might be time to revist the allowing '/' in device and group names. I personally use it a lot because I can easily subscript to all devices in a room, but it does cause a lot of issues frequently.
The text was updated successfully, but these errors were encountered: