I’m experiencing exactly the same as @Mattie
Lost my tellstick switches when I updated to 0.60, no config change done
anyone with a working tellsticksetup on hassio 0.60?
Mine works just fine. Recently added 4 wallswitches and 2 socket relays
Works fine here too.
Check that you have the latest version of the add-on (0.4) don’t forget to copy out the add-on settings if you reinstall or update the add-on .
In my configuration.yaml I have the tellstick settings with host and port set up.
It is important with the indentation on the parameters.
tellstick:
host: core-tellstick
port: [50800, 50801]
as well as the switch settings in configuration.yaml:
switch:
- platform: tellstick
Also make sure to restart hass after changing Tellstick addon settings.
Note, I have had issues with tellstick when doing restart home assistant via hass.io menu. Two things has worked for me:
a) Make a reboot via hass.io, advanced settings Host OS.
Or… quicker:
b) Go to configuration in the left menu, select General. Scroll down to server management and push restart.
Everything is working fine. Does anyone know if it’s possible to set a default starting value for a dimmer? I want to start the light with only approximately 30% of the full strength. I’m using the Nexa CRF-2027 light bulb.
I am on Home Assistant v0.60 and TellStick and TellStick Duo service v0.4.
Everything works fine.
This is my configuration.
configuration.yaml:
tellstick:
host: core-tellstick
port: [50800, 50801]
signal_repetitions: 3
Tellstick config (in TellStick and TellStick Duo service):
{
"devices": [
{
"id": 1,
"name": "nexa01",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "1"
},
{
"id": 2,
"name": "nexa02",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "2"
},
{
"id": 3,
"name": "nexa03",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "3"
},
{
"id": 4,
"name": "nexa04",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "4"
},
{
"id": 5,
"name": "nexa05",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "5"
},
{
"id": 6,
"name": "nexa06_outdoor",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "6"
},
{
"id": 7,
"name": "nexa07",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "7"
},
{
"id": 8,
"name": "nexa08",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "8"
},
{
"id": 9,
"name": "nexa09",
"protocol": "arctech",
"model": "selflearning-switch",
"house": "81",
"unit": "9"
}
]
}
I followed the tips I got from @endor (in this thread), and that made everything work 
Hi,
Great work making this work.
Now, two other questions.
-
I need to scan the codes sent out by a Nexa Wall Transmitter WTE-2 to enter them as devices in the config and use the WTE-2 to control some functions. Any idea how to scan for codes as you can do with a normal linux installation with rawdeviceevent?
-
To add new sensors i need to manually enter the ID, datamask 127 has never solved it for me. So, same question as 1, is there a way to scan for sensors in hassio?
Br, T
T
-
Can you do this with tdtool, then it might be possible with a service call in hass. Otherwise you can check raw output of events using SSH add-on and run
nc core-tellstick 50801…give it a try to see if you can see your wall switch event. -
Use a service call as described in the tellstick add-on documentation, use function list or list-sensors then check your add on log for results…
They produce a bit different results so you might try both to see what gives you the data you need.
- Another way is to plug in the tellstick in a windows computer and run Telldus Center. There you can scan the codes easily, then just copy them to your HA setup.
1 Like
Hi!
- Thanks, the “nc core-tellstick 50801” worked great, picked up the wall transmitters codes.
2a. Still quite sure that the, at least for me, the list-sensors service call only gives me the already configured sensors. By configured I mean the IDs that I have named manually in configuration.yaml. I tought that sensors should appear automatically when datatype_mask: 127 is configured but this never worked for me… However, now I can use the “nc core-tellstick 50801” to find the ID so Im happy!
2b. Good idea on the windows computer.
Big thanks!
T
I struggle to get my tellstick to work with me. I’m stuck since there is so little configuration to be done.
Running Home Assistant 0.60.0 and Tellstick 0.4 on a new install on a PI-3.
I get “Invalid config tellstick” Please check your config. on start.
Tellstick service is running fine as it seems, here’s the log:
starting version 3.2.4
[Info] Initialize the tellstick configuration
[Info] Exposing sockets and loading service
[Info] Starting event listener
telldusd daemon starting up
Connecting to TellStick (1781/C30) with serial A6003xxx
Developer info gives me:
Error during setup of component tellstick
21:19 components/tellstick.py (ERROR)
Thu Jan 04 2018 21:19:58 GMT+0100 (W. Europe Standard Time)
Error during setup of component tellstick
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/setup.py", line 193, in _async_setup_component
component.setup, hass, processed_config)
File "/usr/lib/python3.6/asyncio/futures.py", line 332, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.6/site-packages/homeassistant/components/tellstick.py", line 99, in setup
tellcore_devices = tellcore_lib.devices()
File "/usr/lib/python3.6/site-packages/tellcore/telldus.py", line 173, in devices
count = self.lib.tdGetNumberOfDevices()
File "/usr/lib/python3.6/site-packages/tellcore/library.py", line 257, in check_int_result
raise TelldusError(result)
tellcore.library.TelldusError: Could not connect to the Telldus Service (-6)
configuration.yaml:
#Enable Tellstick
tellstick:
host: core-tellstick
port: [50800, 50801]
signal_repetitions: 3
#Set tellstick switch
switch:
- platform: tellstick
I have tried different settings in the tellstick config but no change.
Any help is greatly appreciated.
I hade a problem with my USB-kable after a change that my tellstick duo works fine.
If you or anyone with the same error can ping me on discord (endor) I can support by looking in on the problem a little closer.
I have a tellstick net and some switches and sensors.
But due to the delay i bought a telldus duo hoping for less delay and more reliable automation
Using Hass.io and installed the module TellStick and TellStick Duo service…
Do i have to manually add all devices or will they be detected?
starting version 3.2.4
[Info] Initialize the tellstick configuration
[Info] Exposing sockets and loading service
[Info] Starting event listener
telldusd daemon starting up
Connecting to TellStick (1781/C31) with serial XXX
Added the example yaml:
tellstick:
port: [50800, 50801]
signal_repetitions: 3
Well here was the solution
Hi, I just installed the Tellstick hass.io add-on, connected my Tellstick Duo, did the HASS config addition and restarted. Everything works fine.
Then I want to edit the device file in the add-on configuration page. Prior to this I run a service command to list out all the observed Tellstick devices. This is presented to me in the log-file under the add-on config page of the Tellstick Add-on:
Info] Read list-sensors /
[Info] TellStick list-sensors success → type=sensor protocol=mandolyn model=temperaturehumidity id=12 temperature=2.2 humidity=71 time=2018-05-10 00:23:21 age=3
type=sensor protocol=mandolyn model=temperaturehumidity id=103 temperature=21.9 humidity=42 time=2018-05-10 00:22:51 age=33
type=sensor protocol=mandolyn model=temperaturehumidity id=102 temperature=11.8 humidity=49 time=2018-05-10 00:22:57 age=27
type=sensor protocol=mandolyn model=temperaturehumidity id=11 temperature=16.7 humidity=53 time=2018-05-10 00:23:05 age=19
I change my config to implement the first of these units, the id 12 like this;
{
“devices”: [
{
“id”: 12,
“name”: “Temperature Balcony”,
“protocol”: “mandolyn”,
“model”: “temperaturehumidity”,
“house”: “A”,
“unit”: “1”
}
]
}
But I get a error like this;
not a valid value for dictionary value @ data[‘options’]. Got {‘devices’: [{‘id’: 12, ‘name’: ‘Temperature Balcony’, ‘protocol’: ‘mandolyn’, ‘model’: ‘temperaturehumidity’, ‘house’: ‘A’, ‘unit’: ‘1’}]}
It seems to be related to the model and protocol fields. Are these not in sync? Am I using an old firmware on my Duo?
@kenavn the Mandolyn protocol was not listed as a supported protocol on tellsticks wiki page for supported protocols neither was model temperaturehumidity that’s why it’s not allowed in the add-on config.
But when looking at your listing and also verifying with the source for telldus-core i can see it should be available.
I have created a PR for the add-on to version 0.5 with support to have mandolyn and temperaturehumidity along with a few others.
Please stand by for the change to be approved before the plugin update is available in your hassio and ready for you to use.
Done, v0.5 is now ready for you.
1 Like
Hello again,
I updated the plug-in, and successfully changed the config. Nice! But the only drawback was that the devices are registered as “switch”, thus do not report any states at all…
Checked out your PR as well, and had a look at the Tellstick code in the main repo. I figured out that the mandolyn etc. are sensor data, and needs to be configured as a sensor. So they should not be included in the config of the hass.io plugin. Am I right? I guess the config file in the hass-io plugin is not a prerequisite for using a device as a sensor?
Sorry, but new to HA, and haven’t touched the Tellstick for a while either…