Let's Control It

paxi

Tasks consume RAM which is limited by the ESP8266 itself, not the flash memory.

paxi

Hmm, strange. This always worked for me.

How are you powering the sonoff for flashing?

paxi

The log looks ok.
There may be some residual settings in the flash, try to clear it with the attachment in this post:
viewtopic.php?f=5&t=721&p=13435#p13435

paxi

https://github.com/letscontrolit/ESPEas ... couple.ino

Nothing a little bit of phantasy and googling couldn't fix.

paxi

Try a precompiled image from here and use the included flash.cmd: http://www.letscontrolit.com/downloads/ESPEasy_R147_RC8.zip Then powercycle the device. Use mains power or a seperate 3.3V supply, FTDI adapters usually don't provide enough current to run the esp. It can take a while for the "ES...

paxi

You can use that module (in theory). Be aware that it takes 5V as charging input, the output is "only" battery voltage. I don't know how the 4056 will react to varying input voltages/currents from the solar cell. The protection circuit in it just cuts the output if 3A are exeeded or Vbat i...

paxi

The ESP datasheet says 3.0 to 3.6 volts. The wemos has a 3.3V pin, I guess one can feed it from there but it seems the USB bridge is also powered from it. Found a nice page about the wemos' voltage divider and how to adapt it to measure a lipo. ;) You can still carry this over to a bare ESP-12 modul...

paxi

... when I press the "on" button, while I am on the devices tab of the easy esp it will display a IR code number 716107913 but if i go to the log section of easy esp it will display 2aaef089. so I am confused as to why they are different. I take either of those numbers and pipe it into a ...

paxi

This says the 1 MOhm ressistor won't work with the WeMos, sorry. 1 Meg is the internal resistance of the ADC pin, wasn't meaning any external resistors with that. ;) You have to ensure that current through the pin << crurrent through the divider for decent, linear readings. Running a buck/boost con...

paxi

Stepping up Lipo voltage to 5V just to burn it down to 3.3V through the linear regulator is by far the biggest waste of energy. Also the USB/UART bridge on the wemos will unneccesarily eat your battery. You should use a different, less complex module for this task and at best feed it through a low q...

paxi

If you see input/output in the above statement from the broker's perspective that's right.

Always a joy to let these little lightbulbs glow in other peoples mind.

paxi

I still don't see the need for your request. You need that information only once, right? Why should a (admittedly small) delay be introduced in the boot process that isn't needed in 99.9% of cases? Just to save you typing a single word while sitting at the console anyways - to get something that's s...

paxi

Take a look at the command reference:

GPIO (pinnumber),(value) is a command,
(devicename) (valuename),(value) is not - it is a sensor which sends its value back to the broker.

If you want to use something less cryptic in Openhab then wrap the gpio command in a rule and call that via mttq.

paxi

Always a joy.

You can even fine-tune the behaviour: depending on the selection (active high/active low) the toggle happens on pushing or releasing the button.

paxi

Let's hope the resistor does not fire.

Technically the internal pullup resistor gets connected between the pin and Vcc.

paxi

Looks like you're using a push button. So select this (in field "switch button type") and it will toggle the state each time you press it.

paxi

Before going down the route to write a new plugin you should make sure the hardware can work correctly: terminate the I2C bus with external pullups. If the modules work for other users that may be the culprit. ;) On another note (datasheet): Supply Voltage (VDD) and Ground (VSS) must be decoupled wi...

paxi

Done - in the "official" repo.

Thanks!

paxi

Typing "settings" doesn't do that? I don't use serial that much...

Also after the initial setup in AP mode you see the new IP in a link that takes you right to the "full" webinterface. Assign a fixed IP from there and you'll never have to touch you router.

paxi

Sure, everything's fine.

paxi

Exactly. Almost everyone will intuitive flip the switch a second time (if lamp was remote-off) but then it has to come on fast (or you'll hear "your lights are broken").

We are almost neighbours,
Grüße aus Enger

paxi

Well yes, thats my problem and I know the alternative - it's just not practical. I don't think I'm the only one with such a setup. Most of us have to work with the existing wires. To me it makes simply no sense to have pins boot states configurable when these are executed "long" after boot...

paxi

My setup is different, the wallswitch breaks power to sonoff.

Mains > switch > sonoff > lamp

Wiring the switch to gpio would require to open walls and run additional wires or dig holes to burry the units...

paxi

The lamps are controled by relais and can of course be controled remotely. The point is to make them also controlable manually and boot as fast as possible into "relay on" so the tech-stuff becomes mostly transparent. Improve usability and prevent confusion and anger if the "home auto...

paxi

Especially with the sometimes unstable sonoffs it can take a long time until the configured boot states for GPIOs get applied. Found the reason in ESPEasy.ino (line 564ff): hardwareInit() is run after the wifi stuff is done. I use several sonoffs buried in lamps, they are powered through the origina...

paxi

Great!

Depending on how often the pushbuttons are used I'd prefer to update the switch states immediately instead of once per minute:

Code: Select all

on PowerSwitch1#Switch do TaskValueSet 20,1,[PowerSwitch1#Switch]

paxi

Ok, your edit made it clear.

The solution is to keep the "unique name stuff" aka the physical devices and their representation in software completely inside espeasy (send data disabled) and work with a dummy to send data to and recieve commands from your controller.

paxi

Its really really difficult to follow without seeing the working/failing setups.:roll: Give us the complete picture. ;) I'm going to guess: 1) You created 4 switch devices with the same name? Or 2) PowerSwitch is a dummy device with the values switch1-4? In case 1) it must fail because the firmare s...

