Repository navigation
support: Kevolt PD0080G-TPM-EU 3-phase; hybrid inverter #15
Description
Activity
Thanks for the support archive.
I checked the package. The collector is reachable and the inverter/charger does respond through the Eybond WiFi stick, but the local register layout does not match any currently supported local profiles. Because of that, integration cannot safely identify this inverter yet, so some entities may show0orunavailable.
Please install the latest beta release first:
https://github.com/groove-max/ha-eybond-local/releases/tag/v0.3.0-beta.1After updating:
- Restart Home Assistant.
- Open the EyeBond Local integration.
- Create a new Support Archive.
- If the integration offers Cloud Evidence / cloud diagnostics, please run it too using the same account that sees this device in SmartValue / ValueCloud.
- Attach the new ZIP archive here.
The newer beta contains improved diagnostics and cloud-evidence export. It may still not fully detect the inverter locally, but the new support package should give me enough information to map the Kevolt PD0080G-TPM-EU register layout and add proper support.
Reacted by Kiq0101KXNCNR8TS2GPR03YH0QXBDB4_20260717T082039336339Z.zip
I created the new support file.
I cannot use my ValueClouds user and pwd, so this section is missing.As I see, the new support file didn't generate useful 'raw_capture.json'.
I tried to read registers from 500 to 599, but nothing answer.v0.3.0-beta.2 now includes an exact read-only profile for the Kevolt PD0080G-TPM-EU 80 kW inverter: https://github.com/groove-max/ha-eybond-local/releases/tag/v0.3.0-beta.2
The profile is gated by the captured Deye-compatible high-register fingerprint and exposes status, energy, battery, three-phase grid/load/generator, and PV telemetry. It intentionally adds no controls.
Please retest on the inverter and check that the model is detected and the main telemetry values are plausible. A fresh Support Archive would be especially useful for confirming battery current/power sign semantics before those fields are treated as canonical.
The exact read-only Kevolt PD0080G-TPM-EU profile remains included in v0.3.0-beta.4. Beta.4 also unifies the driver/runtime/entity telemetry path, so a value accepted by the profile should no longer disappear or be reinterpreted by a separate entity projection.
Please update the existing entry and check the main three-phase grid, load, PV, battery, and energy values. I am especially interested in the sign of battery current and battery power during both charging and discharging. A fresh Support Archive after that check would let me promote only the fields that match the real hardware. The profile intentionally remains read-only.
01KZRBSS4JB5V8W3MZVWDDE2NF_20260826T103216457411Z.zip
I installed the v0.3.0-beta.4 version.
Here is the new support archive.Thank you for the updated diagnostics. This is an unusual case: the collector connection and its metadata are working, but the local inverter data path is not returning responses, while the captured cloud traffic shows that the same inverter does respond there.
The available support archives are not sufficient to determine exactly where this difference occurs, and I would prefer not to make speculative changes that could affect other collectors.
If you are comfortable with it, temporary remote access would make debugging much easier:
- SSH access to a test Home Assistant system connected to this collector; or
- temporary remote access to the collector’s local network.
The access can be limited, temporary, and revoked immediately after testing. Please do not post any credentials, SSH keys, VPN links, or tokens in this public issue. If you agree, contact me privately via Telegram:
@groove_max, and we can arrange a safe method.If remote access is not possible, that is completely fine. We can instead prepare a diagnostic build and step-by-step tests, but identifying the cause will likely take longer.
Thank you again for providing temporary remote access. It made it possible to identify the actual problem instead of guessing from the existing archives.
This collector uses AT commands for its management interface, but the inverter replies on the same live connection using correlated EyeBond FC4 frames. The integration previously assumed that both sides of the session used the same transport, so valid inverter replies were not reaching the Kevolt driver.
The current
mainnow negotiates the inverter data path independently on the exact live collector session. It includes the Kevolt PD0080G-TPM-EU telemetry profile and the documented Deye-compatible control surface.The controls remain disabled by default and are marked as untested. They become available only after selecting Full control, so please verify the device behavior from the Home Assistant interface and let me know what works correctly and whether anything still appears unavailable.
The updated code is available here:
https://github.com/groove-max/ha-eybond-local/archive/refs/heads/main.zipHey — late note for the archaeology file.
Your AT-management / FC4-inverter-on-the-same-session finding wasn't an aberration: the Anern SPI-12000W path in #45 is another FC4-on-AT (ValueCloud/SmartValue) case. Different command family (short-ASCII
MD/Q1/F/RB+ solicited5AA5/aabb), same general shape Maksym already fixed for Kevolt.Mostly posting so the next person searching "SmartValue works locally doesn't" sees both threads.
Cheers,
Mike
Preflight
Home Assistant version
Home Assistant Snap Core 2025.10.4
EyeBond Local version
0.1.53
Support Archive filename
01KXNCNR8TS2GPR03YH0QXBDB4_20260716T121924485964Z.zip
What kind of support issue is this?
Unsupported hardware
Inverter / collector model
Kevolt PD0080G-TPM-EU + Eybond WiFi stick (SmartValue app on phone; ValueClouds on web)
What is missing or broken?
The device detected, entities imported into HA but some values are shows "0" value, others are "unavailable".
01KXNCNR8TS2GPR03YH0QXBDB4_20260716T121924485964Z.zip
Extra context
No response
Where did you hear about EyeBond Local?
Search engine (Google, etc.)