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.

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!

Use Aeon Labs Key Fob

Aeon Labs Key Fob

The Aeon Labs Key Fob is a nice and small remote control for Z-Wave devices, it might be a little hard to understand the manual and the different modes it has though.
In order to make it easier to use, we've put together a small guide on how to include and configure this device.

The Key Fob can act as a Primary Controller if you don't have an existing Z-Wave network, but we will include it into the TellStick ZNet Lite Z-Wave network.
Start by add a new device in Telldus Live!. Use a pin or paperclip and push the learn button located on the back side of the Key Fob.
Give the new device a name.

Until now, the Key Fob has been in the Setup mode. Now we need to change the mode to Use Mode.
Use a pin or paperclip and push the learn button and the mode button for 3 seconds.
The LED will light up red for 3 seconds and then green for 1 second, confirming the mode change.

Since TellStick ZNet Lite does not support Z-Wave Scenes at the moment, we'll need to use the group mode to control devices.
Group mode is the default mode. To check the current mode, click on the device in Telldus Live!, click Edit device, Click Configuration, Click Advanced settings, check configuration number 250, it should be set to Group mode.

Now it's time to select a device to control from the Key Fob.
The device you wish to control needs to be included to TellStick ZNet Lite.
Depending on the mode of the device when it's paired with the Key Fob, the button will act as follows:
ON - Toggle the device
OFF - Turn off the device
DIM - Toggle dim on the device.
Press and hold the button on the Key Fob that you wish to use.
Start learn mode on the device. Please refer to the manual if you're unsure how to do this.
Release the button on the Key Fob.

If the device is controlled using the same button as start learn mode, you'll need to set the correct state before you start the learn mode.
Many switches start learn mode by pressing three times on the button that also controls the device.
When pressing three times, the status will also change three times. Make sure the device is OFF before starting learn mode if you want the Key Fob button to toggle the device.

Sensor data export, beta update

We are now introducing the ability to export sensor data for beta users. This is your data, so you should be able to do what you want with it. Head over to  http://live.telldus.com/sensor/index2, open up the sensor graph, update it with the interval you are interested in and press "Export range". The data will be exported to a CSV-file.

Just as in the graph we are at the moment limiting the exports to 5000 data points, but you can of course choose a new range and export again if not all data is included the first time.


The time is displayed as a unix timestamp. If you want to convert them to readable dates, you can use this algorithm for each timestamp, and then change the format of the cell to "date": =A2/86400+25569 (assuming the timestamp is in A2, this is tested in Libre Office, might be a bit different in Excel)

We know that this is a highly anticipated feature, and we hope you'll find it useful. If you discover any problems with it (it's still beta), let us know.

If you are not a beta user already, please sign up for all functions and consistent values: http://developer.telldus.com/blog/2015/03/24/sensor_history_beta

Sensor history, small update to beta

For you using the beta, we have now added a (very) basic time interval setting.

Just enter two dates to change the range in the graph. Right now we are limiting the data to a few thousand measure points, so you might not be able to view the whole selected interval in the graph. Since we are storing fewer data points further back in time (every third hour vs every 5 minutes), you might for example be able to see the graph for a whole year two years back, but only a few months back at a time if you start from today, since the number of data points is the same.

To access this function you need to use the new test version of the sensors-page, available at  http://live.telldus.com/sensor/index2

If you find any problems, except from design issues, with the graph or the index2-page (it should load much faster), please let us know.


Remembering those sweet summer days...

If you are not using the beta yet, it's still possible to sign up here: http://developer.telldus.com/blog/2015/03/24/sensor_history_beta

New products from Telldus

A while ago we announced our new platform. But we did not tell you that much about our upcoming products. It's now time.

Let’s start with the new generation TellStick. Before starting developing the new generation of products we really listened to you. We wanted to take the TellStick you love and make it even better. With almost 10 years of feedback from our community we have received many great ideas and suggestions.

