Behind the scenes we have been working on a new version of Telldus Live!. We have had the vision to create a better and more up to date web interface for quite a while, and while releasing many new features in the app during 2018, we have been simultaneously working on the new web. We now invite you to try it out!

The new interface is responsive and although mainly intended for desktop it works perfectly for tablets and other mobile devices as well. It may also give some hints of cool features to come...

For the development we are using variations of React (​React and ​React Native) for both Telldus Live! v3 and the app. This way we can offer new features for both the app and the web in a much easier and faster way than before.

Telldus Live! v3 is a work in progress and many features are still not available. But as we continue the development you are very welcome to try it out and tell us what you think. We value your ​feedback!

Telldus Live! v3 is currently only available to test for our Premium users. Go to ​https://live.telldus.com/v3/beta to take it for a spin!

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:

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:

• Keywords cannot currently be directly followed by a dot (.)
• Only the device states on and off are available at the moment

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.

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 [[beta:9 sign up here]].

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

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 [[beta:8 sign up here]].

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 [[beta:7 sign up here]].
Update: This beta test is now public. Sign up here:
​https://play.google.com/apps/testing/com.telldus.live.mobile

Previously we hinted about more hackability and features in our new generation TellStick. It is now time for the next step, plugins.

With plugins you will be able to extend the functionality of your TellStick even further.

TellStick already supports a great amount of both Z-Wave and 433-devices already, but it is possible to integrate other types of devices available over the network. How does support for Philips Hue, Netatmo, Sonos, and Eliq sound?

We are ready for real world testing of plugins for TellStick ZNet Lite (v1/v2) and TellStick Net v2 and need you to help us test it.

The beta test is open for Pro users only. [[beta:6 Sign up here]].

Do you want to develop your own plugin? Please ​contact us and we will help you setup.

Initially we have created the following plugins for you to test.

Import ​Eliq energy data into Telldus Live!	Plugin that allows you to control ​Lifx bulbs.
Send emails from lua scripts	Use ​Netatmo weather station in Telldus Live!
Control ​Philips Hue lights	​Pushover makes it easy to get real-time notifications on your Android, iPhone, iPad, and Desktop (Pebble, Android Wear, and Apple watches, too!)
Plugin that allows you to control ​Sonos speakers	Plugin to control ​Logitech Squeezebox from TellStick
Plugin that allows you to control ​TP-Link HS100/HS110	Plugin to read status from a ​Verisure Alarm
Control ​WEMO Insight	Import weatherdata from the current location from ​yr.no

How about the source code for the plugins? It's available here:
​https://github.com/telldus/tellstick-server-plugins

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:

• When an astronaut enters space, ring my bell.
• When I plug in my phone to the charger at night, turn off all lights in the house.
• Log my sensor data to a Google spreadsheet.
• When someone rings on my doorbell, tweet about it.
• When I leave home, lock my door.

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:5 beta test]] for this. Since there is limited number of spots in this test they will be reserved for Pro users.

Our [beta:4 beta] tests for TellStick ZNet Lite is going well. Most of the known issues has been fixed so it is time to invite everyone to this test.

Since version 1.0.8 in TellStick ZNet Lite the local API is included by default. Please note that this is still in beta and anyting can change before the final version.

The documentation for the local api can be found here: ​https://tellstick-server.readthedocs.io/en/latest/api/intro.html

We have tried to mimic the same API as the Telldus cloud API. This to help you port any existing application. The documentation for the individual calls can also be found in Telldus Live! api explorer found here: ​http://api.telldus.com/explore/index

The user matzh have started a forum thread that you may follow and discuss this. ​http://www.telldus.com/forum/viewtopic.php?t=5887

Have fun!

When we announced TellStick ZNet Lite we told you that the device was prepared for local control.

We have been working on this and it is now time to start testing. We want the input from all you developers out there.

We have prepared an early beta firmware with the local api activated. If you want to help us evaluate this and give your input to us, please sign up for this [[beta:4 here]].

This is a closed beta for now since a custom beta-firmware must be loaded into your TellStick ZNet Lite.

A public beta might be released in an official firmware at a later stage.

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

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

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:

• Z-Wave EU controller
• No 433 MHz is available
• Requires an internet connection

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

• You need to have your own Z-Wave accessories since we have no possibility to supply this.
• We expect a report at least once a week on your experiences.

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.

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:

• Beta is only available for Pro-users
• The sensor history might be purged without warning if necessary for development reasons
• Beta users will be using a completely different storage system for all sensor values, and even if the system has gone through a lot of testing there might still be issues that could effect ordinary sensor viewing or event executions. If you got important sensor events the beta perhaps isn't for you. However, it's always possible to change back to non-beta, should there be any problems.
• The sensor values in Telldus Live! are right now only viewable from the last week, even if there actually might be history stored from a year back. They are displayed in a very rudimentary graph right now (see picture below), where scales or time frames cannot be set. But it's possible to access all history using a new API function.

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.

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.

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!

