Hello!
Great work what you did there! The integration is going perfectly.
Is there a way that the temperature and redox values only change when the pump is in operation? Outside the filter runtime, the values are not correct.
Thanks!
Daniel
HA NeoPool MQTT: integration of Tasmota NeoPool (for Sugar Valley, Hayward/Aquarite, Bayrol devices)
No, and that has nothing to do with the Sugar Valley, NeoPool or this intergration.
This is normal and is the case with every system. In idle state, the probes are not flushed, so where should the current measured values come from? The water around the temperature sensor slowly takes on the ambient temperature and the redox value usually drops, as the water around the probe is no longer refreshed from the pool.
1 Like
So the values are not correct on the system display either, right? You wanto to tell Sugar Valley to fix the firmware or rethink a little bit more about the question? 
Jokes apart, the provided values come from the system, we’re not manipulating anything. Water flow is essential for the sensors to provide realistic values.
2.57V is not a correct value, you should have 12V on pin1 of Sugar Valley connector.
Check here for details.
Reading it a second time, I realized that you may only want to disable data collection outside the filtration times.
This can be done with the help of Tasmota Rules, but only for the entire system data, not for individual selected data like temp and redox only.
Whoah! What a find, this thread!
Will this work with a HF2211 also?
FYI: I followed this thread, but want to exclude the Da-gen (or Vistapool) app totally.
I don’t yet know exactly how this interface should be integrated into the overall solution.
For this solution you need Tasmota + NeoPool connected to a Sugar Valley System RS485, which makes the system data then available via MQTT. The solution from Alessandro here then integrates this into HA.
An RS485 interface alone is not enough.
It might work if you manage to connect the Atom Lite to the HF2211 appropriately, but I don’t think you can do it. The NeoPool driver runs on Tasmota, it expects the A/B rs485 connections on the Tasmota device pins (bridged to TTL). But the beauty of this solution is that the Atom Lite + Tail485 or the Atom Lite + Atomic RS485 base, which I’m currently using. It costs much less than the HF2211.
With this solution, everything is read LOCALLY. In the thread you mentioned the solution is based on a script that scrapes data from the cloud. I don’t use the cloud for almost anything related to my home automations. When I buy something, I first make sure I can control it locally.
I use the HF2211 to read the Oxilife through modbus. So no cloud involved either.
That’s why I was thinking about using it.
But I ordered the Atom + tail earlier today. Nice to play around with and I’ll be able the cut the cloud by not needing to use the apps again for pump speeds etc.
Very eager to give this a go!
Hello!
Yes, exactly. I created a rule in openHAB where the redox and temperature values only change when the pump is in operation. Is this option also available in Home Assistant? I don’t want to do this via Tasmota because I also have a room temperature sensor connected.
Yes, but the idea here is to leverage NeoPool driver to get MQTT data into HA. And NeoPool is a Tasmota driver, so it requires tasmota on the device that interfaces your Oxilife.
You’ll have lots of fun with the Atom+Tail. I recently switched to the RS485 Atomic base because it’s more compact, but less flexible if you neex extra pins.
Enjoy the project. 
1 Like
I think I have everything up & running, very nice!
I do have 1 question however: when you select “Auto” mode, in the Da-gen (or Vistapool) app, you can specify some start/end times. Can we replicate that through HA as well?
EDIT
Hang on, after I changed some settings in the GPIO’s, I have everything back:
Remarks below aren’t applicable anymore:
However, some things aren’t clear…
The switch to turn on the filtration doesn’t have any effect?
I also don’t see the values anymore on top of my Tasmota webpage?
I may have entered some commands too much in the console?
I see following in the console, when I click that switch:
23:18:10.197 MQT: stat/SmartPool/RESULT = {"NPFiltration":"Error"}
23:18:10.293 MQT: stat/SmartPool/RESULT = {"NPFiltrationmode":"Error"}
23:19:05.982 MQT: stat/SmartPool/RESULT = {"NPFiltration":"Error"}
You can’t break Tasmota using such way, the reason is your RS485 connection
“Error” as a result of a NeoPool Tasmota command means your Tasmota is compiled with NEOPOOL module, GPIOs are assigned but your device does not respond to Modbus commands via RS485. Reason can be wrong or poor wiring, wrong GPIO assignment or not working RS485 interface.
As long as you don’t see any NeoPool data on Tasmota WebUI as described onTasmota NeoPool page, the integration can not work.
This results also in no visible values on main Tasmota WebUI
Indeed, “wrong GPIO assignment” was causing this. All good now!
But I still have that one request: when you select “Auto” mode, in the Da-gen (or Vistapool) app, you can specify some start/end times. Can we replicate that through HA as well?
In HA you can create powerful automations, powerful scheduling, you just need to leverage all the entities that the integration provides. It’s just about being “creative”, you have all the tools you need.
@Everybody: I updated the package and lovelace file:
- Created new Water Flow mqtt binary sensor based on hydrolysis_fl1 binary sensor (inverted state)
- Updated lovelace UI to accomodate Water Flow sensor
Hi,
How does the auxiliary relays work? What kind of physical contactors do you need to control lights, UV and so on?
Normally open or closed, or pulse relays?
This is described in the operating instructions for your device:
Aux1 and Aux2 each have two contacts for (230V) AC devices connected directly with AC Phase and Neutral. Caution: One of the two contacts carries (230V) AC output when Aux is ON.
Aux3 and Aux4 are potential-free NO contacts, the two contacts are connected to each other when Aux is switched on.
It’s different: pH pump is like Aux1 and 2 and supply 230V AC, Filtration and Light are potential-free NO contacts. Again, please refer to your manual.
The most important things to know about Aux (and only Aux!) with this integration:
Aux1-4 only works with this integration when using an ESP32 with installed NeoPool enhancements script.
Thank you very much!
Iv’e understood that the PH pump and aux2 can be connected directly, as long as the power draw is low, but i cant find anywhere in the documentation what you mention for aux 3 and 4. This solves it, thanks!
I was having issues getting this to compile and upload. After running
platformio run -v -e tasmota32 --target upload --upload-port /dev/ttyUSB0
It would error and using the Install Tasmota to retrieve the console logs, it showed it was stuck in a
flash read err, 1000
reboot loop
To resolve this, I had to edit the platform_override.ini file and do the following
-
- Comment out tasmota and uncomment tasmona32 from the default_envs section
-
- Uncomment the upload_speed setting, set tio 115200, in the env:tasmota32_base section
Note that I’m not sure which of these solved my problem, I just know I did both