support ChemSync (pH/ORP) device type + disambiguate multiple ChlorSync units

[ottoloco-tech]

Environment

• Integration version: 1.0.4
• Home Assistant: 2026.7.2 (Home Assistant OS 18.1, aarch64)
• PoolSync controller: firmware 860, hardware 3.0
• Equipment attached: 1x ChemSync (pH/ORP), 2x ChlorSync chlorinators — one plumbed to the pool, one to the spa

Summary

After pairing, the integration correctly creates the PoolSync controller device and one chlorinator device — but my system actually has three pieces of equipment attached (visible in the PoolSync app: a Chemistry tile showing pH/ORP, plus two separate Chlorinator tiles, one for the pool and one for the spa). Three issues:

1. ChemSync (pH/ORP) isn't supported at all — no entities are created for deviceType: "chemSync", even though the local API returns full pH/ORP/feed data for it.
2. The second ChlorSync unit is dropped. Both chlorinators report nodeAttr.name: "Chlorinator" (differing only by nodeAddr: 18 vs 19), and only one ends up with entities — I'm guessing they collide because the device/unique_id isn't keyed by node address when the name is identical. Since one unit serves the pool and the other the spa, this isn't a redundant reading — I need both.
3. sensor.chlorinator_water_temperature is mislabeled as °C but the raw value is actually °F. The entity carries unit_of_measurement: "°C" but reports the device's native Fahrenheit reading unconverted (e.g. state 94.96 tagged °C — a scary number for water, and physically impossible for a home pool). Converting that same raw value as Fahrenheit gives ~35°C, which lines up with the ~36°C the PoolSync app shows for that loop.

Issue 1 — ChemSync not created

Raw payload for the Chemistry device (devices.0, deviceType.0 == "chemSync"):

​json { "nodeAttr": { "name": "Chemistry", "pid": 10752, "nodeAddr": 21, "idmpAddr": 0, "online": true, "flags": 0, "bootMode": 2 }, "status": { "flags": 368, "ph": 8.16, "orp": 709, "boostRemaining": 0, "acidConsumed": 1941, "boardTemp": 114.41 }, "system": { "fwVersion": 533, "hwVersion": "F", "modelNum": "ChemSync", "serialNum": "REDACTED" }, "config": { "sysMode": 3, "phEnabled": true, "phSetpoint": 7.2, "phMin": 7.2, "phMax": 7.8, "phOffset": 0.02, "orpEnabled": true, "orpSetpoint": 650, "feedRate": 87662, "feedRateUnits": 0, "feedAmount": 0, "maxDailyFeed": 100, "flowSensorEnable": true, "flowPolarity": 0, "acidTankAlertAmount": 640, "manualMode": true }, "faults": [4] } ​

Would love to see this exposed roughly as:

• sensor — pH, ORP, board temp, acid consumed
• binary_sensor — fault, flow present
• number (optional) — pH setpoint, ORP setpoint, if writable via the same PATCH pattern used for chlorinator output

Issue 2 — second ChlorSync unit collides with the first

Both units, for comparison — note identical nodeAttr.name, distinct nodeAddr:

Chlorinator A (devices.1, nodeAddr 18) — this one gets entities today:
​json { "nodeAttr": { "name": "Chlorinator", "nodeAddr": 18, "idmpAddr": 0, "online": true }, "status": { "waterTemp": 94.96, "boardTemp": 99.95, "fwdCurrent": 890, "revCurrent": 890, "outVoltage": 577, "cellRailVoltage": 4959, "saltPPM": 3716, "boostRemaining": 0 }, "config": { "chlorOutput": 0, "poolCoverCtrl": true, "tempCompEnable": false, "gallons": 60000 }, "system": { "drvModelNum": "PCR0002A", "drvFwVersion": 773, "cellFwVersion": 9, "cellHwVersion": 66 }, "faults": [0] } ​

Chlorinator B (devices.2, nodeAddr 19) — missing from HA entirely:
​json { "nodeAttr": { "name": "Chlorinator", "nodeAddr": 19, "idmpAddr": 0, "online": true }, "status": { "waterTemp": 96.33, "boardTemp": 99.17, "fwdCurrent": 1246, "revCurrent": 1141, "outVoltage": 0, "cellRailVoltage": 4865, "saltPPM": 3877, "boostRemaining": 0 }, "config": { "chlorOutput": 0, "poolCoverCtrl": true, "tempCompEnable": true, "gallons": 60000 }, "system": { "drvModelNum": "", "drvFwVersion": 773, "cellFwVersion": 9, "cellHwVersion": 66 }, "faults": [0] } ​

Suggested fix: key the device/unique_id off nodeAddr (or pid+nodeAddr) rather than the display name, and fall back to a suffix like "Chlorinator 2" for the friendly name when duplicates are detected. Since these are functionally pool vs. spa units, it'd also be great if the integration (or a config option) let us label each by nodeAddr, e.g. "Chlorinator — Pool" / "Chlorinator — Spa".

Issue 3 — water temperature reported in °F but labeled °C

sensor.chlorinator_water_temperature currently returns:

​ state: 94.96 unit_of_measurement: "°C" device_class: "temperature" ​

