Ok, great! Would you suggest I comment out the yaml code to disable cloud integration prior to setting up local integration?
No, you get to pick and choose when you follow the second step. It’ll ask you if you want cloud, or local etc
1 Like
Thanks so much for your guidance. I will give that a go tonight when I get home from work. Much appreciated Merry Christmas/Happy Holidays.
1 Like
All the best, let us know how you go. Nothing better than having your A/C able to be automated in time for the holidays! 
Merry Christmas to you too
1 Like
Especially in a sub tropical climate (southern hemisphere) this time of year 
1 Like
Yeah I’m from New Zealand. Bring on summer 
1 Like
Hello from across the ditch 
1 Like
I ran into the same problem. Solved it without changing password by adding “device: airconwithme” to configuration.yaml (and restarting) :
climate:
- platform: intesishome
username: <<myusername>>
password: <<mypassword>>
device: airconwithme
As described here: IntesisHome - Home Assistant device is having IntesisHome by default. airconwithme or anywair can be set optionally.
1 Like
Ok, I got everything installed and selected local config providing local host, U: Admin P: admin to connect to one of my local Fujitsu devices. The Integrations page still shows it as depends on the cloud? I can access the device UI via IP address in browser so I have local connectivity. Any thoughts?
Yes because it can optionally be configured to use the cloud, so it’ll still show with that even if you configure it to use intesishome_local.
Kill your internet connection and confirm 
1 Like
Ah, that’s clever. Will try that in the morning. If I killed the Internet now the family would be hunting me down 
Thanks again. Happy New Year
EDIT: Sorry one last question. I’m assuming I need to adjust the Entity ID for all my Automations to the ‘local’ one? I have two currently. The original yaml (below) created cloud entities.
climate:
- platform: intesishome
username: **********
password: **********
device: anywair
Yeah you will. If I was you, I’d remove the YAML one, just use the intesishome_local created through configflow, then you won’t accidentally be using the cloud-based one in any automations.
And very wise doing it when the fam is in bed or something
1 Like
All working, tried pulling the Internet connection and local definitely works. The only oddity I notice is when turning on (same for turning off) it briefly shows it’s off again then reverts to on?
Thanks for all of your assistance, this is truly great to get IntesisHome out of the cloud. Now I just need to work on Local Tuya, although for some odd reason I lose my ceiling fan lights?
Work in progress 
1 Like
This happens for my device too. Nope I hardly ever turn on it off the device manually. So doesn’t bother me at all.
1 Like
Yeah this has to do with the way that the cloud service and the local intesishome device works. You can see it if you log into it locally from a web browser.
Despite it being local, it still seems to poll the device for certain aspects every 30 seconds, just part of the way that the WiFi module interacts with it. I added a 35 second delay to certain aspects, both for the temperature changes as well as the automations that turn it on
If you want to see that live, log in to the WebUI and play around with turning it off and on again. It’s not “instant” per-se, after your first interaction with it, the next set of changes seem to only take effect when it reloads and sends details to the cloud after 30-odd seconds. This is the same with the myAnywAir app too from what little experience I have with it (for my Fujitsu units).
Sorry I’m not keeping up 
Does adding a 35sec delay resolve the toggle issue I am seeing?
To automations, yes, because by then it’s definitely got the latest settings from the unit
1 Like
Oh ok, I’m with you now.
1 Like
Would someone who uses this integration with a Mitsubishi Heavy Industries AC and the MH-AC-WIFI-1 adapter be able to do me a favour and let me know how well it works? Reliability, latency, etc?
I have read through many recent pages but it’s hard to determine exactly, especially with this specific AC brand / wifi adapter.
Asking as I’m having a broken AC unit replaced with a MHI 9.5kW unit next week, and trying to determine if the wifi adapter is worth it when I already have a Sensibo.
Conceptually the cloud aspect of the Sensibo doesn’t bother me too much, but it can be practically quite frustrating. Latency - sometimes pretty extreme latency - and relatively frequent reliability issues too. Plus, where I have to place the Sensibo to make it work in this room is not ideal.
Thanks.
Yeah the WiFi adaptor is great if you want local, and reliable. Sensibo (at least the first-gen stuff I had) is just an expensive IR blaster. I didn’t have the feedback of “this is what it is, now”.
Definitely worth it, the Intesis stuff, although only 2.4Ghz etc (probably some sort of ESP8266 or similar in them) is well worth it, reliable for local, and “just works” with this integration now. Definitely worthwhile in my opinion!
2 Likes