Intesishome stop working after update

Configuration
1

I update once every quarter, because otherwise I need to spend to much time on HA.

End of march I did my update round, and al of the sudden my Toshiba airco cannot be controlled anymore, I get this error message;


Logger: homeassistant.helpers.frame
Source: helpers/frame.py:324
First occurred: March 31, 2025 at 14:28:20 (1 occurrences)
Last logged: March 31, 2025 at 14:28:20

Detected that custom integration 'intesishome' calls async_forward_entry_setup for integration, intesishome with title: intesishome_local IS-IR-WIFI-1 (DEVICE_02CEA9) and entry_id: 01JQP3S5MKXCN5WTQWEYZ6PZFH, which is deprecated, await async_forward_entry_setups instead at custom_components/intesishome/__init__.py, line 19: hass.async_create_task(. This will stop working in Home Assistant 2025.6, please report it to the author of the 'intesishome' custom integration

Who is the author?, and is there a way around this?

2

If your using custom integration, there is now a new official integration

It was added in 2025.4

3

I am using the official integration.

I found this; Request for official inclusion (outside of HACS) of the "IntesisHome (with config flow)” integration in Home Assistant - #5 by kitopopo

and this;

4

The official integration doens’t work with local devices…

5

Not sure if you resolved this? I just switched to this version to allow local control and so far) it seems to work really well:

6

I’d like to share that the unofficial HACS integration for IntesisHome / AC Cloud has recently stopped working. After contacting technical support, they confirmed that with the latest firmware update the local access (web + API) has been completely removed, citing compliance with the European RED (Radio Equipment Directive 2014/53/EU).

In practice, this means:

It’s no longer possible to access the device locally by IP as before.

Port 80 is still open, but the local web server has been disabled.

All communication is now forced through the official AC Cloud service.

This is really unfortunate. I had been using the module in local mode with Home Assistant for over a year without any issues, and now I am forced to rely exclusively on their cloud. My Mitsubishi AC unit is old, and without local access I have no other option than using the cloud.

I don’t think support will provide any solution, since it seems clear their strategy is to shut down local access and move everything to the cloud. Hopefully, more users can raise a formal complaint, because we have lost a very valuable functionality in a unilateral way.

7

Well, to be honest, I think Intesishome sucks. Expensive, controlling etc. etc. what we see with all company’s who are delusional in thinking they are going to dominate the home automation market by forcing people to their cloud. Ive already gave up on them, fuckin 200 euro’s down the drain.

I have a toshiba, and found a nice solution for my AC’s;

https://community.home-assistant.io/t/toshiba-ac-central-systems-integration-ab-protocol/

8

Hi,

In my case, my AC unit is a Mitsubishi MSZ-HJ35VA, which is quite old and does not have any accessible communication bus for local control. Therefore, ESPHome/TCC-Link solutions that work for Toshiba units are not applicable to my system.

The only option for local control was through the Intesis IS-IR-WIFI-1 module, but after the firmware update it now forces cloud-only access.

Since many users rely on local control for their automations, I think it would be useful to organize and submit a joint complaint to Intesis, requesting at least an option that allows keeping local access.

Would anyone else be interested in coordinating this initiative?

9

I don’t think intesis will be very impressed. Intesis is doing the same to other products of theirs as well. It it a clear strategy which other brands have done as well.

For your mitsubishi unit I would suggest going fully local without any cloud control.
Like ClimaControl by ProtoART: https://clima.protoart.net/shop/climacontrol-mitsubishi-electric-airtoair/

I’m sure these guys will have something for Toshiba soon as well.

Intesis is shielding with the EU RED directive, which is related to cyber security effective august 1st 2025. Instead of just blocking access they could also do a little more effort and add encryption and API keys to local communication, but I guess that is too much work.