I’ve been experiencing repeating issues in #HomeAssistant with devices not responding. It’s been manifesting in the system log as an error:
cp210x ttyUSB0: failed set request 0x12 status: -110
That’s Zigbee dongle. The workaround was to reboot the system, but I’ve changed it’s USB port and it seems to be gone.
The system is #RaspbianOS on #Raspberry Pi5. Pi is powered via PoE and it should have sufficient power budget, though it’s running of an nvme.2 and with USB hard drive, so who knows…
@WestkirchenAndi Ich nutze einen Raspberry Pi 4 mit 8 GB RAM mit externer SSD über USB angeschlossen. Das Ganze läuft mit Raspbian OS und komplett verschlüsselter Platte, inklusive Remote Passworteingabe per SSH. HomeAssistant läuft über docker compose.
Ah... Let's get to it shall we?!?
Bash and Nano on the good ole RaspbianOS!
****ferris Buller plays (Oh Yeah - Yello)
So... Let's begin the updates shall we?!
Updating RaspbianOS. Time to apply all that was studied these prior moons.
Side note: Cmatrix always gets me in the mood to code.
Ok this is incorrect. I didn't realize that Waveshare has two different versions of their dtoverlays, one for legacy versions of RaspbianOS and one for “new" versions. Obviously, if I try to load the wrong version, the OS won't initialize the LCD properly.
When I load the Waveshare dtoverlays and modify the config.txt and cmdline.txt *after* the first boot of a fresh RaspbianOS install, the DPI LCD is not used.
If I load the Waveshare dtoverlays onto the SD card and modify the config.txt and cmdline.txt *before* the first boot of a fresh system, everything works as expected.
Is there some intermediate step happening on first boot?
So, I had to use #raspbianos to get the v3 camera module working on my pi3A+. This feels like a huge downgrade from my usual #dietpi install. Once everything was said and done with the camera working, I finally disconnected it from my TV to run headless. A lot of frustration later, I find out that VNC isn't working properly with the new #bookworm release.
