HA NeoPool MQTT: integration of Tasmota NeoPool (for Sugar Valley, Hayward/Aquarite, Bayrol devices)

Share your Projects!
,
445

Hi,
Thanks @curzon01 , but there is no change removing errors, this AL4 don’t know what does it mean in manual doesn’t appears, and looking for internet nothing. With the tootchpad works with AL3 but not with AL4, The problem is that it doesn’t let me start to chlrorine.
Very strange.

446

I think I remember that AL4 means cell worn out, too little salt in the water, but I’m not sure, it’s not documented anywhere in the register descriptions. However, AL4 is probably an error associated with hydrolysis, as it is assigned to this group in the online portal.

The error is probably confirmed by resetting, but it reappears immediately because the cause still exists (unlike AL3, which indicates that the pH has been dosed for too long, which the system can only detect after a while).

Try the following: Go to the Electrolysis/Hydrolysis menu and let the system measure your salt content. If it already malfunctions or displays an error, you have found the cause (cell defective, too little salt in the water).

447

AL4 is an alarm relating to the cell (mentioned in various Hayward brochures: AL3 for pH measurement injection, AL4 for the cell).

Try testing it with the internal salt measurement.
Either the cell is defective, there is not enough salt in the water, or the cable to the cell has a loose connection.

448

Hi,
I did a config reset and finally now it looks that it doesn’t show AL4, I hope I’ll fix it.
Thanks

450

If the manual NPRead/Write worked (which they did for Aux1-3), then the Tasmota cmnd NPAux1, NPAux2, and NPAux3 (example NPAux1 ON) should now work on the console (provided you have installed the Berry extension neopoolcmd.be).
If it does, then you should also be able to switch Aux1-3 with this HA integration.

If Tasmota cmnds NPAux1, NPAux2, and NPAux3 are not doing what they should, it is because the reason we cannot get Aux4 to work is also the reason why the Tasmota cmnd NPAux1-3 is not working.

I would really like to see that you can switch Aux4 using NPWrite first:

Please try the following steps

  • Manually switch Aux4 on at the system; NPRead 0x49D should now return a 3 as data.

  • Manually switch Aux4 off at the system; NPRead 0x49D should now return a 4 as data.

Then try switching Aux4 again via Tasmota.

  • Enter NPWrite 0x49D,3 and then NPExec as separate cmnds. a following NPRead 0x49D should now return a 3 and Aux4 should be active.

  • If the step before doesn’t work, try a NPWrite 0x49D,3 followed by a NPSave. Subsequently a following NPRead 0x49D should now return a 3 and Aux4 should be active.

451

Hi, Excuse me I’ve been out of my home, coming back to work I did these steps with bad results as you can see:

Manually switch Aux4 on at the system

image
image227×200 39.8 KB

11:02:31.731 CMD: NPRead 0x49D
11:02:31.755 MQT: stat/SmartPool/RESULT = {“NPRead”:{“Address”:“0x049D”,“Data”:“0x0000”}}

Manually switch Aux4 off at the system

image
image228×204 39.8 KB

11:05:59.401 MQT: stat/SmartPool/RESULT = {“NPRead”:{“Address”:“0x049D”,“Data”:“0x0000”}}

Then try switching Aux4 again via Tasmota.

11:07:06.007 CMD: NPWrite 0x49D,3
11:07:06.049 MQT: stat/SmartPool/RESULT = {“NPWrite”:{“Address”:“0x049D”,“Data”:“0x0003”}}
11:07:37.381 CMD: NPExec
11:07:37.407 MQT: stat/SmartPool/RESULT = {“NPExec”:“Done”}
image

11:09:15.553 CMD: NPWrite 0x49D,3
11:09:15.595 MQT: stat/SmartPool/RESULT = {“NPWrite”:{“Address”:“0x049D”,“Data”:“0x0003”}}
11:09:21.858 CMD: NPSave
11:09:22.025 MQT: stat/SmartPool/RESULT = {“NPSave”:“Done”}

