Let's Control It

pwassink

Hi guys and girls. When upgrading an couple of esp 82* to mega-20240229 i've found that somehow the whole web-config part is missing in the energy -build 4M1 version they falll back to normal and the option web is missing in tools>advanced config menu. not a showstopper, but please investigate .. :-...

pwassink

searched on several keywords, did not find thsi isssue, so i reported it ..

But great that it is solved already ..

pwassink

Great,

but if no one mentions it and reports it that fixing wouldnt be done ..

so now td'er can fix these issues too .

pwassink

Well, reflashed the esp with beta *1125, came up allright, in devices the ds18B20 config appearedto be alright, but no temperatures or "macadresses" of the sensor were visible, a submit command and they reactivated again, seems to do the trick, but has not behaved like this before as far a...

pwassink

platform Esp8266
release ESP_Easy_mega_20201125_normal_ESP8266_4M1M
icm Domoticz

After updating yesterday of some test-nodes, all the Ds18B20 based sensors stopped working on all used versions of esp8266, seems a glitch in the last actions included in this update ?

Anyone has same eperiences ?

pwassink

Tried it on a OTA flashed your testversion to a esp12S node, works fine !
tested a bunch of sensors, P2p traffic also works

Direct upload via flasher to a separate nodemcu also works ,

the normal esp8266-4m1m binfiles in both cases ..

pwassink

Yesterday i checked for update found the mega-20200228 Beta version released, got it on github, made a esp32 version from it too

Then i looked into the released version at github-website and found no more binaries there, has something gone wrong there ?

Or have i missed something ?

pwassink

if so, be aware that the setup itself is stable, even in in a housing, the usb (powersupply) cable is fastened and not wiggeling. So all wiring, solderjoints, sensors, esp itself is fixed, does not change, cant vary in any way. Still there is a sw (core) related and reproducible fault, it had ran fa...

pwassink

Updated to version : Binary Filename: ESP_Easy_mega-20190805_test_core_260_sdk2_alpha_ESP8266_4M.bin Lets find out how that is behaving then Has been running since yesterday evening, also same issues, already more than 15 occurances of "out of sensor spec" co2 values So it seems core relat...

pwassink

I can, after 48 hours no faults appeared on hub08. Now it is running Binary Filename:⋄ ESP_Easy_mega-20190805_normal_core_252_ESP8266_4M.bin And well see how this one behaves, also for approx 48 Hours ? i think we have found something, at 21:50 the first unreal value was sent And it did continue giv...

pwassink

Just looked at the syslogdata of my hub08 esp , since last Saturday running on Binary Filename: ESP_Easy_mega-20190805_normal_core_241_ESP8266_4M.bin No glitches have occured since the downgrade, works as a charm and as designed .. Will continue to monitor this Esp, but this is an outcome i did not ...

pwassink

Did not made any analysis of the esp and noise yet. While upgrading to mega *1116 for the rest of the test net i did downgrade the fauling Hub08 to the version : ESP_Easy_mega-20190805_normal_core_241_ESP8266_4M.bin Which was the oldest i had online available on this desktop, lets see if that change...

pwassink

the reset of the stats is also a bit confusing ? yes it is .. Sensor-fault , that is why i did replace this sensor to begin with, problem stays so it has to be the combination of components and must be Esp or Sw related. Had some thoughts on this again and for a while, dit produce > 20 esp-sensor bo...

pwassink

Timing Oled seems better with these fixes , see some improvement on the bogus-values but still get them sent to domoticz. Counter of the Esp hub08 running for >27 hours now Software version : ESP_Easy_mega-20191113_normal_ESP8266_4M1M.bin Checksum (pass/fail/reset): 30/28/40 Looked at the syslog of ...

pwassink

Updated this Esp hub 08 to the new release with Oled fixes #2706 this morning P_36_Display - OLED SSD1306/SH1106 Framed READ 11 0.02 138.500 142.876 148.757 P_36_Display - OLED SSD1306/SH1106 Framed ONCE_A_SECOND 655 1.00 0.592 0.952 3.085 P_36_Display - OLED SSD1306/SH1106 Framed TEN_PER_SECOND 652...

pwassink

That last screen print was running on Oled mode "very-fast", changed that to "Instant" now which seems the fastest ?

Oled timing-page value now :

P_36_Display - OLED SSD1306/SH1106 Framed READ 10 0.02 174.722 290.892 402.140

So still around 400 Ms ?

pwassink

Correction, Oled has 2 x 4 lines of data to display and 4 lines in between are empty - not used.. Changed the scrollrate to Fast at your request now, unit is back on the bench now, waiting for the first correct Co2-value, Timings page is now like this : Oled values seems decreased a bit. http://oldv...

pwassink

Your idea is something that crossed my mind also, mainly because this is the only esp that suffers from this problem. This esp has a Si7021 for temp/hum, a BH1750 for Lux, the MHZ-19B for Co2 and a Framed Oled with 4 lines of data in "slow" mode. Also it has 4 "remote p2p" device...

pwassink

Well, Did some additional reading, looked at the plugin code, enabled syslog functon for this Esp, changed the device-filter from skipped-unstable to Fast_Response and captured this sequence a bit later, look a see: Ppm value measured, filtered and the Ppm value it actually sends out is a bit differ...

pwassink

abt that U value included a image of the deviceconfig from the confirmed mhz-19B 0-5000 Ppm variant sensor i use: http://oldvolvo.nl/gasten/fotos-in-webpages/mhz-19b-sensor-espeasy.png Sensor is in a very well ventilated housing, on its side, both openings are free to breath without direct sunlight,...

pwassink

Device = Esp8266-Nodemcu v2 Running at (official) Git Build: mega-20191108 Normal 4mb I have a couple of mhz-19A and B type Co2 sensors in use here for quite a while now, and now i have seen unexpected behavior of a 0-5000 Ppm mhz-19B model here. It is in a home environment and will vary between 380...

pwassink

i can confirm after some playing around that the version : mega-20191028 on sender and receiver has working p2p again! Had to delete the devices on the receiving end, after that they came up right, altering the remote (source) node-id-number did not seem to work, when i deleted the receiving-device ...

pwassink

Probably you should leave one sender > multiple receivers intact, use it as a broadcast style protocol. In my setup i do use this, have a esp which registers outside temp and other weather-sensors at several heigts those values are sent to domoticz but also broadcasted by p2p to the living quarters ...

pwassink

Yes it could be improved a bit ..

i just tried to disable the sending controller, reboot, enabling it again, reboot, no changes visible at the receiver (device list for the remotes still empty)

pwassink

Ok, tried this on a receiving node running at 1003 version, freshly restarted after update from a p2p working 0805 version Then deleted all "remote" devices, what youve asked for, waited a while (>15 minutes ? ) no go / no devices came up and no remote Event messages in the web-logscreen i...

pwassink

To be clear, Tested with the receiving end running on version ESP_Easy_mega-2019****_normal_ESP8266_4M1M / result Sender is running mega-20191003 normal 4mb , after each reboot of receiver with other sw version it has been running for approximate half an hour and the sending device has been disabled...

pwassink

Well, I spent some time tweaking with 2 nodes trying to figure out why the p2p messages from the remote did not appear . i mean messages like this in the logging on the receiving end : 2159611: EVENT: graspriethoogte-schuur#Temperature=14.56 I've read the documentation, this did not work as describe...

pwassink

sorry, have been quite busy with other things last week(s). Found this development document at github explaining teh way to go, sounds like, looks like it, that this is my issue more or less: https://espeasy.readthedocs.io/en/latest/Controller/C013.html?highlight=p2p Will investigate this and try to...

pwassink

I thought i did that by removing the devices on the receiving side,
did not reappear in the mega 0903 version on the receiver after that

Sender is nunning the older version mentioned in the stratpost, is that the reason that it did not re-appear ?

pwassink

Hi, Udp-port i do use here is 10466 and all units with that problem had several reboots on both sides P2p based sensor data displayed and used on several other esp-nodes was working fine for many months but stopped working after mega version 0805, after downgrading to 0805 they were working again, t...

pwassink

Hello, Today i've spent some time in getting p2p data > other Esp working again, had to downgrade both esp's to the mega 0805 version Possible that the changes TD'er made in the code in the next version (release note entry : [ESPeasy p2p] Show remote node as port description on device page are causi...

pwassink

version mega-20190315 and mega-20190311 Hello, Just updated some Esp's toe mega-20190315 here, found that the web log data display in the tools,log option does not give any data anymore checked another node with version mega-20190311 that has also no log data visible, screen stays in "Fetching ...

pwassink

I was just wondering, how is the antenna arrangement done. could you describe that or add a picture of it ? The image and the description of the postal-cluster box say its made from metal, uhf lowpower signals are not very capable of penetrating that. and i think that an external rp-sma based antenn...

pwassink

Found the new function in the tools, advanced config menu, select Old Engine enabled, after that reboot esp and the old rules work again.. Remains the question how to migrate from old to new rules engine and what the Eventname naming convention should be there Tried a single letter in capital and lo...

pwassink

Hello, Did a couple of esp-updates today with the yesterday released version mega-20181208 On one of the esp's i had a ruleset working what produced a "co2-stoplight" led display on certain values that stopped working, the rules file is still there. Tried to enter the rule config in the em...

pwassink

You are right,

And it will probably end there, but it will be more reassuring for me, and a lot less load on development
if it has been confirmed by more users having these same symptoms ?

pwassink

Hi, Might have found a little bug. I have an esp32 for testing also on esp-easy, and have another mega node using global-sync / easy udp p2p. i saw that there was a difference in how that displayed the incoming (udp messages) outside Temperature. Checked the debug-level settings of the web interface...

pwassink

Done,

#1158 opened 3 minutes ago by pwassink

pwassink

Hello,

Would it be a great change to move the factory-reset button just one menu lower, in the load firmware section ?

It is awfully close to the Save one, and it might be a more system management item anyway
so it might be be an idea to put it one tab lower in that area ?.

pwassink

Probably because i dit enter it in the mega branch ..

now it's here : Missing menu-items #1021

pwassink

tried that, hope it is in the right place ..

pwassink

Hello, This morning i tried the daily GIT version: mega-20180305 on a Esp12F with 4 Mb, the "normal" image . Still found that when logging in to the the esp it does not come up with the normal main screen, and the two menu options on the right of the menu-bar are missing completely. option...

pwassink

Login issue was fixed with mega version 27-02-2018, can be closed

pwassink

Hmm,

Thanks, I probably spent too much time finding out for sure it was not my (browsercache) fault ..

pwassink

Good morning, I did spend some time updating my testnodes tot the mega version 221, 223 and 224 - 4 Mb normal, via the webinterface/update firmware option After a reboot the node still sends correct data to Domoticz, but i am not able to login anymore via the easy-webconsole, layout top left seems g...

pwassink

One remote esp12 sender, and two receivers were used, every esp has an unique name / nodeid one with an lcd, one with oled for displaying the temperature outside the house in this testcase both do work simultaneous now, using the workaround by defining a local device name on the receiving ESP (effec...

pwassink

great, Sorry for the unclear description off the global-sync fault, tried to make it more clear. I was unable to use the device name which was automatically created on the receiver and coming off the sending node, tried to display the temp with that device name on a Lcd, oled and oled framed, nogo. ...

pwassink

Ah, Ok, that brings some light in this ! Thanks for the explanation and the job ahead , i will wait impatiently and be one of the first testers :-) Updating to mega-20180130 now, Got all the options i was missing and it does mention version 20100 in the nodelist also .. Unit 8 hub08 20000 ESP Easy M...

pwassink

Hello, I have been busy updating a lot of mainly esp-12 based nodes in and around the house last couple of days, moved them all up to Mega, version GIT version: mega-20180104, with a manual rebuild of the config on the nodes, backing up several times, and yesterday went on with version GIT version: ...

pwassink

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. Yes, but only when typ...

Search found 60 matches