Let's Control It

ThomasB

So I put both codes in a ascii decoder and it appeared that the not working code had for space not ascii code 32 but 160 (non-breaking space).

Good catch.

- Thomas

ThomasB

The problem is that neither one is a "one size fits all" build and it also does seem to be related to a lot of environmental factors like RSSI value, number of other APs in the neighborhood etc. That's an interesting twist to this debugging saga. I placed a "working" NodeMCU nex...

ThomasB

Can you test this one: ...

Respect! That works fantastic. Fast page loads, no hangs.

So what is the secrete to this magic?

BTW, I used OTA flash. System info reports DOUT mode. The previously "DOUT" test file reported DIO mode.

- Thomas

ThomasB

Thanks for the DOUT information. For this 20190805_normal_ESP8266_4M version, can you see what core version was used? ESP82xx Core 2_5_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.1.2 PUYA support I also tried ESP_Easy_mega-20191016-11-PR_2667_test_ESP8266_4M_VCC. It uses the exact same core version as note...

ThomasB

Well if the last build was working fine, then I think it may still be related to the way we use flash. Unfortunately the story has become convoluted and perplexing. Here's a timeline summary: 1. Sonoff Basic module is upgraded to 4MB flash. ESP_Easy_mega-20200222_normal_ESP8266_4M1M.bin is loaded. ...

ThomasB

To use the VCC option you must flash with a firmware file that has "_VCC" in its name. For example:
ESP_Easy_mega-20200222_test_ESP8266_4M1M_VCC.bin

Or if you self compile you need to configure the FEATURE_ADC_VCC flag in your build settings.

- Thomas

ThomasB

Last merges I made today brought the build size of the minimal OTA builds below the max again, even for core 2.6.3 Nice! I wanted to check the minimal OTA build using your mega-20200301 release. I have a Sonoff running mega-20200222, but this recent version has OTA disabled. So my experiment will h...

ThomasB

I used ESP Easy Flasher and reloaded ESP_Easy_mega-20200222_normal_ESP8266_4M1M (with Force D-OUT). Web browsing is working, but now it takes several seconds to load some pages. So the progress made today has slipped away. This makes me think that my "hardware problem" comments are a false...

ThomasB

Further testing revealed a problem. I enabled the Openhab MQTT controller plugin and the Sonoff device crashed (unresponsive). I've cold booted and still can't connect with the browser.

I need to finish up some other tasks, but will return to debugging later tonight.

-Thomas

ThomasB

I don't see anything unusual with the test release. But the installation is simple; Just the switch, dummy, and Sysinfo plugins. NTP and Rules are working. System var replacements are Ok. OTA flash, Email Notifications and HTTP event commands are Ok. I noticed that the "erase" command is n...

ThomasB

I found that the Flash Memory chip does not have its own decoupling cap. Its Vcc pin connects to the nearby status LED. To remedy this, I installed a 0.1uF SMD cap across the LED Anode (3.3V) and the ground plane near the ESP8266 (see photo, red arrow). It's hard to say for certain, but it seems to ...

ThomasB

Some Sonoff devices in the past were missing some proper decoupling and thus became unstable when powered via mains. For my safety all the Sonoff testing is with 3.3V power. This allows death-free connection to the serial port. It's the exact same setup I always use with Sonoff devices, which has w...

ThomasB

I can make you a "DOUT" build to test. That is a good idea. Since it is a custom build, please make it a [test_ESP8266_4M1M] without VCC. Extra foam. BTW, I flash with Grovkillen's Easy flasher. I've already tried its "Force D-OUT" function; I assumed that changed the bin's flas...

ThomasB

Very odd problem. 1. Get rid of any unused rule files by going to Tools=>FileSystem=>FileBrowser . Delete all rulesX.txt files except rules1.txt. 2. Assign a spare GPIO to a LED (with current limit resistor). Write some rules to test the LED (like you did to test the relay). If the LED works correct...

ThomasB

Regarding the OTA support for the older 1MB modules, I do miss that. My workaround has been to swap the 1MB Flash chip with 4MB. For sure this is not a practical solution for most users. And Sonoff has killed the Flash upgrade idea by "improving" some of their modules with the crippled ESP...

ThomasB

On my problematic ESP32 node, I had NTP off for a while to get some idea of the clock drift. It doesn't look that much, so I guess that's not likely to be the issue here. I can try the NTP wander test on my EPS8266 device. But web access is painful (persistent timeouts). Is there a secrete command ...

ThomasB

@grovkillen, I'm using ESP Easy Flasher version 0.04.007. As reported by GravityRZ, I also confirm that the WiFi Password field does not tolerate my credentials that have a $ (dollar sign) symbol. The command window shows the full password, but what gets stored in flash is terminated at the $ sign. ...

