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:


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!


1. s c <simonchorley@…> -- 2014-05-12 19:32

Great stuff.

It would be useful to have more information, like where the command came from. This would help with error finding. Logs for events would also be useful to see the trigger. Even a raw log for every thing at a location would be useful for understanding what triggered what.

2. geir solem <geir@…> -- 2014-05-12 21:52

Looks very good. Export function would be good, preferably to csv. Auto-export or upload to ftp would also be nice, even if I could of course use the API for this.

3. s c <simonchorley@…> -- 2014-05-16 01:16

1 Clearing a log = Because you move the sensor or get results that throw out the mean or scale of a graph.

  1. If you make logging an option for each device/sensor you will not have to collect too much information.
4. håkon svendsen <haakon.svendsen67@…> -- 2014-08-29 11:41

Very good. I've just used the log and found that I need to set a bigger "cooldown-limit" on one of my events -> Less traffic on you servers I guess :)

It would be nice to be able to export selected logs, and it would be good to be able to unselect devices. I.e. I personally don't care how often the lamp in my bathroom goes on and off (although Sheldon Cooper might need that), but I would like to have statistic of when my dehumidifier in the basement starts/stops.

If I could select which devices I want to log, and skip the rest, it might mean less diskstorage for you.