In my experience, it’s to be expected. It is a cloud-dependent integration. From what I’ve seen (being an active tester for the devs and following their progress in discord and GitHub), the devs have taken several precautions in designing the integration because there has been a constant up-hill battle with Amazon’s authentication services and, even more so, Amazon’s rate limits.
If you ever had AMP installed at some point, you’d know a 1 to 2 minute startup time isn’t nearly as intensive as what it would take AMP to startup sometimes.
Well, ok.
But blaming it on “cloud” isn’t the indication (or maybe it is).
Spotify take 3s, Google Calendar (with 5 calendars) takes 3.7s.
Alexa takes 76.3s …
20 times longer to load seven Alexas than 5 google calendars.
Seems to me that (possibly) it is authenticating each one and waiting for that to work to authenticate the next one? And maybe this is an Alexa issue?
But holding a boot cycle (that is what apparently happens) seems wrong to me.
If it takes times to authenticate the connection, fine … do not stop booting for this.
I should be able to reboot and be back in line in 30s or so, not have a 76s or worse wait in the middle to wait for Alexa.
Translation:
I make changes that need a reboot.
I reboot.
Wife comes out of house, I cannot access the vacuum.
I say “wait …” I just rebooted.
Now waiting 5 mins and waiting 30s is two different things. Especially to my wife who just opens the vendor app on the phone and runs it. Yes it’s only on reboot and I get it, but 76s to reboot any portion of HA seems so wrong.
