[Help Needed] ESP Easy Rule for Automatic Pool Filtration Management

[Neoseb38]

Thank you, it worked the first time and it was a power supply problem.

On the other hand, I panic...

Indeed, I installed everything on 2 new esp32 eth01 through the link you provided me and the adapter for usb connection.

Wifi connections also via this link.

Then, I restored my .tar backup (there too on my 2 new esp)

And there, it is impossible to reconnect to wifi.

Only the ethernet connection is possible.

I tried many manipulations on the 2 new esp32 (clones of the original and by plugging them only 1 by 1, never 2 at the same time) and impossible to connect to wifi or even find them on my router.

The only way is to connect to ethernet, go to wifi setup and start the procedure again and it works.

I keep the wifi ip address and at the slightest power outage of the space or internet cut, it is again impossible to reconnect to wifi.

The problem is the same on the 2 new esp32.

On the other hand, no worries on my original esp32 eth01 where I can connect easily or in wifi or ethernet.

I tried to impose the wifi ip but it doesn't work either.

My problem is therefore this one, if I install my pool project at my father-in-law and me and that it is mandatory to go through my usb serial adapter to search for wifi or other it will be very complicated especially since my esp32 is found in a box and a pcb that will prevent me from recovering it and accessing the gpio0, EN, RX and TX.

IMG_5883.jpeg (2.24 MiB) Viewed 1264 times

Do you understand?

The day I change my internet provider or wifi password?

Please tell me that there is a simple solution to reconnect the esp32 to wifi in case of change and especially at the moment T to connect it at all

My project is coming to an end and if it's so complicated to connect to the wifi, it's really going to cause problems (5 months that I'm on it between the code where I didn't understand much, the design of the pcb and the box or there too I have to learn at all)

PS: the AP mode never appeared on my iPhone or MacBook even by removing the ssid and wifi pass to test.

[TD-er]

Is the ESP still connected to Ethernet when you also try to make it connect to WiFi?

The current implementation is that Ethernet is the preferred network, when available.

Using static IP can become an issue, especially when using the same static IP in different networks.
For example, what if the other network is not using the same subnet?
Or a router gets replaced for one of a different brand which uses a different subnet?
(e.g. 192.168.1.x or 192.168.178.x)
Also if you plan on using a VPN for remote access to the other network/location, you may also need another subnet on both sites.

[Neoseb38]

Is the ESP still connected to Ethernet when you also try to make it connect to WiFi?

No, only in wifi. Either in ethernet or in wi-fi, never both at the same time.

I re-try for a good 2 hours but nothing changes.

I try without going through the usb since in the future, it will be very complicated for me so I might as well find the solution without.

Each esp32 has been renamed differently and with a different number.

Nothing went into WiFi and ethernet IP Settings. (dhcp)

Unable to find any wi-fi network for any of my 2 new esp32. (only the original contains its wifi network and the possibility of connecting to it)

To succeed in connecting to wi-fi without going through your link and the usb, here's how I do it:

Connection esp32 in ethernet then:

Tools - Setup wifi

I choose my network to enter the ssid and the password.

Connect and after 20 seconds, everything is ok.

I note the wifi ip, I unplug the ethernet and everything is ok.

