I rolled back to 0.102.3, but it is still HassOS 3.10.
- State history has returned (had to reset ha db too)
- plugins all started on their own this time
- node-red started, but is having trouble talking HA again.
Have to see how things go over the weekend. Time in Node-Red seems to be correct now, but without HA connection…this might have to be another reinstall, but I suspect it won’t be as involved this time.
I think HA has reached a point where it is necessary to have a test device.
Perhaps a feature could be added similar to enterprise networking hardware. Keep the current and upgrade version in parallel. Presuming the current version (for me 0.102.3) is working. When time to upgrade, the “working” version is not wiped or overwritten, but the new version is loaded next to the current (0.105.3), Ha restarted using new version for test/validation. Once complete, if everything is successful (user validated), update and make it the “operational” version, if not, then simply flip the switch back, and restart.
Yes, I understand that might be considered a wipe & restore after HA downgrade, but that took well over 30-40 for me on rPi 3 B+. Using the method I suggest above, could be minutes.
Just some thoughts. Looking forward to testing 0.105.3+ and hoping some of the issues get resolved.