Pool and Spa Chlorination Setpoint error in .26

[mda]

Hi spud

It looks like there is bug in .26 when trying to set the pool or spa chlorination set points from HS3. I have an Autelis running on firmware 1.6.16 on a Jandy iAquaLink system.

Debug shows:


Mar-20 8:42:26 AM AutelisDEBUG 500 Internal Server Error: Expected data not present
Mar-20 8:42:26 AM AutelisERROR WebException: ProtocolError The remote server returned an error: (500) Internal Server Error.
Mar-20 8:42:26 AM AutelisINFO CMD SENT: http://192.168.1.35:80/set.cgi?name=chlrs&value=9
Mar-20 8:42:26 AM Device ControlDevice: Pool Spa Chlorination Setpoint to (value)% (9) by/from: CAPI Control Handler
Mar-20 8:42:03 AM AutelisDEBUG 9 25 54 5 54 0 0 0 0 0 0 0 0 0

Mar-20 8:37:59 AM AutelisDEBUG 500 Internal Server Error: Expected data not present
Mar-20 8:37:59 AM AutelisERROR WebException: ProtocolError The remote server returned an error: (500) Internal Server Error.
Mar-20 8:37:59 AM AutelisINFO CMD SENT: http://192.168.1.35:80/set.cgi?name=chlrp&value=30
Mar-20 8:37:59 AM Device ControlDevice: Pool Pool Chlorination Setpoint to (value)% (30) by/from: CAPI Control Handler


I am not sure if this is just in .26 or has been there for a while since I am just opening my pool back up after a while.

Thanks


——-
EDIT:

same problem with Setting pump speed

Mar-20 8:50:12 AM Autelis DEBUG 500 Internal Server Error: Expected data not present
Mar-20 8:50:12 AM Autelis ERROR WebException: ProtocolError The remote server returned an error: (500) Internal Server Error.
Mar-20 8:50:12 AM Autelis INFO CMD SENT: http://192.168.1.35:80/set.cgi?name=vsp1&value=2
Mar-20 8:50:12 AM Device Control Device: Pool Pump 1 Speed to Pool (2) by/from: CAPI Control Handler


However, turning the spa heat on worked fine:

Mar-20 8:51:25 AM Autelis DEBUG 1
Mar-20 8:51:25 AM Autelis INFO CMD SENT: http://192.168.1.35:80/set.cgi?name=spaht&value=1
Mar-20 8:51:25 AM Device Control Device: Pool Spa Heat to On (1) by/from: CAPI Control Handler

[spud]

I see the problem, and I will fix it asap.
However unless they changed the API, I think those commands have never worked before. Did they work at any point for you before?

[mda]

I see the problem, and I will fix it asap.
However unless they changed the API, I think those commands have never worked before. Did they work at any point for you before?

Thanks! I don’t really know, I don’t remember if I tested them in the past (I have not done a comprehensive test of all the commands).

[spud]

Please test version 3.0.0.27 available in the beta section of the updater.
Thanks!