WemoServer widget display

[Stephen Davy]

I'm completely new to this.

Some background...

I bought AutomationManager for an old Android phone to control a WeMo device but don't yet have access to the WeMo, so I bought the MppDevices extension to play about controlling a couple of Orvibo S20s and then bought an ESP-01/relay combination module to play with that as well.

Unfortunately, as it turns out, the relay module uses the serial output from the ESP-01 to turn the relay on and off and the ESP8266 bit of AutomationManager doesn't have a suitable device type for this, as far as I can make out.  Anyway, using Arduino I've cobbled together a web server on the ESP-01 that lets AutomationManager control the relay using the HTTP device type in MppDevices.

Observation....

The WemoServer widget on my Android home page shows the state of the 3 devices (2 S20s and the ESP relay).

I can control the S20s from the widget but if I try to control the relay from the widget it does nothing, but it reliably shows the state of the relay if I control it from elsewhere (either WemoManager or WemoRemote on another phone).

Question....

Is this to be expected?

Cheers

Stephen

[Mike P]

I think it should work from a widget if it works when using the WemoManager app.  Which widget type are you using?  It should be the DeviceWidget and probably of type "toggle".  Have a look in the log after touching the widget to see if the command has been sent.  It's possible it's the old android, but if the widgets are working with the orvibos that would eliminate it.

Do you know the serial chip that's used?  The MppDual for the Sonoff dual uses a serial chip to set the states, it might work with this device too.

[Stephen Davy]

It's the WemoServer widget that I'm talking about.  But if I use a DeviceWidget (toggle) it behaves the same.  It goes yellow when touched and then reverts to the correct state colour without changing the state.

The Android is a Samsung S2Mini running Android 4.1.2. But both the WemoServer and a WemoDevice widget can control the Orvibos.

The chip appears to be an STC15F104.

[Mike P]

If it turns yellow that means it's trying (a change has been requested and is pending).  If it turns back grey it means the device has responded after the request with the new state which in this case appears to be the same as the old state.  It may be there's a bug in that part of the code (the custom web devices) as it's not used much.  First place to check is the log (open WemoManager, touch the "eye") to see if the pending state and the response states are there.  If you could clear the log first, then try the widget, and return to the log and then send it to me I can have a look.

That chip looks like a custom CPU - sort of overkill for relay control as the ESP01 can already do it on it's own...  But if you know the serial protocol for it you might be able to use MppRelay and override the SetRelay function.  I could do an MppCustom file type that would exclude it from firmware updates if that'll help.

[Stephen Davy]

Mike

It behaves as you described. I've emailed you the log. 

I agree it looks like overkill - a simple transistor would have done the job. I think the chip might be a micro. I only know the "on" and "off" commands which I've picked up elsewhere.  I wouldn't go to any trouble.  I have the solution and it's only for experimenting with at the moment.

FYI this is the module: http://www.chinalctech.com/index.php?_m=mod_product&_a=view&p_id=1204

[Mike P]

It's a bug in MppDevices (I'm wasn't handling the "toggle" function from the widget properly).  Fix is posted at the bottom of this page:  https://sites.google.com/site/mppsuite/android-apps/mppdevices.  Sorry about that!

[Stephen Davy]

No problem.  Thanks for the fix.