This is the first, and hopefully last, release candidate for TelldusCenter 2.1.2. There are only a few changes, compared to the beta versions. The only major one is concerning callbacks in Linux/Mac that sometimes stopped functioning earlier.

The only other noticeable addition is support for the Oregon Scientific pool thermometer (THWR800) in TelldusCenter.

See earlier blog posts for a list of all new features in TelldusCenter 2.1.2:
http://developer.telldus.com/blog/2013/11/25/tellduscenter_2.1.2_beta10
http://developer.telldus.com/blog/2013/10/02/tellduscenter_2.1.2_beta8
http://developer.telldus.com/blog/2013/05/23/tellduscenter_2.1.2_beta1

HOW TO INSTALL

WINDOWS

Download here:
​http://download.telldus.com/TellStick/Software/TelldusCenter/beta/TelldusCenter-2.1.2_rc1.exe

MAC

Download here:
​http://download.telldus.com/TellStick/Software/TelldusCenter/beta/TelldusCenter-2.1.2_rc1.dmg

LINUX

Follow the instructions here: http://developer.telldus.com/wiki/TellStickInstallationUbuntu but instead use this Apt-line:

deb http://download.telldus.com/debian/ unstable main

If you have had a 2.1.2-beta installed before, please run this instead:

apt-get update
apt-get clean
apt-get install libtelldus-core2 libtelldus-gui2 tellduscenter telldus-core --reinstall

