Skylink announces IFTTT compatibility with connected home accessories

Skylink announces IFTTT compatibility with connected home accessories
Skylink, a leading provider of connected home safety solutions, announced its compatibility with IFTTT. The new function allows homeowners to connect the SkylinkNet Alarm System Kit to other industry leading connected home accessories including Amazon Echo, Nest® Cam™, WeMo®, and Phillips Hue. Homeowners can also run recipes for functions unrelated to other smart devices, bringing advance functionality to the SkylinkNet Alarm System Kit.

SkylinkNet & IFTTT recipes

Turn Philips Hue to Red when SkylinkNet is in Panic (Alarm)
Use Amazon Echo to set your SkylinkNet alarm system to Arm Away
If motion sensor is activated, turn on Wemo® light switch
When you leave home with smartphone, set SkylinkNet to Arm Away
If Nest® Cam™ detects motion, turn on SkylinkNet lamp
Create an event log on Google Drive for all related events
When SkylinkNet Hub is in specific mode, send an email notification
Arm/Disarm SkylinkNet with a push of a button
“Homes have become much smarter and we are offering our customers new ways to make them even more intelligent,” says Gallen Tsui, President, Skylink. “Our system provides homeowners with a more hands on experience of keeping their families safe, while cutting costs on monitoring fees, and with the introduction of the IFTTT functionality they will be exposed to other facets of the smart home.”

SkylinkNet alarm system kit features

Controlled by an Internet Hub and includes a motion sensor, keychain remote, 2 door or window sensors and added video monitoring features
Affordable home alarm system with no monthly fees or long-term contracts
Works with up to 100 wireless sensors and controllers and 10 wireless cameras
Smartphone app allows users to track all recent sensor activations and notifies them who has armed and disarmed the system and at what time
App allows up to 6 users to monitor one or various locations at the same time
 Source: Skylink

Share to:
Comments ( 0 )