Device scanning too fast (?), skipping and missing devices

Hi,

I have one device that offers 5 different switches via a RESTful service. Everything is working fine, apart from the fact that the device seems to be too slow to answer HASS.IO’s initial discovery messages. The log file hints to that. Result: Of the 5 switches, at least one is always missing. Always a different one.

Question: Is there any way to actually slow down or delay the discovery / setup process? I know, most people ask about the opposite, but I’d be happy with a 5 minute boot time if after that, all my devices would be there.

Thanks!

I think possible to intilize state somehow.

What do you mean? How?

The switches in the device can be triggered by different REST commands, and give back the current state. It looks like when HASS.IO starts, it probes for the state once per switch URL. If that reply doesn’t come (my suspicion: blocked by another call to a different switch), the switch simply isn’t there.