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
Unbiding from non-existing group fails #4901
Comments
Can you provide the debug log when unbinding from this group? To enable debug logging set in advanced:
log_level: debug |
I have the same issue Group 901 is created on UI without devices in : When i try to remove 901 group : error 2020-11-08 13:46:00: Request 'zigbee2mqtt/bridge/request/group/remove' failed with error: 'message.trim is not a function' info 2020-11-08 13:46:00: MQTT publish: topic 'zigbee2mqtt/bridge/response/group/remove', payload '{"data":{},"error":"message.trim is not a function","status":"error"}'` |
@Koenkk I'm experiencing this right now with an IKEA E1743 switch!
Following this, I also tried using MQTT message "zigbee2mqtt/bridge/config/remove_group" with payload "901" but that also failed:
|
After better reading this on the docs, I managed to solve my problem! I still seem to not being able to fully "unbind" from the 901 group, but at least the button is usable inside the group I wanted! |
When trying to unbind the device from a group that does not exist in the configuration.yaml - something definitely happening with the IKEA default of 901, I get
(I did try to reproduce this by first creating the group, the removing it from the yaml). Trying to delete the group, results in
The group does show in the group list of the new UI though - that's how I triggered both unbind and delete. |
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) |
* Update zigbee2mqtt-frontend to 0.2.71 (Koenkk#4928) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update zigbee2mqtt-frontend to 0.2.72 (Koenkk#4932) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update zigbee2mqtt-frontend to 0.2.74 (Koenkk#4935) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Fix set/get with property including endpoint name having _ not working. * Fix unbind for default_bind_group (901) not working from frontend. Koenkk#4901 * Update zigbee-herdsman to 0.13.28 (Koenkk#4946) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Expose `position` for compatible thermostats (Koenkk#4936) This exposes an absolute position. * Display manufacturer name for unsupported devices (Koenkk#4938) * Display manufacturer name for unsupported devices * fixup! Display manufacturer name for unsupported devices * Fix state.json not pretty printed (Koenkk#4943) * state.json format Since 9774031 the state.json file is not formatted anymore, it's just 1 line. * Update state.js Co-authored-by: Koen Kanters <koenkanters94@gmail.com> * Update zigbee2mqtt-frontend to 0.2.75 (Koenkk#4953) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update zigbee2mqtt-frontend to 0.2.76 (Koenkk#4957) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update zigbee-herdsman to 0.13.29 (Koenkk#4955) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update zigbee2mqtt-frontend to 0.2.77 (Koenkk#4961) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update zigbee2mqtt-frontend to 0.2.78 (Koenkk#4962) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Koen Kanters <koenkanters94@gmail.com> Co-authored-by: Kamil Trzciński <ayufan@ayufan.eu> Co-authored-by: Drzony <drzony@gmail.com> Co-authored-by: Nonsense112 <35377929+Nonsense112@users.noreply.github.com>
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
What happened
I bought an Ikea IKEA E1524/E1810 yesterday, which is pre-bound to a default group. In my case it was 901, I suspect this is the one Ikea uses for all its devices.
In order to control my devices, I needed to bind the to the remote. However, according to the Z2M documentation, I had to first unbind from the default group. But that did not work because group 901 did not exist on my system before.
The UI was showing group 901 as empty, but neither could I delete it over there nor could I unbind the device from the group. Instead, I had to first manually add it to the configuration.yaml.
What did you expect to happen
Unbinding the group & deleting it should work independent of whether it has an entry in configuration.yaml or not.
How to reproduce it (minimal and precise)
See above. I suspect creating a group, binding a device, then manually deleting the group from configuration.yaml will set up the system in a similar way. Didn't try to.
Debug info
Zigbee2MQTT version: 1.16.1
Adapter hardware: CC1352P-2
Adapter firmware version: 20201026
The text was updated successfully, but these errors were encountered: