I haven’t mentioned (until my response to @freshcoast’s question ) that I also have a Wyze Hub, that is still working. It’s located at /dev/hidraw0. Notice it is not listed in the Hardware list.
OK, I’m sorry but I’ve reached the end of my technical knowledge on how to continue troubleshooting this.
I don’t use a supervised version in production but just as a test platform. And I’m on the ~latest versions of everything and my Aeotech Z Stick is showing up just fine along with all of my other USB devices.
And I use docker for pretty much everything on my HA machine but I’ve never tried to modify the supervisor docker run command to explicitly add any devices to the path (but I have needed to do that with my production HA Container version so the command is understood by me). I just ran the Supervised install script and it found everything automatically. That’s what I meant above when I said I have seen that docker run command for the supervisor - that I’ve never seen anyone actually modify their run command to pass a USB device.
Where did you get the idea that you needed to modify that docker command? Because I don’t remember that ever being recommended in the docs or forum anywhere.
The modification of the hassio-supervisor comes from my own use and knowledge of docker. Prior to my retirement a couple years ago, I had managed a WISP ISP Data Center for 12 years. I worked extensively with converting bare metal servers/services to microservices and HA (High Availability) for any and all basic network services (DNS, DHCP, NTP, Mail, Radius, Sandvine Bandwidth Mgmt/Motorola
& Huawei WiMAX, ZTE LTE and Unlicensed Technology Provisioning, Tool Sets for T1/T2 Support and Management, Network Monitoring, etc.), to give you an idea of the range of docker use application.
Circling back around to your description of your production environment. I don’t have a specific love/desire/need to run supervised. In fact I would prefer not to as I don’t love the control it has over the host. But I seemed to understand that it was the necessary “evil” in order to benefit from add-ons.
Perhaps I was unclear on that point. I’m well versed in Docker Containerization, it’s Networking and Volume management. Given that, you mentioned you don’t use supervised but
“…use docker for pretty much everything on my HA machine”
So do you spin up docker containers for the add-ons you use, i.e. Node-Red, ESPHome, etc?
Also, your System Health seems to indicate you are running supervised. Can you clear up my confusion?
I too, but doing so with the “Home Assistant Google Drive Backup” Add-on. I wasn’t aware it would backup/restore the host docker hassio-supervisor startup script. Or are you speaking about a backup from outside the Docker Container?
Hmm, very interesting. I’ll investigate. Having said that, it puts anyone who reverts back to an installed core with a security issue with the recommendation to disable all add-ons. Now, some may have a better idea as to the exposure risk of one add-on over the other. I don’t have that information.
That’s interesting. Up until I looked today, based on your comment, HA’s website stated 2021.1.4, or at least I would swear by it. And now the advisory states 2021.1.3. What gives? So rhetorical question, why is it that my install stated to update the 2021.1.4. See my other post prior to my upgrade and initiating this thread which shows a screenshot of said version.
As I said I don’t run Supervised for my production system. I just run HA Container and I run my own non-add-on containers for everything. Well, except for the NUT-UPSD container - I run that from the Supervised HA as an add-on since I couldn’t ever seem to get a non-add-on container to work. It’s literally the only reason I still even have the Supervised HA version hanging around (I really need to get that running separately…).
If you are well versed in Docker then I would just switch to HA Container and get away from Supervised. And for the exact reasons you mentioned. There is really no benefit to you to run that install type. Even snapshots aren’t important if you have a good backup plan.
THe only reason I posted the pics of my supervised version was to show you that my zwave and other USB devices actually showed up there so it isn’t the “supervisor install” that is causing your issues. There has to be something else going on. And since you have been modifying the Supervisor Docker environment the that might be the likely cause. ??
The UDEV rules there I were definitely not for use with the Supervised version. There was no such thing in 2016.
the advisory always stated that you need to be running at least 2021.1.3 for the security patch to be in place.
The screenshot from above was just the system telling you that there was an update available. Not that it was a recommended update for the security patch.
After weeks of trying to resolve my broken ZWave after the update to 2021.2.1, I have yet to sort it out,
ZWave still broken. So it looks like my next step is to do a fresh install!?!?
So my question is, what Zwave hub would you recommend? Still the Aeotek? Nortek GoControl? Or other?
I have the Aeotec as my main production controller since I bought that first when I got started with HA. I’ve never had any problems in three years of using it.
Then later when I decided to get some zigbee stuff I bought the Nortek stick.
But now I’m using the zwave portion of the Nortek stick for testing the zwavejs system. And it’s working fine too for that.
