[APP][Pro] Mitsubishi WF-RAC - Cooling, heating and ventilation

I’ve got 1 AC with 4 accounts, and 1 with 2 accounts. How is that even possible? I’ve got a new phone, maybe thats something.
And, how can I delete them?

Still trying to figure out why this is happening, whitout a total new install of the AC’s, en rebuild the massive flows.

Edit: both AC’s does have a static IP via DECO, en WIFI signal is good.

You can do it here: GitHub - edwinvdpol/homey-wfrac: Mitsubishi (WF-RAC) for Homey

1 Like

Yeah after the update last month it’s unusable. Sometimes they are online, most of the time not reachable. Is it possible to get the update from last month?

It had been working perfectly for over a year

1 Like

Hi @evdpol,

Thanks again for keeping to support this. I noticed you’ve updated the app to version 1.3.11 yesterday. I deleted the app, reinstalled it and added both airco’s again. Unfortunately one of the two keeps on giving the “unreachable” error. It has been like this since we got them installed a few months ago.

They both have a fixed IP, are almost next to an access point and connect to the 2.4Ghz wifi channel on my Deco WiFi 7 Mesh System.

Eerste verdieping: Mitsubishi Heavy Industries - SRK50ZS-WF ← This one is keep on giving problems
Tweede verdieping: Mitsubishi Heavy Industries - SRK35ZS-WF ← This one is working fine

App report: 7c8da3d7-39c3-420e-b80e-3f40095b5197

Can you please give me some guidance on what to do? or what i’m doing wrong?

Good evening, any update on the connectivity issues?

1 Like

Well, yes! Just now I noticed a bug. Will update the app shortly.

4 Likes

@evdpol the bug fix 1.3.13 helped ! Thanks . All airco’s are now responding to control command again . Great

1 Like

Good evening @evdpol

Thanks for developing this Homey app for MHI Arico’s

Just got my 4 Mitsubishi Heavy Industries - SRK20ZS-WF airco’s installed today.

Connected them with the Smart M-Air app and with your app on my Home Pro mini. But i keep getting the unreachable error on all four of them. I’m using version 1.3.13.

All four Airco’s have a fixed IP and are connect to the 2.4Ghz wifi channel on my Deco WiFi Mesh System (1 X50 main and 3 M9 Plus on a wired backhaul).

App report: 72f49ab0-522d-49d0-802a-1742f48cba09

Just checked the new update seems to work fine!! Thanks!!!

Unfortunately the update didn’t work for me. One unit is working fine, the other one still isn’t working.

I was wondering if there is a difference between both units so, I took both units and wifi modules apart. And there indeed is a difference between both wifi modules.

Wifi Modules:

  • Model: BL3332-P (Ver: 52010) ← This ons is working

  • Model: BL3372-P_1v1 (Ver: 62025) ← this one is not working

To make sure the wifi module indeed is the issue, I switches them around. The result was that the airco that had the BL3332-P module installed worked fine, but the unit with the BL3372-P_1v1 module installed didn’t work. So, the “issue” indeed seems to be the wifi module.

fyi: Both wifi units work fine in the M-air app, but Homey keeps giving the "device unavailable” error with the BL3372-P_1v1 module.

App Report: 511ae314-4279-423a-998c-dda6a56ab208

@evdpol or anybody else any thoughts?

Thx for the update.

I will check the hardware versions of my WLAN cards and report back on it here.

unfortunately i got the same issue “Device unavailable”
ea4b1ce8-bde1-4762-a8a3-108747862bbd

Is there something i can do?

I was able to solve this by buying a BL3332-P (Ver: 52010) on Marktplaats and replace the BL3372-P_1v1 module. Now both airco’s work!

(Ps there are still a couple of modules available on Marktplaats. Do ask the seller to open the case and check for the model number)

Nice that you could solve the problem by replacing the WLAN hardware with the other (older) model.

But I would need to replace all four of my WLAN cards (€€€€) and there are not that many availble on Marktplaats :slight_smile: .

@evdpol I hope there is also a software fix posible to solve this problem, since I think that the BL3372-P_1v1 will be included in all new MHI airco’s.

1 Like

I think I have the same issue. I had two new Mitsubishi air conditioners installed, planning to integrate them with Homey as well. I probably also have the 1v1 modules (haven’t been able to check yet).

Both air conditioners are recognized (found/discovered) when adding a device, but they are almost immediately shown as ‘device unavailable’. I do hope there’s a software solution, because replacing the modules for older models from Marktplaats doesn’t seem like the ideal solution to me. From now on, I think all air conditioners will be delivered with such a 1v1 version (if they aren’t already). Is there anything I can provide so the software can be looked into? Happy to help.

Went for an alternative (back-up) solution by buying a ClimateControl Module for MHI. It works with the Homey ClimateControl control app.

It’s much faster then the standard MHI WF-RAC and Smart M-Air app. An other advantage is the wireless temperature sensor that prevents false readings near the unit, because you can place its anywhere in the room.

Tested is today for 1 of my Airco’s and it works like charm, So I will buy them for all of my Airco’s.

While this could work, I hope a software fix will resolve the issue with existing Wifi modules. I’m unsure why we can’t connect to newer modules or if it’s possible to solve.

Regarding the temperature issue, you can already use an external sensor (connected to Homey and a Custom Flow) to adjust the airco accordingly if the built-in sensor fails to report the correct room temperature?

1 Like

The developer remains silent. I know it’s all volunteer work, but a response would be appreciated. We don’t know if this issue is even being considered for a solution.

I’m also willing to (beta) test if that would contribute to a solution.

1 Like

Woud you please be so kind to direct me to the correct documentation, as I do not have any hardware that runs on the newer firmware? You have your solution already in place as far as I could read? What is your point exactly?

I believe you can find the documentation here: https://fcc.report/FCC-ID/2ATEV-BL3372-P-1V1/6474557.pdf

I did indeed find an alternative solution, but there are others for whom it doesn’t work, and it would be great if it worked for everyone.

Thanks in advance for your efforts, and if I can help, for example by testing, please let me know.