Recent posts (max 20) - Browse or Archive for more

Database maintenance Wednesday, March 21st

On Wednesday, March 21st, Telldus Live! will switch over to a new database system. We don't expect any downtime, but it's a really major operation involving many steps with a lot of potential pitfalls. The switch itself will take place at 11:00 CET. We will then closely monitor all systems and fix problems that may show up. Follow us on twitter (@telldus_status) for the latest updates.

In a worst case scenario we might have to rollback to the state before the switch over attempt. In that case, editing made during this time would be lost. Also device logs (sensor logs are not affected) and new locations, schedules, events and accounts would be affected. Therefore we encourage you not to do a lot of editing of your setups this day.

We are doing this to increase database performance, but especially to have a more reliable failover design. Almost all other Telldus systems are using this database in one way or another, and it's critical that it's reliable.

SSL and https

We in Telldus take Security very seriously. As soon as information about the Drown and Poodle attacks on SSL was published, we started to examine the affects and the resolution to these issues.

With this message we would like to assure you, that apart from Security, user satisfaction is one key foundation defining how we work. This is also one of the reasons, we are delayed with the resolution. To deal with these vulnerabilities, we had the option to close down TelldusCenter and support you to instead setting up Telldus Live! via our new TellStick Gateways. That would mean swapping the old TellStick with Version 2 of our Gateway. This is in our opinion the best option for you who are using TelldusCenter, and in the process also get to the optimum security and feature set that we today have. In short, we want you to not be left behind but walk with us towards a safer, more secured Smart Home Solution as compared to the old version.

But we haven’t closed down Telldus Live!-access for TelldusCenter because we want to affect your running setups as little as possible, and keep your options open, therefore we chose to upgrade TelldusCenter. This is taking more time than expected due to the complexity and we are working hard to finalize these changes which we believe should happen shortly. Once done, these vulnerabilities will be removed.

In addition to this, we have also decided on a few other Security updates and restructuring, that would allows us to better separate servers that needs to remain open for TelldusCenter from the others. These upgrades will also allow us to turn on https as default for the Telldus Live!-web.

Update 2018-02-28:
As some of you have noticed, there is a difference between servers regarding what SSL versions they accept. We are only using api.telldus.com for TelldusCenter and that URL is now considered legacy. If you are connecting to our API using SSL, you should use pa-api.telldus.com instead.

New app version released

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/

Sensor values and device states in event actions

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:

Sensorvalue in event action

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.

Beta testers wanted to test Amazon Alexa integration with TellStick

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 sign up here.

Update to mobile app beta

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

Beta testers wanted for Telldus Live! mobile (iOS)

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.

ASUS™ AiProtection reports suspicious networking behavior from TellStick

Some users have been reporting their (ASUS™) routers reports suspicious networking behavior from TellStick. The router alerts that TellStick tries to connect to a suspicious server on the internet.

The alert looks similar to this:

Alert type : Infected Device Prevention and Blocking Source : (AC:CA:54:XX:YY:ZZ) Destination : 193.11.114.43

RT-AC87U’s AiProtection detected suspicious networking behavior and prevented your device making a connection to a malicious website

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.

root@mangocrap:/var/lib/misc# nslookup 193.11.114.43
Server:		192.168.1.1
Address:	192.168.1.1#53

Non-authoritative answer:
43.114.11.193.in-addr.arpa	name = tor1.mdfnet.se.

Authoritative answers can be found from:

A DNS lookup in tor1.msfnet.se however revealed no associated IP address,:

root@mangocrap:/var/lib/misc# nslookup tor1.mdfnet.se
Server:		192.168.1.1
Address:	192.168.1.1#53

** server can't find tor1.mdfnet.se: NXDOMAIN

suggesting this is a stale record of the reverse DNS lookup.

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.

Lua-script for sirens



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.

 https://github.com/telldus/tellstick-lua-examples/blob/master/zwave/AeonLabs/Siren.lua

 https://github.com/telldus/tellstick-lua-examples/blob/master/zwave/CoolCam/Siren.lua

 https://github.com/telldus/tellstick-lua-examples/blob/master/zwave/Philio/Siren.lua

  • Posted: 2017-06-12 10:47 (Updated: 2017-10-11 11:45)
  • Categories: lua z-wave
  • Comments (0)

Small update on sensor history



Just would like you to know that we just pushed a small design update to the sensor history.

Beta testers wanted for Telldus Live! mobile

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

IFTTT to the people!

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.

Read more about IFTTT  here.

Telldus Live! in Norwegian

Finally! - Telldus Live! is now available in Norwegian!

If you see any strange translations, please let us know.

Philio (and D-Link) multisound siren

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

Testers wanted for TellStick plugins

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. 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.

http://fw.telldus.com/plugins/Eliq-1.0.png
Import  Eliq energy data into Telldus Live!
http://fw.telldus.com/plugins/Lifx-1.0.png
Plugin that allows you to control  Lifx bulbs.
http://fw.telldus.com/plugins/Mail_sender-1.0.png
Send emails from lua scripts
http://fw.telldus.com/plugins/Netatmo_Weather-1.0.png
Use  Netatmo weather station in Telldus Live!
http://fw.telldus.com/plugins/Philips_Hue-1.0.png
Control  Philips Hue lights
http://fw.telldus.com/plugins/Pushover-1.0.png
 Pushover makes it easy to get real-time notifications
on your Android, iPhone, iPad, and
Desktop (Pebble, Android Wear, and Apple watches, too!)
http://fw.telldus.com/plugins/Sonos-0.1.png
Plugin that allows you to control  Sonos speakers
http://fw.telldus.com/plugins/SqueezeBox-1.0.png
Plugin to control  Logitech Squeezebox from TellStick
http://fw.telldus.com/plugins/TP-Link-1.0.png
Plugin that allows you to control  TP-Link HS100/HS110
http://fw.telldus.com/plugins/Verisure-1.0.png
Plugin to read status from a  Verisure Alarm
http://fw.telldus.com/plugins/WeMo-1.0.png
Control  WEMO Insight
http://fw.telldus.com/plugins/YR_Weather-1.0.png
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

We're hiring!

We are looking for a frontend developer to our office in Lund, please read more here:

 http://telldus.se/rekrytering-frontend_lund/

  • Posted: 2017-03-21 08:26
  • Categories: (none)
  • Comments (0)

Looking for translators

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

Release of Telldus IFTTT channel

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.

Update: The channel is now released.

Make sure your Christmas tree does not run out of water

We've put together a Lua script to make sure your christmas tree doesn't run out of water! Watch it on GitHub:  ChristmasTree.lua

Use Aeon Labs Minimote

The Aeon Labs Minimote is a nice looking remote control for Z-Wave devices. It might be a little hard to understand the manual and the scenes and associations described though.

This remote control does not support normal association where the main controller can set the nodes in association groups. Instead this is done on the remote control itself.

The remote control can only control devices that uses Switch Multilevel and Switch Binary, that means most dimmer and most on/off devices.

To make this device control other devices set it up by following these steps:

  1. Include it into the Z-Wave network: Add a new device in Telldus Live! Press the Learn-button on the remote control
  1. Press and hold the button you like to configure - the blue led will flash after 1 sec.
  1. While still holding the button, make the device you want to control send out it's Node Information Frame. The blue led will stay steady blue.
  1. Set the dimmer level or the on/off-state you want the button to set.
  1. Release the button.