HomeKit bridge with Telldus Live
Updated 2019-03-18 !
Do You have Telldus devices up and running and want them to be visible and used in Apples Home app ?
With some software and a Raspberry Pi(RPi) they will appear in the HomeKit environment.
Other HomeKit posts on this Blogg
If You also have Z-wave products there is a parallel solution found in this post and if You have both Z-wave and Telldus devices there is no problem running them at the same time, on the same RPi and also together with native devices.
Do You have Telldus devices up and running and want them to be visible and used in Apples Home app ?With some software and a Raspberry Pi(RPi) they will appear in the HomeKit environment.
Other HomeKit posts on this Blogg
If You also have Z-wave products there is a parallel solution found in this post and if You have both Z-wave and Telldus devices there is no problem running them at the same time, on the same RPi and also together with native devices.
With Homebridge up and running, emulating HomeKit, install the Telldus Live plugin, TLP, that bridges the functions to Telldus live registered devices, with command
where You have copied the 4 keys and tokens You got from the Telldus website.
Start hombridge
$ homebridge
and if everything goes right it will show
Run Your Home App again and add Homebridge and the accessories will appear.
Then configure autostart at power on/failure with this post (systemd).
Restart the RPi
$ sudo reboot
and now all should be up and running.
If You are adding new devices You have to reboot the RPi for a new initialization.
If You also are having Z-Way devices here is a congfig.json for several plugins.
HB autostart at power on and failure, installed with a script !! , is found here.
Instructions updating the installation is found here
A post for connecting temperature sensors direct to RPi and show in Homekit.
$ sudo npm install -g homebridge-telldus
For those who have a TellStick ZNet Lite Vx and want a local setup check here. (This setup will make Your schedules work without a working internet connection)
Now You have to fetch some keys from Your Telldus live account. These are used for the plugin so the RPi can log on and fetch the device info.
For those who have a TellStick ZNet Lite Vx and want a local setup check here. (This setup will make Your schedules work without a working internet connection)
Now You have to fetch some keys from Your Telldus live account. These are used for the plugin so the RPi can log on and fetch the device info.
- Go to https://api.telldus.com
- Click on "Your keys" then login.
- After the login click "Generate a private token for my user only"
- Then click "Do You accept? Yes"
- The next screen will show 4 rows of i keys and tokens, which will be used in the configuration file for the plugin.
{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "Telldus plugin",
"platforms": [
{
"platform" : "Telldus",
"name" : "Telldus Liv!e",
"public_key": "FEXXXXXXXXUNU",
"private_key": "ZUXXXXXXXXX6EF",
"token": "88XXXXXXXXXXXb7d",
"token_secret": "a57XXXXXXXXXXXXXed5f"
}
]
}
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "Telldus plugin",
"platforms": [
{
"platform" : "Telldus",
"name" : "Telldus Liv!e",
"public_key": "FEXXXXXXXXUNU",
"private_key": "ZUXXXXXXXXX6EF",
"token": "88XXXXXXXXXXXb7d",
"token_secret": "a57XXXXXXXXXXXXXed5f"
}
]
}
where You have copied the 4 keys and tokens You got from the Telldus website.
$ homebridge
and if everything goes right it will show
[2018-8-16 11:41:26] Loaded config.json with 0 accessories and 1 platforms.
[2018-8-16 11:41:26] ---
[2018-8-16 11:41:26] Loaded plugin: homebridge-telldus
[2018-8-16 11:41:26] Registering platform 'homebridge-telldus.Telldus'
[2018-8-16 11:41:28] ---
[2018-8-16 11:41:28] Loading 1 platforms...
[2018-8-16 11:41:28] [Telldus Liv!e] Initializing Telldus platform...
[2018-8-16 11:41:28] [Telldus Liv!e] isLocal: false
[2018-8-16 11:41:28] [Telldus Liv!e] Loading accessories...
[2018-8-16 11:41:28] [Telldus Liv!e] Found 2 sensors in telldus live.
[2018-8-16 11:41:28] [Telldus Liv!e] Device 1513975707 has no name from telldus, ignoring
[2018-8-16 11:41:28] [Telldus Liv!e] Creating acc. ID 774082. Name from telldus: Framledning 11
[2018-8-16 11:41:30] [Telldus Liv!e] Initializing platform accessory 'Framledning 11'...
Setup Payload:
X-HM://0023ISYWYGKAF
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
[2018-8-16 11:41:31] Homebridge is running on port 51826.
Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘
Run Your Home App again and add Homebridge and the accessories will appear.
Then configure autostart at power on/failure with this post (systemd).
Restart the RPi
$ sudo reboot
and now all should be up and running.
If You are adding new devices You have to reboot the RPi for a new initialization.
If You also are having Z-Way devices here is a congfig.json for several plugins.
HB autostart at power on and failure, installed with a script !! , is found here.
Instructions updating the installation is found here
Comments
I had to manually configure the Nexa switches in config.json to get them to be recognized.
"unknown_accessories": [
{
"id": 12345,
"model": "selflearning-switch",
"manufacturer": "Nexa"
},
{
"id": 23456,
"model": "selflearning-switch",
"manufacturer": "Nexa"
},
{
"id": 78901,
"model": "selflearning-switch",
"manufacturer": "Nexa"
},
{
"id": 234567,
"model": "selflearning-switch",
"manufacturer": "Nexa"
}
]
Everything works fine, but i dont get the autostart to work.
The file looks like this.
# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
printf "My IP address is %s\n" "$_IP"
fi
su -c "screen -dmS homebridge homebridge" -s /bin/sh pi
exit 0
Have any idea about why it dont work?
Is there any way to expose it to the outside, so that I can use it while away from home?
God fortsättning!
https://timleland.com/setup-homebridge-to-start-on-bootup/
And here is the link to Homebridge github page where they discuss different ways to autostart homebridge on boot.
https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi
http://pysselilivet.blogspot.com/2017/01/homebridge-autostart-with-systemd.html
-----------------------------------------
{
"bridge": {
"name": "Homebridge",
"username": "CC:21:3E:E4:DE:33",
"port": 51826,
"pin": "031-45-154"
},
"description": "Configuration file for (e)xtended Domoticz platform.",
"platforms": [
{
"platform": "eDomoticz",
"name": "eDomoticz",
"server": "127.0.0.1",
"port": "8080",
"ssl": 0,
"roomid": 0,
"mqttenable": 1,
"mqttserver": "127.0.0.1",
"mqttport": "1883",
"mqttauth": 0,
"mqttuser": "",
"mqttpass": ""
}
],
"accessories": []
}
----------------------------------
Dock får jag ingen av mina accessories att initialize utan tvingas sätta samtliga under unknown_accessories. Alla är z-wave, vet du om det ska vara så? Är alla dina 433? Tack på förhand, Johan
However, I have two "locations" on the same Telldus account, the other one being in a completely different physical place (and different network too, of course).
Any ideas what would be the best way to get that one into HomeKit too? A second RPi at the other location? Or should I setup a VPN between the two local networks?
I see all the 2nd location remote switches in HomeKit but they are shown as "Not supported" at the moment.
I now have 1st location with [Tellstick NET, RPi w/homebridge, OpenVPN server], and 2nd location with [OpenVPN client, Tellstick ZNet Lite v1].
Works perfect for me (without any previous skills).
However I can not get my rain sensor (Oregon PCR800) and UV Sensor (UVN800) to work. Is it possible. It says not supported (stöds ej). However they work with tells and are supported on the tells live-homepage and app.
Any suggestions to fix it?
Many thanks!
Check the log when Homebridge is starting up and then manually configure, as done in the first comment in this post. That should help. /Mats
I'm having the exact same issue, that my 433 MHz Nexa switches are "Not supported" in the Home app. I'm pretty sure I've got the ID's right, and I've configured them as selflearning-switch.
Any ideas?
Bockar och bugar det ödmjukaste
Uffe
Har nå masse automasjon i hjemmet takket være innlegget ditt!
Takk igjen, Mvh. Kenneth - Trondheim
Är det bara config.json som skiljer sig? Föredrar du molnvarianten?
"unknown_accessories": [{ "id": 27, "model": "MODEL", "manufacturer": "unknown" }]
Valid models are: selflearning-switch, codeswitch, selflearning-dimmer, temperature, EA4C, temperaturehumidity, 1A2D, window-covering, switch
I have also tried to disable some of the devices, but i still get the same error.
Any idea??
Happy new year!
Post a Comment
Feel free to leave a comment ! ... but due to a lot of spam comments I have to moderate them. Will reply ASAP !