Our new model of TellStick is named TellStick ZNet Lite. Just as TellStick Net this is a standalone unit that connects and is controlled from Telldus Live! We have included a Z-Wave chip so it can communicate with over 1000 Z-Wave certified products. Since many of you already have a home full of 433 products and switching everything to Z-Wave is nothing you do over night, we have also included a 433 transmitter. This means you can still control all your existing 433 products and still leverage all the benefits from new Z-Wave products.

We know some of you don't always have a stable internet connection and relying on a steady connection is not always possible. That is why TellStick ZNet Lite runs all schedules and events offline. That means that even if you lose internet connectivity the schedules and local events will still run as nothing happened. Skipping the extra roundtrip to the servers also makes them a lot faster. With Z-Wave being a faster protocol than 433 to begin with, the events really come to their full potential when they are run locally.

We will also release another model, called TellStick ZNet Pro. This one has all the features from TellStick ZNet Lite and we have also included a 433 receiver to receive signals from 433 sensors. It is as easy to control as the TellStick ZNet Lite, but is also perfectly suited for all you hackers out there. With this model you will be able to run your own plugins and code directly on the device.

This products is aimed to be fully hackable.

Both TellStick ZNet Lite and TellStick ZNet Pro are, with a built in web server, prepared for local control in the future.

In addition to our new gateways we are also releasing our very own Z-Wave On/Off receiver and a door/window sensor. Just as the gateways, both hardware and firmware are developed and designed by ourselves, so that we have full control of all functions.

Edit: Available for preorder at m.nu here:  https://www.m.nu/telldus-znet-lite-forhandsbestallning-preliminar-leverans-september-p-2341.html

Telldus Z-Wave beta 1

We are looking for testers for one of our Z-Wave based TellStick. This is not the final hardware and might be disabled when this test is complete. After this test period, an upgrade program to the final hardware will be available.

This TellStick has the following specifications:

We are looking for testers for the software and platform. These are our requirements:

After signing up please send an email to mp@… and motivate why you should be accepted in this test.

There is only 4 pieces available for this test so be sure to motivate well why you should be chosen.

Interested? Please sign up.
THIS BETA IS CLOSED.

We are enhancing Telldus Live!

With a guide it will be easier and clearer

More and more devices are supported in Telldus Live! We think that is very pleasant! But at the same time it has made it somewhat difficult to identify the correct accessory that you want to add to your smart home system. That is why we have made a completely new guide.

This enhancement means that you will identify your device much easier by brand and pictures of each device. In the last step you will get a step-by-step guide of how to install that specific device into your smart home system. So now you can almost skip reading the the manual how to install the device.

Just follow the guide in Telldus Live! and you will make no mistakes.

Sensor history - Beta

One of the most requested features is the possibility to view sensor values over time. Did the temperature at any point go below 0°C last night? How much does the temperature in my fridge fluctuate? How humid was it in my basement in August compared to June?

We are now launching a closed beta where you can follow your sensor history. Sensor history is mainly a Pro-feature, so while the stored values are only saved every 10 minutes and kept for 2 hours for non-pro-users, they're stored much longer for Pro-users. For Pro-users, incoming values are saved with 5 minute intervals for one month, 15 minute intervals for three months, 1 hour intervals for a year, and every third hour a value is stored with no expiration date at all. These limits may change in the future. In the beginning of the beta it will however only be possible to view values from a week ago in any case.

Temperature, humidity, rain and wind values are stored. The total rainfall and wind direction is not presented in a sensible way yet, but it's kept for future use. For Z-Wave, power consumption and luminescence sensors are also included.

If history should be kept or not is set per sensor and is off by default for all new sensors. Max and min values are recorded for all sensors though.

If you are interested in joining the beta please note this first:



Interested? Please sign up here.
[EDIT] Since all beta slots now is taken, it's possible to access the sensor history beta by navigating to:  http://live.telldus.com/sensor/index2 to activate/access the sensor history without applying for a beta slot.

