Non-WeMo device extension app for Automation Manager.
MppDevices is an adapter (proxy) that would run on your WemoServer device, adapting devices other than WeMos to work with WemoManager. It can also be used on your phone if you don't use the WemoServer.
Available on play for a small charge to avoid non-AutomationManager customers from trying it and leaving a bad review when it doesn't work for them, and to help fund new device integration.
The downloadable version on this page can be used to test with Web, Tasker, and Automagic integration before purchasing a license for the maintained version.
Security Advice!!! There are many new and inexpensive IoT automation devices available. Note that these devices only connect to a "cloud" server to give you easy setup and remote access.
Do you know where these cloud servers are located or who can access them? Neither do I...
But you can use MppDevices to control them rather than the cloud enabled apps, and you can automation them and provide remote access using YOUR OWN server using AutomationManager. Then for complete security you can disable remote access and lock them out with your router firewall.
Currently supported device types are:
- Orvibo Smart Switches
- When using the Orvibo devices they must be on the same network segment as MppDevices or you will need to route multicast 255.255.255.255 between segments.
- TP-Link switches and bulbs are now supported natively in AutomationManager/WemoHome.
- Usr Iot/Lonhand devices available on ebay for about 1/2 the cost of a Wemo socket.They are available for multiple country power standards including Europe. I wouldn't want to access them through a cloud based in Asia, but you can deny the devices access to the internet and control them using WemoManager and WemoServer.
- TinyOS based Lazybones relay switches from TinySine. Don't bother. There are cheaper and easier to use devices available.
- Custom devices built using Tasker or Automagic
- Intercept MppDevices standard android intents and implement the interface in Tasker. Use the "Copy Intents" menu for the device to copy/paste the MppDevice intents to your Tasker/Automagic implementation.
- Extras as needed: state (boolean), value (float), udn (string), name (string), time (int)
- Custom devices built using a web (REST-like) interface
- NOTE: you can now use the MppDevices REST interface for native AutomationManager support rather than using this interface through the MppDevices app.
- Customize the HTTP calls made by MppDevices to your mini-web server running your device. Details are provided in app. Specify a GET url for MppServer to fetch the current state or value (for analog devices) and a PUT url (for switch state changes). On the GET return a JSON body with state or a float value (for analog sensors).
- Optionally report state changes back to the MppDevices web server with a PUT to ..:8898/report/udnString?state=xxxx or ?value=fffff
- with either
- state is true or false
- value is a float
- DTMF devices - plays a tone. Currently handy for testing but will be more useful in the future.
- Phone information, for use with battery minders
- BatteryLevel (analog sensor, value - battery charge level)
- BatteryHealth (sensor, "on" if battery is healthy)
- ChargingWireless, ChargingAC, ChargingUSB (sensor)
- Charged (sensor, on when battery fully charged)
- Notification - display a notification to your phone
- Custom (low end) android phones driving relays. Some assembly required. The phones adapt them to wifi/AutomationManager via MppDevices for a very low cost
The "Discoverable" checkbox controls whether each device will be visible to your WemoManager/WemoServer.
Typically you will install MppDevices on the same android device you use for running your AutomationServer. You need at least one device defined before MppDevices will respond. Use a DTMF device (on/off sounds a tone on the phone/tablet) as it's handy for testing.
When installed on the same device as your WemoServer use the "search" menu button and select "Find new Wemos" whenever you add a new MppDevice, though usually they will be discovered automatically by the WemoServer with no search action.
The AutomationServer uses its REST port for incoming notifications of state changes from MppDevices. The WemoServer REST server must be enabled and operating on the default port 4030 (confirm that the indicator on the AutomationServer widget is green).
When you are not using the AutomationServer at all you need to install MppDevices on each handset using AutomationManager, and you will need to add the custom devices to each instance. Discovery of your configured devices should be automatic.
If the MppDevices server is installed on a different (dedicated) device, use the "search" menu "Find MppDevices" action in WemoServer to find it. Point it to your MppServer IP on port 8898.
When you're using AutomationRemote with a AutomationServer your custom MppDevices will show up automatically in AutomationRemote once you have configured the AutomationServer/MppDevices pair.