Skip to content

fix(pumps): use rpm/watts to determine running state instead of command==10#61

Open
celestinjr wants to merge 1 commit intoCrewski:mainfrom
celestinjr:fix/pump-running-state-regal-modbus
Open

fix(pumps): use rpm/watts to determine running state instead of command==10#61
celestinjr wants to merge 1 commit intoCrewski:mainfrom
celestinjr:fix/pump-running-state-regal-modbus

Conversation

@celestinjr
Copy link
Copy Markdown

@celestinjr celestinjr commented Apr 11, 2026

Problem

PumpOnSensor relied on command == 10 to determine if a pump is running.
This is incorrect for Regal Modbus pumps, which emit command=4 while
actively running (e.g., rpm=3450, watts=1406, command=4), causing the
running state sensor to incorrectly toggle off/on with each state update.

Solution

For non-relay pumps, use rpm > 0 or watts > 0 as the running indicator.
These fields are always present and accurate regardless of pump protocol.
Relay-based pumps retain existing relay > 0 logic.

Testing

…nd==10

PumpOnSensor relied on command==10 to determine if a pump is running.
This is incorrect for Regal Modbus pumps, which emit command=4 while
actively running (e.g. rpm=3450, watts=1406, command=4), causing the
running state sensor to incorrectly toggle off/on with each state update.

Fix: for non-relay pumps, use rpm>0 or watts>0 as the running indicator.
Relay-based pumps retain existing relay>0 logic.

Aligns with the same fix applied in nodejs-poolController-dashPanel.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant