Post by wshealy on Apr 3, 2021 12:09:02 GMT -8
I am growing concerned at how hot the RPI4 in my Sky2 is getting. Outside we are see major swings (24 and wet to 70+ in 3 day) plus I have noticed radiant heating of my rack and Sky2 unit. My Sky1 needed the fan. I have one ready to mount from my Sky1 and was wondering about directions.
Secondly, after several days my systems hangs sometimes hangs. It takes a power cycle to have it reboot. Almost always the first time it gets stuck at stopping and restarting the db. The second reboot it starts and my new Netgear Orbi Pro expects a higher quality signal than it is getting (it's normal mode is to expect higher quality signal than my old router). Frequently the first round of attempts after a clean boot it fails to connect and RPi4 stops wlan0. The next boot it retries several times until Orbi gets a satisfactory connection and then it runs for days. I have a watchdog that if there was a plan could handle these reboots like Sky1. I have seen it mentioned.
** Third, is there a way to speed up boot time? From the time Sk2....py starts it takes a long time before it finds MQTT and starts scanning. For some reason it finds the rack first and then takes a while to find the indoor sensors much nearer. It seems like 20 minutes after boot before dash, blynk and WSTEM are responding and sometimes longer for WU. I have learned to check WU to know if I'm really up and sharing data. I have noticed that dash gets an updated picture long before weather data.
If I am having unstable WIFI issues I get strange results, camera fails for lack of resources, or blynk max reached. Almost always when I get a clean boot and strong WIFI I have no errors for days. I upgraded to Orbi to be ready for fiber in a month or so. But I am wondering about stronger WIFI moving it for testing next to the router doesn't solve the issue. I ended up with depending on the router by reservation to assign the right port. Add the static ip to /etc/dhcpcd.conf just caused wpa_supplicant to not login. So right now I'm just using wpa_supplicant.conf. I tried Network Manager because Docker/HomeAssistant insisted and hated it requesting 100s of connections but once it was stable it was a rock. I have disabled Docker and HA Supervisor and am using a clean SDL SDCard v15.
Oh if all my toys played together well. I never thought I would hear the day my wife complained about missing Alexa Turn On Sleep.
W
Secondly, after several days my systems hangs sometimes hangs. It takes a power cycle to have it reboot. Almost always the first time it gets stuck at stopping and restarting the db. The second reboot it starts and my new Netgear Orbi Pro expects a higher quality signal than it is getting (it's normal mode is to expect higher quality signal than my old router). Frequently the first round of attempts after a clean boot it fails to connect and RPi4 stops wlan0. The next boot it retries several times until Orbi gets a satisfactory connection and then it runs for days. I have a watchdog that if there was a plan could handle these reboots like Sky1. I have seen it mentioned.
** Third, is there a way to speed up boot time? From the time Sk2....py starts it takes a long time before it finds MQTT and starts scanning. For some reason it finds the rack first and then takes a while to find the indoor sensors much nearer. It seems like 20 minutes after boot before dash, blynk and WSTEM are responding and sometimes longer for WU. I have learned to check WU to know if I'm really up and sharing data. I have noticed that dash gets an updated picture long before weather data.
If I am having unstable WIFI issues I get strange results, camera fails for lack of resources, or blynk max reached. Almost always when I get a clean boot and strong WIFI I have no errors for days. I upgraded to Orbi to be ready for fiber in a month or so. But I am wondering about stronger WIFI moving it for testing next to the router doesn't solve the issue. I ended up with depending on the router by reservation to assign the right port. Add the static ip to /etc/dhcpcd.conf just caused wpa_supplicant to not login. So right now I'm just using wpa_supplicant.conf. I tried Network Manager because Docker/HomeAssistant insisted and hated it requesting 100s of connections but once it was stable it was a rock. I have disabled Docker and HA Supervisor and am using a clean SDL SDCard v15.
Oh if all my toys played together well. I never thought I would hear the day my wife complained about missing Alexa Turn On Sleep.
W