paxi

Espeasy is a single threaded system and the fade runs in a simple loop, indeed it can't do anything else until the fade is done. But there has been something worked out for RGBs, you want to read this: http://www.letscontrolit.com/forum/viewtopic.php?f=6&t=2395&hilit=Rgbw http://www.letscont...

paxi

Leaving IDX=0 is a common trap - are they all different and ≠0?
Save your settings and attach them here or make screenshots of all devices. We need every detail.

Can you make the buttons work again by removing the sensors?

paxi

Erm, I think you posted screenshots but there is nothing to see. Please edit your post.

paxi

- SonOff powered with main AC Power AND wire between 2 finger to 3.3vor gnd pin : With OK !!! I don't get it - please elaborate on what you did exactly in this test. Mains power and finger in the same sentence sounds dangerous. :shock: ESP8266's are a "spikey" load. The sonoffs have very ...

paxi

Yes, this should work for @velja.

Be carefull, @38domo kind of hijacked this thread

and we're actually discussing two different topics here (desired direction of data flow over the serial interface).

paxi

You are right toeffel. But one can "wrap" that command in a rule and trigger this new event via mttq.

@38dome:
I haven't used it yet but from the description ser2net should be capable of what you're trying to to (send data to serial port) but you'll have to use telnet instead of mttq.

paxi

Make sure the last linr in rules ends with CR/LF is another idea.

Or simply erase the flash - if it worked before there's something messed up.

The sympthoms clearly indicate this.

paxi

Mind to share your solution? ;) Sadly no AND. From rules tutorial: Also simple if ... else ... endif statements are possible, but nesting and Boolean logic are not supported. But there's a workaround: ... if condition1 event checkAND endif ... on checkAND do if condition2 desired action endif endon ...

paxi

Post your rules.

If in doubt if back and forth flashing messed up then erase flash (see here) and start from scratch. Since settings are stored outside the actual firmware it is possible that some residual data is confusing espeasy.

paxi

I think the $20 mark applies to dev boards with usb/uart bridge. I recall seeing modules for around $6 but can't find them again.

paxi

You should mention you've posted an affiliate link - I'm fine with that but let readers know it.

I've seen them way cheaper from china.
Or for about the same price shipped from germany: http://www.ebay.de/itm/Espressif-ESP32- ... 2176225110

paxi

You have a strange AP, usually they assign always the same IP to a given divice. Anyway, fixed IP settings are at the bottom of the config page in espeasy. Re updating click the "?" next to "firmware load" in the tools page.

paxi

I see that the cap helps to smooth supply for the active ESP but don't understand what it does for deep sleep where current draw is about 0.1mA. What is battery life now?

paxi

Don't forget a current limiting resistor(1k) in line with the switch. Your post isn't clear, you write switch at first and later button. For a momentary pushbutton configure the switch type accordingly. Then the pin isn't set as input but anyhow - gpio 16 is somewhat special, I'd try to pull it high...

paxi

I have "!" and spaces in my ssid, though the key is only numbers but I don't think the characters in your WiFi credentials are a problem. I suggest you try to set your AP to b/g only. Often re-flashing the esp module helps. Or maybe you're just typing wrong - happened to me before, now I o...

paxi

Short rx and tx pins and power up for a minute.

paxi

I have a gut feel that the pin is fried somehow. Likely by putting out high level while tied to gnd through the switch and exceeding the allowed 12mA limit. Use a 1k resistor in line with the switch for current limiting to prevent this on the next module/pin. Sending a state to a pin meant as input ...

paxi

If you address an espeasy unit directly you must use the default port for http: 80
It doesn't care what port your broker is listening on.

paxi

Did you configure gpio 2 as "input" in the hardware tab?
"Pull up" ticked for the switch task in devices?

If that doesn't suffice add an external pullup resistor (10k or whatever you have at hand) between gpio 2 and Vcc.

paxi

What you need seems to be in wifi.ino: wifi.scanNetworks() returns the number of visible APs and fills an array called wifi.ssid but I'm not skilled enough to go from there - a plugin around these would be nice.

paxi

Glad you got it working now! And so easy - I don't use a sever thus wasn't aware of that tickbox.

You can still sum up the two seperate relay#state rules into one (like in my toggle example above).

paxi

Unit number must be within 0-31.

I prefer SendToHTTP over sendto (TCP vs. UDP). Correct syntax is

SendToHTTP 192.168.1.205,80,/control?cmd=GPIO,2,0

Search found 121 matches