Introducing battery status

Many sensor models report their battery status (for example Oregon Scientific and Mandolyn). In an upcoming server upgrade we're starting to show this in Telldus Live! for sensors reporting it to TellStick Net. An icon to the right indicates the status.

Typically "battery low" is reported when there is 10% capacity left in the battery, but how much longer the battery will actually last is totally dependent of the sensor type.

There is no event associated with low battery.

This is a slow rollout, so you'll see the battery status depending on if the server your TellStick Net currently is connected to is updated or not.


For developers

The battery status is now also included in the sensor/info and sensors/list API call. Possible values are:
0-100 - percentage left, if the sensor reports this
253 - battery ok
254 - battery status unknown (not reported by this sensor type, or not decoded)
255 - battery low

At the moment, all supported sensors only reports "low" or "ok". The percentage left is reported by some Z-Wave devices however and will be used in the future.

Telldus next generation. A new chapter begins

For the last two years we have been working hard on the next generation of TellStick and accessories. It is time for us to present our next step.

One of Telldus main philosophies is that we don't want to lock our users into a one company closed down solution, limiting what products to use and how to extend it further. This thought is the foundation of the TellStick family. We want the user to be able to reuse the products in their home and freely choose what products to purchase to extend the smart home. When we started to work on the TellStick over eight years ago the (Swedish) market consisted nearly exclusively of 433 MHz products. Therefore the choice for communcation in the first TellStick was easy.

Some years have since then passed and the market has evolved. The needs are no longer the same as it where. We have thoroughly followed the development of the "Smart Home" and "Internet of things" areas to find out what the best next step is for Telldus. We still strongly believe that interopability is the key. We will never be able to solve everybodys needs ourselves. Instead we want you to freely choose between different vendors and products.

Therefore, we believe, the next step for us is Z-Wave.

Let us first explain what Z-Wave is and what it can do for you.

Z-Wave is a communication standard developed by the company Sigma Designs. Sigma Designs does not develop nor sell any own products. Instead they focus on the communication technology and let other companies use this standard for their products. In order for a company, like us, to be able to use this standard we must also guarantee compatibilty with all other producs on the market also using Z-Wave.

Different companies specialize in different areas. Z-Wave allows all these to talk the same language and communicate each other. Each company can focus on their area of expertise and what they do best, thermostats, garage port openers, or water leakage detectors.

This is one reason why we strongly believe in Z-Wave.

Another benefit is that Z-Wave has two way communication. Any command sent will be acknowledged by the receiver, ensuring the command actually was received by the receiver and resend the signal when needed. The receivers themselves can also act as a repeater and repeat the signal and extending the range even further.

Since about a year Telldus has been a member in Z-Wave Alliance. Z-Wave Alliance is a cooperation between the companies developing Z-Wave products. It aims to help companies ensure the interoperability between all the products using the Z-Wave logo.

What about the 433 MHz products, you may wonder?

We still believe in 433 as well. The 433 products are more affordable and easier to find in the market. For a lot of applications there is no need for Z-Wave. We will continue to support 433 and we are working on products with both 433 and Z-Wave. This way you will be able to mix and match what products fits you the most. And you will be able to use 433 and Z-Wave together in your home.

We have been developing both next generation TellStick as well as new accessories. We are now ready for testing and we will soon start looking for anyone wanting to help us test our new system and new products. Please keep an eye on this blog for beta-announcements in the near future.

Holiday tips for sensor events

We get a lot of questions on how to use sensors in events. I would like to take the opportunity to clear out some common misconceptions.

First of all, when you add a new sensor trigger, it will never trigger right away. Let's say you add a sensor trigger that triggers below 10 degrees and your sensor is currently 5 degrees. You sensor must first go above 10 degrees once before it will ever trigger.

