Tried it all (except for flashing with the official flash tool), used the factory.bin and used your suggested template.
Still nothing.
If you wouldn’t mind sending me your bin-file, I can at least try that.
And for using the official flash tool; I don’t have any Windows machine available, so am kind of stuck with Apple on this. Any suggestions on that?
This is the bin file I sent Cosmin (on discord):
https://cdn.discordapp.com/attachments/1152368143751205016/1152697761049890986/tasmota32-core2.factory.bin?ex=65342ff2&is=6521baf2&hm=9fa22f146ea078e45659a3c19f75757daeba6f5dec1f22e981c6069a9f25d1d7&
did you check the release page of the GH repo? There’s a mac version:
https://github.com/espressif/esptool/releases/download/v4.6.2/esptool-v4.6.2-macos.zip
Nice, missed that.
I installed ESPTool on my Macbook, and downloaded the bin-file.
With ESPTool (I think) I flashed the downloaded factory.bin.
The command I used:
esptool.py -b 1500000 write_flash 0x0 tasmota32-core2.factory.bin
This is the result:
Is this a succesful flash?
Of course the device doesn’t connect to my Wifi because the credentials where not fashed on there.
But to be sure I do not break anything; how do I change/reset the wifi without messing up the firmware?
There is no tasmota_xxxxxxx SSID, I have checked that. And I read something about pushing the button for 40 seconds, but that resets the complete device.
It seems like my old wifi-settings are not erased, because the device is still connecting to my home wifi.
Unfortunately there is still no data visible in the webui (or anywhere else).
So the flashing went wrong, or the bin you gave me doesn’t solve my problem.
That bin was flashed by @Cosmin.FRC and it worked fine.
So you have a different issue, recheck cables etc.
Don’t know what else to tell you, sorry. It should work immediately if the cables are ok and you flash correct fw and configure it properly.
Thanks again for all your effort and help, really appreciate it.
I tried flashing again, this time with the online tool (web.esphome.io).
This did succeed (at least with erasing the old firmware).
Because after that flash I had to connect to a SSID and go to 192.168.4.1 where I had to give in the Wifi details of my home wifi.
After doing that I filled the template, etc. hoping the data would become visible.
But once again my hope was in vain…
If somebody else has some suggestions, feel free to jump in.
Ok, in order to debug the modbus communication and errors, you need this in the custom firmware:
#define DEBUG_TASMOTA_SENSOR
and then in console you use this command:
Weblog 4
I compiled it for you. There’s no wifi predefined. And btw, you can change wifi config using esp web flash tools, there’s a “change wifi” option once you connect through usb.
Here’s the two bins, factory and the standard one: https://file.io/0PdRD2qND8Qr
Once you flash it, go to console, do weblog 4 and then watch the console output for modbus logs, report them back here. It’s something like this:
Flashed the factory.bin file you send me.
Changed the wifi with the web.esphome.io flash tool.
Copied and activated the template you gave me:
{“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}
After restart went to Console, put in Weblog 4 and hit enter.
Extra info, I have installed the following modules and relays on my Sugar Valley:
so it seems there’s no error, right? did you check the TX/RX gpio pins config?
Try issuing this command, and post the result here: NPFiltration.
Check this discussion too, curzon01 is the main dev of the NeoPool tasmota driver: NeoPool commands results error · arendst/Tasmota · Discussion #18991 · GitHub
This is the result (an error).
Same error when I issue NPpH (I tried that before because there is a pH-sensor connected to the Sugar Valley).
I will look into that discussion.
But also already ordered a new Atom and Tail, just to rule out that the ones I have are faulty/broken.
good idea ordering a new atom/tail, just to double check things. but I doubt it’s the device I used many of them and never found a hw issue. they’re very solid.
you might want to look at that discussion and open a separate one describing everything providing all logs, etc. the developer might help understanding where the problem is.
NPFiltration error is an indication that the NeoPool driver is running (it knows the command) but communication is not working. But I would expect modbus errors in the log with Weblog 4.
If NeoPool driver was not active, you would’ve seen ‘command unknown’.
As far as I can follow this discussion, it relates to the power supplied to the RS485 and ESP (TTL to UART converter).
But the Tail485 and Atom Lite (should) manage this automatically right?
Should I try and use a different connection for power supply to the Tail485? And what are my options within the Oxilife or with and outside adapter?
I didn’t say your problem is power. I chose Atom+Tail485 exactly for the power problem. 
I said follow the discussion to understand how to debug your specific issue. I advice you to open a separate discussion over there, so that the devs can help.
Thanks, will open an thread with the developer.
In it I will put all details we have tried and discovered so far.
Opened a new discussion on GH;
Issue solved; broken Tail485 caused all the stress. New Tail485 and the data was visible immediately.
Thanks to everyone helping (especially @alexdelprete and @Cosmin.FRC for their patience and suggestions)
I completed the full custom integration of NeoPool using only MQTT integration entities.
Created a separate thread here: HA NeoPool MQTT: integration of Tasmota NeoPool (for Sugar Valley, Hayward/Aquarite, Bayrol devices)
I’ll be available over there to discuss/test/improve the integration.
Hi i have also a aquarite did you find the way to add on HA?
Hi did you find a way to communicate with Hayward aquarite to HA ?
In any case there are indications this is solved, so this is being moved to Third Party for future reference.
