Closed MattWestb closed 9 months ago
puddly
commented
11 months ago ZHA currently bundles universal-silabs-flasher and will try to probe firmware if setup fails to detect if RCP/Thread firmware is flashed by accident to a coordinator plugged straight into ZHA.
Is the flasher addon set to autostart on boot or does it have the watchdog setting enabled?
MattWestb
commented
11 months ago Thanks for replay P. It was installed but not started and never used then i was installing it on all my "active" (Z)HA installations (all other is network NCP or RCP installations (its also network but only on local machine) but the production is running on native PI comport with Billy EZSP 6.10.X). So i was very surprised see in the portainer log that it was probing the SOC on the comport on my RP3 for all possible firmware and com speeds then ZHA have starting and have double and tipple checking that is was not activated in the addon GUI.
For my its no problem for the moment then the production system is up and running and i going to Sofia for 2 week so dont have time digging but it can being good if other user is getting the same problem or if you can triggering it and finding the reason for it to happening.
github-actions[bot]
commented
10 months ago 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.
Describe the issue you are experiencing
After updating my production system to HA 2023.12 ZHA is trying starting but is going offline and in portainer is the Silicon Labs Flasher porbing firmware after the NCP is initiated => ZHA is loosing the NCP and crashing and looping endless.
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?
Silicon Labs Flasher
What is the version of the add-on?
Current version: 0.2.0
Steps to reproduce the issue
1. 2. 3. ...
System Health information
System Information
Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Debian GNU/Linux 11 (bullseye) -- | -- update_channel | stable supervisor_version | supervisor-2023.11.6 agent_version | 1.4.1 docker_version | 24.0.7 disk_total | 58.3 GB disk_used | 13.0 GB healthy | true supported | failed to load: Unsupported supervisor_api | ok version_api | ok installed_addons | Custom deps deployment (1.3.4), Log Viewer (0.16.0), File editor (5.7.0), Matter Server (5.0.0)Dashboards
dashboards | 2 -- | -- resources | 1 views | 6 mode | storageRecorder
oldest_recorder_run | November 30, 2023 at 16:17 -- | -- current_recorder_run | December 7, 2023 at 09:03 estimated_db_size | 575.76 MiB database_engine | sqlite database_version | 3.41.2Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
No response
Additional information
My 3 RCP system is not having this problem and was upgrade OK. Also then having deleting the not started addon HA was trying starting it from cashed container with it and was needing one restart of the host system then it was away and ZHA is now starting OK.
Perhaps its somthing to do with ZHA is starting later now and the addon is not knowing ZHA is up and running on NCP coordinator (I think our Puddly is knowing how its working on the code level).