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
72.8k stars 30.5k forks source link

Receive Errno 2 after restarte of HA< need 2/3 trieds to get rid of it... #111632

Closed Timsche2210 closed 4 months ago

Timsche2210 commented 8 months ago

The problem

after each update or restarte the following failure appeares: image

I need to shut down the VM at the Syno and after 2-3 restarts it is working again

What version of Home Assistant Core has the issue?

core-2024.2.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

ZHA

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

used hardware: Synology DS220+ ConBee II Stick

home-assistant[bot] commented 8 months ago

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `zha` 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 zha` 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)


zha documentation zha source (message by IssueLinks)

PiLoT650 commented 8 months ago

Same for me - after last update to 2024.2.4 and deconz software my conbee and zigbee are offline. Under 2.4 i got i working after couple of restarts. Did to 2024.2.5 today - trying everything - it is not working anymore - even with unplug or restarts. Is there any rock solid zigbee solution for hA ? different stick / zigbee2mqtt?

puddly commented 8 months ago

If the Conbee is physically missing, there is nothing that can be done. ZHA expects the serial port to exist. If your VM or hypervisor has issues with the Conbee and USB passthrough, you will need to find a workaround, as it's a layer above HA OS.

Timsche2210 commented 8 months ago

I thought maybe my Conbee 2 stick is broken - so I bought Conbee 3. There were some troubles with the change from 2 to 3 in HA, so I decided to link all devices again with the system. Right now it is working w/o problems, I will update this post if the next update is avialable & system restart was initiated

puddly commented 8 months ago

The Conbee 2 is a little strange in that it manages its own USB interface and also fully resets (i.e. "unplugs" itself USB-wise) if nothing communicates with it for 30s. If your hypervisor has issues with hot plugging USB, you'll have problems with it.

PiLoT650 commented 7 months ago

Maybe try this (Solution form Jesper) https://community.home-assistant.io/t/zha-conbee-2-not-working-after-update-2024-2-5/697336

It did work for me - but i really had to remove the conbee 2 - and shutdown the pi - disconnect energy- start up again - connect conbee 2 - reconfigure and it was working again. All the restarts before - also of the pi did not solve the problem.

60% of my Zigbees are back - aqara door sensors and temperture sensors are still offline. Will try skyconnect now.

Timsche2210 commented 7 months ago

currently the ConBee 3 stick is running w/o any issues... Maybe @puddly is right and my Synology VM has the problem with the 30s communication...?

issue-triage-workflows[bot] commented 4 months 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.