Realistic start time?

Configuration
1

I’m just curious about what a realistic start time for the HA service is. I hate making changes or even trying to improve anything outside of automations.

Once again I’ve been trying to get my service up and running for over 2 1/2 hours. Right now I’m 17 minutes into a service start and I’m still waiting. Nothing has changed. No updates done. No new component added. Just trying to restart.

EDIT: So I thought that post 14 was my solution. Seems NMAP was devouring resources for no reason. Literally causing the system to HALT to a stop. I’ve removed NMAP and no have zero issues.

2

How many components are you using (info page)?

What hardware are you running HA on?

eg I have 95 loaded components, about 70 remote devices, 300KB of yaml files and my raspi 3 restarts in about 2 to 5 minutes.

3

I would tell you but it’s not up yet. Before .8x I could restart in a matter of minutes… now I literally have to sit at the prompt restarting every few minutes until it starts again.

I don’t have that many physical devices and I probably have less than 50 components

4

Anything significant in the log?

If you are using a pi I think you can connect a display to check the system messages.

5

nothing other than Setup of platform xxxxx is taking over 10 seconds

I can ssh in just fine. It just sucks that I’ve been trying to start it since 1830 and its still not running because it just stops trying.

6

So after further review I’ve narrowed it down to device_tracker.owntracks when the device_tracker: component is enabled. Oddly enough, this doesn’t exist this way in my install

I now need to figure out where and how it is trying to load in order to remove it from loading.

7

Telling you have been trying since 1830 is bugger all use since we are all in different time zones.

8

has no baring anyways. I could have said it was 2445 and it still wouldn’t matter.

The issue is disabled components that don’t disable.

9

Precisely, so why not post something useful like your log file?

10

There’s nothing relevant in the log file and the problem is this ^

11

There is no device tracker/owntracks anymore. Check the docs.

12

Can you point me in the direction?

I don’t have a device_tracker/owntracks component. I switched over to the new one when it changed.

13

Ah, OK.

So, you need to double check that you have definitely saved the removal of that.

If it’s definitely not anywhere in your configuration but being picked up by homeassistant it could be an early indication of sd card failure if you’re on a pi because it is still being read even though its deleted.

If you’re not on a pi, then try a disk recovery with fsck.

14

I finally found it. Some random directory, that wasn’t even’t referenced, had some old files that had an old config in it was getting processed at startup.