Alexa drops FauxmoESP after some time

[kfeger]

Dear all,
I have used fauxmoESP for a couple of switches with no special alteration to the examples provided. What I see is that Alexa drops those switches after some time. Starting discovery then again finds the switch and the cycle is repeated. I have no idea, what causes Alexa to drop the switches.
My system in total consists of a managed WiFi with 4 APs, four Echos and a FireBox. No issues to the WiFi are known. Any hind what causes the drop of a fauxmoESP-unit? Is there a way to get hands on the reason of disassociation?

[m-kozlowski]

Similar case here: two APs broadcasting same ssid and 4 echo devices.
Tried to bind all echos and all smart devices to single AP. Didn't help.
Disconnecting all echos except one helped and it worked stably for several weeks, but of course it's not an acceptable solution.

[kfeger]

I followed the hint of another github member: Full reset and with that comes a software update for the Echos. I have done that several months ago and all issues are gone since then. So: highly recommended. My setup: 5 Five Echo Dots/Echos and four Aps (managed via WiFi controller), two main SSIDs. Lots of homemade FauxmoESP switches. Von: m-kozlowski ***@***.***> Gesendet: Montag, 24. April 2023 13:33 An: vintlabs/fauxmoESP ***@***.***> Cc: Karl O. Feger ***@***.***>; Author ***@***.***> Betreff: Re: [vintlabs/fauxmoESP] Alexa drops FauxmoESP after some time (Issue #241) Similar case here: two APs broadcasting same ssid and 4 echo devices. Tried to bind all echos and all smart devices to single AP. Didn't help. Disconnecting all echos except one helped and it worked stably for several weeks, but of course it's not an acceptable solution. — Reply to this email directly, view it on GitHub <#241 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDNWDB3S466L2MLLMX2J5DXCZQFVANCNFSM6AAAAAATDPZVCA> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ABDNWDFBFEE47XAKF3HVU33XCZQFVA5CNFSM6AAAAAATDPZVCCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS2TDLAO.gif> Message ID: ***@***.*** ***@***.***> >

[m-kozlowski]

Tried that long ago, as I'm facing this issue for over a year.
Recently I've also tried to implement GetState responses, which didn't help either, but made issue a bit more fun, because despite forgetting all FauxmoESP, I can see in the logs how the echo regularly polls their status every 10 minutes.

[kfeger]

Sorry but I can not confirm the problem after factory default/software update of all my Echos (1xEcho 2. Gen, 1xEcho Dot 1. Gen, 3xEcho Dor 2.Gen, 1xEcho Dot 3.Gen). Now Its absolutely stable. Did you recompile the Fauxmos with the current version? Von: m-kozlowski ***@***.***> Gesendet: Samstag, 29. April 2023 17:55 An: vintlabs/fauxmoESP ***@***.***> Cc: Karl O. Feger ***@***.***>; Author ***@***.***> Betreff: Re: [vintlabs/fauxmoESP] Alexa drops FauxmoESP after some time (Issue #241) Tried that long ago, as I'm facing this issue for over a year. Recently I've also tried to implement GetState responses, which didn't help either, but made issue a bit fun, because despite forgetting all FauxmoESP, I can see in the logs how the echo regularly polls their status every 10 minutes. — Reply to this email directly, view it on GitHub <#241 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDNWDBK5ECVPQ3K3NDHVODXDU2VXANCNFSM6AAAAAATDPZVCA> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ABDNWDDCQE6GWGPMPBQMOFDXDU2VXA5CNFSM6AAAAAATDPZVCCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS3D7UCC.gif> Message ID: ***@***.*** ***@***.***> >

[m-kozlowski]

Did you recompile the Fauxmos with the current version?

of course:)
including some forks, currently burlizzi/fauxmoESP, as it adds onGetState callback support.

[Miq1]

Looks like Alexa is ignoring the responses given on the poll request and hence will forget the device after some unsuccessful polls.

The response Fauxmo is sending is perfectly okay according to the Philips Hue specs, so Alexa must be looking for something special we do not know here.