It's been a while since we last did a release of our Android/iOS app.
We've been working hard for a long time to re-write it from scratch and that hard work is finally finished.
We are now releasing a new version of the app! The new version (3.4) is written in a new framework (React Native).
It’s very similar to the old app (2.0.10) regarding features, but React Native makes it a lot easier to add new ones later on.
We will start the beta testing of version 3.5, with some nice new features, soon after the release of 3.4.
If you are interested in being a beta-tester, please read more at: ​http://telldus.com/development/

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.