TSUN Local iconTSUN Local
TWO PLAY2 HARDWARE PATHS OBSERVED · 02B0 + 1097

Sunology PLAY2 in Home Assistant with TSUN Local

Sunology has shipped PLAY2 units with more than one local hardware/protocol path. TSUN Local now recognizes the validated GEN3 Plus / 02B0 variant and the field-tested GEN4 / 1097 variant.

Add TSUN Local to HACS⭐ Star on GitHub

Two PLAY2 generations are now observed

Real-world reports show that Sunology PLAY2 is not a single local protocol variant. Two hardware generations have been observed under the same PLAY2 commercial name. TSUN Local detects the local protocol automatically, so the user does not need to choose a generation or protocol manually.

✅ GEN3 Plus · protocol 02B0Validated on real PLAY2 hardware through the normal Home Assistant integration flow. The tested path uses an LSW5BLE logger and the 02B0 sensor list.
🧪 GEN4 · protocol 1097The GEN4 PLAY2 path is detected with sensor list 4247 (0x1097). Communication and daily-energy stability are currently being field-tested.
✅ Automatic protocol detectionTSUN Local identifies the local protocol at runtime. The same PLAY2 page therefore covers both observed generations.
✅ Local read-only telemetryBoth paths remain read-only and do not require a cloud service or proxy in the Home Assistant data path.
Status: 02B0 is the validated PLAY2 path. GEN4 / 1097 has real-hardware evidence and remains under field validation while the ongoing stability test is completed.

Two local protocol paths

Observed PLAY2 generation 1 — GEN3 Plus / 02B0

Sunology PLAY2 → GEN3 Plus hardware variant → LSW5BLE logger → TCP 8899 / Solarman V5 → sensor list 0x02B0 → Modbus RTU FC03 → TSUN Local → Home Assistant

Observed PLAY2 generation 2 — GEN4 / 1097

Sunology PLAY2 → GEN4 hardware variant → profile Tengsheng_G4 → sensor list 4247 / 0x1097 → TSUN Local 1097 adapter → Home Assistant
Known 02B0 field firmware: LSW5BLE_17_02B0_1.08-D1. The GEN4 unit reports the Tengsheng_G4 profile internally. TSUN Local uses what the device exposes locally rather than assuming a protocol from the PLAY2 product name.

Easy installation

  1. Install TSUN Local from HACS.
  2. Restart Home Assistant.
  3. Open Settings → Devices & services and add TSUN Local.
  4. Let automatic discovery find and identify the PLAY2 logger.

No proxy deployment. No cloud account required for the data path. No protocol selector. No manual IP in the validated automatic flow.

What data can appear?

PVVoltage, current, power, daily energy and total energy for detected inputs.
ACVoltage, current, frequency, power, daily energy and total energy.
CommunicationOnline state, last successful communication, duration and consecutive failures.
DiagnosticsLogger/device information and read-only advanced diagnostics where supported.

Explore the visual entity reference →

Readable alarms on both protocol families

The validated PLAY2 uses the 02B0 alarm catalogue, while the GEN4 field variant uses the 1097 catalogue. TSUN Local keeps stable protocol-specific diagnostic codes, for example 02B0-A014 or 1097-A041, and uses neutral wording where a manufacturer meaning has not been confirmed.

Why are there two PLAY2 protocol paths?

The first independently validated PLAY2 exposed the 02B0 path and was narrowed to the TSUN GEN3 Plus family. Another real-world PLAY2 report exposed protocol 1097, confirming a GEN4 local path under the same PLAY2 commercial name. TSUN Local therefore detects the protocol at runtime instead of hard-coding PLAY2 to 02B0.

Follow the PLAY2 1097 stability issue →

Read the original PLAY2 protocol research history →

Community validation credit

Thanks to @dca31 for independently validating the PLAY2 GEN3 Plus / 02B0 path through the normal TSUN Local Home Assistant flow, and to @phildeg31 for the real-hardware PLAY2 GEN4 / 1097 diagnostics and ongoing stability testing.

Independent community project

TSUN Local is unofficial and independent. It is not developed, approved, endorsed or maintained by Sunology or TSUN. Product names belong to their respective owners.