I think it is could be possible to access and change the sources if you’re a docker wizz, however it’s not straight forward otherwise.
I did not have the idea of creating custom components. Maybe this would have been better. Because now I cannot update.
What bugs did you fix, can you tell me an example?
Home assistant is complicated, upgrades often contain breaking changes. I have found it essential to use a good upgrade/rollback strategy.
Python VE’s, docker, or even a separate VM provide you the ability to roll back to different extents so you can continue to have a working house when you are not working through upgrade issues.
I am currently using docker and backing my configs up using Git. But I am considering just moving it all to it’s own VM due to recent changes in the docker requirements (root user) and more reliance on integrations and the db.
Custom components are better because you don’t break the core of HA and you can update freely.
My HA sits in .homeassistant. If I copy it to .homeassistant2, I can install new version. If I want to go back, I just switch the directories. Keeping it simple and smart…
But then all your changes to the core files are lost, right?
Yes of course…
- in visualizations, % humidity and % disk-volume-used are put into one graph because its both percent.
- zigbee smart plugs show only 1/10 of the power consumption
- if my NAS is down, there is a crash in the sensor
- arguments for ZHA device calls are wrong
- emulated hue cannot switch on a light with a color
You know what’s smarter and simpler?
Containerization
2 Likes