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! Pro-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! Pro users.

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.

These types of reports should always be treated seriously. It could be a sign that one of your devices on your network is infected with a malware.

tl;dr

If you aren't interested in the technical description below you can safely ignore this warning. The warning is a false positive.

The technical…

Upon inspection of the captured packets, the IP address reported (193.11.114.43) was not found in the communication of the gateway and the Internet, suggesting the infected source was not on the gateway.

Upon further inspection on the frequent traffic, it was found that NTP accounted for most of the traffic when the gateway is in idle mode. Cross checking with the search results on Google on this IP address indicated it once belonged to the pool of NTP servers under pool.ntp.org.

Querying the IP address via NTP Statistics confirms this IP address was indeed part of the ntp pool machines.

However, a reverse DNS lookup on the same IP yielded a different domain name: tor1.msfnet.se.

The ASUS AiProtection works by querying a third party service (WRS database provided by Trend Micro™) on a suspicious IP address to determine if it is a malicious host.

Looking from this case, it is reasonable to believe either ASUS or Trend Micro uses reverse DNS lookup for the domain name and match it with the list of malicious hosts. In practice, since domain names can be binded to different IP addresses at different time intervals, the IPS mechanism shall not only rely on domain names but also verify using the IP address for malicious host detection in order to reduce false positives.

In conclusion, the IP address that was associated with a malicious web site was being reused as one of the NTP machines in pool.ntp.org for serving network time, the reverse DNS lookup still shows that IP address is being associate with the malicious web site, thus triggering a false positive in the AiProtection mechanism, resulting in the security alert given from the ASUS router. To mitigate, suggest user to report to ASUS on this false positive, and if the router have a whitelist function, add this IP address to the whitelist so that the router will stop generating alerts for this IP address.

We've just pushed Lua scripts to enable controlling different sounds on the sirens from AeonLabs, CoolCam and Philio (and also D-Link that is same device as Philio) from dummy devices. The siren()-function can of course be used in other ways as well.

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

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.

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

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.

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@…

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.

Last year we announced two new TellStick. One to be released shortly after the announcement and one to be released later (at an unkown date). The first one (TellStick ZNet Lite) was release but the second (TellStick ZNet Pro) has still not yet been released. Let us explain what has happened since the announcement what the current roadmap looks like.

Let's first start with some history.
When we decided to work with Z-Wave we needed some new hardware because TellStick Net cannot support Z-Wave since it lacks the required radio hardware.
We wanted to create two new TellStick. One with a good price that would fit most of our users and one for our (hard)core users, a.k.a. "the hackers".
To create an affordable product you need to compromise with the hardware. To keep the cost down you cannot add a lot of flash, ram, cpu and other goodies. Instead you need to keep it to what you really need and then optimize the software for this. This kind of product is not ideal for hackes since it can be quite limiting. This is the reason we started working on a Pro model. A model with more CPU, more flash, more RAM, and more other fun hardware upgrades that would benefit hackers.

At the announcement last year the Lite model was almost finished. We were ready to start selling but the Pro model was still on the drawing board. Some prototypes where made but not more than that. Since the development was in such early state we could not give you an estimated time for when TellStick ZNet Lite Pro would be released.

During the year we have trying to find a manufacturing partner for TellStick ZNet Pro. We found that all the goodies we put into the product made it either too hard to produce or to costly. The end price was going to be way to high.

A common misconception was that the difference between TellStick ZNet Lite and TellStick ZNet Pro was that Lite hade only 433 transmitting and Pro had both receiving and transmitting. Even though this is true it was not our goal.
We believed the users for the new gateways where users wanting to fully adopt Z-Wave. Since we could add 433 transmitting without affecting the end price too much we thought it was a good idea to add that as well.
We where wrong. You clearly wanted both Z-Wave and full 433 receiving and transmitting!

So, we needed to rethink.

First we needed to upgrade TellStick ZNet Lite with receiving 433 capabilities. We will release an updated version in September or October or November 2016.

Secondly, since we have developed both 433 receiving and transmitting for TellStick ZNet (which is a completely different hardware platform from TellStick Net) we got an idea. We removed Z-Wave from it and will release it as an upgrade to TellStick Net.
TellStick Net v2 will have the same capabilities as TellStick Net but also a lot of extras from the TellStick ZNet family. Such as:

So, what about TellStick ZNet Pro?
Unfortunately this project is currently on hold. We need to redesign this to be able to have the correct control of the quality during production at the right price. We have some experiments and prototypes but this is still far from production ready. Please don't ask us when it will be ready because at the moment we cannot answer. There is still way to many factors. Ideally 2017 but it could also be 2018.

So, you may ask "what about the hackability?"?
Since TellStick ZNet Pro is so far away we have been investigating the possibilities for hackability in TellStick ZNet Lite. We are going to open it up for you to add your own code. Actually, the Lua scripting was the first step for this. But I am not going to tell you anyting more about this now, it for future blog posts... ;)

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