Hi All,
Silly question, but am I correct in that a connection to the Intesis Server is required for this device to work, and therefore if Intesis ever stops supporting it, this device will no longer work?
I really don’t like the sound of that. If that’s the case I’ll get the Modbus interface instead.
Thanks!
Hello. Did you succeed to connect your home assistant to modbus?
I am talking to it via Modbus, but I ended up using Node-RED instead. For my application this worked out to be very simple and quick. Happy to share the flow and further details if anyone’s interested.
I may integrate it with HA in the future, but for now I’m very happy with Node-RED.
I have a LG ducted AC system and I want to control it with my home assistant. I am very happy with home assistant so I don’t want change our have another system. It is possible to buy a dry contact board to add modbus or bacnet to my AC but I don’t know how to integrate with home assistant as I am not a developer. Any help would be great.
Buy the Modbus interface and play with it until you get it working. Incidentally the lacking Modbus documentation is what turned me off Home Assistant in the first place. The OpenHAB documentation is much better.
Modbus is an easy protocol to use, you’ll find a huge amount of information online. Key is to study the manual of the interface unit to find out which registers do what.
BTW, since you’re not a developer, seriously take a look at Node-RED. Implementing Modbus control with it is easy and zero coding is required for basic control. Then you can integrate the Node-RED control logic into Home Assistant quite easily (note I haven’t done this, but information is out there showing how to do it). Alternatively you’ll have a decent understanding of Modbus at that point, and you could re-write the code in Home Assistant natively more easily.
Good luck!
Hi @jnimmo, any plans update the IntesisHome component to work with the climate new platform of HA?
I’m getting a “supported_features NotImplementedError”, and after doing some reading, all custom components must implement this property now.
Running HA v0.63.1.
Hey shlomki, unfortunately I’m unable to maintain this project anymore as I don’t have an IntesisHome anymore. Any volunteers to take it over?
I am new to Python so struggled trying to get jnimmo’s library to work so I decided to try a different approach. I now have a working integration using the default MQTT HVAC component of Home Assistant
I have published my code on Github for anyone else who wants to use it. https://github.com/bradleyscott/intesis-mqtt
Its hot off the press so it might be a little buggy. But it might solve your problem @shlomki. PRs and suggestions welcomed
Looks like a nice solution, will this also update states if the remote is used?
Yup. It listens on the socket for those messages regardless of source. Same with the app.
Thank you @bradleyscott I got your docker running and it’s working great. What thing I was wondering is how do you find the deviceid? I ended up just looking at the page source but I’m thinking there’s a more obvious place to find it?
Good to hear it’s working for someone else 
I think I did something similar. Probably watching the API responses which list the device metadata. There is probably some clever way I could hydrate the config files with some of the deviceId information that comes back from Intesis, but I just haven’t implemented anything like that.
Does anyone have 2 intesis devices running? I am finding a problem where sometimes 1 of my 2 devices doesn’t respond properly to an ‘on’ command. It quickly turns off (within 1 second). Then later on, the other device might suffer the same problem. Only 1 device has this problem at a time though.
I don’t have the problem using the Intesis official app though. So must be to do with something I am doing on the websocket. I can’t figure it out though, so hoping someone else might be running the same config
Hi Bradley,
Im trying to configure it but i can’t for now…
I trying to get running docker container but don’t urdenstund where i must place default.json file (on docker link folder or on homeassistant path???)
Docker container not run when i try to start it, any special way to set up it?
THKS
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.