waterTemp in the raw API payload is in Fahrenheit — 94.96°F converts to 34.98°C, consistent with a heated pool/spa in the Bahamas in July and with the ~36°C shown in the PoolSync app. Right now Home Assistant shows the raw Fahrenheit number under a Celsius label, which reads as an alarming/impossible water temperature until you realize the unit tag is wrong.

As a stop-gap on my end I added a template sensor that converts the raw value:
​jinja {{ (((states('sensor.chlorinator_water_temperature') | float(0)) - 32) * 5 / 9) | round(1) }} ​
but obviously this should be fixed at the source so °C and °F installs both display correctly without a workaround.

Confirming evidence from a second, simpler system

I have a second PoolSync controller ("Beach Spa") with just one ChemSync and one ChlorSync cell. Pairing that one was clean — because I'd already given the chlorinator a unique name on the device itself ("Chlor Cell Beach Spa" instead of the generic default "Chlorinator"), it didn't hit the name-collision problem from Issue 2, which supports that diagnosis.

However, the same two other bugs reproduce exactly:

• The ChemSync on this system also reports live pH/ORP (ph: 7.4, orp: 705) but gets no entities — Issue 1 again.
• sensor.chlor_cell_beach_spa_water_temperature shows 91.65 tagged °C — same unit bug as Issue 3 (91.65°F ≈ 33.1°C, which matches this spa's actual temperature).

So this isn't specific to one controller/firmware — happy to provide diagnostics from either system.

Happy to help test

I have two PoolSync controllers (1x ChemSync + 2x ChlorSync on one, 1x ChemSync + 1x ChlorSync on the other) running and can pull more diagnostics, test builds, or before/after payloads on request.

[ccpk1]

This is a really good level of detail, thank you. I can build a lot of the required fixes from this, but the most helpful thing you could do is provide me a diagnostic download from the integration. Considering I only have a single heat pump, one of the biggest challenges is getting example data I can use to get all of the other devices and data file mapped in correctly.

Thanks!

[ottoloco-tech]

Thanks so much for the quick reply, and honestly for building this whole thing in the first place. Going from zero official support to a working integration with top noch quality architecture that talks to the device locally is no small effort, especially while juggling it solo. Really appreciate you taking the time to look at this. Attached are two diagnostics downloads that should cover both gaps. poolsync_diagnostics_main.json is my main system: 1x ChemSync plus 2x ChlorSync (pool and spa chlorinators) poolsync_diagnostics_beach_spa.json is a second, simpler controller: 1x ChemSync plus 1x single ChlorSync cell Between the two you've got a clean single chlorinator example alongside the duplicate name collision case, plus two independent ChemSync payloads to build the pH/ORP entities against. Happy to test any branch or build against either system, or grab more data if something's still missing once you start mapping it. Thanks again for keeping this going! Otmar On Jul 15, 2026, at 5:23 PM, ccpk1 ***@***.***> wrote: ccpk1 left a comment (ccpk1/AP_PoolSync#6) The most helpful thing you could do is provide me a diagnostic download from the integration. Considering I only have a single heat pump, one of the biggest challenges is getting example data I can use to get all of the other devices and data file mapped in correctly. Thanks! — Reply to this email directly, view it on GitHub , or unsubscribe . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android . Download it today! You are receiving this because you authored the thread. Message ID: ***@***.***>

[ccpk1]

@ottoloco-tech - It looks like you tried to attach the diagnostic files to an email where I think they get stripped. The only way to post them here is to do it manually via the GitHub web interface.

I'm actually about 90% complete with the architecture changes I think are required to support your situation based on what I could glean from your overview data, but the diagnostic download would help me ensure I have it right.

Couple of other things:

• Do not use beta 2 I published last night, that is where I found some bigger architectural changes I needed to make around naming and such to support multiple devices of the same type. That said, beta 3 will have the first pass support for all this.
• If you want to provide a couple of screenshots from the app of your chlorsync and chemsync device screens it might help give me some context of how it is displayed. I made some guesses that are probably close, but best when I can emulate and understand what the vendor was trying to do.
• At this point I'm only going to be able to show you the data in sensors as read only for these other devices like chemsync. I'll need you to do some packet captures from the app in order to figure out what the underlying api calls need to be to make changes on the controller. (This is already mapped out for the heat pumps which is what allows us to make mode and temperature changes, but for anything else you change in the app we have to do a little reverse engineering)

[ccpk1]

I'm still hoping to get your diagnostic downloads, but went ahead and released this anyway.

---

1.0.5-beta.4 is ready for testing — Release notes here

This release adds a lot of new functionality, but I need your help validating it on real hardware.

What changed

I spent a significant amount of time reverse-engineering the PoolSync Android app (decompiling the APK, disassembling Hermes bytecode, and live-probing the local API) to figure out the write payload formats for things like ChemSync pH/ORP setpoints, pump RPM control, group toggles, and action buttons. All of the new write features are built on those findings, but if this doesn't work then the next step will need to be packet captures from your devices.

The catch: I don't have the equipment to test any of these writes on actual hardware, and I had to make many assumptions since I can see the actual data packets from your system.. The HTTP layer works (the ESP32 accepts the payloads and returns 200), but I can't confirm the pool controller actually acts on them. That's where you come in.

How to help

The best way to test is to:

1. Install the beta.4 update
2. Go to Settings → Devices & Services → PoolSync Custom and look at every device that was created
3. Click through each device and entity and compare what you see against the official PoolSync app
4. For the write features (buttons, numbers, switches, selects) — try making a change and see if the device responds. Is the pH setpoint actually changing? Does the prime pump button kick the pump on? Do the group switches turn groups on and off?
5. Report everything — what works, what doesn't, and any errors you see in the Home Assistant logs

One thing to note: after making a change, there's a delay until the controller refreshes (depends on your polling interval setting). You can use the "Refresh data" button on the PoolSync controller device to pull fresh data immediately instead of waiting.

Heads up on regressions

I had to do a pretty significant refactor to properly support multiple devices (ChlorSync, ChemSync, heat pumps all needed to coexist). My initial smoke testing on a T75 heat pump looks good, but I honestly won't be surprised if some edge cases pop up — especially around entity IDs, device names, or sensors that may show as unavailable on configurations I don't have access to.

If something looks wrong after updating, the most likely culprits are the entity ID consolidation changes. Double-check that your automations and dashboards still point to the right entities.

Thanks in advance for any testing you can do! Every report helps close the gap between "reverse-engineered guess" and "confirmed working."

[ottoloco-tech]

hi , sorry for this late reply, wasnt at my desk the whole day. here ill paste the diagnosticis files for you. hope it works this way

poolsync_diagnostics_main.json

​json { "config_entry_id": "01KXKGB3NNHA8000VE0NTFDNTY", "data": { "data": { "runtime_data": { "poolSync": { "config": { "name": "PoolSync®" } }, "devices": { "0": { "nodeAttr": { "name": "Chemistry", "pid": 10752, "nodeAddr": 21, "online": true }, "status": { "ph": 8.48, "orp": 723, "boostRemaining": 0, "acidConsumed": 1941, "boardTemp": 109.52 }, "system": { "fwVersion": 533, "hwVersion": "F", "modelNum": "ChemSync" }, "config": { "phEnabled": true, "phSetpoint": 7.2, "phMin": 7.2, "phMax": 7.8, "orpEnabled": true, "orpSetpoint": 650, "flowSensorEnable": true }, "faults": [4] }, "1": { "nodeAttr": { "name": "Chlorinator", "pid": 9730, "nodeAddr": 18, "online": true }, "status": { "waterTemp": 93.32, "boardTemp": 95.12, "fwdCurrent": 884, "revCurrent": 884, "outVoltage": 639, "saltPPM": 3686 }, "config": { "chlorOutput": 0, "poolCoverCtrl": true, "tempCompEnable": false, "gallons": 60000 }, "system": { "drvModelNum": "PCR0002A", "drvFwVersion": 773, "cellFwVersion": 9, "cellHwVersion": 66 }, "faults": [0] }, "2": { "nodeAttr": { "name": "Chlorinator", "pid": 9730, "nodeAddr": 19, "online": true }, "status": { "waterTemp": 94.69, "boardTemp": 94.63, "fwdCurrent": 1240, "revCurrent": 1135, "outVoltage": 546, "saltPPM": 3853 }, "config": { "chlorOutput": 0, "poolCoverCtrl": true, "tempCompEnable": true, "gallons": 60000 }, "system": { "drvFwVersion": 773, "cellFwVersion": 9, "cellHwVersion": 66 }, "faults": [0] } }, "deviceType": { "0": "chemSync", "1": "chlorSync", "2": "chlorSync" } } } } } ​

poolsync_diagnostics_beach_spa.json

​```json
{
"config_entry_id": "01KXKJ780WVCTV0YT7AX78B2MW",
"data": {
"data": {
"runtime_data": {
"poolSync": {
"config": { "name": "BEACH SPA" }
},
"devices": {
"0": {
"nodeAttr": { "name": "Chemistry", "pid": 10752, "nodeAddr": 27, "online": true },
"status": { "ph": 7.46, "orp": 704, "boostRemaining": 0, "acidConsumed": 4041, "boardTemp": 120.94 },
"system": { "fwVersion": 533, "hwVersion": "F", "modelNum": "ECA0486" },
"config": { "phEnabled": true, "phSetpoint": 7.4, "phMin": 7, "phMax": 8, "orpEnabled": true, "orpSetpoint": 650, "flowSensorEnable": false },
"faults": [0]
},
"1": {
"nodeAttr": { "name": "Chlor Cell Beach spa", "pid": 9730, "nodeAddr": 22, "online": true },
"status": { "waterTem

poolsync_diagnostics_beach_spa.json
poolsync_diagnostics_main.json

[ottoloco-tech]

Here the screenshots on the app:

[ccpk1]

Thanks for the feedback and diagnostics, that helped me clean up and improve a few other things. 1.0.5-beta.5 is now available in HACS for you to download, restart home assistant, then test out.

Thanks!

[ccpk1]

Just checking in. Let me know when you get some time to focus on this. Thanks