Open lodged78 opened 1 week ago
Thanks for all the information as you saw/noted your configuration was incorrect extended_device_id
MUST be set for VSP to work correctly, without that you are only getting 1/2 the information that’s taken from the pump directly.
One thing to note for VSP Pumps is you need to take the MQTT on/off state over everything else / it’s the priority. Ie if the pump is off, ignore all RPM/GPM values. SWG is its own device and that’s why it works slightly differently. Pump RPM/GPM reporting will depend a lot on how things are configured & protocols used. But if you take the ON/OFF value and/or Pump/Status over everything else, you will be fine.
But what’s interesting (maybe a bug) is that during priming, as you noted, the control panel does not report RPM/GPM but the pump “usually” does, and since you have button_01_pumpID=0x78
in your config, AqualinkD should be reporting that RPM/GPM taken directly from the pump.
EDIT 2: Using the Aqualink Touch protocol
extended_device_id=0x31
works better - power / rpm goes to zero when the pump is turned off, shows higher power when priming, then the correct power / rpm at steady state. The rpm value is not shown during priming, but I don't believe rpm is reported by the controller during priming. Power during priming fluctuates between zero, the last power reported, and the higher priming power - but this is very minor.aqualinkd.log
EDIT: I edited my config file and added the line
extended_device_id=0x41
- power / rpm values are now published to MQTT when the pump is running in steady state.When the pump is turned off, power / rpm values of zero are not published to MQTT as expected.
Turning the pump on publishes MQTT zeros for power / rpm
But actual power / rpm values aren't updated during priming - power / rpm remains at zero. Info: One Touch: Menu Line 2 = JANDY ePUMP 1 Info: One Touch: Menu Line 3 = PRIMING Info: One Touch: Menu Line 4 = WATTS: 578
When priming is complete, the correct power / rpm values are published to MQTT.
My system was running fine with 2.3.6, including reporting VSP rpm / power to MQTT. I noticed when the filter pump was off, AqualinkD continued publishing the last known power / rpm to MQTT instead of zero.
I upgraded to 2.4.0 to see if it fixed the issue, but actually made things worse.
Turning the pump off causes the SWG to publish MQTT that the SWG is off; I would expect the same sort of logic for power / rpm when the pump is off.
My /etc/aqualink.conf was not overwritten by the upgrade, and I made no change to the config file after upgrading.
I found AqualinkD 2.4.0 is no longer publishing power / rpm to MQTT at all, or displaying power / rpm in the log.
The log previously showed power / rpm messages
After upgrading to 2.4.0, the log no longer shows and power / rpm messages from the controller, but I can see the current power / rpm on my One Touch panel.
Long clicking on the filter pump in the web interface correctly shows the current RPM (but no power) - the rpm is clearly being received from the controller, put isn't being published in the log or to MQTT.
Serial Logger
Config file