AutomationManager

AutomationManager (AM) is an android based application you would typically run on your phone for local control of your IoT devices.

A more interesting and better use of AM is as a stand-alone android or pc/mac based automation controller (a hub/server). It will operate your automation (by following rules) without relying on an internet connection or an external cloud (improving reliability, speed, and preserving your privacy). You probably don't want the automation that runs your home to leave your home - everything that happens should happen inside your home network.

Remote access and device integration is supported either by a direct connection back to this server through your router, by connecting to it through your own account in Google's cloud, or by using IFTTT with Alexa, Google Home, or any other IFTTT supported service.

See Features for a summary of features.

You can use AutomationManager for IoT to manage Philips Hue, Lifx, Belkin WeMo, TP Link, and custom ESP8266 based automation products.

ESP8266 devices are very flexible, low cost wifi devices that you can customize and integrate into the AutomationManager engine (see ESP8266).

AutomationManager aka WemoManager can be found on Google Play @ AutomationManager. Read on to see why it's useful for iPhone users as well.

WemoHome (a separate app) is a subset of AutomationManager function. If you don't need advanced services and only want easy local control (e.g. single touch widgets on your tablet that work as light switches).

WemoLEDs (a separate app) is for managing LED bulbs using the Wemo Link. It can be used on its own for local control (much like WemoHome), or combined with AutomationManager or WemoHome to add the additional capabilities of the LEDs to your Wemo automation.

To work your WeMo device must first be connected to your wifi network. There are some tips on getting connected in the "Finding Wemo" or "Finding TP Links" section. This can be a bit tricky, if you continue to have trouble you will need to consult with Belkin or TP Link support as the setup APIs are not available for use by me in my app.

AutomationManager has a built in rules engine (the WemoServer) and provides an interface for remote control. The included WemoServer requires (allows!) you to manage and run your own local server on android phone or tablet (see Running MPP Servers) or any PC/Linux/Mac (see WemoServer (java)) system that has Java installed to replace the Belkin and/or TP Link internet/cloud servers. The WemoServer needs to stay on and connected at all times you need rules or remote access.

Typical AutomationManager setup - the AutomationServer running on a spare phone/tablet/pc managing your rules, logging, etc, and WemoManager used on your personal phone while at home, or WemoRemote when you are away from home.

Additional AutomationManager help is available on this site:

• Finding Wemo (and others) - how to find your devices using AutomationManager
• FAQ - general questions and facts about AutomationManager
• HowTo - detailed step by step on how to use AutomationManager and it's parts
• Rules and Automation - the rules and actions that are available

Why AutomationManager?

There are a number of weaknesses that make the typical IoT vendor approach unsuitable for some of us. The devices themselves can be problematic, the implementation of their uPNP services is somewhat lacking, and the IoT vendor owns your account online - you are not given access to it. The devices can be quite difficult to configure. A cloud based solution for control is subject to outages and delays in your network, your internet service, vendor cloud service, and to make changes to your online account you often need to contact the vendor directly.

Belkin has struggled with a poorly designed and poorly tested android application, combined with questionable firmware in the switches themselves. They have had issues with firmware updates that have broken the devices and access, and with their cloud service that occasionally stops functioning. Relying on an online service for the application of rules is problematic, subject to the same outages as the rest of their system.

Their implementation is also subject to a number of security risks. Most notable is that any of your rules and switch status is now available on the internet, and your devices can also be controlled remotely by someone through the internet. Thus you become prey to hackers breaking into your device, your network through your device, and into the WeMo or IFTTT system.

You are also open for scrutiny by various security or government agencies either legally or illegally. Note that the app itself incorporates freeware and other bits that seem to have been acquired, so who knows what those pieces actually do or what security exposures they have ('cause Belkin sure doesn't!).

AutomationManager app avoids all of these issues. You can use it to control your devices while you are safely connected to your own network. You can setup your own secure server (with encrypted data) so that you rely on no one but yourself for remote access to your devices and the device availability. You can run your own rules server for the same reason (with the added advantage that the AutomationManager rules server actually works, works instantly, and can properly compute sunset, sunrise, and the difference between night and day).

You can go further to pair the AutomationManager with Automagic or Tasker to build very sophisticated automation systems, all local, integrating different aspects such as your security system with motion detection, cameras, your thermostat, etc. For example I use my security system motion detectors to trigger room lights, and if an alarm sounds the AutomationManager flashes my outside lights on and off to make it easy for emergency responders to spot.

Unlike the Belkin app, it has NEVER been necessary for a AutomationManager user to reset the switches, delete all of their rules, uninstall the AutomationManager then reinstall it and recreate all of their original work. Here at MPP we solve the ACTUAL problem and fix it properly.

Here's some automation you can perform with AutomationManager using the rule engine:

Wemo light switch manager for outside lights:

• RULE NetCam motion at front door turns the outside light on when someone comes to the door at night
• DscManager alarm system zone sensors on the front and garage doors sends an intent to trigger a AutomationManager rule to turn the light on only at night
  • This is for someone opening a door to leave, or arrives using the garage door opener
• DscManager alarm system alarm sends a AutomationManager intent to start the lights flashing. Clearing the alarm stops the flashing with another AutomationManager intent
• RULE - scheduled to turn the light on at sunset (so it always looks like someone is home)
• The wemo switch itself of course turns the light on
• RULE - the light turns itself off after 10 minutes during the day (handy if needed during a total eclipse or big dark storm, but they won’t stay on too long if turned on by accident)
• RULE - the light turns itself off after 30 minutes any time it’s turned on at night (interruptible, a new event will restart the timer)
• RULE - a scheduled rule always turns the light off at dawn just to be sure

Another example for an office using a light plugged into the wemo socket and wemo motion

• RULE - wemo motion detected turns the light on at night
• RULE - wemo no motion turns the light off after 15 minutes using the delay
• This delay rule is interruptible – if new motion is detected (and stops) the rule is restarted
  • Belkin does not have "motion off" nor rule interrupt capability.