Skyconnect broken after reboot

[dennisbrouwer91]

The problem

Got a SkyConnect USB stick last week and configured it with one temperature sensor, worked great, until an update of Home-Assistant OS this morning to OS 11.2.

What version of Home Assistant Core has the issue?

core-2023.11.3

What was the last working version of Home Assistant Core?

OS 11.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

SkyConnect Zigbee

Link to integration documentation on our website

No response

Diagnostics information

I removed the entire SkyConnect zigbee config this morning after it failed to try and re-add it, but that shows this in the logs :

2023-12-05 12:28:07.132 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.CPC at 115200 baud 2023-12-05 12:28:11.449 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.CPC at 230400 baud 2023-12-05 12:28:15.765 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.EZSP at 115200 baud 2023-12-05 12:28:17.007 INFO (MainThread) [universal_silabs_flasher.flasher] Detected ApplicationType.EZSP, version '7.1.1.0 build 273' (7.1.1.0.273) at 115200 baudrate (bootloader baudrate None)

2023-12-05 12:32:08.049 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.read_parameter' command with seq id '0x02' 2023-12-05 12:32:11.054 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2023-12-05 12:32:13.062 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.CPC at 460800 baud

And because of the above errors i can re-add it to Home-Assistant

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (homeassistant_sky_connect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homeassistant_sky_connect` 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 homeassistant_sky_connect` 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)}}

---

homeassistant_sky_connect documentation homeassistant_sky_connect source _{^{(message by IssueLinks)}}

[dennisbrouwer91]

Whatever i do, i can't re-add the SkyConnect USB device :

2023-12-05 20:28:08.922 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2023-12-05 20:28:10.929 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.CPC at 460800 baud 2023-12-05 20:28:15.271 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.CPC at 115200 baud 2023-12-05 20:28:19.588 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.CPC at 230400 baud 2023-12-05 20:28:23.903 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.EZSP at 115200 baud 2023-12-05 20:28:28.911 INFO (MainThread) [universal_silabs_flasher.flasher] Probing ApplicationType.SPINEL at 460800 baud

[104mapo]

I think I am experiencing the same issue. So far my solution is to disconnect the SkyConnect USB device before performing updates or reboots of my Raspi. After the reboot I put it back in and only restart HomeAssistant. Without that none of my other to USB devices (Jeelink for Lacrosse and HmIP-RFUSB for HomematicIP) work after the reboot.

Once the SkyConnect stick is broken. I can do the same procedure (unplug, reboot, plug, restart). And use the ZHA repair function to fix the Zigbee network.

[issue-triage-workflows[bot]]

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.