-
-
Notifications
You must be signed in to change notification settings - Fork 6
SmartHome cloud get_token is still broken #201
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
Comments
Hi @mill1000 as some members report our midea-ac-py fixed the cloud token issue. I want to share some info with us, timeline and history:
in fact, for these cloud services, I also found these cloud service may have region/geolocation limiation, as we have found some user can't login to smarthome cloud with the user/password, but once they switch to a new IP with VPN service, it will be available. finally, switch to nethome plus maybe a temp solution these months, but per my understand, this service also will be offline like meiju cloud and smarthome cloud. Thanks |
Hi @wuwentao
Well thanks to you as well. I used midea-local and midea-beautiful-air as references when implementing the NetHome Plus cloud and to confirm that my SmartHome cloud implementation wasn't the only broken one.
Yes I've noticed this as well. It seems to be particularly troublesome for EU users (maybe due to GPDR?).
Yes I've suspected there must be a new v2 API. I unfortunately don't have any Midea devices any more so my ability to RE is pretty limited.
Yes this is the best we can do for now. I have update my documentation to remind users to save these values in case the cloud goes away, |
This issue was originally reported in #193, the solution at the time was to migrate to the NetHome Plus cloud via #194.
Ideally, the
get_token
method should be fixed by a proper RE of the SmartHome cloud. Early attempts were unsuccessful as the SmartHome app is not trivial to analyze.The text was updated successfully, but these errors were encountered: