Originally Posted by Britman (Post 134922)

Excellent, what would be an acceptable response time, are we looking at just a few milliseconds?

Sent from my ONEPLUS A6013 using Tapatalk

Originally Posted by Bob (Post 134918)

Hi Daniel.

1) I considered it - also thought about using the web server contained in the re-flashed switch firmware for the same purpose but decided it was too much hassle for a small advantage. The start-delay with count-in ticks can help if you need time to get ready before it starts counting.

2) Sorry, too much hassle again. The blocks-style coding used by App Inventor makes even moderately complex programming logic very difficult. It's fine for simple stuff, but as soon as you need to add control logic beyond a few lines, it becomes unwieldy. If I ever get around to learning to code Android in native code then I will revisit it.

3) An OLED screen uses active LEDs in the display which physically light up whereas LCD displays use a backlight shining through coloured LCD pixels that are switched from opaque (almost no back-light gets through) to clear. The "almost" bit is why you can get fogging with an LCD screen as some green and blue light gets through an OFF pixel). This results in much purer colours in an OLED display, reducing the chances of fogging as the App only uses different intensities of red.

But, if your LCD phone is not causing issues then I would just stick with that - I don't have any OLED devices myself.

Originally Posted by mesires (Post 135061)

Hi Bob,
thank you for your feedback and detailed answer!

Re 1) You are right. I use the test strips mode in AUTO mode and it is really good. No problem with that.

One additional question: Is there a way how to turn off the green led inside the Sonoff Basic???
I think I have read all the posts in this thread but have missed any such information.

Daniel

Originally Posted by Bob (Post 135080)

Hi Daniel. The LED is controlled separately by the Sonoff board so the firmware I added cannot affect it. Two options I have done: cover it with some tape (I used a bit of black paper under the tape for extra effect) or, I have also used a pair of pliers to grab and twist it off the board! But you may not want to do this if this is your only Sonoff device as there is a small chance of damage to the board.

Cheers, Bob.

Originally Posted by Bob (Post 134925)

Ideally within a couple of tens of ms but more important is repeatability. If the time to switch on or off varies widely then it becomes impossible to get an accurate time.



This is why using an internet connected socket becomes useless - a two second delay is fine as long as it is always two seconds, but of course, it will vary from a half a second to several seconds which is hopeless. Even connecting to your local WiFi router will introduce varying delays, albeit smaller ones. That is why I designed the app to connect the Android device directly to the power switch rather than go through the home router. It's an extra hassle to connect to it, but it removes all those varying delays (it also means the power switch is not connected to the Internet, which is a good thing given the amount of IOT hacking going on!)



My Basic R3 will be delivered tomorrow and I can have a play :)

Originally Posted by Britman (Post 135089)

Hi Bod,
Did you have a tinker with the basic R3?

Sent from my SM-T810 using Tapatalk

Originally Posted by tillari (Post 138016)

Hello Bob,
I'll try to use the sonoff device. I can by a sonoff r2 or r3. Does the code work on the R3? Can I reprogram it via OTA?
Thanks a lot,
Ariel

Originally Posted by Bob (Post 138022)

Hi Ariel. Sorry, I have not tried it properly on the new R3 (OTA or otherwise). I had intended to try but did not get around to it and used my R3 for something else...

I expect it will still work OK - as long as they have not changed the i/o ports etc. - and even if they have, the sonoff code is on github and is trivial to change.

Good luck!