home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.38k stars 30.64k forks source link

Deconz Sunndly not working and not possible to fix it #120134

Closed ahmedbarakat83 closed 3 days ago

ahmedbarakat83 commented 4 months ago

The problem

Hello All, I was using HA for almost 4 years now, and recently I was hit by the issue of "Connection Lost... Reconnecting" with no possibility to revert back to my backups, so I decided to start clean.

I downloaded the latest HA: 2024.6.3 on RPI-4 as fresh installation and started to add the Add-Ons and Integrations. For Zigbee I have a Conbee II stick I was using it with ZHA before and eveything was fine all my sensors and switches were working fine. I decided to switch to Deconz in the new setup after some research that it is better with the Conbee II.

I installed and added my devices created the needed integrations and everything worked fine for 1 day.

Today in the morning I was hit that no device anymore working, I checked found Deconz failed to initialize and can"t recognize the Host, I was using the IP address of the RPI-4 to avoid the issue of the IP change of the Gateway.

The fix of Hostname = "core-deconz" didn't work for me, the IP worked and everything was fine, then suddnly can't detect the gateway on that IP.

Tried sever resets, adding the IP shown in Phoscon but no success, in one reset it worked again but it showed gateway ID 00000000.

I checked the documentation and tried to follow it to fix this issue\ Took a Backup, uninstall it Install it again and configured, started Then in Phoscon the gatway is no more shown I can"t find the IP I can give to the integration and in the logs I still see that the Gateway id is 0000000000 Sorry for the long story, hopefully someone can help

What version of Home Assistant Core has the issue?

2024.6.3

What was the last working version of Home Assistant Core?

2024.6.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

deconz

Link to integration documentation on our website

No response

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

home-assistant[bot] commented 3 months ago

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.

(message by CodeOwnersMention)


deconz documentation deconz source (message by IssueLinks)

Kane610 commented 3 months ago

Tried sever resets, adding the IP shown in Phoscon but no success, in one reset it worked again but it showed gateway ID 00000000.

I checked the documentation and tried to follow it to fix this issue Took a Backup, uninstall it Install it again and configured, started Then in Phoscon the gatway is no more shown I can"t find the IP I can give to the integration and in the logs I still see that the Gateway id is 0000000000

It sounds to me that you're having issues with deCONZ itself, then you should report it here https://github.com/dresden-elektronik/deconz-rest-plugin

issue-triage-workflows[bot] commented 1 week ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.