-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Neopool - NPFiltration incorrect behavior #18871
Comments
Please add the missing Infos asked in the template. |
@fdebrus |
StateText |
I tried to call NPFiltration 0 mutiple times in a row 10:09:53.513 CMD: NPFiltration 0 NPFiltration 1 mutiple times in a row 10:11:11.341 CMD: NPFiltration 1 So the first call to NPFiltration gives a wrong status while nexts are good. |
Looking at the code I don't see any problem with the logic
You can interrogate the device with command
|
Hi @curzon01 I think you were the main contributor on this code |
Here you go 12:03:18.561 CMD: NPFiltration Note: |
So the problem is on the device which do not update it's state quickly Possibilities:
|
It seems @barbudor are right, the Auarite system might be very slow updating their internal register. Pls provide "NPControl" and "Teleperiod" (topic .../SENSOR) result to see the system info and FW version number (pls be patient, I'm busy 'till ne t week) |
14:10:56.256 MQT: stat/SmartPool/NPCONTROL = {"Modules":{"pH":1,"Redox":1,"Hydrolysis":1,"Chlorine":0,"Conductivity":0,"Ionization":0},"Relay":{"Acid":1,"Base":0,"Redox":0,"Chlorine":0,"Conductivity":0,"Heating":7,"UV":0,"Valve":0}} 14:11:21.778 MQT: stat/SmartPool/TELEPERIOD = {"TelePeriod":300} tele/SmartPool/SENSOR = {"Time":"2023-06-14T14:11:22","NeoPool":{"Time":"2023-06-14T15:09:49","Type":"Generic","Modules":{"pH":1,"Redox":1,"Hydrolysis":1,"Chlorine":0,"Conductivity":0,"Ionization":0},"Temperature":30.2,"Power":{"Version":"V3.57","NodeID":"05DE 2D35 3837 574E 4318 0937","5V":5,"12V":14,"24-30V":32,"4-20mA":0.120},"pH":{"Data":7.2,"Min":7.0,"Max":7.4,"State":3,"Pump":2,"FL1":0,"Tank":1},"Redox":{"Data":663,"Setpoint":700},"Hydrolysis":{"Data":15,"Unit":"g/h","Runtime":{"Total":"42T17:52:10","Part":"42T17:52:10","Pol1":"21T03:40:54","Pol2":"21T14:11:16","Changes":492},"State":"Pol1","Cover":0,"Boost":0,"Low":0},"Filtration":{"State":1,"Speed":3,"Mode":0},"Light":0,"Relay":{"State":[0,1,0,0,0,0,0],"Aux":[0,0,0,0],"Acid":0,"Heating ":0}},"TempUnit":"C"} |
may be I can fix it, let me check next week meantime workaround: |
thanks, not sure how to use that workaround from HA but I can code something similar. For the time being this is how I call the command mqtt: then an automation is calling NPFiltration again after 5secs alias: NPFiltration
that works :) |
you're not patient enough :-) |
PROBLEM DESCRIPTION
When using Tasmota with Neopool, the NPFiltration command accept 0 "OFF" 1 "ON" or 2 "Toggle" as values.
The opposite is reported in MQTT stat
Calling NPFiltration with 0 reports the below in MQTT, the Filtration pool controller is OFF
{
"NPFiltration": "ON",
"Speed": "2"
}
Calling NPFiltration with 1 reports the below in MQTT, the Filtration pool controller is ON
{
"NPFiltration": "OFF",
"Speed": "2"
}
So stat/.../NPFilration is incorrectly set when calling NPFiltration with 0 or 1
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
send NPFiltration with 0 or 1 over the MQTT command channel and check stat channel
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: