MQTT light commands stopped working?

[johnny2678]

Not sure if something changed with 7.7 - used to be I could send the payload {"id":2,"isOn":"on"} to pool/easytouch2-4/state/circuit/setState and the pool lights would turn on. Confirmed that the topic is updated in MQTT explorer when the payload is sent, but no lights.

I'd attach a replay but nothing is showing up when I push the payload.

No errors in the logs that I can see, and MQTT is getting updates from njspc like always. I pushed the lights on payload right after the info line below:

1|poolController  | [6/9/2022, 10:32:50 AM] info: [10:32:50 AM] 192.168.5.140 GET /state/all/ {}
1|poolController  | [6/9/2022, 10:32:54 AM] silly: Batching influx chemController data point chemControllersPh,chemistry=auto,dosing\ method\ desc=null,dosing\ status\ desc=Monitoring,id=50,mode=pool,name=REM\ ChemControl acid\ demand=0i,daily\ volume\ dosed=4i,delay\ time\ remaining=0,dose\ priority\ int=1i,dose\ time\ remaining=0,dose\ volume=5i,dose\ volume\ remaining=0i,dosing\ status=2i,dosing\ time=0,flow\ only\ mixing\ int=1i,flow\ readings\ only\ int=0i,high\ tolerance=7i,level=7.823,lockout=F,low\ tolerance=7i,max\ daily\ volume=1400i,mix\ time\ remaining=0,pump\ is\ dosing=0i,setpoint=7.85,start\ delay=5i,tank\ capacity=3.5,tank\ level=2.389720307901961,temperature=29,tolerance\ enabled\ int=1i,volume\ dosed=0i 1654785174766000000
1|poolController  | [6/9/2022, 10:32:54 AM] silly: Batching influx chemController data point chemControllersOrp,chemistry=auto,dosing\ method\ desc=null,dosing\ status\ desc=Monitoring,id=50,mode=pool,name=REM\ ChemControl daily\ volume\ dosed2=0,delay\ time\ remaining=0,dose\ priority\ int=0i,dose\ volume\ remaining2=0,dose\ volume2=0.014583333333333334,dosing\ status=2i,dosing\ time=1,flow\ only\ mixing\ int=0i,flow\ readings\ only\ int=0i,high\ tolerance=850i,level=688,lockout=F,low\ tolerance=550i,max\ daily\ volume2=0,max\ dosing\ time=20i,mix\ time\ remaining=0,mixing\ time=1200i,orp\ demand=-38i,pump\ dose\ time\ remaining=0,pump\ is\ dosing=0i,setpoint=650,start\ delay=5i,tank\ capacity=0,tank\ level=0,tolerance\ enabled\ int=1i,volume\ dosed2=0 1654785174797000000
1|poolController  | [6/9/2022, 10:32:54 AM] silly: Batching influx chemController inverse data point invalid point: {"tags":{"name":"REM ChemControl","id":"50","type":"REM Chem","status":"Ok","alarm: comms desc":"Ok","alarm: flow desc":"Ok - No alarm","alarm: body fault desc":"Ok - No Faults","alarm: flow sensor fault desc":"Ok - No Faults","warning: orp daily limit reached desc":"orp Daily Limit Reached","warning: water chemistry desc":"Ok - No Warning"},"fields":{},"name":"chemControllersGen","time":"2022-06-09T14:32:53.825Z"})
1|poolController  | [6/9/2022, 10:32:54 AM] silly: Batching influx chemController data point chemControllersGen,alarm:\ body\ fault\ desc=Ok\ -\ No\ Faults,alarm:\ comms\ desc=Ok,alarm:\ flow\ desc=Ok\ -\ No\ alarm,alarm:\ flow\ sensor\ fault\ desc=Ok\ -\ No\ Faults,id=50,name=REM\ ChemControl,status=Ok,type=REM\ Chem,warning:\ orp\ daily\ limit\ reached\ desc=orp\ Daily\ Limit\ Reached,warning:\ water\ chemistry\ desc=Ok\ -\ No\ Warning alarm:\ body\ fault=0i,alarm:\ comms=0i,alarm:\ flow=0i,alarm:\ flow\ sensor\ fault=0i,alkalinity=30i,borates=0i,calcium\ hardness=325i,cyanuric\ acid=30i,flow\ sensor\ state=19.45,lsi\ range\ enabled=1i,saturation\ index=-0.503,warning:\ orp\ daily\ limit\ reached=4i,warning:\ water\ chemistry=0i 1654785174825000000
1|poolController  | [6/9/2022, 10:32:54 AM] silly: MQTT send:
1|poolController  | topic: pool/easytouch2-4/state/chemControllers/50/remchemcontrol/ph/level
1|poolController  | message: 7.823
1|poolController  | opts:{"retain":true,"qos":0}
1|poolController  | [6/9/2022, 10:32:54 AM] silly: MQTT send:
1|poolController  | topic: pool/easytouch2-4/state/chemControllers/50/remchemcontrol/pHLevel
1|poolController  | message: {"pHLevel":7.823}
1|poolController  | opts:{"retain":true,"qos":0}
1|poolController  | [6/9/2022, 10:32:54 AM] silly: InfluxDB successfully wrote 7 lines.
1|poolController  | [6/9/2022, 10:32:55 AM] silly: Batching influx filter data point filter,body=Pool/Spa,filterType=Cartridge,name=Filter,units=Pounds\ per\ Sqare\ Inch cleanPercentage=61.75,isOn=T,isOnVal=1i,pressure=19.53,referencePressure=19.53 1654785175260000000
1|poolController  | [6/9/2022, 10:32:55 AM] silly: MQTT send:
1|poolController  | topic: pool/easytouch2-4/state/filters/1/filter/pressure
1|poolController  | message: {"pressure":19.53}
1|poolController  | opts:{"retain":true,"qos":0}

any ideas?

[Crewski]

Maybe try with either "isOn": true or "isOn: 1 instead of the string on/off. Here is what I use that works:

      state_topic: "pool/state/circuits/2/poollight"
      value_template: "{{ value_json.isOn }}"
      command_topic: "pool/state/circuit/setState"
      payload_on: '{"id": 2, "isOn": 1}'
      payload_off: '{"id": 2, "isOn": 0}'
      state_on: "on"
      state_off: "off"

[johnny2678]

Interesting, "on" always worked in the past

tried "isOn" = true, 1, and "on" - all get passed to MQTT but the circuit doesn't change

[rstrouse]

Pull njsPC and dashPanel. I tried your scenario and it worked fine. I did some code cleanup on that processor a few days ago that may have fixed some weirdness with the wildcard topics,

"on", "y", "yes", 1, and true are all valid values for truthy isOn and "off", "n", "no", 0, and false are all valid values for falsey isOn. You can also use the element state.

[johnny2678]

Not sure what kind of funky state my njspc was in, but a restart fixed it and now it responds to my original "on" cmd. thx!

Will still pull the latest after a decipher your last comment on my MQTT pull request ;) Will respond there.