The sensor trigger and sensor condition has an option to set a temperature equal to a temperature. In reality this is rarly the case. Let's say you have a sensor trigger that equals 20 degrees. When your sensor goes from 19 to 21 degrees it might never be exactly equal to 20 degrees. One sensor report might send 19.9 to TellStick Net and the next 20.2. In this example the trigger will never trigger.

If you run into trouble and need support, we are here for you. To help us help you there are some things you can do to give us the required information to follow your events. If you want help with your events, please include this in your report:

This is an example how your report could be:
Hi Telldus
I have some troubles with my event xxx. The sensor zzz is used to turn my heater on when the temperature is below xx degrees. Last night at about XX:YY the temperature dropped below xx degrees but my heater didn't start. Could you help me figure out what is wrong?

Another common way to use the events together with sensors is to control a heater. Some of the questions we get is how to add events to control the heating at a certain level during the day and another during the night. I will try to explain how to do this and why.

In this example we have one temperature sensor and one TellStick controlled heater. We would like to have the temperature at around 20 degrees during the day (08:00-23:00) and 15 degrees during the night.

First, start by creating our first event. We call this "Day - Heater ON". We need a sensor trigger that triggers on the temperature. Add a sensor trigger that triggers when the temperature goes below 19 degrees. This event is only used during the day so we will add a time condition between 08:00 and 23:00

Next we need an event to turn off the the heater ("Day - Heater OFF"). This is similar to our previous event:
Trigger: Sensor above 21 degrees
Condition: Time between 08:00 and 23:00
Action: Turn heater off

The reason we do not set the sensors trigger level to 20 degrees is because the triggers rearm boundary. You can read more on this in our previous blog entry.

For the night we add two similar events: Night - Heater ON
Trigger: Sensor below 14 degrees
Condition: Time between 23:00 and 08:00
Action: Turn heater on

Night - Heater OFF
Trigger: Sensor above 16 degrees
Condition: Time between 23:00 and 08:00
Action: Turn heater off

So far this is quite simple. The problem arrives if the temperature is not within the interval when we are switching from day to night or vice versa. Lets say the temperature is 17 degrees at 07:59. The heater will be off due to the event "Night - Heater OFF". When the time is 08:01 the heater will still be switched off since there is nothing to turn it on again. The temperature will continue to drop and the heater will not be turned off. To solve this we need to add another trigger and condition to our events.

In the event "Day - Heater ON" add a time trigger at 08:01 and a sensor condition on the sensor must be below 19 degrees. The event should now look like this: Trigger: Sensor below 19 degrees OR Time is 08:01
Condition: Time between 08:00 and 23:00 AND Sensor is below 19 degrees
Action: Turn heater on

Now this event will take care of both scenarios. We need to add the same to the night. Event "Night - Heater OFF"
Trigger: Sensor above 16 degrees OR Time is 23:01
Condition: Time between 23:00 and 08:00 AND Sensor is above 16 degrees
Action: Turn heater off

To use AND in conditions you need a  Pro account. If you don't have a Pro account it is still possible to achieve the same results, but you need two extra events. For non-Pro users. Your setup should be configured like this:
Event: "Day - Heater ON 1/2"
Trigger: Sensor below 19 degrees
Condition: Time between 08:00 and 23:00
Action: Turn heater on

Event: "Day - Heater ON 2/2"
Trigger: Time is 08:01
Condition: Sensor is below 19 degrees
Action: Turn heater on

Event: "Day - Heater OFF" Trigger: Sensor above 21 degrees
Condition: Time between 08:00 and 23:00
Action: Turn heater off

Event: "Night - Heater ON"
Trigger: Sensor below 14 degrees
Condition: Time between 23:00 and 08:00
Action: Turn heater on

Event: "Night - Heater OFF 1/2"
Trigger: Sensor above 16 degrees
Condition: Time between 23:00 and 08:00
Action: Turn heater off

Event: "Night - Heater OFF 2/2" Trigger: Time is 23:01
Condition: Sensor is above 16 degrees
Action: Turn heater off

