Welcome to Telldus API

Here you will find information and sample code for develop against Telldus Live!

In order to get started, please see our php example implementing the API.

You can also test the API right in your browser using the API explorer.

Database maintenance Wednesday, March 21st

On Wednesday, March 21st, Telldus Live! will switch over to a new database system. We don't expect any downtime, but it's a really major operation involving many steps with a lot of potential pitfalls. The switch itself will take place at 11:00 CET. We will then closely monitor all systems and fix problems that may show up. Follow us on twitter (@telldus_status) for the latest updates.

In a worst case scenario we might have to rollback to the state before the switch over attempt. In that case, editing made during this time would be lost. Also device logs (sensor logs are not affected) and new locations, schedules, events and accounts would be affected. Therefore we encourage you not to do a lot of editing of your setups this day.

We are doing this to increase database performance, but especially to have a more reliable failover design. Almost all other Telldus systems are using this database in one way or another, and it's critical that it's reliable.

SSL and https

We in Telldus take Security very seriously. As soon as information about the Drown and Poodle attacks on SSL was published, we started to examine the affects and the resolution to these issues.

With this message we would like to assure you, that apart from Security, user satisfaction is one key foundation defining how we work. This is also one of the reasons, we are delayed with the resolution. To deal with these vulnerabilities, we had the option to close down TelldusCenter and support you to instead setting up Telldus Live! via our new TellStick Gateways. That would mean swapping the old TellStick with Version 2 of our Gateway. This is in our opinion the best option for you who are using TelldusCenter, and in the process also get to the optimum security and feature set that we today have. In short, we want you to not be left behind but walk with us towards a safer, more secured Smart Home Solution as compared to the old version.

But we haven’t closed down Telldus Live!-access for TelldusCenter because we want to affect your running setups as little as possible, and keep your options open, therefore we chose to upgrade TelldusCenter. This is taking more time than expected due to the complexity and we are working hard to finalize these changes which we believe should happen shortly. Once done, these vulnerabilities will be removed.

In addition to this, we have also decided on a few other Security updates and restructuring, that would allows us to better separate servers that needs to remain open for TelldusCenter from the others. These upgrades will also allow us to turn on https as default for the Telldus Live!-web.

Update 2018-02-28:
As some of you have noticed, there is a difference between servers regarding what SSL versions they accept. We are only using api.telldus.com for TelldusCenter and that URL is now considered legacy. If you are connecting to our API using SSL, you should use pa-api.telldus.com instead.

Sensor values and device states in event actions

We have recently started testing the possiblity to include a sensor value or device state in mail/SMS/push/URL-actions. An early version is out on the servers now, and by manually adding keywords to messages it's already possible to test this for Telldus Live! Premium-users.

This is how it works:
If triggered by an sensor/device event, the triggering value can be entered into the mail/SMS/push/URL action message by adding [STATE] and [VALUE] into the message. For example:
"The temperature in the closet is now [VALUE] degrees, time to do something about that!" = The temperature in the closet is now 45.5 degrees, time to do something about that!
or
"The lamp in the attic is now [STATE]" = The lamp in the attic is now on

It's also possible to use the following keywords:
[SENSOR] = The name of the triggering sensor, useful if several sensors can triggers the same event
[UNIT] = Unit type for triggering sensor, for example "m/s" or "%".
[DEVICE] = The name of the triggering device
[TIMESTAMP] = The time the event triggered, useful if for example your push notifications gets delayed sometimes

[STATE] is transformed into "on" or "off" by default. It can be other things, for example:
"[DEVICE] is [STATE](locked/unlocked)" = Front door is locked
or for other languages:
"[DEVICE] är [STATE](påslagen/avstängd)" = Barsebäck reaktor 2 är avstängd
Note that only the states on and off are supported at the moment (not "dim" for example).

The message:

The temperature was [VALUE][UNIT] at [TIMESTAMP] .

...will produce:

Sensorvalue in event action

We are currently internally testing the possibility to specify a device/sensorid if it's not the value of the triggering device/sensor that is wanted, more information about this will follow.

Later on these keywords will of course be integrated in the UI on the webpage when adding an action.

Limitations and known bugs:

This is an early beta, so don't expect everything to work without glitches right away. All feedback is very welcome though!

Also, again note that this is only available for Telldus Live! Premium users.

Beta testers wanted to test Amazon Alexa integration with TellStick

Amazon Alexa devices let you play music, control your smart home, get information, news, weather, and more using just your voice. It's the part "control your smart home" that is interesting to us.

We are currently testing integrating Telldus with the Smart Home Skill in Alexa. This allows you to control all your devices in Telldus Live! using your voice!

"Alexa, turn off the livingroom lights." "Alexa, turn on the garden lights." ...

Well, you get the picture. You can even initiate Alexa commands with "Computer, ...". As of now there is no actual self destruct sequence however, but some day we'll get there.

