When compiling your build add the following to user_config_override.h:
#ifndef USE_NEOPOOL
#define USE_NEOPOOL // Add support for Sugar Valley NeoPool Controller - also known under brands Hidrolife, Aquascenic, Oxilife, Bionet, Hidroniser, UVScenic, Station, Brilix, Bayrol and Hay (+6k flash, +60 mem)
#endif
If you use tasmocompiler (benzino77-tasmocompiler) add that part in Custom parameters.
Thanks, I think this will get me there.
Will plan an evening this week to put some time and effort in this.
It is just under the title, highlited with red, it’s like a drop-down list. Just click on the “>” in the right.
Compiled and flashed the Atom Lite yesterday.
It is connected to my Wifi and to the Sugar Valley, double checked the A/B and Tx/Rx connection.
Everything done like stated in the ‘manual’ Sugar Valley NeoPool Controller - Tasmota
And got exactly the samen issue as @RalphT and @Smarinof
I compiled and flashed again, but with the same result; no data visual in the WebUI of Tasmota as seen on the first image in this post.
Anyone got some advice on where I went wrong?
Did I use a wrong compiler? Did I chose a wrong board (Atom Lite = Generic ESP32?):
Any advice would be more then welcome!
Edit;
I checked via Console if the NPControl command works, just to check if the right optional parameters and firmware are on the Atom Lite. This seems to be the case because I got a response;
@alexdelprete I have the exact same components as you have (Atom Lite and Tail485), would you please let me know which steps you have taken to get your setup to work?
You chose the wrong GPIO pins in the configuration. Configure all GPIOs to None, then configure 26 & 32 like this:
I don’t know why you chose 1 & 3, if you check the Tail485 docs, in the PinMap section you see the correct pins:
Thanks for the suggestion. I used 1 and 3 because the manual (Sugar Valley NeoPool Controller - Tasmota) said so, not thinking this would be different when using a Tail485.
So thanks for pointing this out.
Unfortunately this did not solve the issue because I still have no data visible in the gui.
These are my module settings now;
I have tried switching the Tx and Rx, restarted multiple times and tried using a template (which I made the same as above module settings).
I double checked the wiring and connections which all are solid and correct.
I have tried with and without MQTT settings, all without succes.
Any other suggestions?
Please show some pictures of the connection to the mainboard: a general view and a close-up of the connector where we can see the pins and how you connected them. Also how you connected the wires on the Tail. I hope we can distinguish the colors.
This is the second set of wires I used. Because I wanted to rule out a faulty wire I replaced the first set.
Wifi connector, from top to bottom;
1 - Red → 12v on Tail485
2 - empty
3 - Yellow → A on Tail485
4 - Green → B on Tail485
5 - Orange → GND on Tail485
I have tried connecting to ‘Display Modbus 1’ , ‘Wifi Modbus 2’, Extern Modbus 3’ and ‘Display’.
And I have tried switching the AB wires (so Yellow to B and Green to A).
None were successful.
The 12v and GND seem to be connected correctly because when connected to the Sugar Valley I can reach the Atom Lite (with Tasmota webUI) normally. I just seems like the AB connections are not working.
Also when I give the command NPControl I get all ‘0’ which implicates the none of the modules are connected;
I read something about the modbus in the override file:
#ifndef NEOPOOL_MODBUS_ADDRESS
#define NEOPOOL_MODBUS_ADDRESS 1 // Any modbus address
#endif
Is this something I might need to put in the override file when compiling?
Edit; just to be sure I want to point out that I did not change any settings in the Sugar Vallet itself when I connected the Atom and Tail485. So I didn’t change any settings in the service menu (like node address in connection, or master/slave settings). Maybe I need to change something in there?
I used benzino77/tasmocompiler which gets the sourcecode itself.
And compiles this in tasmota32.bin with my custom settings.
Did some extra testing with @fdebrus like compiling with Modbus Bridge on or with MODBUS_ADDRESS 1 in the override settings.
Nothing has helped solving this issue.
I connected the display to the other 3 ports (Display, WIFI and EXTERN) and the display works correct when connected to the other ports.
I also disconnected the display and connected the Atom Lite to the Wifi port to see if this would work (maybe one device at a time is able to connect)?
Wiring is correct and changed the first set of wires with new ones, just to be sure.
But connection is established with the Atom Lite when connected, so it gets the 12v current.
Really at loss here with why this is not working.
Seems to be something in the way I compile, flash or in the Tasmota settings I use (module, GPIO, etc.)
Help would be really appreciated
If your Atom is new and never had Tasmota flashed in it, you should compile and flash the tasmota32.factory.bin not tasmota32.bin. I’ve had the same problem as you have and at @alexdelprete’s suggestion I did this and worked.
Don’t touch anything related, the defaults are fine. Modbus address 1 is ok. It has to work, if it doesn’t reflash the firmware. Are you using the factory bin?
Nope, at the end of the compilation you can download several images, among which is the factory bin. You didn’t download it probably. First time you flash, always use factory.
Don’t start changing everything, otherwise you’ll never solve the issue. You need to do one step at a time properly, I have 3 people/friends with the Tail485 working, Cosmin included. You can connect to Wifi or Ext port, it doesn’t matter, I tried on both and it works fine.
If needed I can send you my factory bin file. But I think I preconfigured my wifi settings and mqtt setting, so you’ll need to change those after you flash.
BTW: how are you flashing the device? which sw are you using?
Good advice. 
I tried flashing the tasmota32.factory.bin but my flash tool rejected it.
I am using ESP-Flasher-macOS, one of the flash tools with a gui that works on Macbook.
Edit; am trying with esphome.io at this moment, who knows if the factory.bin will stick now. Let you know in a minute.
Man this is getting frustrating
Flashing the tasmota32.factory.bin with esphome.io was succesful.
After flashing I connected the Atom to the Tail485 which is connected to the Sugar Valley.
Via the webui I changed the module to ESP32-dev (0), after saving and the restart I changed the GPIO 26 and 32 to the correct settings.
I was really hopeful that after the restart the data would become visable.
But unfortunately still no succes.
Did I do it correctly? Or do I need to do something else after flashing the factory.bin?
In Tasmocompiler, choose M5Stack Core2, since you use the Atom. Even though it should work with Generic too, I used both successfully.
I highly recommend the official espressif flash tool: GitHub - espressif/esptool: Espressif SoC serial bootloader utility
The Atom supports 1.5Mb/s on serial, so you can flash faster, here’s my cmdline (on win11) to flash:
esptool.exe -b 1500000 write_flash 0x0 tasmota32-core2.factory.bin
If it still doesn’t work, check cabling…maybe tx/rx are not correctly connected. It has to work immediately.
Also, try this Template config:
{"NAME":"NeoPool Atom Lite + Tail485","GPIO":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,6976,0,0,0,0,0,7008,0,0,0,0,0,0,0],"FLAG":0,"BASE":1}
Then in module, choose that one:
In the end, in Template you should have this:
Will try all suggestions, keep you posted.
Thanks a lot for all your help so far!