Device state history beta, continued

Device state history is now open for everyone. It's still beta, so all reservation in the previous blog post still apply.

We have also, as requested, added information about where the device state change came from. From where was the device controlled? Was it perhaps an incoming signal, a schedule or an event? Or just controlled from the web interface?

We also wanted to mention another small, but often requested feature that we have added today. It's now possible to see from which IP address your TellStick Net is connected (or last connected if currently offline). Click your TellStick Net in the "My Locations" tab to see the IP.

Introducing device state history - Beta

Since "My Events" was introduced in Telldus Live!, the most requested feature is device and sensor logging. We have tested different storage systems for a while now (it's a lot of data), and have decided on the Cassandra database.

Device state history means that you can for example view when your devices were turned on or off, dimmed, a bell chimed or blinds pulled up or down. The device history shows the state changes no matter if they were initiated from Telldus Live!, a 3rd party app or if the signal was received from a remote or a motion detector.

We are still evaluating the long time performance of the storage solution, but for device logging the data and functions are already in place, so why not make it available? In the first phase this will only be available for Telldus Live! Pro-users. After evaluating this, it will be introduced to everyone. If you are a Pro-user you can try it out now right away by opening up a device in Telldus Live! and click the "Show log history"-button (for TellStick Net)! Later on, when not limited to Pro-users, there will be a "Log"-button directly in the device list if you have a TellStick or TellStick Duo with a TelldusCenter connected to Telldus Live! .

If you are a developer, a new API-call is available:

device/history

This can be accessed by non-Pro users too already.

This is a beta, and since we are still testing the storage system there is no redundancy yet, so data may disappear if something fails. Don't count on the device log for anything very important.

We would like to know what you think of this. Please post comments below. For example, the device logs are currently kept for one week. Is that sufficient? Or too much? Should it be possible to clear device logs, and why? Is it important to be able to decide which devices are logged? Do you want to be able to export this data? In that case, how? Suggestions for other ways to view the logs besides this list are also welcome. Now is a good time to influence the upcoming development.

Sensor logging? Yes, we are planning for that too. But it demands even more from the storage system, completely new functions and the data must be presented in different ways, e.g. graphs, so it will not be available for a while. And sensor storage for more than a couple of hours will require a Pro account.

Hope you find the device state history useful!

Pebble app for Telldus Live!

During the christmas holidays one of Telldus employees started a project to use his new Pebble smartwatch to control the lights from a TellStick Net. Currently it only supports on and off.
The code is located here:
 https://github.com/mickeprag/telldus-live-pebble
Are you developing Pebble apps? Help out and extend this with more functionality.

It has been uploaded to the comming Pebble appstore and will be available once 2.0 of Pebble OS is released. If you already have 2.0 installed and don't want to wait you can download the app below. You need at least beta3 installed on your phone. Currently only Android have been tested.

Please note that this app was developed by Telldus Technologies employees during their free time and is not officially supported by Telldus.

Sensor triggers and rearm boundaries

We have added some extra options to fine tune the sensor triggers in Telldus Live! events. I want to take this opportunity to explain how sensor trigger works.

Sensor triggers are only activated when a threshold value is passed. It will only be activated once and not repeated while the sensor value is still exceeding the threshold.

To avoid that the trigger is triggered many times while the value swings around the threshold there is also a rearm value. Before a trigger can be activated again the sensor value must pass the rearm value. This value was previously fixed to one degree over and under the trigger threshold value. This is demonstrated in the following figure. This shows a sensor trigger set to trigger when the temperature reaches over -21,5 degrees. The rearm values are set to -20,5 and -22,5 degrees.



This shows an example where the trigger will not be activated even though the sensor value passes the trigger threshold.

We have now added an advanced setting to sensor trigger where you could set this value between 0,1 and 15 degrees if you need to fine tune this for your sensor. For most users the default value of 1 degree is suitable.