Let's Control It

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 5 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...

Ath

According to this page the DHT22 should be quite OK, but maybe it suffers condensation where it is currently located, and is disturbed by that. Reading that list above, it seems the ATH20 is a better choice, as it has a range of 0..100%RH, where the DHT22 only allows 5..95%RH In another story I read...

Ath

@antro31 I've added added PR #5051 to the ESPEasy repository to add this functionality. The binaries will be available from this GH Actions run.

Can you test and report your findings here?

Ath

@Dick60 I've added a PR that should resolve your issues, it adds an event <taskname>#Address,<state>[,<address_high>,<address_low>] when the new option Event with iButton address is enabled and the Device Address is set to None. A test-build can be obtained from this GH Actions run Please report you...

Ath

I've created pull request #5049 to add support for the new BeFlE v3.x hardware, based on the updated code in the BeFlE SoMoSe repository @sptotal I haven't planned to order the new sensor, but I assume you are ordering one. Can you test the code from the PR on the actual hardware? Download binaries ...

Ath

Well, the value read from the board is an int32 (32 bit integer), that can hold a max value between -2147483648 and +2147483647, so you're not yet close to that limit. The value read from this sensor should be seen as a relative value, and as you have proven, is (mostly) related to the board, not so...

Ath

You mean calibrate from raw value to real units or something else ? I just compare now raw value bettwen two identical constructions. Yes, as said, the analog voltages can be very low, so amplification has to be high to get measurable values with enough resolution, so calibration is required to mat...

Ath

Problem is new HX711+D1. But i try 10pcs of hx711 and still overlimit Ok, reduced to a hardware/board issue, that's unfortunate, but not much ESPEasy can do about that :? Edit: NB: You always have to calibrate the board and the sensor using real world weights, as there are analog parts involved, th...

Ath

Have you checked your wiring? Don't make that too long, (triple)check the soldering/connections, the sensor-side is really low voltages, so quite sensitive to external influences.

Ath

We're not using the library from BeFlE, (and looking at that code makes me really unhappy, seeing f.e. the inconsistent method naming and the many spelling errors :(). When will that sensor be available? as it looks best & easiest to me to have it added as a new/extra model to the plugin, and in...

Ath

I found only 1 Failure in the actual Firmware but i dont know if this is for every S2 version. In the "Hardware" section of the ESPEasy FW the LED is not GPIO-4 (D4) it is GPIO-15 (D?). A couple of issues here: The manufacturer can decide to provide a LED on any GPIO they desire. The GPIO...

Ath

Are you running ESPEasy on your board, or 'plain' Arduino, or IDF?

Ath

Your MQTT broker is returning a 'Relay....' command to your unit, when you publish to the Relay topic.
This implies your configuration issue is in the MQTT broker, not on the ESPEasy side. ESPEasy doesn't have a 'relay' command, AFAIK.

Ath

kniazio wrote: ↑03 May 2024, 10:12 Has anything changed regarding RF Switch?

Well, no, still too much going on

but I do have the intention to implement these plugins.

Ath

As usual in IT, "It depends" :lol: - ESP8266: Skip that, as it's (IMHO) outdated, and really limited, in both RAM and max. bin size (The amount of work to make ESPEasy fit is increasing with every useful feature we try to add) - ESP32 (Classic): Fine for most tasks, great if you need Ether...

Ath

@knighToFdemonS The PR has been merged, and will be in the next ESPEasy release.

Ath

@oisisi The PR has been merged, and will be in the next ESPEasy release.
I originally started working on ESPEasy code, because of the poor configurability of this plugin...

most likely you need to tweak the settings, indeed

Ath

@jgrad The PR has been merged, and will be in the next ESPEasy release.
It also now has the added feature of sending events for P2P Nodes when they 'join' or get 'out of sight', for you to respond on.

Ath

@damiak The PR has been merged, and will be in the next ESPEasy release.

Ath

Thats why I was asking how the reset-pin works in ESPEasy and about the "try to clear i2c bus if stuck" option. Currently iam trying to have this option disabled and see what ESPEasy will do in case of a bad sensor. I can see the "clearing i2c stack..." in the log but it pops up...

Ath

Any particular device you use that requires this? As the only I2C sensors I know that are causing I2C bus-issues are the ATH10 & AHT15 temperature/humidity sensors, but those are of mediocre quality anyway, out of production by the original manufacturer, and have properly working replacements in...

Search found 3583 matches