Closed Filhgd closed 5 years ago
I don’t get this. This isn’t solved at all.
I experienced thsi with my bluetooth tracker. It sometimes does not load:
2019-01-08 12:02:39 ERROR (MainThread) [homeassistant.loader] Unable to find component device_tracker.bluetooth_tracker#
There might be other components/platforms that causes this. But asuswrt had this problem, I also had similar problems when my isp had issues.
Hi, the problem isn't solve, I got problems with
Home Assistant release with the issue: 0.83.2 and 0.82.0
Last working Home Assistant release (if known): not a single one. Having these problems since the beginning.
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
Component/platform: Raspberry Pi 3 Model B
Description of problem: I'm having these problems since a year right now and I can't find the solution. I have a home assistant client running trough Hass.io on my raspberry Pi with the following components enabled:
I'm very happy with home assistant and it is wonderful software to build your own smart home. However there are always components who aren't working after a reboot. In some home assistant versions it's worse than in others. This last one is again terrible so I reloaded a snapshot with HA 0.82.0 which also has these problems but less serious.
When i reboot my system one of the following components isn't loading and giving errors:
It is a very strange problem because every time I reboot HA, one of the components work while the other two don't load or partially load (in case of tado). When I do a reboot of the hass.io host system (and I am very lucky or the stars align or something) then everything loads like it should. I have a lot of errors during booting but I don't know how to handle them. I'm getting desperate because I would really love to have a stable system. Maybe the raspberry Pi isn't heavy enough to handle everything? I don't know anymore.
Could you guys please take a look at my setup because I suppose that other users are also having the same problems if they start with expanding their system and building more complex automations.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: Errors during booting