About MppDevices4AutomationManager
MppDevices is an extension to AutomationManager for IoT (it can also be used for stand-alone manual control) of a collection of different device types.
MppDevices adopts custom and non-Wemo devices into AutomationManager Devices added here are fully supported in the AutomationManager feature set include widgets, rules, remote access, full logging, voice control, grouping, renaming, etc.
Supported device types:
- Switches - on/off and toggle functions
- Momentary - switches that will toggle after a period without wifi, e.g. for rebooting routers, etc.
- Sensors - detect and report on/off states, e.g. door sensors
- Analog - detect and report analog values, e.g. current, temperature, power, useful with the rule engine
Supported devices:
- Custom DIY devices built using Tasker or Automagic - integrate anything. Use standard android intents from MppDevices to integrate the custom device interface.
- Custom DIY HTTP based devices (REST-like). Customize the HTTP calls made by MppDevices to your own mini-web server managing your device, or to devices that have their own REST or web server. Configure MPP devices to make HTTP calls, or configure the device to make HTTP calls to MppDevices (or both!).
- DTMF devices - plays a tone. Currently handy for testing now and will become more useful in the future.
The following production wifi devices are supported:
- TP-Link HS100, HS200, HS110
- USR IOT LonHand, e.g. USRWM1
- Lazybone wifi from TinySine
- Orvibo smart switches
- custom devices using the published interface
More to come.
The small fee for this app prevents re-publishing and invalid ratings by non-users. It's available free on my developers site if you would prefer or wish to try it first. A purchase does provide automatic notification of updates and the revenue is used for purchases for additional device integration, and indicates of the level of interest in the app. If you do purchase it and it doesn't work for you send me your transaction ID for a refund.
by A####:
Never discovers Orvibo B25 socket unfortunately. I have tried another server based application to test and that can't discover it either . It seems that Orvibo have changed something?