Same error here running a VM in virtualbox on Ubuntu. Even if the error isn’t causing the problems I do see problems after the recent update. I will randomly lose zha or zwave functionality at some point until a reboot (or sometimes fixes itself automatically) and sometimes home assistant just becomes unresponsive entirely until a reboot. Just started yesterday.
@frenck I’m not sure it makes sense to come on a thread of a bunch of people clearly experiencing similar issues with dropouts, slow starts, or usb stick failures and say nothing to see here, move along. Even if this particular error is a red herring there seems to be something going on for those of us rhat run hass in a VM
Ok, I manage to recreate my VDI from an old load and upgraded everything that indicated an upgrade and would reboot each time (EXTREMELY time consuming). When I upgraded to HA OS 5.11, I was unable to startup. Say what you will but it was the only addition that affected me. Looking at ha> info, indicates I’m in startup. I made a backup load this time and will create a more controlled change process when applying updates. Too much time involved
Firstly thanks for your active responses - that is helpful, but xxx
This may be true, but this is the first ‘clue’ that I (we) was presented when not able to access the web front end after an update, so is an obvious starting point.
After 1-2 attempts to restart server (normally does the trick) my next efforts (given that there was, as I can understand, just a need to ‘wait it out’) I am likely to do more damage in the OS terminal screen tinkering - perhaps there should be somewhere more obvious that says I am still doing something?!..
Great suggestion, (and being honest didn’t at that point even think of it) - but I wouldn’t know what project to link the issue too. - guidance as to where you would have pointed this to would be useful, core update, HACS update?
Anyway - don’t take away that I prefer the active feedback and just sharing my perspective!
So although the error that brought us together seems to be a red herring (thanks Frenck!), I thought it best to describe how I resolved my issue, regardless of the cause… looking at you deconz…
After having a snapshot fail to restore, I went the other way and updated everything!
I unplugged my Conbee II which allowed the RPi4 to boot and gave me the webUI. I found out later that it stopped working after 10 minutes or so. So I rebooted, then immediately updated the core from the terminal, then the OS. Then deconz (through the UI - I don’t know how to do it from the CLI). Then I plugged the stick back in (while running) to see if it would detect it, and it did. 12 hours later I restarted the core (for other changes), and it’s still booted up ok.
So the versions I updated to are:
Core-2021.2.2 (from 2021.2.0 … or .1)
Supervisor-2021.02.6
Home Assistant OS 5.11 (from 5.10)
deconz 6.6.4
I see just now that there is a 6.6.5 available, but I’m going to wait a bit and see if I have any more issues with my current config.
Conbee II will no longer connect to Home Assistant, very frustrating. Using Deconz windows app. Reinstalling the HA integration works, but connection drops after that. All devices show as “unavailable”. Latest Core/Supervisor/OS/Deconz
Log Error
Logger: pydeconz.websocket
Source: /usr/local/lib/python3.8/site-packages/pydeconz/websocket.py:92
First occurred: 9:38:19 PM (5 occurrences)
Last logged: 9:39:17 PM
Unexpected error [Errno 104] Connection reset by peer
Quite a frustrating process. I’m running HA on RPI4 with no USB connections. Experienced the same problem of no access to the Web interface, and the “Bind failed” error on the console. Tried restoring different backups to no avail. The only way to restore was a complete rebuild, and restoring to ‘stable’ backup. That said, where I can usually rebuild the PI and restore within an hour, the process took me around 6 hours last night, the normal 20 min initialise waiting time was almost 3 hours. I’m now running the following versions (which seems stable for now).
Core-2021.1.3
Supervisor-2021.02.6
Home Assistant OS 5.10
Updated to 2021.2.3 and still no go for ZWave.JS.
Powered down the VM, unplugged USB Aeotech Gen5 stick and bootet up. Still same error message and addon unavailable as expected. Powered down again
Plugged in USB stick in another USB port in the pc and bootet up VM. Works fine (so far, crossing fingres).
Hope this can help others.
So the only USB item for me was a Wyze Sense hub. I removed it, including it’s integration components. I started up from HAos 4.16 backup VDI. Upgraded items one at a time and eventually got down to having only HAs 5.11 remaining. backed up and even copied my VDI. Was running stable, though it was a little slow on startups from a reboot. I rebooted 3 times to verify.
Ok, reinstalled Wyze integrations from HACS and restarted. So far so good. Plugged in Wyze Sense Hub/Bridge (the little white usb brick transmitter with blue light). Restarted per GitHub instructions, and it’s been 1hr and has not come up. Headed to lunch and hopefully it will resolve.
So I’ve spent 4 days troubleshooting. I appreciate what everyone is saying, but there’s something amiss.
I think so far we can agree on that something concerning USB devices is triggering this. For me it is starting of Deconz with the Conbee II stick.
I also have an TI CC2531 connected to the same instance which is a test for ZHA. That seems to be working fine.
In the logging I indeed saw the dtr/rts error as well.
+1 from me… deCONZ (ConBee II) in Oracle VirtualBox on Windows 10.
What I noticed, but isn’t mentioned yet: When this problem occurs, I hear the Windows USB-disconnection sound in ~2-5 second intervals (but no connection sound).
Update here…So working with the boys over at @digiblur Discord, we determined that the errors were somehow affecting “the recorder”. Removed the Wyze USB, deleted the home-assistant.log and a home-assistant_v2.log, and HA restarted in less than 3min. Shocked me how fast. So the error we see on the VM is still there. Plugged the Wyze USB bridge back in and it came up, but all my Wyze sensors will not come up. I don’t think those are related, as the Wyze sensor problems are a known PITA. As it stands, I am up to date on my loads and at least working…very fast I might add.
I too am having this issue running on a raspberry pi 3b+. it’s taken my system completely offline. multiple restarts and it never comes back up. since I can’t get into the web UI I’m kinda of at a loss on what to do.
