Esp-homekit-devices: Plug when WiFi is not yet available, stays in unresponsive homekit state.

Created on 22 Aug 2018 · 9Comments · Source: RavenSystem/esp-homekit-devices

When I plug in the sonoff device while the WiFi is not available yet, the state stays unresponsive even though the WiFi becomes available later.

If I unplug-replug while WiFi is available it is discovered normally.

Source

ageorgios

Most helpful comment

It could also have a timeout in AP mode , during which if no client connect it should go back to client mode. And those two states could keep altering every ie 90 seconds ...

peros550 on 22 Aug 2018

👍3

All 9 comments

Sonoff RavenCore 0.2.4 keeps searching wifi for 75 secs, then it turns into AP mode. Wifi must be available into first 75 secs since device boots.

RavenSystem on 22 Aug 2018

This means that my FritzBox 7490 router needs more than 75sec... please consider doubling the timeout on a next release

Thanx.

ageorgios on 22 Aug 2018

It could also have a timeout in AP mode , during which if no client connect it should go back to client mode. And those two states could keep altering every ie 90 seconds ...

peros550 on 22 Aug 2018

👍3

Try version 0.2.5.

RavenSystem on 24 Aug 2018

awesome thanks!

ageorgios on 25 Aug 2018

Hi Jose,

in latest version 3.0.0 I still have this issue. My router is an ASUS RT-AC68U and it takes a lot to boot and activate wifi. Would it be possible to implement it in a way that if no client is connected in AP mode for 1-2 minutes, it will try again to connect to old known Wifi network?

Thanks
Yiannis

peros550 on 2 Oct 2018

👍1

Now I have an ASUS ROG Rapture GT-AC5300 and it takes a lot to boot too.

RavenSystem on 2 Oct 2018

Same situation here with Unifi AP in my house, taking too long to boot... probaby the solution is something similar to @peros550 "retry" proposal. Gran trabajo, saludos!