The esp32 works quickly (I'm next to my internet box)

My box finds the name of the esp32 in its network.

But at the slightest internet cut or restart of the esp32, everything has started again.

When I want to reconnect to the IP address, it grinds and nothing happens and nothing in the network devices of my box.

The only thing that differentiates the 2 new esp32 and the old one (which as a reminder has no problem) is the firewire.

Here are the versions of the esp32 that pose a problem:

ESP_Easy_mega_20250402_normal_ESP32solo1_4M316k_LittleFS_ETH

And that of the one who works:

ESP_Easy_mega_20241216_normal_ESP32_4M316k_LittleFS_ETH

I would like to add that the initial installation of the wifi passed after the installation of the firmwire via your link.

I have never managed to switch the 2 new esp32 to AP mode.

Even by deleting the ssid or cutting my internet box, I never found espeasy to connect to it via my iPhone.

Is it normal? The first installation of the one that works, I put connected on it (AP) then entered configesp if my memories are good. But now, it doesn't want.

PS: I won't use a VPN afterwards and I'm very new to IPs, static networks etc...

[TD-er]

Why do you use the solo1 build?
That's for a different CPU type.
The board you have does have dual core CPU. (please double check on the sysinfo page the CPU core count)
Since on dual core builds the WiFi code is running on the other core, this does actually make a difference.

You should be able to update to the other build via the web interface without loosing any settings.

[Neoseb38]

Thanks again for your help. I thought my Esp32 ETH01 was an S1 version, who knows why

I hope this is the problem and will solve all this.

I'm trying tonight after work.

For the update, I switch to ethernet and update directly under espeasy? I download this version in .bin?

IMG_5889.jpeg (206.21 KiB) Viewed 1172 times

If this solves my concern, can you explain to me (I would like to do tests) how to change the wifi ssid and password in case of change of internet operator or password change afterwards without going through your link and the usb?

Basically how can I connect with my iPhone on the esp32 via AP?

Thank you again for your help, sincerely.

[TD-er]

Yep, looks OK
ESPEasy should (I know it doesn't always do this, working on a fix) start an access point when the configured WiFi access point cannot be found.
Sometimes you may need to power cycle the ESP to achieve this.
The name of the started access point is with the node name you configured.
The default password is "configesp", but you can change this yourself on the config page.
This allows you to connect to it using your phone.
Then you can enter http://192.168.4.1/setup in your browser.
The browser should automatically go to this IP-address when connecting to the Access Point started by ESPEasy, but sometimes your phone will not do this, no idea why not.
I use standard "captive portal" instructions, you also see when connecting to some public hotspot to redirect you to some "I agree to behave nicely" page or where you need to enter some key from your restaurant receipt... well you know the use cases.
But for some reason some phone may not redirect to the page, so you can also bookmark this URL on your phone to be sure

[Neoseb38]

Thank you for your answer.
I will do tests and cross my fingers so that the new version of the firmewire solves my problem.

As for the AP mode, I was asking the question because on the SOLO1 version, it never appeared, not for lack of trying by cutting the internet etc...

Sometimes you may need to power cycle the ESP to achieve this.

Not understood?

If with the new firmewire the AP mode appears when I cut the internet or delete the ssid, you must always connect to it via this link (http://192.168.4.1/setup ) after swigging the wifi of my phone to the name enter in espeasy of my esp32 (node?)

[TD-er]

I know there is still some bug in the ESPEasy code where it doesn't consider all possible access point candidates to be tested
So this will then result in never starting the access point.
When you power cycle (remove power from the ESP, unplug from mains....) the ESP may act differently as there never was a successful connect.

When the ESP starts the access point, it will be using the same name as you gave your ESPEasy hostname.
So when scanning for WiFi access points on your phone, you will see it listed as such (e.g. "ESPEasyPool_123")

[Neoseb38]

Great, so to summarize, if the esp32 can no longer find internet after changing ssid (once at my father-in-law's for example) or internet cut, if I can't find the network (from the name of my esp32 in espeasy) on my phone, I unplug (I put an inter on/off in place of the jumper for the choice between the 230v power supply and the usb power supply of my pcb if you remember what leaves me the choice of the power supply and an on/off) and reconnect the power supply to force it to switch to AP mode.

Is that right?

Then I connect to the ip and enter the password.

At worst, I connect it to ethernet and change the ssid and password via ethernet if it doesn't work?

But hey, if the box is fixed in the pool room (very close to the house at my father-in-law but hey...)

[TD-er]

Or... I will fix this bug and you upload the new firmware before your father-in-law needs a new router
Plug in Ethernet (if possible) is by far the safest fallback as that will simply work. (please test though... )

[Neoseb38]

Thank you

I hope that for my part the non-SOLO1 version will correct the concern of losing the wifi network at each restart.

PS: if I insist on the simplicity of change for wifi, it is because my father-in-law in a house is more than 2 hours from my house, and being over 75 years old, he knows nothing about the internet (so I have to be there to look at his box for wifi identifiers etc...) and simplify his life in terms of pool management.

[TD-er]

I get it... Digging fiber optics between your houses is easier and faster to achieve compared to getting the other side to push the right reset button...

I also know a few in my family like that.

[Neoseb38]

So,

It was very very laborious but I think I found it.

I took everything back from the beginning.

1/ USB installation on one of the new esp32 eth01

2/ I didn't go through the usb for the wifi config but through the AP to test (it doesn't forgive because if there is a typo in the password either the ssid or for the configesp, it's dead, you have to restart the flash... or I don't know)

3/ connection in operational wifi but not in ethernet (I did not understand at the beginning but... normal, the gpio are not yet configured )

4/ Restore .tar file

5/ Problem..... connection impossible in wifi.

6/ now on, only the ethernet connection is possible and I struggle to understand this (because I had put it in fixed in config - Ethernet IP Settings on my original esp32 and that inevitably, it restored everything the ip) for the wifi, I had left nothing so dhcp

After struggling for 3 hours, I found the solution:

The problem came from the line Hardware - Preferred network medium which was on Ethernet.

When I switch it to Wi-fi, the wi-fi works and the ethernet no longer works (the ports no longer flash)

There, I tested to make a clear wifi in Tools / setup wi-fi/Clear WiFi credentials.

And at restart, the AP mode appears and so I can put everything back.

The concerns this poses:

If typing error during AP mode, I'm afraid that everything is lost to reconnect and no possibility to reconnect in ethernet since either wi-fi or ethernet.

Will there be a solution to this?

What is strange is that on my original esp32 with my version "ESP_Easy_mega_20241216_normal_ESP32_4M316k_LittleFS_ETH" (which was a test version that you provided me at the time because I could not save my rules in ethernet), well I have no problems.

With this version, I am in ethernet (in Hardware - Preferred network medium) and I easily switch between ethernet and wi-fi without having to restart the es32 (just by changing the ip in my browser).

The advantage is that if I make a mistake in the AP mode for the wifi configuration, I at least have the possibility to change to ethernet.

So, QUIZZ to all this, does the new version we talked about above have a bug or is it normal?

The problem is that I can't find this version on my pc and therefore I can't test.

Hoping not to have lost you on the way for understanding

[TD-er]

If you have access to the ESP via either WiFi/Ethernet or serial, you can easily set the wifi password and/or SSID using commands:

Code: Select all

wifissid,YourWiFiNetworkSSIDName
wifikey,YourSuperSecretWiFiPassword
save

These commands can be entered via the serial console (the web flasher page also allows you to open a console window, or use some serial terminal tool like Putty) or the "command" field on the Tools page.
One line at a time, so do not copy/paste these lines all at once.
And of course you need to fill in your own values.

The web flasher page also can help you to select a WiFI network via the wifi setup button when you connect to the ESP.

I think part of the fix used in the 'test version' which fixed the rules save issue was that it also was using a newer SDK which happened to have just that fix but was otherwise quite new and relatively untested.

So we can make a newer build for you.

Sadly the past few weeks I have been extremely busy with non-ESPEasy stuff which delays all testing and programming on ESPEasy.

[Neoseb38]

Thank you for all your new information and I take good notes.

Or can I find the version you gave me at the time, if of course it is possible to find it?

I would have liked to confirm that the problem comes from the firmewire version because if this is the case, it is much simpler since if you connect an ethernet cable to the esp32, it switches directly to ethernet and vice versa to the wifi when unplugged.

So much better than having to choose one or the other and thus risk wifi problems (in the years to come) without the solution of folding into ethernet to remedy it. More easily.

[TD-er]

You can see the build time on the sysinfo page of the version that is working (apart from saving the rules maybe)
Then I can look on my PC to see whether I have it still there.

[Neoseb38]

Capture d’écran 2025-04-15 à 21.41.59.png (116.17 KiB) Viewed 1052 times

[Neoseb38]

These commands can be entered via the serial console (the web flasher page also allows you to open a console window, or use some serial terminal tool like Putty) or the "command" field on the Tools page.

How do we enter the esp32 once in the console or putty?

[TD-er]

Found it and made a ZIP for both files for you: https://www.dropbox.com/scl/fi/k8g5og9c ... guavx&dl=0

Remember, the "factory" build to flash via serial port and the file without "factory" in the name to flash via the web interface.

[Neoseb38]

Thank you, I'll test all this tomorrow night.

Yes, I remember well.

.Bin for update and factory for the first installation.

On the other hand, if this version works and the problem came from there, if afterwards I want to install it directly (without going through an espeasy update) how do I do it on your link?
https://td-er.nl/ESPEasy/latest/

[TD-er]

These commands can be entered via the serial console (the web flasher page also allows you to open a console window, or use some serial terminal tool like Putty) or the "command" field on the Tools page.

How do we enter the esp32 once in the console or putty?

Just connect the ESP via the serial port or any USB to serial adapter you may have.
So the USB adapter's RX to TX on the ESP and TX of the USB adapter to RX of the ESP.

Then either load the web flasher page ( https://td-er.nl/ESPEasy/latest/ ) and press "Connect" (doesn't really matter which build you select)
Then select the correct serial port in the pop-up window and continue.
Then the web flasher page will show a white pop-up window showing the name of the device, detected ESP model and some other info. Below that there will be 4 links you can click, one of which is "LOGS & CONSOLE"
Press that last one and a black console will be shown in which you can enter the commands I mentioned.
Or you press one of the other links "CHANGE WI-FI" and follow the next steps.

[Neoseb38]

Then either load the web flasher page ( https://td-er.nl/ESPEasy/latest/ ) and press "Connect" (doesn't really matter which build you select)
Then select the correct serial port in the pop-up window and continue.
Then the web flasher page will show a white pop-up window showing the name of the device, detected ESP model and some other info. Below that there will be 4 links you can click, one of which is "LOGS & CONSOLE"
Press that last one and a black console will be shown in which you can enter the commands I mentioned.
Or you press one of the other links "CHANGE WI-FI" and follow the next steps.

Ah ok, I knew that yes, I spent so much time on it his last days

I thought I could do it without going through the serial port and therefore USB.

As already said above, I would like to do without this option because the pool management box will be placed in such a way that it will be difficult to access the esp32. Especially since this one is soldered to the pcb and has no original USB port

[Neoseb38]

I don't know if you had time to see:

Thank you, I'll test all this tomorrow night.

Yes, I remember well.

.Bin for update and factory for the first installation.

On the other hand, if this version works and the problem came from there, if afterwards I want to install it directly (without going through an espeasy update) how do I do it on your link?
https://td-er.nl/ESPEasy/latest/

[TD-er]

If you have a node with Ethernet, why not using that one?
After all, it is way more stable than WiFi.

And the WiFi antenna on those Eth boards is always sub-optimal.

Another thing you can consider is to add a simple WiFi extender which you can plugin in a wall outlet at maybe a better position to receive WiFi from the house and even act as a local WiFi extender near the pool.

I had one of those cheap TP-link ones and you could set it as a transparent bridge from WiFi to Ethernet.
This way I could couple my SMA SunnyBoy PV inverter to my network, which was in the back of my garden.
It had an Ethernet connector and as such only that one was configured to connect to WiFi.
When you need to 'fix' any WiFi issues, you just need to unplug that extender and nothing else.

[TD-er]

I don't know if you had time to see:

Thank you, I'll test all this tomorrow night.

Yes, I remember well.

.Bin for update and factory for the first installation.

On the other hand, if this version works and the problem came from there, if afterwards I want to install it directly (without going through an espeasy update) how do I do it on your link?
https://td-er.nl/ESPEasy/latest/

You can also download the 'all.zip' and just extract the bin file you need and update it via the web interface of ESPEasy.
So on Tools-page and then "Upgrade firmware"

[Neoseb38]

The ethernet port is for my pool which already has a pulled network cable in my pool room.

For my father-in-law's, it will be in wifi and as already said, I will avoid putting too many devices on it.

For the range, it is not excessive and I soldered an antenna on the esp32 lol

IMG_5892.jpeg (2.42 MiB) Viewed 1021 times

[Neoseb38]

Otherwise, I had thought of passing the wired network through a carrier current...

To meditate

[TD-er]

Ehh can you show a close-up of how that antenna is being soldered?
Not sure if that is how it should be done.
Antenna impedance matching is quite tricky to do it well.
As in that's exactly what I've been doing the past few months as a paid job. (apart from other things)
And it is absolutely tricky to do.

Also soldering coax cable to PCB traces can easily break.

[Neoseb38]

IMG_5894.jpeg (1.9 MiB) Viewed 1008 times

I used this post:
https://community.home-assistant.io/t/h ... ard/131601

The ESP32ETH01 has exactly the same integrated antenna as the first message of the tutorial.

So I tried to apply myself and I used flux for welding.

I also tested the good continuity of the mass with the ohmmeter and checked that the 2 wires do not touch each other, which is the case.

On the other hand, I don't have the impression that the gain is enormous, I'm waiting to be able to test concretely once this new ESP is operational

[Neoseb38]

I just tested the test version you made me and how to say:

It works perfectly!

In wifi, I connect the network cable and direct I can connect in ethernet with the other ip. In addition, the speed is instantaneous during navigation.

I unplug the network cable and direct it switches to wi-fi where I can connect to it via the ip and all this without having to restart the esp32.

The rules can be saved (well, it happens that the submitted light is not displayed and that it does not pass but by scrolling the save it passes directly )

Not yet, test the AP mode in case of loss of internet.

In any case, what a shame that the new versions of espeasy do not have this operation.

To be forced to choose in the hardware / Preferred network medium tab and then reboot is a shame.

[TD-er]

Well good to know that I need to look into this before any new official build is made.
So not 'a shame' but thank you for reporting such an important issue!

[Neoseb38]

To be forced to choose in the hardware / Preferred network medium tab and then reboot is a shame.

Unfortunately, this is not what I had initially marked.

I had ended the sentence with "is complicated", I would never have allowed myself to say that.

The fault of Apple translation and not having reread (as often)

Apart from that, tonight I will test to simulate internet outages to see if the AP mode is triggered in the event of a cut.

If this does not work, will there be a solution (rules or other) to ensure that espeasy checks that the wifi connection is operational and that if "no" it automatically switches to AP mode until the connection returns.

Ditto in case of a typo of the ssid or ssid password since this will necessarily include a non-return of the internet connection.

Do you understand what I mean?

[TD-er]

Yep I totally understand what you're asking.
Just keep in mind that the English language also isn't my mother tongue.

How it should have worked:

With credentials saved:
Can ESPEasy connect to a network?
If no, retry a number of times and after some time (I think it is 60 sec), start soft-AP mode

If soft-AP mode is active and no client is connected to it, then 60 sec after it was started (or 60 sec after client was disconnected from soft-AP mode), stop soft-AP mode and retry to connect to a network.


Without any credentials saved: (e.g. after factory reset or clean flash)
Scan for WiFi networks so we can present a list of networks quickly
start soft-AP mode
If no user is connected to soft-AP mode, after 5 minutes, stop soft-AP mode and perform a scan to have an updated list.
Then start soft-AP mode again.

[Neoseb38]

Yes, that's it.

Of course, I know that there is the solution of the serial port with the usb connection (so much simpler) but I assume that there are many projects based on esp32 where it remains inaccessible (swimming pool, tank etc...)

This is the reason why the connection via AP remains the priority for me.

Sure the current version of espeasy (not the test version that I have not yet tested on this subject) after flashing the esp32, I encountered 2 problems.

- If the ssid password is typing error on the espeasy page (in AP mode), well, we lose the AP connection and therefore the possibility of changing it.

- if typing error during the password to access espeasy (configesp), it is the same problem.

I didn't try on the test version that solves the ethernet problem to see if this problem is solved.

I also did not test once everything is operational (first complete wifi installation after the flash) to see the behavior of espeasy if internet outage (to simulate a change of ssid password or change of internet operator)

[Neoseb38]

At the top, I just tested with wi-fi password deletion and after restarting, connection in AP mode then access to the page http://192.168.4.1/setup.

Ditto if I delete the ssid, after restarting, connection in AP mode also then access to the page http://192.168.4.1/setup.

On the other hand, if I make a mistake in the password 'configesp", it becomes a pain because no longer access to the page (http://192.168.4.1/setup) and after restarting, it no longer asks me for the password which is problematic because no more access to the espeasy web page in AP mode.

So I was able to reconnect to ethernet and re-enter the wi-fi connection information.

I think that by entering a wrong password (I had deliberately done it to see), my Mac to save the connection information to this network with the new password and probably the reason why it no longer asked me for a password in AP mode.

After forgetting the network, everything came back in order (by putting configesp back this time)

So it works well on my test version.

Thank you again.

[TD-er]

When entering the wrong password for 'configesp', your phone probably remembers the password.
So maybe you can long-press on the found AP on your phone and then select something like "forget" or however it is named.