Available for: i386, amd64, armhf (#229) and armel (telldus-core only, compiled for Excito b3 this time, please test it)

Tested on Ubuntu 12.04 (i386/amd64), Debian 7 (i386, amd64, armel and armhf (raspbian))

The new functions in TelldusCenter 2.1.2 beta are now available for Windows and Mac.

New functions since the old beta (2013/05/23/tellduscenter_2.1.2_beta1) are:

• Support for wind/rain sensors for Oregon Scientific version 3 (WGR800 and PCR800)
• Support for Oregon Scientific THGR810 and THGN801 (#284)
• Support for RollerTrol blinds (#310)
• Possibility to send sensor values to Telldus Live! (#186)
• (Windows only) Possibility to upgrade TellStick/TellStick Duo firmware from TelldusCenter (no need to shut down the service when upgrading from there)

This version is already available for Linux, | beta 8, with the exception of the firmware upgrade utility inside TelldusCenter.

• New firmware for TellStick Duo (version 12):
• Support for some Oregon Scientific version 3 sensors (see above)

Download from here: ​http://download.telldus.com/TellStick/Software/TelldusCenter/beta/TelldusCenter-2.1.2_beta10.exe (windows) ​http://download.telldus.com/TellStick/Software/TelldusCenter/beta/TelldusCenter-2.1.2_beta8.dmg (mac)

As usual, let us know of any bugs and problems. It's still a beta.

This beta release adds support for some Oregon Scientific version 3-sensors, for example THGR810 and THGN801 (WGR800 (wind) and PCR800 (rain) are also received in this firmware, but they are not yet handled correctly in the Telldus Live! interface).

If you have other Oregon Scientific 3-sensors that are received with this firmware, please let us know, since it's not always clear which models share the same sensor identification.

Download the flasher here:

​http://download.telldus.com/TellStick/Software/TellStickNetFlasher/beta/TellStickNetFlasher16.zip (windows)

​http://download.telldus.com/TellStick/Software/TellStickNetFlasher/beta/TellStickNetFlasher_v14.dmg (mac) (It's the same firmware version actually, despite the name. The "14" is just there to add to the general confusion.)

For additional information about this beta firmware, please see 2013/04/17/tellstick_net_beta_firmware

November 4th is approaching fast. We still have time for another update for Telldus Live! events though.

New features are:

• Repeats on all device actions.
  This is similar to the scheduler. Some devices might need the signal to be repeated several times for it to turn on or off. The repeat option is under "Advanced settings".
• Offset for suntime condition.
  If was only possible to set an offset for sunset trigger previously. Now this is also available for suntime condition.
• Pause an event.
  If you do not need an event but don't want to remove it, it is now possible to inactivate it instead.

There is also a lot of minor fixes for different browsers, form validation, default email address, and other things to make it work more smoothly for everyone.

We appreciate all your feedback for events. It you find a bug or have a new idea, don't hesitate to contact us!

We are still busy implementing a lot of new features for Telldus Live! events, but we want to push what we have so far so that you can try them out while the events are still in beta.

Some of the new features are:

• Delays on all actions.
  It is possible to delay the execution of an action. You can for instance create an event that turns a device on and in the same event also add another action to turn off the device 30 seconds later. To access this feature you need to add the action as usual and then edit it. The delay is under "Advanced settings".
• Block heater trigger ("motorvärmare" in Swedish).
  This is a new trigger used for turning on a block heater depending on the outside temperature. We use an algoritm based on the Swedish Energimyndigheten's recommendations. We would like to thank Roy Henriksson and his son for helping us with this.
• Trigger and condition on humidity.
  It is now possible to both create a trigger and condition based on the humidity on a sensor. It was unfortunately only possible to use the temperature before.
• Update minimum repeat interval.
  After an event has been activated there is a 30 seconds delay before the event can be activated again. This is to prevent for instance motion sensors that sends updates for several seconds to flood actions. Without this an event could be executed up to ten times within a couple of seconds. Sometimes you might need to lower this limit and sometimes you might need it to be even longer. We now allow you to edit it to fit your needs. You can find this setting under "Advanced setting" where you edit your event.

We appreciate all your feedback for events. It you find a bug or have a new idea, don't hesitate to contact us!

We're happy to announce a TelldusCenter 2.1.2 beta for Linux too.

In addition to the functions described in the previous blog post about the beta, http://developer.telldus.com/blog/2013/05/23/tellduscenter_2.1.2_beta1, we have also added:

• Support for wind/rain sensors for Oregon Scientific version 3 (WGR800 and PCR800) (new firmware needed, it will be posted here later on, but send us a support ticket for now if you are interested in trying it out)
• Support for Oregon Scientific THGR810 and THGN801 (#284)
• Support for RollerTrol blinds (#310)
• Possibility to send sensor values to Telldus Live! (#186)

A new beta with these functions will also be released for Windows and Mac.

HOW TO INSTALL
Follow the instructions here: http://developer.telldus.com/wiki/TellStickInstallationUbuntu but instead use this Apt-line: deb http://download.telldus.com/debian/ unstable main

Available for:
i386, amd64, armhf (#229) and armel (telldus-core only)

Tested on Ubuntu 12.04 (i386/amd64), Debian 7 (i386, amd64, armel and armhf (raspbian))

Known issues:
TelldusCenter sometimes still segfaults on some platforms
TelldusCenter may stop automatic update of sensors and device state

We are still working on these issues, and if you run into them, or other problems, please let us know your system setup and, if possible, how to reproduce them.

Do you want to let a bell sound when the temperature in your fridge gets too high?
Do you want an email when someone trigger a motion detector in the office?
Or do you just want to turn on the outside lamp when the sun goes down, but only if its later than 23.00 and the backyard door is open?
Of course you want to!

We are finishing the event system for TellStick Net. Some of you have already been trying the system during the development phase. We are now ready for a more extensive beta.

Anyone with a TellStick Net can take part in this beta test. We will open this up to 100 users or until October 1st, whatever happens first.

What are you waiting for? [[beta:1 Sign up here]].

Update: We now have a release date.

We have just released the API for accessing our events in Telldus Live!

This is currently only open to the same beta group testing out the events. You can read more about this in its own blog post.

Head over to the ​API explorer and check it out!

It's time again for a new beta test. This time we are looking for testers wanting to try out events from TellStick Net. This means you can for instance trigger action upon temperature sensors and device state change.

We are going to test this in several steps. Right now we are only looking for developers. To qualify this round you need an application using our API. If you want to participate, please see below.

Applications using the development key will unfortunately not qualify at this time.

Update: We are now accepting any developer to try this out. To participate, email mp@… with the name of your application, a description of what the application does and screenshots.

Update 2: Anyone will now qualify for this test. [[beta:1 Check it out!]]

We are finally ready for beta testing of device event reception and remote control scanning in Telldus Live!

We need your help to test the following in the web interface:

• Scan remotes (and motion detectors and magnetic switches) (#118)

• Live updates of sensor values (has been active for a while now) and device state when TellStick Net receives an incoming signal.

We are interested in having this tested on different platforms and different browsers, and we want you to look for bugs and have opinions about the UI. We will also monitor the impact this may have on the server performance.

This functionality is only accessible from Telldus Live! on the web, not in the API.

If you are interested to try this out, post a comment below and we'll pick out some of you and activate beta access. We'll not add any more beta testers at the moment.

We are working on a new application for mobile phones. We are currently in the state where we need beta testers. If you are interested in testing our new app, please leave a comment below with the model of your phone.

We will pick out a handful of testers and let you know how to participate.

Edit: Thank you all for your interest. We have not enough testers now. Please do not forget to send your feedback to feedback-1.0.1@…. Don't forget to include the model of your phone in the report.