some switches become unavailable in HA work ok on ewelink app
all hardware model: RM-07 (got 7 of them) RM-08 (got 4) RM-09 all become unavailable in home assistant
eWeLink actually had to restart services on the server. They also are dropping the old way called v1 for a new way. Please see their response below:
Greetings,
We appreciate your engagement with our services.
Our server has observed a substantial influx of requests originating from this project. After a thorough analysis, we've identified that many users are utilizing default personal APPID configuration parameters. However, as this project still employs the v1 interface, which is no longer under maintenance, it's leading to various issues.
To ensure interface security and mitigate potential risks, we are gradually discontinuing the v1 interface and will render it entirely inaccessible in the future.
We encourage individual users to utilize the eWeLink Developer Center for free. By visiting https://dev.ewelink.cc/, you can create your own application and obtain a unique APPID. This personalized APPID can be used continuously within reasonable limits. We've also taken note of reports from numerous users indicating certain feature limitations due to the project being inactive for the past three years. An alternative option available is the https://www.npmjs.com/package/ewelink-api-next library. This library leverages the v2 interface and has comprehensively encapsulated all available v2 interfaces. It offers local area network discovery, and control functionalities, and facilitates bidirectional communication with devices through established WebSocket connections. This enables real-time data exchange and receipt of device-generated updates.
So it looks like this integration will need to be re-written ASAP and documentation updated
Same issue here. Updating a few weeks ago the latest version 3.5.2 had got the integration working again with the new APPID numbers in V3.0X. A reload of the integration does get the authorization to update for devices to again function from HA. However comment from lordwizzard>ewelink/coolkit it seems this may not be lasting for long. Newby ? - Were to you verify/find in HA>HACS the Sonoff integration version your presently on?
I could not find current version when looking at the Integration and then Sonoff, all the doc does; is point to the repository with 3.5.2 version is listed as latest. It would be nice if that data was given in the Integration Panel for Sonoff
On finding the version on your HA. I found it - click on HACS in the sidebar menu, this loads a screen showing all of the HACS running on your HA instance. Find Sonoff in the list, click on the 3 dots, click on on "Show" that gives the version running on your HA.
I am seeing this as well - need to reboot Home Assistant 2-3 times a day to get the connection working again. On 3.5.2
The devices actually work ok for me only after I open ewelink, and manually turn on/off a switch. Then it immediately pops up in HA as active again.
Also not working: King-Q4 GTTA59
Should we assume that it won't work for now?
eWeLink actually had to restart services on the server. They also are dropping the old way called v1 for a new way. Please see their response below:
Greetings,
We appreciate your engagement with our services.
Our server has observed a substantial influx of requests originating from this project. After a thorough analysis, we've identified that many users are utilizing default personal APPID configuration parameters. However, as this project still employs the v1 interface, which is no longer under maintenance, it's leading to various issues.
To ensure interface security and mitigate potential risks, we are gradually discontinuing the v1 interface and will render it entirely inaccessible in the future.
We encourage individual users to utilize the eWeLink Developer Center for free. By visiting https://dev.ewelink.cc/, you can create your own application and obtain a unique APPID. This personalized APPID can be used continuously within reasonable limits. We've also taken note of reports from numerous users indicating certain feature limitations due to the project being inactive for the past three years. An alternative option available is the https://www.npmjs.com/package/ewelink-api-next library. This library leverages the v2 interface and has comprehensively encapsulated all available v2 interfaces. It offers local area network discovery, and control functionalities, and facilitates bidirectional communication with devices through established WebSocket connections. This enables real-time data exchange and receipt of device-generated updates.
So it looks like this integration will need to be re-written ASAP and documentation updated
Is a re-write being planned?
For your info https://github.com/AlexxIT/SonoffLAN/issues/1224#issuecomment-1717465867
https://github.com/AlexxIT/SonoffLAN#issues