TD-er wrote: ↑19 Dec 2023, 15:47 OK, so no need to look into it further?

No, your hint was enough. I take it back and start my own investigation. Thanks

The temperature reading is always too high? I think that's the clou. What I saw that last time that I swapped the BME280 from the new one back to the old one, it first looked fine. Then after a few minutes, it started to change. That now brings my to one change that I forgot: in the old setup I had...

I was already thinking about how often to read, so I already changed from 60s to 120s.

I was running an old version of espeasy, from somewhere around 2021, on an ESP32. A BME280 was connected to it and had an offset of about 1 degree celcius. No problem. Now I created a new set: new ESP32, new BME280 and the latest version of espeasy. Now the reading is almost 5 degrees too high, and ...

Actually yes and no. I would like this to work, out of the iphone-box. We have a couple of iphones here and all keep using the default Safari just as usual. In the meantime, I tried my own suggestion. The mycustom.htm is now filled with the #getLevel piece as expected (20.30) but the current tempera...

I tried the suggestions on: https://www.letscontrolit.com/wiki/index.php/Mini_Dashboard and https://www.letscontrolit.com/forum/viewtopic.php?t=7038 What I want to create is a simple page for setting my thermostat, which is a Level Control plugin via a mini dashboard, that also shows the current tem...

Ah, and then I found an old posting, where someone was not sure if the Serial port under Advanced should be disabled, or just Log to None and the Serial Enabled.
So I tried it with the Serial Enabled, and now I see the messages in the Putty session to port 8088.

I am struggling for a while now with espeasy and my P1 meter. It's a Kaifa MA304, afaik DSMR v4. This meter is sending data at 115k2/n/8/1 with an inverted signal. This signal is reverted to normal via the usual resistors and bc547 transistor. I know the meter is working fine, for two reasons. 1. Wh...

You can even simplify it by just setting the millis() in the ISR call. When reading you set it to 0 again. So then in the 50/sec call you only need to compare it with 0 and if not, just copy the value for further processing and set to 0. Sounds creative. :) But I don't understand what you mean... I...

PLUGIN_READ is the function that tells the connected controller whether or not there is new data to send. If that function returns "success = true;" then any connected controller will receive the task data and also events are sent to be processed in rules. So that PLUGIN_READ is typically...

You can set a flag in the ISR code which stores the millis() in a volatile parameter. In the 50/sec call you then check this parameter and reschedule the call to PLUGIN_READ using Scheduler.schedule_task_device_timer(event->TaskIndex, xxx); // the volatile parameter + 5 See for some examples the co...

For now I will experiment with the PLUGIN_TEN_PER_SECOND
Any better idea is very welcome.

I am trying to get a plugin (_P145_Itho) working on an ESP32. It is based on a cc1101, connected to the esp over SPI, with an SS(CS) pin and an additional pin from the cc1101 GDO2 to the esp to signal when data is received. It works fine on esp8266, both for sending to the itho box and receiving fro...