-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat(cloud): add support for Japanese Toshiba IOLife devices #301
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are limited to specific labels. Labels to auto review (6)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Hi, thank to so much for the contribution! Please always use the correct env (devcontainer or use at least setup script) so you'll have the complete env for development and get the checks running locally. |
After a lot of effort, I've realized that the lua files aren't fetched from the API at all, they are only distributed with the app, so the downloadLua will probably never work, at least not for my appliances. It always returns 404 (when authenticated), and not 401, so that's maybe telling, and maybe it will work for someone else's Japanese Toshiba appliance. I will extract the lua files from the app and start porting the protocol. The list_appliances function work well, and I don't think there are more cloud functions needed to get local support working. Do you prefer to keep the vestigal download_lua function in case it's activated later, or should I just remove it from this PR? |
Since you renamed this to feat(cloud), then maybe I should open a separate PR for parsing the protocol? I'm looking forward to finally getting this working :) |
@audunmg if you want to add a new cloud support, you should find out the cloud URL and params for this cloud URL, also include the cloud server URL for this cloud, then you can got a expected http 200 response from the server. I'm not familar with all the detail, but just try to read all the source code and exist feature, got this per my understand. |
@audunmg these id/key maybe works for you. please check with MeijuCloud and SmartHomeCloud args, use these value for your midea-local/midealocal/cloud.py Line 31 in 498bbe2
if
thanks |
Thanks! I will try at the first opportunity! |
Not intended to be merged, but opening a PR to show this is being worked on (slowly), and maybe attract comments and help.
For now, the cloud functions are working (except the one to download lua files, and i suspect that will never work), but that's the only working thing.
The local protocol to actually communicate with the devices is not working at all (yet).