0.40.0 Setup of [X] is taking over 10 seconds and slow startup

Configuration
21

I’m on 0.52.1 but am still experiencing these messages.
Specifically on harmony.remote and my Sonos playbar.
My log is full with it.
Any idea anyone?

22

did you manage to understand what the hell is it. I have same problem since two days now. WIth 0.54

23

@anon35356645 - nope. It’s been consistent since 0.40.0:

2017-10-05 18:50:15 WARNING (MainThread) [homeassistant.setup] Setup of binary_sensor is taking over 10 seconds.
2017-10-05 18:50:16 WARNING (MainThread) [homeassistant.setup] Setup of sensor is taking over 10 seconds.
2017-10-05 18:50:16 WARNING (MainThread) [homeassistant.setup] Setup of media_player is taking over 10 seconds.
2017-10-05 18:50:17 WARNING (MainThread) [homeassistant.setup] Setup of switch is taking over 10 seconds.
2017-10-05 18:50:17 WARNING (MainThread) [homeassistant.setup] Setup of cover is taking over 10 seconds.
2017-10-05 18:50:17 WARNING (MainThread) [homeassistant.setup] Setup of light is taking over 10 seconds.
2017-10-05 18:50:18 WARNING (MainThread) [homeassistant.components.calendar] Setup of platform google is taking over 10 seconds.
2017-10-05 18:50:26 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of platform iss is taking over 10 seconds.
2017-10-05 18:50:27 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform bitcoin is taking over 10 seconds.
2017-10-05 18:50:27 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform ups is taking over 10 seconds.
2017-10-05 18:50:29 WARNING (MainThread) [homeassistant.components.cover] Setup of platform myq is taking over 10 seconds.

Doesn’t seem to actually be a problem though so I haven’t worried about it.

24

to me is a problem sinci it continues endlessy with those messages, and HASSio is not booting

25

Oh that sounds like another issue then. I’m not using HASSio and those messages shouldn’t cause it not to boot.

26

I just move to HASSIO out of desperation, the problem was also in hassbian

27

Don’t use hassbian either so can’t comment there. Random guess though you have an IO problem. Have you tried a different memory card in your pi?

28

yes first thing I did.
I run hassio log I noticed this. I put now API password in configuration… but how to change inside HASIO if I can’t start it

17-10-05 23:00:54 INFO (MainThread) [hassio.addons] Startup application run 1 addons
17-10-05 23:00:54 ERROR (SyncWorker_19) [hassio.addons.addon] Addon core_configurator have wrong options → Missing required option ‘password’… Got {‘homeassistant_api’: ‘http://homeassistant:8123/api’, ‘homeassistant_password’: ‘’, ‘username’: ‘admin’, ‘password’: None, ‘certfile’: ‘fullchain.pem’, ‘keyfile’: ‘privkey.pem’, ‘ssl’: False, ‘allowed_networks’: [‘192.168.0.0/16’], ‘banned_ips’: [‘8.8.8.8’], ‘ignore_pattern’: [‘pycache’]}
17-10-05 23:06:33 INFO (SyncWorker_17) [hassio.dock.interface] Restart homeassistant/raspberrypi3-homeassistant

29

Not sure mate. I’d start your own thread about it.

1 Like
30

now it starts, but it stops after a minute …

31

Is it stopping or just using up every available resource? Also why are you banning 8.8.8.8? It’s just the Google DNS server.

32

how to check your first question?

I have not banned anything, its a clean HASSIO installation

33

17-10-05 23:00:54 ERROR (SyncWorker_19) [hassio.addons.addon] Addon core_configurator have wrong options → Missing required option ‘password’… Got {‘homeassistant_api’: ‘http://homeassistant:8123/api’, ‘homeassistant_password’: ‘’, ‘username’: ‘admin’, ‘password’: None, ‘certfile’: ‘fullchain.pem’, ‘keyfile’: ‘privkey.pem’, ‘ssl’: False, ‘allowed_networks’: [‘192.168.0.0/16’], ‘banned_ips’: [‘8.8.8.8’], ‘ignore_pattern’: [‘pycache’]}
17-10-05 23:06:33 INFO (SyncWorker_17) [hassio.dock.interface] Restart homeassistant/raspberrypi3-homeassistant

a simple top from the shell will tell you

34

What is this?
@forsquirel

Ok it was the hassio configuraror not configured. I uninstalled it.

Anyway after a few minutes hassio stops (so the block was not the error above or at least not the only cause) ,
how to troubleshoot?

35

if the log file isn’t helping anything cut it down to basics… start with minimal and run. if all is good add another component until you find the culprit.