ThomasB

No matter what I do I cannot get past the mega-20190215 on all of my SONOFF (basic) modules (resoldered 4MB). @TD-er, I decided to try the OP's configuration with ESP_Easy_mega-20200222_normal_ESP8266_4M1M.bin. And I'm having WiFi problems too. Background info: I used a Sonoff Basic (original versi...

ThomasB

See the attachment Since you are using a electro-mechanical switch a De-bounce value is needed. For your magnetic reed switch application I suggest changing the 0mS value to 100mS. The settings at the bottom of the plugin's screenshot are missing. So I cannot see the Values name. Your rules use &qu...

ThomasB

Flash memory may have been corrupted. I suggest starting over using the latest Mega release, as follows: 1. Back up the existing settings and rule files. 2. Using the ESP.Easy.Flasher.exe flash utility, serial flash with blank_4MB.bin. 3. Serial flash with ESP_Easy_mega-20200222_normal_ESP8266_4M1M....

ThomasB

In the last setup I can turn the relay off with the switch and the rule, but I can't turn it back on. Couple things come to mind: 1. Switch Input plugin configuration might be incorrect. Post a screenshot to the reed switch's plugin settings. 2. The wire leads to the reed switch might be too long (...

ThomasB

I can’t test now but do you think it’s possible to send the string « .102.210.206.201.205 » ? Normally you would need to send each numeric value separately and use the i[idx] to indicate which value is being sent. But it seems this requirement will soon change (TD-er is adding support for text stri...

ThomasB

You can also access the /setup url. So for example: http://<ip>/setup @TD-er: I tried this on a working mega-20200222 (already has WiFi credentials). All I see is the "WiFi Setup Complete" page; No editing allowed at this URL. In this discussion the OP wants to restart the WiFi setup wiza...

ThomasB

Is there a function inside code of EspEasy that I could run to reset only Wifi Settings? Yes. This is what should happen on the current Mega releases: 1. Confirm your ESPEasy device is working on your network. 2. Delete the SSID from the Config Page. Be sure to press Submit to save the changed conf...

ThomasB

print "|u,i123545,n,s" print rooms.txt This Nextion code isn't compatible with ESPEasy because the s[value] parameter must be a number. That is to say, a common text message is not permitted as a value. The workaround is to assign a unique numeric code that represents the message you want...

ThomasB

But what is the remote/client sensors dont report on frequent time? If they are battery powered then I can understand why they don't report very often. But if they are mains powered then simply create a timer rule to periodically report to the host. ... the clients turns off sometimes. I suppose yo...

ThomasB

Perhaps the new release requires different http syntax? That is to say, maybe the new rules parsing (or some other recent change) affects incoming http. As an experiment, change the curl commands to this kind of format: curl -s http://192.168.0.198/control?cmd=lcd,2,1,\'Consumi+$x2+W\' {This curl fo...

ThomasB

so no numbers, and no words that comes after numebers (the part missing is what i write in bold and red colour) why? how i can fix? If you are using ESPEasy rules to publish the values then please be aware that the parameter parsing method has changed. See this: https://github.com/letscontrolit/ESP...

ThomasB

If emoncms is not connecting, and you have reconfirmed the controller settings, then try using ESPEasy's log to aid your debugging. Perhaps the debug level log messages will provide some insight to the connecting issue. If you are using rules to publish the values then be aware that new parsing requ...

ThomasB

Your S20 POW may be a version with only 1MB flash. So try the bin file named with "hard_other_POW_ESP8285_1M"

- Thomas

ThomasB

It appears that your relay board expects serial commands from the ESP8266. There are many variations of the module so the exact details can vary. For example, see the last post by ntissm in this old discussion: https://www.letscontrolit.com/forum/viewtopic.php?t=2491#p12159 Although it's just a rand...

ThomasB

Unreliable boot has been reported on some ESP32 development boards. The solution has been to add a 1uF ceramic capacitor between EN and GND.

Additional advice can be found here:
https://github.com/espressif/arduino-esp32/issues/1274

- Thomas

ThomasB

as I said i have included directly Onewire lib to the plugin's code and its fine , because now the plugin is working as usual. Glad to know you have it working with your modified code. It would be helpful to try the new pull-up value with the unmodified ESPEasy firmware (latest Mega version). If it...

ThomasB

@TD-er: Agreed. The one-wire bit timing and logic levels are critical and can be affected by poorly chosen pullup values. Sensor cable length affects it too, so when trouble occurs the sensors should be directly connected (no cable) to allow debugging. After it is working the longer cable can be re-...

ThomasB

1. Please state which version of ESPEasy you are using. 2. Confirm the PHP script works. That is to say, validate it without using the ESPEasy device. That way you can determine if the problem is due to the ESPEasy controller settings. 3. Monitor ESPEasy's system log messages. They may help you diag...

ThomasB

My NodeMCU test device (with mega-20200204 firmware) has reached six days without a reboot. That's a record for it. So I'm popping the cork on the good bubbly; Have a glass on me. The final piece of the puzzle was to set Tools=>Advanced=>Connection Failure Threshold to zero, which disables the featu...

ThomasB

If I power some DS18B20's with 5V, I assume that I also need a level converter for the GPIO?

Don't use 5V. The DS18B20 will tolerate voltages as low as 3.0V and requires less than 2mA current. So that means you can power it from the ESP8266's 3.3V supply.

- Thomas

ThomasB

1) I did consult the pin mapping guide, but I lack a clear explanation of which "applications" are suitable for each GPIO. Your flow sensor should use a GPIO that does not have any precautions listed on the mapping guide. That means GPIO D5, D6, or D7. 2) Just so I understand it correctly...

ThomasB

I see a typo on first line; Should be:

Code: Select all

on Box#Temp do

In case it matters, I would omit the first comma seen in your notify. Should be:

Code: Select all

notify 1, "Box temperature is [Box#Temp]°F!"

- Thomas

ThomasB

1: Consult the pin mapping guide: https://www.letscontrolit.com/wiki/index.php?title=Configuration 2: No experience with those flow sensors, but I noticed they are 5V logic output devices. The ESP8266 is 3.3V logic; Therefore you'll need to level convert to 3.3V. Sometimes a resistor divider can be ...

ThomasB

You know what this does???? If the ESP -for whatever reason- has exceeded this set threshold of failed connect attempts, it will issue an reboot. That is what I assumed it did. A few weeks ago I set it to 25 because that is a much larger threshold than zero and I was trying to stop the reboots. A b...

ThomasB

Thanks everyone for the advice. Some comments: 1. The test board sends MQTT messages at ~10 second intervals. But I'll enable "Force WiFi no sleep" and "Periodical send Gratuitous ARP" anyways. 2. I set connection failure threshold to 25 thinking this would allow the node to be m...

ThomasB

In my quest to fix the random reboots I have been validating releases of ESPEasy firmware since last fall. The latest testing on a NodeMCU device with the new ESP_Easy_mega-20200204_test_ESP8266_4M1M_VCC.bin shows good stability when it is in close proximity to the WiFi router. But reboots continue ...

ThomasB

I think it is not only the SW. I had several units with same or similar SW-Version that behaved completely different (reboot every 2 or 3 days) I continuously update SW without becomming better. I agree. Hardware problems can haunt some ESPEasy installations. I tend to see different reboot behavior...

ThomasB

Are the strings much longer? (running out of memory) ...? Maybe? My rules send MQTT strings like this example: Publish %sysname%/STATEVAR/rlyval,[STATEVAR#rlyval] Plus some plugin's send data using the device controller function. ... or is it something else? Perhaps it has something to do with the ...

ThomasB

Nice Uptime. Respect. It seems to me that the long Uptimes are on ESPEasy Mega devices that don't use the OpenHAB MQTT plugin. I suspect that the OH plugin (or perhaps MQTT in general) is inviting some reboots. A couple days ago I installed ESP_Easy_mega-20200204_test_ESP8266_4M1M_VCC.bin on a NodeM...

ThomasB

I searched some guide over the web but no success. I need to understand the basic principle of functioning to make it work...I am stopped at this point. It's been a few years since I went through the process of installing MQTT on OpenHAB. I've forgotten the installation details but fortunately ther...

ThomasB

Perhaps the serial log's Info Level will provide some useful information. That is to say, compare the sleep messages that appear during Config/Sleep Awake Time versus those you see in the Command DeepSleep . If they are different then post the logs for review. Can you measure what happens on GPIO16 ...

ThomasB

Looks like a fun project for party night. Some expansion Ideas: 1. Add your favorite drinking games to the App. Loser must drink another random beverage chosen by the App. 2. Breathalyzer monitor. If reading too high, automatically reduce alcohol in the recipe to prevent a bad hangover the next morn...

ThomasB

I think i'll have you wait until someone finds out how it can be fixed. I found some experimental code for the Shelly 1 shield on a Tasmota github: https://github.com/arendst/Tasmota/commit/50a25aeb7c52c9154e4f0f9735d57fe14a38eeb6 Unfortunately it shows that the DS18B20 temperature sensor will requ...

Search found 1065 matches