Hi, after step 1 Homey is showing Automatic in thermostat mode. Hans (multsplit with 2 airco’s).
- I set the unit to “cooling” in the M-Air app.
- I waited one minute and then opened the unit in Homey; it immediately showed “automatic”.
- After 10 minutes, I opened the M-Air app again, and it was also showing “automatic”.
So it does indeed appear to be a multi-split specific issue… likely.
After 10 minutes the M-air app is also showing automatic
Any luck finding something yet?
No, since I don’t have a multi-split setup I’m unable to reproduce your situation. A diagnostic report goes to @evdpol, so I can’t check the content of that log directly.
I would be able to test some things for you if you like…
@evdpol a question about vacant property mode, with a concrete proposal.
Right now, setting the temperature below 18 °C or above 30 °C silently turns on vacant property mode (heating below 18, cooling above 30). Going back to 18–30 °C turns it off and restores an earlier operating mode. While testing my other changes I ran into this myself:
- During a test where I had just set the unit to cooling, I set 17.5 °C, a perfectly normal temperature. The unit switched to heating by itself.
- When I raised the temperature again, a unit that was visibly heating switched to cooling, because that was the mode stored from before.
I knew the behaviour exists and still got caught by it, so I think others will too.
I’ve opened two PRs; you can choose either or both:
- PR #15: keeps the current behaviour, and shows a warning on the device while vacant property mode is on.
- PR #16: makes it explicit, like the Home Assistant integration does with its “Home Leave Mode”:
- the temperature dial only covers 18–30 °C and never changes the operating mode;
- vacant property mode is turned on and off with its own toggle and flow cards;
- its temperature becomes a device setting;
- a new “Vacant property mode active” sensor shows what the unit reports.
PR edwinvdpol/homey-wfrac#16 · Make vacant property mode… changes existing behaviour: flows that set a temperature below 18 °C to enter vacant property mode would need the vacant property mode cards instead. Is there a reason it works like this now, for example to match the remote control? I’ve tested both on my own unit.
Thanks for offering to test! I’ve put all my open changes together in a test build, the same version I’m running myself. It contains these open PRs (edwinvdpol/homey-wfrac#12 · Add a setting to turn live power… – edwinvdpol/homey-wfrac#16 · Make vacant property mode…), on top of the current development version:
- A “Measure live power” setting (device settings → Energy). Turn it off to stop the live power request entirely.
- Thermostat mode is read-only. It still colours the thermostat screen, but can no longer change the unit; use Operating mode to change the mode.
- A fix for a timing issue where a sync that was already running could send the previous mode back to the unit right after you changed it.
- The temperature dial (18–30 °C) never changes the operating mode anymore. Vacant property mode now only has its own toggle, with its temperature in the device settings and a “Vacant property mode active” sensor.
Please note this is a test build; @evdpol hasn’t reviewed these changes yet.
A word of warning before you start: installing this is fairly technical. It uses the command line on your computer, the Homey developer tools, and a version of the app that isn’t from the App Store. If that doesn’t feel comfortable, that’s completely fine! Just let me know, and we’ll wait for Edwin to review the changes, and hopefully publish a test version you can install with a single click.
How to install (requires a Homey Pro, plus a computer with Node.js and git):
npm install --global homey
homey login
git clone --branch test/main-fixes https://github.com/kay-arne/homey-wfrac.git
cd homey-wfrac
npm ci
homey app install
homey login opens your browser to sign in. If you have more than one Homey, run homey select first. Without git, you can download the ZIP of the branch instead, unzip it, and run the last two commands in that folder.
It installs over the current app, so your devices, flows and settings stay. To go back, reinstall Mitsubishi (WF-RAC) from the App Store.
What would help me most:
- Use only Operating mode to set your units to a fixed mode (e.g. Heating), and leave Homey alone for a while. Does the mode still jump back to Automatic?
- If it does, turn “Measure live power” off for that unit and try again. If the problem disappears, the live power request is the cause on your units, and I know where to look.
- Please share the model numbers of your indoor and outdoor units, and these values from the device settings (Product): Type, Wireless unit and Microcontroller (not the Operator ID).
Thanks again!
I have to be honest and say that, for me, that step goes a bit too far. If a test version becomes available for direct download, I’d be happy to test it out.
However… what I’ve noticed now is that everything seems to be working exactly as intended.
I’ve tested various things in my system, and everything is functioning as it should—it no longer keeps reverting to “Automatic.”
The only possible explanation—or rather, the only thing that has actually changed—is the Homey V13.5.3 update, which was installed early this morning.
As recently as yesterday, I was still experiencing the issue where it would revert to “Automatic.”
No worries, I completely understand. Interesting that it now seems to work for you. I checked the release notes of the new firmware version and there doesn’t seem to be any changes that might explain the different behaviour. @Wadloper do you have the same experience?
Here it also seems to work as intended: no more switching to automatic. I have not tried yet all possible situations. It is not clear to me what migth has changed. The only thing here is that one of the airco’s is on during the day for heating the living room. I operate the airco’s by the M-air app en Homey flows. I use Homey (dashboards and energy) for info. Greetings, Hans
I think something got “stuck” in the app, and the restart of the app fixed it. I cannot explain it otherwise, as nothing changed.
