You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there @Kane610, mind taking a look at this issue as it has been labeled with an integration (deconz) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of deconz can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign deconz Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
Hello. The integration depends on deconz signaling these kind of changes and as deconz has never fully supported signaling the removal of different properties it has also not been implemented in the integration. This is the first error report for this IIRC since the integrations conception so it has not been a big issue so far
The problem
Deleted devices/sensors in Phoscon/Deconz get not deleted in HA
I deleted a device in DECONZ/Phoscon, but it still remains in HA and is now for sure unavailable.
I have no additional information available.
What version of Home Assistant Core has the issue?
core-2024.5.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Deconz
Link to integration documentation on our website
https://www.home-assistant.io/integrations/deconz
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: