Re the SC have a look at this page. Not exactly espeasy but it's possible to let it talk MTTQ.

Wow, thats really great news!

"toggle" is a user defined event, no native implementation in the firmware. If you dont call it from elsewhere its just a dead piece of code that never runs. It does the same as your button#state rule, that's why you think it works. Takes a while to get the hang of event driven programming...

To enter flash mode hold the button on power up, this pulls gpio0 to ground. This seems to be too basic knowledge, the wiki doesn't even mention it. :roll: I think S stands for signal, the pins are directly connected to the respective GPIOs. V is Vcc (3.3V) and G of course ground. It's all in the sc...

Too bad that TaskValueSet doesn't work via mttq...
We need another rule in the "master":
Btw. how was the toggle event triggered in your original code?

Both can be flashed, instructions are in the Wiki . The module from ebay uses an esp-01 on which info is all over the web. It has only 2 GPIOs exposed and comes with flash sizes of 512kB to 1MB. The powersupply/relay part seems undocumented which may lead to some guesswork. Sonoff SV has a nice docu...

... Can someone suggest a code tidy up for that below? ... on button#state do if [relay#state] = 0 GPIO,12,1 else GPIO,12,0 endif endon on toggle do if [relay#state] = 1 GPIO,12,0 else GPIO,12,1 endif endon on relay#state do if [relay#state] = 1 gpio,13,0 else gpio,13,1 endif endon on relay#state d...

That's exactly what I've obseved, too. Not sure if it is due to the webinterface running a seperate server process or just more packets going back and forth. Once I ran into a situation (with the first device mentioned) where the rules page was loading perfectly but did not accept changes at all (no...

Yes, I had these problems with two (out of 8) sonoffs as well and don't think it's software related. On unit is running fine sine since I moved it some centimeters, on the other I tried reflashing, erasing flash and flashing again with multiple versions - WiFi is still unreliable and fails after som...

Don't hesitate to ask for assistance with automate, I use it a lot. ;) Without knowing anything about the app inventor and minimal knowledge of object oriented programming I just noticed that you use two different "web" objects: webviewer1 and web1. Maybe the whole point is to use just one...

I now thoroughly reviewed the framework base and a bunch of pull requests. I dont see any problem in being able to moving the project forward as well as making a bunch of improvements in the whole development cycle: - faster intergrating of playground plugins: mark them as TESTING in the webgui and...

Ooops, sorry. Link above is fixed.

It seems you don't use ESPEasy, so first off I'd say this is the wrong place to ask. ;) Anyway, here's my very simple approach to get espeasy to interact with android: From the scripting-app called "Automate" a http-get request triggering an event is sent to an esp-module running espeasy. ...

He meant the arduino libs for esp-boards. Instructions are hidden in the Wiki.

No, there is no cycle - the system#boot event is only triggered once. Thus the rules#timer part runs only once, too - 5 seconds after booting is completed. Here is a reworked code snippet that avoids the flickering: on System#Boot do timerSet,1,5 endon on Rules#Timer=1 do if %systime% < 8:00 (off) e...

I had a similar problem with one of my sonoffs. Moving the device a few centimeters fixed it. My guess is RSSI (at -59 even better in my case) doesn't tell the whole picture and reflections/multipathing can kill some packets.

1. Rules are working fine, go for it.
2. If you can propose a mechanism how an unpowered or disconnected device could communicate it's current state you're a freaking genius - otherwise I'd consider your criticism as "kind of lame".

... how device will work if it will be reboot in 14:00? i think GPIO state may be changed to default in this case. is rule " if Clock#Time >7:00 and <22:00 then gpio,13,0" ? what is correct syntax for this case? ... The clock#time event seems to work only with "=". I solved a si...

Yes I did. Now that you mention it I remember having a hard time setting up this specific unit with the original firmware.
Btw. when it becomes unresponsive on the WiFi interface it still reacts to the pushbutton.

Too late to claim a refund, I'll give up on this one...

Update to the post above: Re #15 I've tried factory reset (tx/rx shorted on boot), full erase by flashing 1MB of 0xFF and soldering a 10uF cap close to the ESP - to no avail, this unit still hangs sometimes while the other 2 Sonoff's run solid. Re the PWM-flickering issue I found that it's not relat...

Bug #15 Feedback so far: .... Statistics: 5 to 7 (42% reported as bug) Still only 12 reports. Does this mean that we only have 12 ESP Easy users? :o As Tonia reported, it could also somehow depend on the Wifi environment like type of router or maybe traffic, distance, etc... ... Excuse for complain...