Let's Control It

TD-er

I made a pull request which does take this embedded flash flag into account:
https://github.com/letscontrolit/ESPEasy/pull/5175

GitHub Actions build: https://github.com/letscontrolit/ESPEas ... 2253694421

TD-er

OK, so it is not marked as embedded flash.

I think I can add those pads to the selection, if no embedded flash is present, but with a warning (maybe even double warning...)

TD-er

Ahd how is the flash reported on the sysinfo page?
Is it marked as "external flash" (or at least not marked as "embedded flash") ?

TD-er

Do you have a link to that board and/or a photo of the pins being exposed? And can you also show what is shown on the sysinfo page regarding the detected ESP chip and flash? GPIO-11 could maybe be exposed, if the flash is not embedded. I have to check the datasheet to see when GPIO-12 and -13 might ...

TD-er

Check!

So my motto applies here too

"Measuring is knowing if you know what you're measuring"

(in Dutch: "Meten is weten als je weet wat je meet")

TD-er

Hmm the MQ7 is a carbon monoxide sensor. This is quite hard to test as you really don't want any (!!) CO near you. If you already see some significant changes when simply breathing in this sensor, then I guess it is useless as a CO-sensor as your breath should not have CO in it, or at least not enou...

TD-er

This does depend on quite a lot of parameters. If your switch task is set to do some debounce filtering, then of course this will be the minimal delay. I notice you do check for: "on GPIO#2=0 do" So the event will only be dealt with when the task value changes to '0' Is your switch task se...

TD-er

OK, so it seems the ESP-Home flash tool does create this partition layout.

TD-er

Great!

I wonder how that partition layout was set.
Was there ESPHome installed before or was it the ESPHome flash tool which adds it?

TD-er

Ah that's clear, what is happening :) Luckily it is easy to fix :) As you can see, the file system is only 60k in size, where it should be about 316k (see part of the filename of the bin file) You should first flash an "empty" bin file (supplied in the zip file) with the right size, or let...

TD-er

Hmm that's strange... Does the web page show any information about not being able to save data? Did the ESP have some previous non-ESPEasy build installed? Can you look at the sysinfo page at the flash section (Near the bottom) and see how large the file system is? The sysinfo page can be accessed v...

TD-er

I have just read your posts very briefly. Maybe there is some issue where you need to wait for the MQTT#connected event before sending data? Otherwise it may not be sending out data as it is not considered 'connected'. The published messages should end up in the controller queue, but maybe things wi...

TD-er

Just also make sure you setup everything in such a way that if things fail to switch off, no damage can be done. For example a relay to a pump will always fall back to the position where no damage can be done and there is some clear warning indicator when some sensor cannot be read for a while as co...

TD-er

Right now, I don't think it is a defect. At least it doesn't sound like it. Most likely to me is that there is some strange handling of those GPIO-16 and -17 while accessing the flash to start writing. Since those are being used for Ethernet on this board, you can get strange interactions with the E...

TD-er

OK, that does look good.
I guess I need to test it myself on such a node here.

TD-er

Can you take a look at the web log page with this inspect window open on the network tab?
It should show you a load of JSON about every second.
Just to see if this is regular or not.

TD-er

Please note that this is not just having 2 of the same MQTT controllers, but just any combination of MQTT controllers as they do share a lot of common code. (only the platform specifics like message formatting differs) For any combination of MQTT controllers, only the first enabled MQTT controller w...

TD-er

There are lots of other non-MQTT controllers, like HTTP, or store to flash. So that makes it a valid use case to have multiple controllers available to a task. From a task perspective it should not matter whether the configured controller is disabled or enabled. You simply configure a task to send t...

TD-er

Also as far as I can see, even Home Assistant doesn't allow for >1 MQTT broker to be configured.
In HA: Settings->Devices and integrations -> MQTT
This only allows for 1 item, which looks to me like it cannot have >1 MQTT configuration

TD-er

Frequent disable/enable of controllers will probably have unsdesired side-effects. When disabling a controller, the data in the controller queue will be attempted to flush. However the minimum send interval is going to be obeyed so it may take some time. If flushing fails, then the disable call will...

TD-er

Can you check using the 'inspect' window of your browser to see if the rules JavaScript file is even loaded when connected via Ethernet? Most informative is probably the "network" tab in the 'inspect' window and the 'console' tab at the bottom of the 'inspect' window. Just right-click and ...

TD-er

Also the same "first enabled MQTT controller" rule should apply to making the connection.
If it does actually try to connect to both, then that's a bug and I think it will probably result in a quite unstable system if it actually tries to connect to both.

TD-er

He already mentioned a 1/5 ratio, so I assume he's trying to get 0...5V range into 0...1V range. Nearly all NodeMCU boards I have seen, have already resistors present to map 0... 3.6V into 0 ... 1V for the A0 pin. So adding the 1/5 ratio to it, I think it will be enough. N.B. the resistors present o...

TD-er

That's going to take quite a lot of code changes as there is currently only one MQTT client instance.
Even the used library (pubsubclient) probably needs some changes to be made.

TD-er

What you're looking for is not yet implemented in ESPEasy and it's called "MQTT Auto Discovery" Ton is looking into it as it really makes things a lot easier to add things to HA. I know there are users who managed to publish the right topics to the MQTT broker to make HA work with ESPEasy,...

TD-er

VCC builds are NOT what you need, as those have wired the Vcc that power the ESP8266 to the ADC.
Since that can only be done before even starting the sketch, there is a separate build for it.

