Let's Control It

Ath

Guys, first of all thanks for the many replies. Awesome board!!! :twisted: I did update to version: 20240525 normal 4M littleFS ETH [ESP32] but the "old" version isnt the problem. The BME280 was on IDX 0, changing it to 1, like adviced, helped at least with the temperature problem. Now th...

Ath

Ath

jgrad wrote: ↑27 May 2024, 13:08 there is also system variable %ismqtt%

Well, when would you check that variable? You'd have to add some repeating event to check that, so responding to the original event seems more natural and appropriate.

Ath

Hmm, seems the field numbers are limited to 1..8, and a channel has to be specified somewhere, but atm, I don't see how that has to be specified in the api call we use for sending data to Thingspeak.
Will do some more investigation tomorrow.

Ath

Did some digging in the code (never used the Thingspeak controller myself :?), and you have to set an offset for the field number to use in the IDX field where you enabled the Thingspeak controller for the task. The first IDX/offset to use should be 1, not the default value 0. For any other tasks yo...

Ath

MQTTImport#Disconnected has to do with the MQTT Import plugin P037, and is, sort of, independent from the MQTT#Disconnected event. (IMHO) you can ignore the MQTTImport events for this.

Ath

We even have a wiring suggestion for the UVR42 in the documentation

https://espeasy.readthedocs.io/en/lates ... uvr42-page
This doesn't have a galvanic separation, but would be the first thing to try 'if all else fails'.

Ath

So this problem is solved.. Though not fully understood. :? Well, TD-er already wrote a possible cause above; when using a fixed IP address, the ESP plainly connects to the router, claiming the configured IP-address, not sharing much other information except the (required) MAC address. But when usi...

Ath

Under info it shows me the following: Build:⋄ 20240229 - Mega32 System Libraries:⋄ ESP32 SDK 4.4.6 Git Build:⋄ HEAD_430cc29 Plugin Count:⋄ 48 ["Normal"] Build Origin: GitHub Actions Build Time:⋄ Feb 29 2024 16:18:30 Binary Filename:⋄ ESP_Easy_mega_20240229_normal_ESP32_4M316k Build Platfo...

Ath

For this purpose there are the MQTT#Connected and MQTT#Disconnected events.
When receiving the mqtt#disconnected event you can start any precautious measures needed, and revert them once the server is connected again.

Ath

Again you also have a pulse counter task on the GPIO that's to be used by the DL-bus reader. Can you disable all but 1 task that is trying to use that GPIO, (one of the DL-bus tasks should be the only one enabled), to exclude that as a possible cause of interference? There are, AFAICS, no other repo...

Ath

What exact .bin file did you install on your ESP?

Ath

Hmm, might be a silly question, but you did select the 0x48 address from the combobox, right?

Ath

Rob73 wrote: ↑25 May 2024, 14:53 I have the s3 zero module flashed with the latest max firmware.

Can you test using the latest MEGA merge from this Actions run, it has improvements in the Framework that might help with the NeoPixel issue.

Ath

Hmm, are there other ways to communicate with the device than Bluetooth? As ESPEasy doesn't support connections via Bluetooth, atm.

Ath

Can you disconnect all other sensors from your ESP, so only the VEML (not sure what type you use) is connected? Possibly the combined pull-up resistors cause a too low value, so the sensor can't work properly.
I have tested using a VEML7700 myself.

Ath

@bison00 I did some digging into the library code, and in the default font, despite what's listed in the documentation, the degree symbol is at ascii character 176, so if you use that '░' as a literal character in your rules, you should get the degree displayed (untested, matching hardware is tempor...

Ath

Great

I've also ordered a sensor, and expect to get it delivered today or tomorrow, so I'll play with it soon

Ath

bledad wrote: ↑21 May 2024, 15:21 in log i've " calculate unknown token "
what's wrong with my script ?

This:

