IntesisHome WiFi AC Control

Hi all

I’m trying to get the original setup working by jnimmo with my hassio install of home assistant but am having no success.

I made a new folder called custom_components in my hassio config folder and have copied intesishome.py and the climate folder with another intesishome.py file inside of it.
I then added the following to the bottom of my configuration.yaml file

intesishome:
username: ‘myusername’
password: ‘mypassword’

(I use indents for username and password above, I just can’t get it to work on this post)

When i restart home assistant i get:
Invalid Config
The following components and platforms could not be set up:
intesishome

After i reset a few folders and files get added inside the custom_components folder
pycache
“intesishome.cpython-36.pyc”

I’m still relatively new to home assistant and have only done basic stuff so far but it would be awesome to get this going so any help would be much appreciated!
Thanks!

The default.json file needs to exist in the /config directory.
You can use a volume reference when starting the Docker container to refer to a file on your host OS.

Best read the Docker documentation

thks bradley,

sames now runs better but i get this error on docker log. (maybe because i don’t know how get “deviceId”)

date stream content
2018-07-09 10:00:26 stdout
2018-07-09 10:00:26 stdout npm /root/.npm/_logs/2018-07-09T10_00_26_036Z-debug.log
2018-07-09 10:00:26 stdout npm A complete log of this run can be found in:
2018-07-09 10:00:26 stdout
2018-07-09 10:00:26 stdout
2018-07-09 10:00:26 stdout ╰─────────────────────────────────────╯
2018-07-09 10:00:26 stdout │ │
2018-07-09 10:00:26 stdout │ Run npm i -g npm to update │
2018-07-09 10:00:26 stdout │ Update available 5.6.0 → 6.1.0 │
2018-07-09 10:00:26 stdout │ │
2018-07-09 10:00:26 stdout ╭─────────────────────────────────────╮
2018-07-09 10:00:26 stdout
2018-07-09 10:00:26 stdout
2018-07-09 10:00:26 stdout mnpm This is probably not a problem with npm. There is likely additional logging output above.
2018-07-09 10:00:26 stdout mnpm Failed at the [email protected] start script.
2018-07-09 10:00:26 stdout mnpm
2018-07-09 10:00:26 stdout mnpm Exit status 1
2018-07-09 10:00:26 stdout mnpm [email protected] start: DEBUG=* node index.js
2018-07-09 10:00:26 stdout mnpm ERR! errno 1
2018-07-09 10:00:26 stdout mnpm ERR! code ELIFECYCLE
2018-07-09 10:00:26 stdout at process._tickCallback (internal/process/next_tick.js:63:19)
2018-07-09 10:00:26 stdout at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
2018-07-09 10:00:26 stdout at emitErrorNT (internal/streams/destroy.js:82:8)
2018-07-09 10:00:26 stdout at TLSSocket.emit (events.js:187:15)
2018-07-09 10:00:26 stdout at TLSSocket.handleTLSerrors (/intesis_mqtt/node_modules/mqtt/lib/connect/tls.js:26:18)
2018-07-09 10:00:26 stdout Emitted ‘error’ event at:
2018-07-09 10:00:26 stdout at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1161:14)
2018-07-09 10:00:26 stdout Error: connect ECONNREFUSED 192.168.10.230:29759
2018-07-09 10:00:26 stdout

Unfortunately you’ll have to get your device id by looking at the response from the Intesis Apis.

Hi @jnimmo! I’ve submitted a PR on your github repository to support more modern versions of HA.

If you can’t maintain the component anymore, I’d be happy to take over.

Thanks for the work @grischard. I have just had a play with your component and the issue I have is that when the device is off, I am not able to get it to turn on through Home Assistant. However, if the device has been turned on my another means (Intesis App or remote) then I can change states and turn it off via HA.

I have 2 devices attached to my Intesis account and I notice this problem only seems to affect 1 device at a time. 1 of the device I will be able to get to turn on from an off state. But not the other.

Any ideas?

That’s very odd. Both your intesis-mqtt script and pyIntesisHome? The same device always? And the app manages to switch it on reliably? Probably a faulty assumption we’re making. Is there any chance you could mitmproxy the API calls?

I will have a sniff of the packets once I get a chunk of time to look into it properly.
I have noticed something else: I have an automation that turns on both heatpumps at once via a script that sets the operation_mode. And, that works every time.

So I wonder if it is something to do with what the HA UI is doing when you toggle things through the UI. I might look at the code in the UI to see what its doing also

@jnimmo I’n very interested in the component you are developing. I have 3 Fuji electric duct type ACs and after extensive google research I realized that Intesishome is my only practical option for remote control. However, before spending my money on a badly reviewed item, I would appreciate your advise on the controller and this component. How reliable is it ?Can it be controlled locally or I have to be connected to the internet ?

I will be only buying IntesisHome kit for this component, and would highly appreciate any advise.

Many thanks,

Have you found that Home assistant does not properly restart from the Config menu when running this component?
Recently I have found my instance does not. And in the logs it looks like after I click the restart button the only log entries are from this Intesis component

Hi,
Is it possible to get Power Consumption thru the component ?

/donnib

Hi,

I just setup this component, but I am getting the following error in the log file.

2018-07-29 23:38:48 ERROR (MainThread) [homeassistant.setup] Error during setup of component intesishome
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/setup.py”, line 146, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/intesishome.py”, line 38, in setup
from pyintesishome import IntesisHome
ModuleNotFoundError: No module named ‘pyintesishome’

Hey @datzent83, I got the component working from that same error by just copying pyintesishome.py from /config/deps/lib/python3.6/site-packages/ directly into /config/deps/ (GL trying that)

Heres hoping @jnimmo sees @grischard 's PR and they continue to polish this extremely useful component.

Thanks! I got it working. How do I show the temp in F? Right now it shows C.

donnib,

Would be nice, but the IntesisHome API does not support this:

Martin

Hi,

What have you got deployed? The fix I posted a while back still working for me on .81

I just updated to the latest version .82 and now I am getting an error below.

Error during setup of component intesishome
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/setup.py”, line 148, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/intesishome.py”, line 48, in setup
hass.async_add_job(async_load_platform(hass, ‘climate’, DOMAIN))
TypeError: async_load_platform() missing 2 required positional arguments: ‘discovered’ and ‘hass_config’

They made what turned out to be a breaking change in HA around some of the functions supporting component loading.
This is the change I made that got it working again: https://github.com/bradleyscott/home-automation/commit/67a065fe31e73560b5a261ade16b1c5c4006e587

1 Like

This is great! Now its back up and running. Thanks! Keep up the good work :slight_smile:

The component seems to be working fine, however, the target temperature is in celsius and the current is in fahrenheit. My congratulation file is set to imperial. Is it my setup or that’s the component?