home-assistant / home-assistant/core
Canadian version of Mitsubishi Kumo cloud uses different API from US
- Dominant language
- Python
- Stars
- 90.5k
- Forks
- 38.6k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 597
Description
### The problem
The Canadian version of the Mitsubishi Kumo cloud uses a different end point compared to the US. So this integration doesn't work for Canadians. On top of that the Canadian version uses the V2 API instead of the V3 API. See also https://github.com/dlarrick/pykumo/issues/62
I was able to make it work by creating a fork of the mitsubishi_comfort package and changing the cloud to the V2 API with the Canadian end point. See https://codeberg.org/DeathByDenim/mitsubishi-comfort-canada
This works as a drop-in replacement of your mitsubishi_comfort package. I'm able to control my unit from a Home Assistant dev environment.
So I was wondering if you would be willing to have a drop down in the config flow where people can select US or Canada. The choice for US would then use the V3 API with the US end point and the choice for Canada would use the V2 API with the Canadian end point. I can port my changes to your mitsubishi_comfort package.
Is that something you would be interested in?
### What version of Home Assistant Core has the issue?
core-2026.9.1
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Mitsubishi Comfort
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/mitsubishi_comfort
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
```
### Additional information
_No response_
Contributor guide
Research direction
Start by reviewing the Mitsubishi Comfort integration and its config flow, then compare the linked mitsubishi-comfort-canada fork and pykumo issue for the Canadian endpoint and API details. Done means users can select US or Canada, with US using the V3 API and endpoint and Canada using the V2 API and endpoint, while preserving the existing integration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100