Code: Select all

 Elseif [gr#Power_W] => 400 and [Var#1]= 1 // si w > 400 et var 1 = 1 securite

Should be:

Code: Select all

 Elseif [gr#Power_W] >= 400 and [Var#1]= 1 // si w > 400 et var 1 = 1 securite

Ath

treii28 wrote: ↑20 May 2024, 23:44 Just curious, why 'Input' and not 'Environment'?

Mostly for lack of a better category. Environment implies it has something to do with our living environment, like temperature, humidity etc. and a water level doesn't do that, IMHO. It is an input-only sensor though...

Ath

Now I am sure I have the right version of the build you offer to me. Send you this screenshot before I press on Update Firmware. https://i.ibb.co/z4ndvTm/Update.jpg I waited for 15 minutes but the browser does not refresh.. :cry: After a cold reset I still remain in the old version... Strange, mayb...

Ath

The one I tried compiling. Both cases it came back up but I didn't see the 170 in the list of devices when I tried to add a new device. I don't think you pulled the PR to your local system with the commands you listed, the PR is in the pull/5056 pseudo-branch on GH. My workflow for building someone...

Ath

From the zip file downloaded, I tried uploading the *.factory.bin If you upload that via the Web UI, the unit will go into an endless boot-loop... :shock: When updating via the Web UI (Tools/Firmware update) you should update only the 'sketch', the .bin file, that's installed at the 'other' app par...

Ath

You're still on the original build, you should have a binary dated today, and downloaded from the link I shared above, there is now also an Energy LittleFS build for the ESP32-C3, this download: https://github.com/letscontrolit/ESPEasy/actions/runs/9160400873/artifacts/1519579985 Edit: As said, the ...

Ath

treii28 wrote: ↑20 May 2024, 19:49 I tried uploading the one you sent, the device stopped responding. (I'm at work, device is at home)

SW

What exact bin file did you upload previously? (don't see it mentioned in this thread)

Ath

... (the INA219 doesn't seem to want to read current and the BME240 apparently doesn't support humidity. The two I ordered to replace it wouldn't work at all. ... Both the INA219 and BME280/BMP280 (and a lot of other sensors too) are often 'unclearly labeled' by many of the low-cost suppliers (Alie...

Ath

H Ton, There was no need for that action. The release seems oke to me. The board is running for over 3 days and serves the needed info from the modbus meter over mqtt to Domoticz and Node-Red. That was a change that was on the TODO list anyway, so no better time to start it when someone can make go...

Ath

What have you configured in the MQTT Import task? You need to setup the topic(s) you want to import, it won't give you the raw data, as you can (easily) process that using rules.

Ath

can you please test, using a build from this GH Actions run ? OK, in preparation for when it shows up, I have a feeling I'm going to need a little more info to know how to build something off of that. (not a C person and I have a love-hate relationship with git) ... But again don't see P170. So wha...

Ath

Pieter, I've created a pull request #5057 to switch most LittleFS builds (ESP32 all using IDF 5.1) to include Ethernet support. You can download the (newly added) ESP32c3 Energy LittleFS ETH build from this GH Actions run , that should be usable to upgrade your ETH01 EVO, and include the Eastron plu...

Ath

Hi,

At the moment this is not possible, but why would you want to do that? Domoticz handles all that data just fine, no reason to leave it out, AFAICS?

Ath

@treii28 I've created Pull request #5056 to add support for the Seeed studio I2C Liquid Level sensor.

Assuming you either own or have ordered such sensor, can you please test, using a build from this GH Actions run?
You can report your findings & remarks here or in the PR.

Ath

GPIO 34..39 are input-only on ESP32 (Classic)
They even got a special paragraph in the ESPEasy documentation: https://espeasy.readthedocs.io/en/lates ... gpio-34-39 (Scrolling up from there will show you more info on ESP32 GPIO pins)

Ath

If you are building your own Custom build, either by using a Custom.h or by modifying pre_custom_esp32.py (that's used for ESP32, ESP32-S2/S3 and ESP32-C3), you have to enable that by defining FEATURE_RULES_EASY_COLOR_CODE to be 1 or true. For ESP8266 in most builds this has been turned off for buil...

Ath

@knighToFdemonS I've created Pull Request #5055 to add support for VEML6030 and VEML7700. I've tested locally using a VEML7700, but don't have a VEML6030 available, so if you have one, please (also) test using that sensor. A build is running from this GH Actions run . Please report your findings her...

Ath

Yes, that seems to be the right build for your ESP. No need to change Platformio.ini (to prevent accidental committing that change), you can, from the PlatformIO menu (Alien icon) in VSCode, expand that build (yes, there are quite a few...), and compile it from there. But to make development somewha...

Ath

I've reserved P170 for this plugin, and put it on my name

I'll need you for testing once I've done some coding.

Ath

You can achieve that by prefixing the taskname and a period to the command, as documented here

So, use:

Code: Select all

[taskA].serialsend,your_data
[taskB].serialsend,data_for_other_port

Assuming your tasks are named TaskA and TaskB (task names are not case-sensitive)

Ath

That sensor is using a rather weird technique of 2 I2c addresses to read different parts of the data. Haven't seen that before, this sensor isn't yet supported by ESPEasy. For developing an ESPEasy plugin, there's sort of a standard procedure: - Request a new plugin ID at https://github.com/letscont...

Ath

@antro31 I've changed the argument separator for this plugin from comma to dot (period), so after you update to this GH Actions run, you'll have to update your rules!

So you'd have to use like this: [Pool#sensorstats.1.success]

This will go into the release version, so no reason not to update

Ath

Great, thanks for the feedback

Ath

I was able to fix it sooner than expected, so a GH Actions run is on its way.
Please update and retest.

Ath

I2C Scan should at least list the address, the device names may be excluded, not sure if these names are included in the Custom build. You can enter the found address in the I2C Address field, but I assume you already tried that. Adding a 10k pull-up to 3V3 on both SDA/SCL should fix the pull-up sta...

Ath

Hm, I now see where I made a typo (actually, a copy/paste error)

Will be able to fix that later today, not near my ESPEasy development system ATM.

Ath

A few questions: - How long are the wires to your sensor? - Do you have pull-up resistors installed on the SDA and SCL lines? - You didn't swap the SDA and SCL wires? (no harm, but won't work) - Was the sensor used by someone else before you got it, and reprogrammed it to I2C Address 0x01? - I assum...

Ath

Ah nope, saw what Ton did: https://github.com/letscontrolit/ESPEasy/pull/5051 A bit strange to use a comma here, as we don't do that anywhere else. Why not a dot, Ton? Well, I did that also in other plugins, like P011 and P087, and in AdafruitGFX_Helper (for all supported Display plugins P095, P096...

Ath

Here's a Custom build with the new P047 - Environment - Soil moisture sensor with support for the BeFlE v3.x hardware

ESP_Easy_mega_20240513_custom_274_ESP8266_4M1M.zip: (1.26 MiB) Downloaded 19 times

Ath

That plugin has the plugin statistics enabled, but that entire feature is disabled for the Collection, Minimal and 1M (like the ESP01S) builds (and other 'bin-size limited' ESP8266 builds)... :shock: When buying new ESP's go for an ESP32 (dual-core, stable workhorse), ESP32-S3 (dual-core, many GPIO'...

Ath

What MQTT Controller?

Ath

Ah, that's because of the limitations for binary size, then the later added sensors (Adafruit and the new BeFlE v3) are excluded :o I'll create a custom build for you, and upload it here later today (I'm not near my ESPEasy development system ATM :?) Are there other plugins required for your build t...

Search found 3603 matches