Skip to content
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

Error in 2.19.1, lost all connection to Zigbee devices. Need update to 2.19.3 #2783

Closed
Brian-lub opened this issue Dec 5, 2022 · 6 comments
Labels

Comments

@Brian-lub
Copy link

Describe the issue you are experiencing

I have no connection to any of my Zigbee devices, they all droppede at after a reboot. i have tried everything i can but nothing worked. then took the mater to Discord. I have been talking to "manup" and "Mimiix" on Deconz Discord
https://discord.com/channels/494922323518947329/543511893382529064/1049323615100874843 and thay found that there is a bug in 2.19.1 and that should be fixed in 2.19.3,
image

What type of installation are you running?

Home Assistant Supervised

Which operating system are you running on?

Other (e.g., Raspbian/Raspberry Pi OS/Fedora)

Which add-on are you reporting an issue with?

deCONZ

What is the version of the add-on?

6.17.0

Steps to reproduce the issue

1.It not working at all time
2.
3.
...

System Health information

System Information

version core-2022.11.5
installation_type Home Assistant Supervised
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.10.7
os_name Linux
os_version 5.4.0-135-generic
arch x86_64
timezone Europe/Copenhagen
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 5000
Installed Version 1.28.4
Stage running
Available Repositories 1156
Downloaded Repositories 15
Home Assistant Cloud
logged_in true
subscription_expiration December 12, 2022 at 01:00
relayer_connected true
remote_enabled true
remote_connected true
alexa_enabled false
google_enabled true
remote_server eu-west-2-4.ui.nabu.casa
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Ubuntu 20.04.5 LTS
update_channel stable
supervisor_version supervisor-2022.11.2
agent_version null
docker_version 20.10.21
disk_total 109.5 GB
disk_used 34.0 GB
healthy true
supported failed to load: Unsupported
supervisor_api ok
version_api ok
installed_addons File editor (5.4.2), Samba share (10.0.0), Node-RED (13.5.3), UniFi Network Application (2.4.1), ESPHome (2022.3.1), Z-Wave JS UI (1.3.0), AdGuard Home (4.7.4), MariaDB (2.5.1), Portainer (2.16.2), Nextcloud Backup (0.17.7), deCONZ (6.17.0)
Dashboards
dashboards 1
resources 5
views 8
mode storage
Recorder
oldest_recorder_run November 29, 2022 at 09:22
current_recorder_run December 4, 2022 at 13:57
estimated_db_size 530.55 MiB
database_engine mysql
database_version 10.6.8

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

https://pastebin.com/mFsmT4zg

Additional information

No response

@QuadNL
Copy link

QuadNL commented Dec 6, 2022

Idem, all my lights and sensors are down, now.
House is unmanageable.

image

@QuadNL
Copy link

QuadNL commented Dec 6, 2022

@Brian-lub i did a temp fix.

If addon verison is 6.17 then you can go trough.
Stop the addon and open the terminal:
docker pull homeassistant/amd64-addon-deconz:6.16.0
Remove current image:
docker rmi homeassistant/amd64-addon-deconz:6.17.0
Tag the image 6.16 with version 6.17:
docker tag homeassistant/amd64-addon-deconz:6.16.0 homeassistant/amd64-addon-deconz:6.17.0

start the addon. You are now using Phoscon 2.18.02.
With above commands you use deconz addon version 6.17 in HA with the image 6.16.

@github-actions
Copy link

github-actions bot commented Jan 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jan 5, 2023
@easterapps
Copy link

Is it possible to Release the temp fix? Or is a General fix in the queue?

@Zehir
Copy link

Zehir commented Jan 25, 2023

@Brian-lub could you check with lastest version if it's fixed ?

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 24, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants