Let's Control It

Rampler

Sorry for my late answer ..
I can't detect any issues with the release. Tested on three ESP8266s

Rampler

TD-er wrote: ↑18 Apr 2025, 23:26 Only thing I need is some time to setup those GH Actions workers in such a way that it is also safe to run in my own network.

That would give me the biggest headache ..

Rampler

I was in hope, that we get today the "EASTER release" ....

Rampler

You saved my day !!
Now it is working as execpted - THNAK YOU !!

Rampler

Thank you, for this minor detail.

I wll test it again, when the build is ready ..

Rampler

I use this release: ESP_Easy_mega_20250402_normal_ESP8266_4M1M This sample wont work: on Clock#Time=All,**:** do Let,kv,3 LogEntry,'kv=%kv% o. kv=[var#kv]' If [var#kv] = 3 LogEntry,'HIT' endif endon EVENT: Clock#Time=Fri,15:15 2810109: ACT : Let,kv,3 2810114: ACT : LogEntry,'kv=%kv% o. kv=' 2810116:...

Rampler

Now i do a test with p2p disabled, i will report here ..

Rampler

OK, it doesnt mater what i configure.
The time drift is after a few days at least 15 seconds.
At the moment, i have all devices with ntp defined, exept the deepsleep devices, this devices havent a time defined.

Rampler

NTP activation on the deppesleep devices is not a solution. Timedrift is still happening...
Now i deactivate p2p on the deepsleep devices...

Rampler

.... I will have a look as this could indeed lead to serious time differences. ... So this should never be advertised via p2p when using deep sleep even though it might have been set "just now", it will seriously impact time sync. In the meanwhile i activate NTP also on my deepsleep nodes.

Rampler

Thanks for your quick reply. I have deleted my specific NTP Server entry, as suggested. All your explanations make sense, but do not explain why a have around 6 days time difference !! I use 10 ESP's with NTP enabled, 2 ESP's without NTP. On all devices p2p is active. The 2 ESP''s without NTP are co...

Rampler

Hi Community, i am wondering, why my ESP's (esp8266) have the wrong time. Under advanced, i set "use NTP" . Screenshot 2024-08-30 at 14-29-31 Gartenhaus.png Under Main i see that NTP is succesfully initialzed: Screenshot 2024-08-30 at 14-31-43 Gartenhaus.png But TIME Source says ESPEASY p2...

Rampler

Hi Experts, today i realized that my rule does not work anymore.. On System#Boot Do if [VAR#1]=0 //Variables will be set to 0 only on power cycle, the state will be stored as long battery is connected timerSet,1,30 //Give us 30 seconds after power cycle in order to logon to gui endif timerSet,2,30 /...

Rampler

The debug logging has been disabled for ESP8266 Normal builds for a couple of months. I didn't know that.. THANK YOU What debug log would you want to see? As not much information in that log level is usable for non-developers :? I use the Serial plugin. It was useful to see what was sent or receive...

Rampler

ESP_Easy_mega_20240331_normal_ESP8266_4M1M
The Eastern Version ..

Rampler

Hi Experts, as described here: https://espeasy.readthedocs.io/en/latest/Plugin/_Plugin.html#list-of-official-plugins the normal collection should have the debug option, but it isnt. NORMAL is the regular set of plugins, this is the base set of plugins, and with all secondary features enabled, like I...

Rampler

OK, finally after upgrade all is fine ..

Rampler

OK, for the test i used ESP_Easy_mega_20240321_collection_F_ESP8266_4M1M which do not support {D} i think.
In tools / system variables {D} is missing..

Rampler

OK, i have just flashed the newest version ..
%systm_hm% now works
{D} still not

Rampler

Have you tried to update to the current 20240229 release?

No, because i have problem with that release, regarding disconnects ..

Rampler

Hi Experts,
my ssd1306 no longer shows °C, coded as {D}.
Unfortunately, the variable %systm_hm% is no longer updated with the actual time.
It must have worked at some point in the past....
What happened ?
Using ESP_Easy_mega_20231013_normal_ESP8266_4M1M ..

regards Klaus

Rampler

OK, 29.2 ==> Leap year, sorry for the stupid question ..

Rampler

Hi Experts,
am I correct that leap build is the last build before a big change?

regards Klaus

Rampler

Hi,
i updated my ESP8266 a few days ago to mega-20230930 without problems.
Now a saw mega-20231013 only 14 days later.
Should I worried, because the short interval of the update. Where there any big issues ?

best regards Klaus

Rampler

Thanks for clarifing this ..
New for me was, that there are two different versions of MQTT Plugins depending from which collection i use.
I wouldn't have been suprised if the MQTT plugin missed at all.

regards Klaus

Rampler

Hi together,
i am a little bit confused...
MQTT Plugin differs in:
ESP_Easy_mega_20230513_collection_F_ESP8266_4M1M.bin
and
ESP_Easy_mega_20230513_normal_ESP8266_4M1M.bin.

Is this intented ?
Collection F:

: SZ.png (31.12 KiB) Viewed 2123 times

Normal:

: HMUART3.png (31.21 KiB) Viewed 2123 times

regards Klaus

Rampler

Thanks for the tip, I didn't know that ..

Rampler

Today I did another update with no problems !!
So sorry for the hustle...

Rampler

Is there a plan when the next release will be made?
I assume that this is done as needed, correct?
I ask because I would like to have the new plugin 147.
If a new release were released in the next few days, I would wait with an update..

best regards
Klaus

Rampler

Thank you for your comment

Rampler

Hi together, i have the following working rules.. Is that ok from a performance point of view, or can I simplify it too? Rule 1: on System#Boot do timerSet,1,1 // Init Display after 1 Seconds lcdcmd,off pwm,5,20 Let 1,20 endon on Rules#Timer=1 do // Wait until MQTT is connected lcdcmd,on lcd,1,1,Wai...

Rampler

Sorry for my late answer..

Here is my device configuration:
RX: GPIO-3 (D9)
TX: GPIO-1 (D10)

SDA: GPIO-5 (D1)
SCL: GPIO-4 (D2)

Switch: GPIO-14 (D5)

GPIO0 is not used ...

I currently know whether I should dare to do an OTA update.. that would be my third victim

Rampler

Hi, after OTA upgrade my ESP8266 V1 mini pro is defect. Since the ESP was not reachable over wlan after OTA, i tried to flash it via USB cable. The ESP ist died !! I have many ESP8266 in use, just one always dies during OTA. For now it is the 2nd time happended. Does anybody know under with circumst...

Rampler

@Ath
You made my day !!
Switch to "Home Assistant (openHAB) MQTT" was the solution !!

THANKS !!!!

Rampler

Hi guys, i want to switch a GPIO via MQTT. (The GPIO is only used in rules) Switch the GPIO via http is working fine: http://Heizraum-ESP/control?cmd=GPIO,4,1 Switch via MQTT does not work: mosquitto_pub -d -t /Heizraum-ESP/GPIO/4 -m 1 The device reports already some values to my MQTT Server. Contro...

Rampler

TD-er wrote: ↑23 Jul 2022, 17:45 it is part of "Testing B" (N.B. this will be soon renamed to "Collection B")

Rampler

Now, i have tested with a new CCS811 sensor. ==> Same peaks Nevertheless I have seen that the peeks will caused from my DHT22 sensor. I have choosen the "Enable temp/humid compensation:" in the CCS811 Plugin. Therefore every time the DHT22 gets a "nan", TVOC and eCO2 will rise up...

Rampler

For those who have doubts...
It is difficult to explain that [TESTING] is stable...

: Testing.JPG (49.69 KiB) Viewed 7930 times

Rampler

On the other hand, many users do not use TESTING A B C builds, because they think that they are "only" test builds.

Rampler

"Testing" is a legacy naming schema which we need to change as it is confusing.
I'm open for suggestions for a better name.

As i mentioned before:
NORMAL A B C .. convention would be better.. (instead of TESTING A B C)
And
Leave the [TESTING] behind the sensor name in device list

Rampler

According to the list of plugins this plugin is in the TESTING A build-set, so it is available for use. In my understanding, TESTING builds are builds to test. But it seems, that TESTING A B C .. are normal builds with different plugins. IMHO: NORMAL A B C .. convention would be better.. (instead o...

Rampler

I'm not sure if the SGP30 needs any external compensation, but I think it has that capability/compensation itself. SGP30 Datasheet: The SGP30 features an on-chip humidity compensation for the air quality signals (CO 2 eq and TVOC) and sensor raw signals (H2 signal and Ethanol signal). To use the on...

Rampler

Is it possible to implement temperature and humidity compensation, like the p090_ccs811 plugin does ?

Rampler

Will the _P083_SGP30.ino intergrated into the normal builds ?
What are the conditions in order to migrate the plugin into the normal builds ?

Rampler

Thanks for the information ..

Rampler

Ath wrote: ↑19 Jul 2022, 10:03 Can that sensor be contaminated/schmutzig or just of poor quality? Especially as the SGP30 seems to be working as intended.

Good point.
i will order another CCS811 and test it again.

Rampler

Hi together, a use the CJMCU CCS811 board with temperatur and humidity compensation via DHT22. I am only interested in tVOC values. The sensor had have enough time for burning, more than a week. The sensor is installed in the toilet. Unfortunately the ccs811 produces senseless peaks. peaks.JPG Any i...

Rampler

Hi together,

in the source i see the following line:

Code: Select all

addLog(LOG_LEVEL_INFO, F("SGP30: Restore last known baseline values"));

Could anybody so kind to explain the Baseline handling of the sensor ?
When will the baseline stored ?

regards Klaus

Rampler

Or do you mean the naming "normal" and "testing"? Yes, indeed ! My understanding is that test_A means firmware to test !! (using on your own risk!!) I bought a ccs811 sensor, but a thougt, it is not really working .. Better naming would be for example part 1: 1: included this .....

Rampler

I cant see any problem with the CCS811 plugin.
What have to happen in order do migrate this plugin in normal build ?

Search found 108 matches