Aeotec not starting fast enough on system reboot

[IVB]

Caveat: My Echo stuff is currently 100% broken, trying to fix it now, when I discovered this.

I have an Hue Simulator driver that connects to the Echo. In it's config I have a bunch of zWave stuff. That way I can remove the trigger word, just say "Alexa, turn off the kitchen light". 

It looks like the Hue sim driver is starting before the Aeotec, and I get this in the logs.

[Dean Roddey]

That's not going to change. Z-Wave is very slow, and a lot of back and forth has to go on when the driver starts up in order for the driver to get itself caught up. I try to minimize that a lot compared to what some controllers do, but it's still going to take some time. It can't come online until has had a chance of getting valid data for the fields, and that means taking even longer to try to get data for those units that we can actually talk directly to.

That's just the nature of the beast with Z-Wave. It's not like something like a Hue or RA2 system, where there's a smart controller out there that already knows the state of the state and we can just ask it for a quick summary and be ready. We have to go talk to all the doodads and get that information ourselves every time. And it's slow. Often there will be failures when there's a good bit of traffic and that requires retries which further slows things down. And of course secure devices make it take even longer as well.

[IVB]

ok. Is this something to just not worry about, then?

[Dean Roddey]

No, there's nothing to be really done about it. Well, the emulator driver could in theory look at all of the drivers it has been configured for and not come online until either some period of time has passed or all of those drivers have come online.