Yes the first part is deployed with the libraries in the homeassistant docker.
Now the telldus daemon will be put in an add-on to expose the unix socket, pvizeli has prepared some parts in the tellstick python and created a tellcore-net service for communicating with the tellstick daemon.
I think he will dig deeper in to the addon to enable communication between the tellstick daemon and homeassistant using socat.
@pvizeli unfortunately it seems like the modifications made to tellstick.py broke tellstick support for non-hassIO users as reported here
The compilation and installation of telldus-core (including the daemon) is added inside the homeassistant docker so we only need a way to trigger the daemon for hass…
for hassIO - Check if tellstick: is in configuration.yaml (or add hass.io unique service trigger in config?)
then start the already existing telldusd in hass.io docker early or prior to loading hass.
we should really add -DSYSCONF_INSTALL_DIR=/config when compiling telldus-core in dockerfile for putting tellstick.conf in the shared folder rather than /etc.
I have tried it locally using modified entry.sh in homeassistant docker calling telldusd & >/dev/null and it fires up like a charm and communicates with my devices in homeassistant.
This would mean that we don’t need any changes in tellstick.py.
Just my humble opinions, there might be other reasons for not wanting the telldus daemon running inside the hass.io docker?
I have only got it running via debugmode and it is quite tedious to go through the process as well as if you restart or update hass the modification has to be added again…
So i think the best way forward is to get a release on track that has this built in…
Addon is created you should be able to find it in official hass-io repository in your hass.
As it looks there are still some things to sort out on how home assistant can communicate with the addon and interact with the daemon/service.
You need to add these parameters in your configuration.yaml, but i still receive errors from hassio when rebooting that it is unable to communicate with tellstick service due to the work that remains to complete the interaction…
tellstick:
host: core-tellstick
port: 50800
Please try to install the addon and refresh the logs, you should see something like this:
[Info] Initialize the tellstick configuration
[Info] Run telldusd & socat
telldusd daemon starting up
Connecting to TellStick (1781/C31) with serial A501****
This means that the daemon is started, parsed the config and the addon can connect to your hardware.
¨Yes, I know that the Net works using Telldus live, the problem is that their service is sometimes slow and unreliable. And if Home Assistant loses connection to the internet it wouldn’t be able to control the switches anymore. Thats why I was wondering if this worked with Tellstick Net so it could be used without connecting to the Telldus live server.
Added feature request to be able to issue Learn command to tellstick.
This is important for hassio and imho it would be a clean solution to the problem.
Hi,
Maybe a stupid question but where should I put in the tellstick.conf?
I have seen the gui option to add but that seems not so easy to add the conf, adding more than one switch gives I cant save.
So I guess I should be able to put the file in some conf directory as well. Easier to check syntax as well.