How do I add Mitshubishi integration. I went to HACS, and added the custom repository, it appears on the screen.Is there any other step. I added custom repository long time ago and forgot if there are any further steps to offlow.
The app needs an update. It came available this morning (for Android)
1 Like
Thanks, now it works on Android
In case anyone has a new unit with the built in wifi module and is running into the device limit with 4 devices registered. I found out that the built in module is exactly the same as the old unit, but the buttons are not exposed. Just remove the screws and the enclosure clips open easily. Then you can hold down the reset button to reset the wifi module and device limit.
NOTE: It is stupid to go into the unit while electricity is connected. You can get an electric shock!
1 Like
Hi, is there a way to establish the wifi connection without the mitsubishi app? It does not find the device but wifi was reset and Iām connected to the AP of the device.
Probably I better go with the esp replacement?
Thx
And, It would be very useful the get connection to wifi module after with HA after repowering the airco. Now I have to restart HA everytime when the airco is switched on.
The reason I switch the airco off is because it consumes approx 6 watt in stand by modus.
Probably disabling the integration when the power-sw is off: Integration management - Spook š» a scary powerful toolbox for Home Assistant.
Didnt try it yet
@miksu103 , does your remote allow you to factory-reset the unit?
I have the Ciaras; by pressing timer-off+3D for 5 seconds, then on/off for 5 seconds, it triggers a factory reset.
Maybe your control would allow something similar? Poking about a live circuit board - very dangerous, as you say!
All praise to Jeatheak for the awesome Mitsubishi Heavy integration! My Ciaras mostly are well-behaved.
However, Iām seeing frequent ConnectionRefusedErrors [Errno 111].
And a bit later, problems with url /beaver/command/getAirconStat, stemming from again Connection Refused by the unit.
So: anyone have any idea why the units would be regularly (I see 5 times in 120 mins) refusing connections?
For my understanding; disable the integration and switch the power of. And when I switch the power on, then enable the integration. This is not working. It only works when I restart HA unfortunately.
Hi there! I found this post after days of looking for an answer for this problem. I am experiencing hourly disconnects on 2 Smart-M-Air WiFi Modules. I am on firmware 010/131ā¦ Would you mind checking if the problem came back for you?
Hi @Midifreakz the problem came back for me after a power cut.
I had 1 module at the time. Was stable for a couple days, since the power cut I have hourly disconnects. Maybe coincidence but I think not.
I now have 3 modules, all are on 010/131 and all have hourly disconnects
I also have 3 units, all on 010/131 and all with hourly disconnections. This has happened from day 1 that I have them.
Other IoT devices on the same AP do not have hourly disconnections.
I think the problem is in the WiFi module of the AC units.
Hi everyone, I have two air conditioning MHI SRR and SRK both connected to home assistant. I can turn them off ana on, change modes and set the temperature. Unfortunately, the fan speed setting doesnāt work. Has anyone had this problem and knows how to fix it?
maybe not the placeā¦ but i constant even after a restart receive this error:
Repository ājeatheak/mitsubishi-wf-rac-integrationā exists in the store.
edit after some days of searching and help from the community
found the solution.
Go to the HACS store and search for āSmart Mā install and voila.
Succes.
I also was experiencing the hourly disconnects (and came across this thread) but Iām not a Home Assistant user (so that can be ruled out)ā¦ when I looked at the packet captures from the AP of both aircon units (WF-RAC) I discovered the same source ports are being re-used.
Iāll post more info here: https://community.ui.com/questions/AC-Units-IOT-disconnecting-from-UniFi-Wi-Fi-at-regular-hourly-Intervals/821cd3e4-46a0-4d6b-8fd0-8d5cf182b90f
1 Like
Hi and welcome to our community!
Thanks for sharing the answer from MHI support.
I already suspected that there was a fixed lease time in their Wi-Fi interface, but I am glad that this has now been confirmed by MHI.
https://community.ui.com/questions/AC-Units-IOT-disconnecting-from-UniFi-Wi-Fi-at-regular-hourly-Intervals/821cd3e4-46a0-4d6b-8fd0-8d5cf182b90f#answer/60e3ef8c-7edd-4e63-8d50-4e3b135c055d
Is anyone else experiencing Home Assistant crashing completely when interacting with the aircon units? Occasionally when I start or stop an aircon unit, home assistant completely locks up and crashes. I have to force restart HA. At first I thought it was just a coincidence, but itās happening at least once a day.
Iām also experiencing the constant drop out of aircon units described by many people here. I donāt think itās directly related to the crashing though, as the units are available and normally complete the action before HA dies. Iām going to enable debug logging to see if it helps show anything useful.
The only interesting things I see in the logs at the moment are:
2025-01-18 17:52:23.079 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-01-18 17:51:16.111 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 258
Donāt ask me why, and Iām not for sure, but it looks like a connection issue with the Mosquito broker, running on a RPi.
Thanks, I wasnāt sure whether it was worth posting those errors as I suspect they come from node red, and only occur after the system becomes unreachable. Iām keeping an eye on things and have debugging set so hopefully will get more information if it happens again.