-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hass 2024.1 error: RecursionError #1285
Comments
Hallo. Exactly same problem for me. Always perfect and now stopped. Ewlink app is working fine. I think it is coincident with latest HA update. Following... |
Same problem |
Same here, just updated HA core to 2024.1.0b2, was working fine until 2023 stable and beta versions |
Strangely enough, it is working now! I could not access my Sonoff device through the eWeLink app on Android either. tried reinstalling with no luck. A;so noticed that my phone would not connect to the "guest" WiFi net work with an error like "could not get IP address". Rebooted my AT&T fiber gateway and also had to restart the 2.4 GHz WiFi, and everything now works. I've seen the IP Address problem on the gateway before. haven't had a chance to dig into it. This is what I suspect happened:
|
eWelink app works for me. There is nothing wrong there. I think there is something wrong between Home Assistant and eWelink app. I can turn on a light on Home Assistant which has Sonoff integration, but its state remains off. |
Both the App and Home Assistant are working for me...
…________________________________
From: mesut3000 ***@***.***>
Sent: Sunday, December 31, 2023 2:43:52 PM
To: AlexxIT/SonoffLAN ***@***.***>
Cc: lloydcferguson ***@***.***>; Comment ***@***.***>
Subject: Re: [AlexxIT/SonoffLAN] Integration not working (Issue #1285)
Strangely enough, it is working now!
I could not access my Sonoff device through the eWeLink app on Android either. tried reinstalling with no luck. A;so noticed that my phone would not connect to the "guest" WiFi net work with an error like "could not get IP address". Rebooted my AT&T fiber gateway and also had to restart the 2.4 GHz WiFi, and everything now works. I've seen the IP Address problem on the gateway before. haven't had a chance to dig into it.
This is what I suspect happened:
* The Sonoff device got an IP address while the DHCP service on the gateway was working. I seem to remember that once a device has an address it will keep it even if a subsequent lease renewal fails so, it just kept it even though the DHCP service stopped at some point.
* I did unplug the Sonoff device yesterday and when I reconnected it it could not get an address so it went off-line in both Home Assistant and the Sonoff app.
eWelink app works for me. There is nothing wrong there. I think there is something wrong between Home Assistant and eWelink app. I can turn on a light on Home Assistant which has Sonoff integration, but its state remains off.
—
Reply to this email directly, view it on GitHub<#1285 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZY265ASIDWD3IW7UFARSIDYMHTCRAVCNFSM6AAAAABBIAYJ2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZTGA2DSMRWGM>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Which Home Assistant release do you have. I think 2024.1 beta has this issue. |
Same problem here, my automations started failing and device status it is not working. Problem began after ha core 2024 update |
Running 2024.1.0 stable |
There's a fix for that available in #1288 |
Much love. So many hours today working on it |
I have 24 Sonoff devices in my system. I have been using them for years. But I am not sure why, my system is crashing and devices can not respond from Home Assistant. Everything is OK by the Ewelink app.
I removed HACS addon, integration many times and installed again. I can see all my devices but they do not respond.
For switches there is also a strange thing. When I turn on one, it turns but on Home Assistants it is still off. It cant read its state.
This is what I see this error in my logs:
The text was updated successfully, but these errors were encountered: