my monitoring tool reports that Home Asssistant has gone down twice, once yesterday and once again today. I checked yesterday the parameters we discussed above, and the output that I got was 0x0, however, after today’s reboot, I see `
It looks like my RPI 3B+ has hit a soft temp limit but this seems to not have anything to do with the undervoltage thing discussed a few days back. I wonder if I should buy a new fan…
0xd0000
I really don’t know what to do in order to recover stability. I’m a bit lost. Would you be able to guide me on further fixing my environment? After reviewing the HA logs I see several errors as reported in this issue (opened by me): https://github.com/home-assistant/core/issues/41233
Upon inspecting the HA logs I see that HA has rebooted several times (not only twice as reported by my monitoring tool) and in most cases I believe there is a correlation with this issue https://github.com/home-assistant/core/issues/41233
If it helps, I sometimes see that the NodeRed add-on has also hung and not even the watchdog seems to be triggering an add-on restart.
I’m at a loss. If somebody could shed some light on how to move forward.
thanks a million!
Of course I’d be willing to help! I’ll read through the links you sent and see what ideas I can come up with.
Regarding your fan, honestly, I’d just spend a little extra and get a rPi4B 2GB (or 4GB) and transfer your instance there. There have been A LOT of improvements between the rPi3 and rPi4 including a firmware update that reduces the heat output on the rPi4.
Give me a bit to do some light reading on your links.
Thanks a million @code-in-progress!! Just by trying you are really helping me!! Thank you!
On the RPI4 I’m just wondering if I should not rather rethink my whole setup. I own an ancient Qnap NAS from 2008 (unable to do containers) and I’ve so far added an external SSD to my RPI3 along with an external powered USB hub to my RPI3B+… with so many peripherals it starts to feel like a Christmas Tree…
It is really weird what is going on. After adding the powered USB Hub, my environment worked just fine (at least the monitoring tool did not tell otherwise) for 6 or 8 days, but then three days ago things changed a lot. It has become very unreliable. I just plugged the plug hoping it gets a bit cooler, just to see if that matters at all.
Sorry about the long delay again. Work has been a nightmare the past few days. sigh
To be completely honest, yeah, you might want to.
On my rPis, I only have one that I use a SSD with; All the others (I think I have 9 running now?) use Sandisk USB3 flash drives for boot and storage and they run great. BUT, I also have so many because these are still single board computers and resources, no matter how big they seem, still have constraints with power and traffic across the bus. So, I split apps and services across multiple rPis. My server cabinet ALWAYS looks like a Christmas Tree.
With your issues coming back, I wonder if the rPi3s that you have are just starting to show their age perhaps? It’s entirely possible that due to high heat/weird voltage fluctuations, there could be a chip on the board that is starting to become faulty.
Another thing to look at is to see if you have an old laptop laying around (or one you can buy cheap) and transfer your install to that. The reason being that the motherboard on a laptop supplies much more power to the USB bus, plus, you also get a built-in battery backup. I just recently spun up an HA instance on an old HP laptop from 8 years ago and it runs great.
Yeah, and making the right decision moving forward is also a mess. As I said, I own an old QNAP NAS which is unable to do containers. I could invest in a modern NAS able to run containers and then consolidate HA there along with some other services running today in one other RPI (dhcp, openvpn, etc.). OR I could keep my current NAS as a mundane network file server and add a NUC in replacement of my RPIs.
I just hate to be forced to rethink my environment due to this weird behaviour, specially when I have not yet pinpointed what the root cause really is. My gut feeling however points me to some hardware issue but I would like to narrow it down a bit more because maybe I’m blaming the RPI when the culprit may be the SSD, or God knows what…
PS: 24h of continuous operation after plugging back the plug. I wonder if my problem comes from a combination of multiple factors like the github issue and some other thing…
A few months back I switched to an SSD USB drive from an SD card. In order to do that I had to run HASS.IO 5.1 dev deployment. For months I had the alert saying to upload it to version 4.1. It seems that version 5.x has been released. I would like to know the steps to take to switch from my development deployment to a final release deployment. Any help is appreciated. Thanks,
Hello, after 5 months from the latest crash, it is time to reinstall HA again.
I am HA running inside Docker on an 120 SSD with the old SD booting Rpi4 1Gb.
Yesterday I noticed my HA container has 80 Gb!!! So I did a backup and then a Wipe Restore.
Since then system is very slow or unresponsive.
If I can’t fix it I would like to update to the latest USB boot without any SD, and then still to have Docker and HA so I can restore my latest backup.
Can anybody point to a guide for the USB booting for Rpi4 ?
@code-in-progress and the rest. 1 full week without any glitch. Disabling influxdb and grafana seems to have stabilized the environment. All of this has happened while the NUC was being delivered. Now I have a NUC that is gathering dust because so far the RPI has managed to hold the posture well. I’m considering returning the NUC right now
I have been able to boot via SSD on my RPi 4 but when I restore my snapshot the system never boots back up again. Are we able to restore snapshots from version 4 OS when using version 5 dev 64bit on the SSD or do I need to start from scratch again?
edit: I can SSH in but i still can’t access it from a webpage. Here is the Supervisor log from Putty From the point I did a restore. Nothing stands out to me.
20-11-07 19:25:16 INFO (MainThread) [supervisor.snapshots] Partial-Restore 80eb314d start
20-11-07 19:25:17 INFO (MainThread) [supervisor.snapshots] Restoring 80eb314d Docker Config
20-11-07 19:25:17 INFO (SyncWorker_6) [supervisor.docker.interface] Stopping homeassistant application
20-11-07 19:26:18 INFO (MainThread) [supervisor.snapshots] Restoring 80eb314d folders
20-11-07 19:26:18 INFO (SyncWorker_2) [supervisor.snapshots.snapshot] Restore folder homeassistant
20-11-07 19:26:24 INFO (SyncWorker_2) [supervisor.snapshots.snapshot] Restore folder homeassistant done
20-11-07 19:26:24 INFO (MainThread) [supervisor.snapshots] Restoring 80eb314d Repositories
20-11-07 19:26:24 INFO (MainThread) [supervisor.store] Loading add-ons from store: 67 all - 0 new - 0 remove
20-11-07 19:26:24 INFO (MainThread) [supervisor.snapshots] Restoring 80eb314d old add-ons
20-11-07 19:26:24 INFO (MainThread) [supervisor.addons.addon] Restore config for addon a0d7b954_adb
20-11-07 19:26:24 INFO (MainThread) [supervisor.addons.addon] Restore/Install of image for addon a0d7b954_adb
20-11-07 19:26:24 INFO (SyncWorker_6) [supervisor.docker.interface] Downloading docker image hassioaddons/adb-aarch64 with tag 0.6.3.
20-11-07 19:26:37 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon a0d7b954_adb
20-11-07 19:26:39 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on hassioaddons/adb-aarch64 with version 0.6.3
20-11-07 19:26:39 INFO (MainThread) [supervisor.addons] Detect new Add-on after restore a0d7b954_adb
20-11-07 19:26:39 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_adb
20-11-07 19:26:51 INFO (MainThread) [supervisor.addons.addon] Restore config for addon a0d7b954_adguard
20-11-07 19:26:51 INFO (MainThread) [supervisor.addons.addon] Restore/Install of image for addon a0d7b954_adguard
20-11-07 19:26:51 INFO (SyncWorker_6) [supervisor.docker.interface] Downloading docker image hassioaddons/adguard-aarch64 with tag 2.6.0.
20-11-07 19:26:58 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon a0d7b954_adguard
20-11-07 19:27:04 INFO (SyncWorker_6) [supervisor.docker.addon] Starting Docker add-on hassioaddons/adguard-aarch64 with version 2.6.0
20-11-07 19:27:04 INFO (MainThread) [supervisor.addons] Detect new Add-on after restore a0d7b954_adguard
20-11-07 19:27:05 INFO (MainThread) [supervisor.addons.addon] Restore config for addon core_mosquitto
20-11-07 19:27:05 INFO (MainThread) [supervisor.addons.addon] Restore/Install of image for addon core_mosquitto
20-11-07 19:27:05 INFO (SyncWorker_6) [supervisor.docker.interface] Downloading docker image homeassistant/aarch64-addon-mosquitto with tag 5.1.
20-11-07 19:27:06 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_adguard
20-11-07 19:27:08 INFO (MainThread) [supervisor.discovery] Sending discovery to Home Assistant adguard from a0d7b954_adguard
20-11-07 19:27:08 INFO (MainThread) [supervisor.discovery] Discovery 31256919221247eea6be43374bde3235 message ignore
20-11-07 19:27:10 INFO (MainThread) [supervisor.api.security] /dns/info access from a0d7b954_adguard
20-11-07 19:27:13 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon core_mosquitto
20-11-07 19:27:14 INFO (SyncWorker_6) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-mosquitto with version 5.1
20-11-07 19:27:14 INFO (MainThread) [supervisor.addons] Detect new Add-on after restore core_mosquitto
20-11-07 19:27:14 INFO (MainThread) [supervisor.addons.addon] Restore config for addon a0d7b954_nodered
20-11-07 19:27:14 INFO (MainThread) [supervisor.addons.addon] Restore/Install of image for addon a0d7b954_nodered
20-11-07 19:27:14 INFO (SyncWorker_5) [supervisor.docker.interface] Downloading docker image hassioaddons/node-red-aarch64 with tag 7.2.7.
20-11-07 19:27:16 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
20-11-07 19:27:16 INFO (MainThread) [supervisor.discovery] Sending discovery to Home Assistant mqtt from core_mosquitto
20-11-07 19:27:16 INFO (MainThread) [supervisor.discovery] Discovery ba9640f78de243bb931bf6e0b07de7c1 message ignore
20-11-07 19:27:46 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon a0d7b954_nodered
20-11-07 19:27:47 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on hassioaddons/node-red-aarch64 with version 7.2.7
20-11-07 19:27:47 INFO (MainThread) [supervisor.addons] Detect new Add-on after restore a0d7b954_nodered
20-11-07 19:27:48 INFO (MainThread) [supervisor.addons.addon] Restore config for addon a0d7b954_ssh
20-11-07 19:27:48 INFO (MainThread) [supervisor.addons.addon] Restore/Install of image for addon a0d7b954_ssh
20-11-07 19:27:48 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image hassioaddons/ssh-aarch64 with tag 7.7.0.
20-11-07 19:27:49 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_nodered
20-11-07 19:27:52 INFO (MainThread) [supervisor.api.security] /dns/info access from a0d7b954_nodered
20-11-07 19:28:25 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon a0d7b954_ssh
20-11-07 19:28:25 WARNING (SyncWorker_0) [supervisor.docker.addon] SSH & Web Terminal running with disabled protected mode!
20-11-07 19:28:26 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on hassioaddons/ssh-aarch64 with version 7.7.0
20-11-07 19:28:26 INFO (MainThread) [supervisor.addons] Detect new Add-on after restore a0d7b954_ssh
20-11-07 19:28:26 INFO (MainThread) [supervisor.addons.addon] Restore config for addon core_samba
20-11-07 19:28:26 INFO (MainThread) [supervisor.addons.addon] Restore/Install of image for addon core_samba
20-11-07 19:28:26 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image homeassistant/aarch64-addon-samba with tag 9.3.0.
20-11-07 19:28:27 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_ssh
20-11-07 19:28:31 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon core_samba
20-11-07 19:28:32 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-samba with version 9.3.0
20-11-07 19:28:32 INFO (MainThread) [supervisor.addons] Detect new Add-on after restore core_samba
20-11-07 19:28:33 INFO (MainThread) [supervisor.addons.addon] Restore config for addon a0d7b954_tautulli
20-11-07 19:28:33 INFO (MainThread) [supervisor.addons.addon] Restore/Install of image for addon a0d7b954_tautulli
20-11-07 19:28:33 INFO (SyncWorker_6) [supervisor.docker.interface] Downloading docker image hassioaddons/tautulli with tag 1.5.1.
20-11-07 19:28:55 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon a0d7b954_tautulli
20-11-07 19:28:57 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on hassioaddons/tautulli with version 1.5.1
20-11-07 19:28:57 INFO (MainThread) [supervisor.addons] Detect new Add-on after restore a0d7b954_tautulli
20-11-07 19:28:57 INFO (SyncWorker_1) [supervisor.docker.interface] Starting homeassistant
20-11-07 19:28:57 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
20-11-07 19:28:59 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_tautulli
20-11-07 19:30:44 INFO (MainThread) [supervisor.api.security] /supervisor/logs access from a0d7b954_ssh
I went from microsd 32 bit HA version 4 to ssd 64bit HA version 5.3 bega and restored the snapshot. Been running smooth for the last 4 days now (that’s when I made the switch). So 0 issues on my end.
The reason I asked is that the new version supports snapshot restore in onboarding. I just don’t understand how to get the file on to my pi . It would make it much easier as you install HA and restore. No other programs would need to be installed and setup.
I have tried via the onboarding and the Google Drive Snapshot Backup plugin. For onboarding i just downloaded my snapshot for Google Drive and uploaded it.
Did you wait a long, yes really long time? Or didn’t it even start?
Two weeks ago I saved my last snapshot in 4.x 32bit from my Pi 4 and started with 5.4 64bit on a SSD in my Pi 4. There I selected the snapshot at onboarding and waited 1 hour or so, and then it was ready. The only thing I had to do was to delete the old database (home-assistant_v2.db), as this was not working.
And I had to reenable I2C, as the integration for the Argon One case (really the best case for the Pi 4) uses it.
There are two options when using the snapshot at onboarding. I don‘t remeber the correct names. One is to reset all and use the snapshot and the other is without reset all. I used the one without reset all, because it was a fresh installation.
