IntesisHome WiFi AC Control

I’m getting sporadic issues still @jnimmo with:

Logger: homeassistant.components.climate
Source: custom_components/intesishome/climate.py:108
Integration: Climate (documentation, issues)
First occurred: 5:17:34 PM (7 occurrences)
Last logged: 11:35:13 PM

Error while setting up intesishome platform for climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 353, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/intesishome/climate.py", line 108, in async_setup_entry
    controller = hass.data[DOMAIN]["controller"].pop(config_entry.unique_id)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'intesishome_local_cc3f1d026fbb / 00076200630076'

Unfortunately reloading, or disabling / re-enabling the integration doesn’t seem to resolve it, only a full restart of HA.

Any ideas what may be causing this?

I gave up on this integration. My advice would be to buy an esphome module. Works reliably

Yeah that key being requested looks a bit weird, I’ll have to look at where that key is coming from, it shouldn’t have the extra number on the end

Out of curiosity what does this solution look like?

Potentially the serial number attribute was sometimes being populated with unexpected values on Intesishome local, I’ve pushed an update to try and make this more stable but it’s untested and not sure it will help sorry, fingers crossed.

I’ve ended up with duplicate entities post update. All my automations are now requiring updating. I’m rolling back for now until I know if this was intentional in the change or not.

Thanks for that feeeback, this would suggest the sn attribute has been storing the MAC and serial number without me realising all this time then. I’ve updated the release to mark it as pre-release while I consider this. You would be able to edit the entity IDs to be the same as the old one but would prefer people not need to do that.

1 Like

Please see Mitsubishi Heavy Industries (MHI) Airco WiFi controller MHI-AC-Ctrl (MQTT/ESPHome) aangeboden - Vraag & Aanbod - Tweakers, it is in Dutch, but can be translated. Easy to plug in and tightly integrated with HA. I love it. On top of that, fully local connected, no external cloud.

I had a number of issues with this integration, no disrespect intended, but when I had a power outage (mostly because the power outlet is in the room of my daughter, and she sometimes needs the outlet), i always had to reboot my entire HA before I could use the Airco’s again. And already noticed the cloud connection being offline sometimes (can’t control them with the app either).

1 Like

Have updated and so far so good @jnimmo , thankyou! :slight_smile:

Had to update the entity IDs in automations / dashboards, but if that’s all it takes for me the end-user, then so be it, not the end of the world. Grateful for your time! :+1:

I have recently had 2x MHI air conditioners installed with the MH-AC-WIFI-1 modules, but unfortunately when I try to add the intesishome_local integration with the IP address, username and password (my Intesis credentials) I get “an unknown error occurred”.

Within the Home Assistant logs I can see a big long error that culminates with the following line:

aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.8.159:80 ssl:default [Connect call failed (‘192.168.8.159’, 80)]

I wonder has anyone else come across this? I’m at a bit of a loss what to do (except to use the cloud integration I suppose!)

I got this working but I had to add the device to my configuration.yaml:

device: IntesisHome

the fork with config flow above works perfectly with local access, thanks.

First time I installed it, however, it would hang at the initial config dialogue. After trying everything a delete and reinstall fixed everything.

Any luck with this? I haven’t been able to get local control working with my MH-AC-WIFI-1 unit either.

Hello,

Maybe somebody know how to add fan mode: auto, because in states no auto mode:

hvac_modes:

  • heat_cool
  • heat
  • dry
  • fan_only
  • cool
  • ‘off’
    min_temp: 18
    max_temp: 30
    target_temp_step: 1
    fan_modes:
  • quiet
  • low
  • medium
  • high
    swing_modes:
  • ‘off’
  • vertical
    current_temperature: 26
    temperature: 24
    fan_mode: 0
    swing_mode: ‘off’
    outdoor_temp: 1
    icon: mdi:white-balance-sunny
    friendly_name: DEVICE_021F01
    supported_features: 41

Over the last week I started getting these messages in the logs and can no longer control the AC.
Have reloaded compent and tried previous version without sucess. Any ideas?

2023-10-23 07:50:01.367 DEBUG (MainThread) [pyintesishome] IntesisHome API Received: {"command":"connect_rsp","data":{"status":"ok"}}

2023-10-23 07:50:01.367 INFO (MainThread) [pyintesishome] IntesisHome successfully authenticated

2023-10-23 07:50:01.367 DEBUG (MainThread) [pyintesishome] Resolving set_value's await

2023-10-23 07:50:01.367 DEBUG (MainThread) [pyintesishome] pyIntesisHome lost connection to the IntesisHome server

2023-10-23 07:54:01.370 DEBUG (MainThread) [pyintesishome] sending keepalive to {self._device_type}

2023-10-23 07:54:01.370 DEBUG (MainThread) [pyintesishome] Sending command {"command":"get","data":{"deviceId":224571441768251,"uid":10}}

2023-10-23 07:54:01.371 ERROR (MainThread) [pyintesishome] <class 'ConnectionResetError'> Exception. ('Connection lost',) / Connection lost

I uninstalled all custom components for this and went back to the build in components and it seems to be working again.

Sorry for the stupid question but what do you mean “custom components” and “Build in Components” - Mine is not working similarly.

I had this custom component installed GitHub - jnimmo/hass-intesishome: Experimental fork of the IntesisHome integration for Home Assistant
I removed it and then followed the install on the Built in integration IntesisHome - Home Assistant

1 Like

Had a device drop off as unavailable although still works in the intesis AC Cloud app. Will do some troubleshooting later today, but everyone else still running ok by the looks of it?

Same for me when I updated to 1.07. I didn’t have time to troubleshoot so I just rolled back to 1.05 and it started working again.