Regarding the API login, have you also utilized the “ewelink-api” project on Github? (GitHub - skydiver/ewelink-api: eWeLink API for JavaScript)
If so, the issues you encountered are due to eWeLink team disabling the “Personal APPID” of that Github project (only the APPID has been disabled, the eWeLink API interface remains functional). This is in line with what our colleague mentioned in the Github announcement: CoolkIt: Announcement regarding the expiration of the APPID referenced in this project and the cessation of maintenance of the v1 interface, suggesting migration · Issue #219 · skydiver/ewelink-api · GitHub
We ceased the use of “APPID” referenced in that project because the open-source project “skydiver/ewelink-api” on Github has not been actively maintained for the past three years. The “Personal APPID configuration parameter” referred to in the project was also prone to misuse. Over these three years, eWeLink OpenAPI has undergone several important updates. To prevent negative consequences for numerous developers, we made multiple attempts to communicate with the developer of the Github project, but unfortunately, we couldn’t establish contact. Eventually, we had to officially announce the discontinuation of the APPID for that project after three weeks of notice.
Project link: GitHub - skydiver/ewelink-api: eWeLink API for JavaScript
–
If you’ve been using the “Personal APPID” referenced in that project, this change may impact you. However, there are solutions available:
Since the eWeLink team has disabled the “Personal APPID” referenced in the Github project, you will need to apply for your own account on the eWeLink Developer Platform to migrate the project. The eWeLink technical team has provided an example of OAuth2.0 login for “individual developers” to refer to during migration. Specifically:
If you prefer to log in through a non-OAuth2.0 method, you need to send an email to bd@coolkit.cn to apply for an APPID. Please also specify your specific use case or requirements in the email for expedited review.
The eWeLink OpenAPI v1 interface has been discontinued, and it will gradually be completely deactivated (no longer usable) in the future. Developers are advised to migrate to the V2 interface as soon as possible. For detailed guidance, please refer to: https://coolkit-carl.gitee.io/apidocs/#/en/PlatformOverview