To be able to participate in this test you need to own an Alexa-enabled device,  read more here

Sometimes beta software is not stable. If you (or your family) prefers to have a stable setup at all time, you might want to stay away from beta testing.

Please sign up here.

Update to mobile app beta

The closed tests for the new rewrite of the app is progressing well. A lot of issues has been found by the users and fixed by our developers. It's time for the next step, an open test!

As always. Beta software are not always stable. If you (or your family) prefers to have a stable setup at all time - you better don’t get into BETA testing.

iOS

This beta is currently a separate app being installed. Signup here:
 http://telld.us/iosbeta

Android

The beta test has been moved from a separate app to be a beta of the new app. Running the beta app and the stable app is no longer possible. Signup here:
 http://telld.us/androidbeta

Beta testers wanted for Telldus Live! mobile (iOS)

We are now finishing the re-write on our app and we need your help to test it.
Right now there are no new features. We've changed the framework used by the app and basically built it again from scratch.
We're now inviting iOS users to test the app. We really care about having active testers, make sure you have some time available to play with the app and to provide feedback.
Sometimes beta softwares are not stable. If you (or your family) prefers to have a stable setup at all time - you better don’t get into BETA testing.
Please sign up here.

Small update on sensor history



Just would like you to know that we just pushed a small design update to the sensor history.

Beta testers wanted for Telldus Live! mobile

We are now finishing the re-write on our app and we need your help to test it.
Right now there are no new features. We've changed the framework used by the app and basically built it again from scratch.
We're now inviting Android users to test the app. We really care about having active testers, make sure you have some time available to play with the app and to provide feedback.
Sometimes beta softwares are not stable. If you (or your family) prefers to have a stable setup at all time - you better don’t get into BETA testing.
Please sign up here.
Update: This beta test is now public. Sign up here:
 https://play.google.com/apps/testing/com.telldus.live.mobile

IFTTT to the people!

A while ago, we released our IFTTT channel for our PRO users. Now it's time to launch it for all our Live! users. With IFTTT, you can connect a variety of online services such as Spotify and Philips Hue with each other. The possibilities are endless.

Read more about IFTTT  here.

Telldus Live! in Norwegian

Finally! - Telldus Live! is now available in Norwegian!

If you see any strange translations, please let us know.

Philio (and D-Link) multisound siren

The Siren from Philio (PSE02) is sold as a multi sound device, but to make it play other sounds it has to receive a NOTIFICATION_REPORT. This report is normally sent out from a sensor such as a PIR or door/window-sensor. That means it's possible to e.g. play a Door Chime sound when a door/window-sensor is opened.
When sending a SWITCH_BINARY_SET (which is the default command that will be sent to this device from TellStick ZNet) will only make it play the default emergency sound.
In order to play other sounds, a NOTIFICATION_REPORT has to be sent out from TellStick - that can be done from a Lua-script.
We've put together a script that can send out the NOTIFICATION_REPORT when a device (or dummy-device) is turned on, it's available here:  https://github.com/telldus/tellstick-lua-examples/blob/master/zwave/Philio/Siren.lua

Looking for translators

Each day more people from all over the world are discovering Telldus Live! We want Telldus Live! to be as welcoming as possible for everyone. That's why we want Telldus Live! to be available in your language. Maybe you can help us with this? If you are interested in translating Telldus Live!, we can offer you a Pro subscription for a year, and continuing as long as you keep the translations up to date.

We are now especially looking for translations into Norwegian, Finnish and German, but other languages are also of interest.

Telldus Live! is already available in English, Swedish, French, Polish, Croatian and Danish.

If this sounds like something for you, please write to fredrik.gullberg@…

Release of Telldus IFTTT channel

We are about to release the IFTTT channel. It will hopefully be released at the end of next week, if all remaining tests performed by IFTTT will pass.

We will initially only release this for Pro users. Non pro users will have access to the IFTTT channel in may 2017.

FAQ:
Q: My triggers are delayed before they are executed.
A: This is due to how IFTTT works. IFTTT is requesting the status from our servers regularly. This means that the trigger can be up to one hour delayed.

Q: My sensor triggers are not triggered
A: To get sensor triggers to work the sensor must have history enabled on it. Try enabling history on the sensor first.

Q: My triggers are triggering twice
A: The triggers from IFTTT are requesting the device/sensor history. If the sensor have reported a value twice since last update the trigger will also trigger twice

Q: My sensor trigger is constantly triggering while the temperature is above the threshold. I am getting a lot of notifications!
A: For each value the sensor is over the threshold the trigger will continue to trigger. For a notification that only fires once, please use regular events instead.

Update: The channel is now released.

Use Aeon Labs Minimote

The Aeon Labs Minimote is a nice looking remote control for Z-Wave devices. It might be a little hard to understand the manual and the scenes and associations described though.