image

452

Thx, I’m sorry, my mistake — because unlike the other AUX the addresses for AUX4 are almost identical, invites to swap them and INT1 is also behind INT2 in terms of address.

MBF_PAR_TIMER_BLOCK_AUX4_INT1 = 0x4D9
MBF_PAR_TIMER_BLOCK_AUX4_INT2 = 0x49D

We need to read and write AUX4 INT1 (not INT2), which has the address 0x4D9 (not 0x49D).

Pls can you try again with the correct addr 0x4D9

  • Manually switch Aux4 on at the system; NPRead 0x4D9 should now return a 3 as data.
  • Manually switch Aux4 off at the system; NPRead 0x4D9 should now return a 4 as data.

Switch Aux4 via Tasmota:

  • Enter NPWrite 0x4D9,3 and then NPExec as separate cmnds. a following NPRead 0x4D9 should now return a 3 and Aux4 should be active.

  • Only if the step before doesn’t work (pls skip this step, if the previous works):
    Try a NPWrite 0x4D9,3 followed by a NPSave. Subsequently a following NPRead 0x4D9 should now return a 3 and Aux4 should be active.

  • If you can switch Aux4 using the first step (NPWrite followed NPExec), try switching Aux4 using a Backlog combination: Backlog NPWrite 0x4D9,3;NPExec
    If the Backlog combination doesn’t work, add some delay (start with 2 sec.) between the commands: Backlog NPWrite 0x4D9,3;Delay 20;NPExec

453

Hi @curzon01 ,
Now, it is working fine.

  • Manually switch Aux4 on at the system; NPRead 0x4D9 should now return a 3 as data= OK
  • Manually switch Aux4 off at the system; NPRead 0x4D9 should now return a 4 as data= OK

Switch Aux4 via Tasmota:

  • Enter NPWrite 0x4D9,3 and then NPExec as separate cmnds. a following NPRead 0x4D9 should now return a 3 and Aux4 should be active = OK
  • If you can switch Aux4 using the first step (NPWrite followed NPExec), try switching Aux4 using a Backlog combination: `Backlog NPWrite 0x4D9,3;NPExec = OK

Just a question: I realize that when I switch on/off any aux, the Generic hydrolysis change to 0 and resume to the normal value, I think it is happening with any other command, that’s means that any modbus command we want to change it switches off-on the electrolyser? Could it be dangerous?

Thanks,

454

So, Tasmota command NPAux4 ON / NPAux4 OFF works as well?

If so, you can control Aux via the HA inetgration?

Every time NPExec or NPSave is executed, hydrolysis is briefly interrupted. This is normal behavior for a Sugar Valley. Of course, this also happens when you do this (e.g. switching Aux) directly on the system via the display (which also uses NPExec/NPSave for various functions).
However, this does not cause any harm as long as it does not occur at one-minute intervals (which could affect the cell’s service life).

455

So, right now:

NPAux3 and NPAux4 ON/OFF works well in tasmota console and also in HA.

but I tried with NPAux1 and NPAux2 and it doesn’t work in tasmota console neither in HA.

So close :slight_smile:

456

ok - but wondering what caused your origin issue :thinking: :man_shrugging:

457

My Wi-Fi router for the garden occasionally restarts. However, after restarting, Tasmota does not connect to Wi-Fi. Manually restarting Tasmota helps. Is it possible to set the module to restart if it cannot connect to Wi-Fi for a longer period of time?

458

Yes, but I don’t think it’s necessary. What’s your Tasmota setting for

? (use Tasmota WebUI → Tools → Console to enter the commands)

If you have only one SSID WifiConfig should be 5 and SO56 and SO57 should be 1 - then your Tasmota auto reconnects latest after 1 minute.

459

My config:

{"WifiConfig":{"4":"Retry"}}
{"SetOption56":"OFF"}
{"SetOption57":"ON"}
460

So change it as suggested