Hi all,
Suddenly today I was unable to reach my home assistant from outside. I was suspecting network issues, but when arriving home, automations worked…
so here is the deal :
- Hassio is up and running. Tried restarting, but unfortunately unable to access lovelace frontend.
- Addon Samba is loaded, but not the SSH server addon, so I am not not able to Putty or SFTP into the HASSIO RPI, very strange that it seems that addons are loaded partially (or could there be something else)?
As I can access the home assistant log, but there is only an error of not being able to reach the HUE Bridge… rest seems fully normal. I doubt the bridge is the issue…
2019-03-06 21:43:31 WARNING (MainThread) [homeassistant.loader] You are using a custom component for zigbee2mqtt_networkmap which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-03-06 21:43:31 WARNING (MainThread) [homeassistant.components.mqtt] Data in your config entry is going to override your configuration.yaml: {'broker': '192.168.1.52', 'discovery': True, 'password': 'XXXXXX', 'port': 1883, 'username': 'XXXXXX'}
2019-03-06 21:43:41 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
2019-03-06 21:43:45 WARNING (Recorder) [homeassistant.components.recorder.migration] Database is about to upgrade. Schema version: None
2019-03-06 21:43:54 WARNING (MainThread) [homeassistant.loader] You are using a custom component for life360.device_tracker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-03-06 21:44:04 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds.
2019-03-06 21:44:04 WARNING (MainThread) [homeassistant.setup] Setup of homekit is taking over 10 seconds.
2019-03-06 21:44:04 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 192.168.1.57
2019-03-06 21:44:05 WARNING (MainThread) [homeassistant.config_entries] Config entry for hue not ready yet. Retrying in 5 seconds.
2019-03-06 21:44:05 WARNING (MainThread) [homeassistant.setup] Setup of apple_tv is taking over 10 seconds.
2019-03-06 21:44:05 WARNING (MainThread) [homeassistant.setup] Setup of timer is taking over 10 seconds.
2019-03-06 21:44:05 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.
2019-03-06 21:44:05 WARNING (MainThread) [homeassistant.components.weather] Setup of platform darksky is taking over 10 seconds.
2019-03-06 21:44:47 WARNING (MainThread) [homeassistant.setup] Setup of script is taking over 10 seconds.
2019-03-06 21:44:47 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2019-03-06 21:44:47 WARNING (MainThread) [homeassistant.setup] Setup of zeroconf is taking over 10 seconds.
2019-03-06 21:44:47 WARNING (MainThread) [homeassistant.setup] Setup of plant is taking over 10 seconds.
2019-03-06 21:44:47 WARNING (MainThread) [homeassistant.components.vacuum] Setup of platform roomba is taking over 10 seconds.
2019-03-06 21:44:47 WARNING (MainThread) [homeassistant.components.camera] Setup of platform mjpeg is taking over 10 seconds.
2019-03-06 21:45:04 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_temperature is taking over 10 seconds
2019-03-06 21:45:04 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_moisture is taking over 10 seconds
2019-03-06 21:45:05 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_light_intensity is taking over 10 seconds
2019-03-06 21:45:05 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_conductivity is taking over 10 seconds
2019-03-06 21:45:05 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_battery is taking over 10 seconds
2019-03-06 21:45:05 ERROR (MainThread) [homeassistant.components.hue.light] Unable to reach bridge 192.168.1.57 ()
Does anyone have a clue what could be wrong / done?
Thanks!