This remote control does not support normal association where the main controller can set the nodes in association groups. Instead this is done on the remote control itself.

The remote control can only control devices that uses Switch Multilevel and Switch Binary, that means most dimmer and most on/off devices.

To make this device control other devices set it up by following these steps:

  1. Include it into the Z-Wave network: Add a new device in Telldus Live! Press the Learn-button on the remote control
  1. Press and hold the button you like to configure - the blue led will flash after 1 sec.
  1. While still holding the button, make the device you want to control send out it's Node Information Frame. The blue led will stay steady blue.
  1. Set the dimmer level or the on/off-state you want the button to set.
  1. Release the button.

If patient then success. Finally Telldus+IFTTT=True!

One of the most requested features we get is to connect to the popular service IFTTT. For a long time we have tried to convince IFTTT to connect their awsome service with us. They never replied so we asked you, our users, to also ask them. Our plan was that when enough people requesting Telldus support they might listen. And they did!

We are very pleased to announce that Telldus is getting a channel in IFTTT!

What is IFTTT? IFTTT is a service that allows many different services to communicate with each other. That means Telldus products will be able to control any other service also connected with IFTTT. At the moment I am writing this IFTTT has support for over 300 channels. So at once you can combine Telldus products with Philips Hue, SmartThings, Netatmo, Nest, and more!

What can I do? You can do a lot. But here is some examples to get your imagination going:

Since we are still developing this channel we are not yet ready to launch it yet. But we would really like to have some testers. We have reserved 50 spots in a beta test for this. Since there is limited number of spots in this test they will be reserved for Pro users.

Push Notifications in Telldus Live mobile!

We are very excited to announce a brand new feature for the Telldus Live! mobile app: Push Notifications as an action to an event! Initially this is available only to Pro members, though will be released to all users after the summer. To add a push notification to an event, visit  http://live.telldus.com

Please contact our support if you encounter any issues or have questions about this or any other feature in our products.

http://developer.telldus.com/raw-attachment/blog/2016/05/30/push-notification/iphone-push-notification.pnghttp://developer.telldus.com/raw-attachment/blog/2016/05/30/push-notification/apple-watch-push-notification.png

Telldus Live! mobile app has been updated!

We are happy to announce an update for the Telldus Live! mobile app! Among some of the new exciting features is translations in Swedish and Norwegian, an addition we know will please many of our users, more translations are coming. After feedback from our users we have extensively developed the dimmer slider. Test it by pressing and holding on a button for a dimmable device in the dashboard or device list.

In the recent releases, including this one, we have focused a lot on the connectivity between the app and your TellStick. Your feedback has been very valuable and we encourage you to continue to give feedback on the app and all of our products. It all comes down to the fact that we want to give you the best experience so that you can reliably and conveniently interact with your Smart Home. We are continually investigating ways to improve the reliability of the connection, even if you are at home, in your summer cottage or laying on the beach in the Bahamas, you can be in control.

http://developer.telldus.com/raw-attachment/blog/2016/03/23/my_topic/IMG_2676.PNG

Telldus Live! in Polish

Telldus Live! is now available in Polish!

If you see any strange translations, please let us know.

Hide devices

We have just released a well requested feature, hiding of devices.

Many Z-Waves support multi channels. This means that one device may have several devices in Telldus Live! This is for instance in-wall receivers with dual relays, power strips and others. Sometimes you don't need all nodes a Z-Wave device may offer and those devices will then clutter the interface.

By hiding unused devices it is also possible to prevent controlling of sensitive devices by mistake.

For developers

A new api-call has been added, device/setIgnore. This works exactly the same as for sensors. Ignored devices are not returned by devices/list. Just as sensors/list there is now a parameter includeIgnored to retrieve all devices.

Use Fibaro Motion Sensor

The Fibaro Motion Sensor is a really nice and small PIR with additional temperature and light sensor.

The light and temperature sensor reports are turned off by default, to activate them you'll need to set configurations 42 to 64 to desired values.

To set the interval between light reports, set configuration 42:

To set the settings for temperature, set configurations 60 to 64:

Keep in mind that this is a battery operated sensor and that it will drain more battery to send sensor values more often. Select values so that you get the reports as often as you need them.

The temperature sensor report will only be sent if the temperature differs more than the value set in configuration 60. If the temperature is very steady and the value of configuration 60 is set to eg. 1 degree, the report will be sent very rarely.

The settings will not be sent to the sensor when you press save since it's sleeping most of the time. The settings will be sent automatically on next wake up or if you wake it up manually by pressing the button three times quickly.

Regarding the wake up time, this setting should be set to a low value when you are setting up the device in order for it to wake up often and receive new settings. But after that is done you should set it to only wake up rarely to reduce the battery consumption.

Merry Christmas!