Closed mattreim closed 6 months ago
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.
Unstale...
Honestly, I don't think that is a bug (of deconz). My bulbs interestingly have the same group ID available. However, I can delete it permanently via API, which is the recommended way I believe.
Sorry, but it's more of a botch than a fix and it wasn't like that with older versions. I think it only appeared after the network was rebuilt with version 2.12.06.
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.
Unstale...
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.
Does the issue really belong here?
Is there already an existing issue for this?
Describe the bug
My Müller-Licht bulbs always create a group 240(0x00F0). After deletion, the group is always created again. Also unbind in the bind dropbox and remove group in the group cluster(0004) didn't work.
My bulbs: 2x Müller-Licht - tint LED-Reflektor GU10 white - 404006 2x Müller-Licht - tint LED-Kerzenform E14 white - 404008
Steps to reproduce the behavior
Expected behavior
No further group will be created.
Screenshots
Phoscon:
DB-SQLite:
Environment
deCONZ Logs
No response
Additional context
No response