So better use a build without "VCC" in the name for ESP8266 if you need to measure via the A0 pin.

TD-er

Is your WiFi network on the same subnet as Ethernet? What I'm thinking here is whether your Windows may consider one network as "private" network and the other as "public" network and use different settings in its firewall for both subnets. When saving rules your browser does run...

TD-er

That's possible. You could also wrap more data in an 'event' command. This way you can use multiple arguments and handle in rules what to do with them. Or hand it over as 'asyncevent', so the commands will then be queued and dealt with later. This way ESPEasy may be ready much more quickly as it doe...

TD-er

The PZEM-004T does have some isolation between the section which you connect to the ESP and the mains voltage. However, make sure to keep the wires connected to your ESP out of the way of the mains voltage as those typical 'Dupont wires' you may use are typically not isolated enough to withstand mai...

TD-er

More clearly, it will explicitly free up allocated resources on those pins if no PSRAM is found. So it should no longer be accessible from any PSRAM related code. However... The LittleFS build is using a newer ESP-IDF version, so if it still doesn't work, please also try the LittleFS build. If you m...

TD-er

When the build is ready, can you try this build: https://github.com/letscontrolit/ESPEasy/actions/runs/12147568155 You need to have a GitHub account to be able to download the files. You can update it via the tools->update firmware page when using WiFi. N.B. you need to use the bin file without 'fac...

TD-er

Does the ESP32 ping library of the Arduino IDE support ESP32-C3? https://docs.arduino.cc/libraries/espping/ Without even looking, I am quite sure all those network related libraries out there are not tested on ESP-IDF5.x code with Arduino 3.x For the very simple reason that ESPEasy and Tasmota have...

TD-er

I am working on a network/wifi rewrite of the code, so I can also take a look at the current code to see how hard/easy it is to also include ping for ESP32-xx

TD-er

What ESP32-chip is reported on the sysinfo page?

TD-er

Hmm I got the feeling this might have to be related to PSRAM support (again....) Does by any change your Ethernet configuration use either GPIO 16 or 17? (e.g. for the Ethernet clock) If so, then I guess we really should disable PSRAM support for ESP32-classic as it is hardly available on ESP32-clas...

TD-er

Hmmmm do you have a link to that board? I have not yet seen boards with 8M flash and 8M PSRAM. Since the S3 is a bit tricky to what firmware file is flashed when you have PSRAM on the board, I would like to look into that board to see how the flash and PSRAM is wired to the ESP chip internally. If y...

TD-er

ESPeasy supports ESP32 C6. https://espeasy.readthedocs.io/en/latest/ESPEasy/ESPchips.html#esp32-c6 In that sense XIAO should be supported. Unfortunately, I could not find any tutorial describing how to use it with ESPeasy. Not sure what you mean by that last part as these boards typically use the n...

TD-er

Via the web installer you can also let the ESP scan for WiFi and then enter the credentials. Just for completeness as you now managed to flash it apparently. That was my upload earlier: ESP_Easy_mega_20240822_normal_ESP32_4M316k.factory.bin That file is for the ESP32 (classic) You now have the ESP32...

TD-er

I have not yet tested the C6 of that form factor series from SEEED Studio.
But judging on the quality of the C3 and S3 they make, I would expect those to be very stable and with good WiFi quality.

TD-er

If the board has a 'boot' button (connected to GPIO-0), can you keep it pressed while connecting to USB and keep it pressed till the flashing has begun? And please also try the web flasher: https://td-er.nl/ESPEasy/latest/ (Chrome on Windows, other browsers like Edge may work, but not tested) If you...

TD-er

To do a factory reset, you can also short RX and TX and then boot the device.
The reset button only pulls the EN pin so the device reboots.

TD-er

I don't see any immediate issue.
Only thing I don't understand is the mentioning of 2V on the Victron.

TD-er

That's even better. The reason I did not mention it specifically is because those are not always easy to find and/or sometimes way too expensive. However I really do like these icoupler chips. They are available in many configurations, like for SPI, I2C, UART, etc. And you can get them for quite hig...

TD-er

On ESP32-xx it makes perfect sense why it doesn't work as the current implementation of the addressable LEDs is using RMT. However yesterday the Tasmota team released a complete rewrite of the addressable LED library which allows for switching between RMT/I2S/SPI. (I have been part of the discussion...

TD-er

Sounds like there might be some RF calibration data left in an area on the flash which isn't cleared when flashing a new version. For this reason we do have 'blank' bin files (different sizes) So first blank the entire flash and then flash a newer build. Also why don't you try the web flasher? This ...

TD-er

Oh and the transistor part on the ESP side should be pulled up to 3V3, not 5V.

TD-er

Ah now I see you have the transistor part of the optocoupler which will pull it down when the LED lights up, so I guess you may have had it wired correctly.
Still I think testing with a LED is important to see if it even lights up.

TD-er

I am not sure about the LED. I think the signal will be inverted if it would light up at all. I would expect the LED to be mounted between TX and GND (thus red wire to TX and black to GND) Can you try with a LED and the calculated resistor to see if it even starts blinking when connected between TX ...

TD-er

In the controller settings.

TD-er

OK, that makes total sense that the repeater was to blame here as you had it with (nearly) all your nodes. It should either be something related to HA/MQTT broker or the network. The reasons why I suggested those changes: - Longer timeout... If for whatever reason the MQTT broker responds too slow (...

Search found 9372 matches