Add device config for Arlec/Deta EV200D-HA EV charger - #6088
Open
kbinish-ship-it wants to merge 1 commit into
Open
Add device config for Arlec/Deta EV200D-HA EV charger#6088kbinish-ship-it wants to merge 1 commit into
kbinish-ship-it wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a dedicated device profile for the Arlec/Deta EV200D-HA EV charger (22kW/32A, 3-phase), which is currently unsupported and incorrectly matches
tera_w01_evcharger: wrong min current (this hardware supports 6A, not 8A) and missing several DPs the Tera profile doesn't define.Related issue: #6087, filed with the full cloud DP dump, local DPS captures, and notes on what's confirmed locally vs still guesswork.
This profile matches on product_id
svufayckw5hozqbz(the device's own cloud "thing" dump; firmware self-identifies asH0_ARLEC-V1.0.6), corrects the charge current range to 6-32A, keeps all the Tera-profile entities this hardware also supports, and adds entities for the DPs this device exposes that Tera's profile doesn't: single-phase power (DP5), session energy (DP25), meter ID (DP22), dynamic load management switch (DP101), home max current (DP102), solar mode (DP103, read-only/diagnostic since the full enum isn't confirmed), solar current from grid (DP104), and solar stable time (DP105). DPs I couldn't confirm safely from local capture alone (11, 12, 15, 16, 17, 19, 27, 33) are deliberately left unmapped rather than guessed.Testing: validated with the integration's own matching code (TuyaDeviceConfig.matches() / possible_matches()), where this profile scores 101 against the real device's DPS vs 59 for tera_w01_evcharger (today's fallback match). Also ran it live against the physical device: switched a running Home Assistant instance onto this profile, confirmed all entities (existing and new) report correct values, and confirmed the corrected 6A minimum actually works on the hardware.
I'm aware PRs are currently paused. Opening this anyway at the device owner's request, since the fix is tested and the corresponding issue is already filed. Happy to wait for review whenever bandwidth allows, and to make any changes requested.
🤖 Generated with Claude Code
https://claude.ai/code/session_01X3P3d2rdYSTW9tXCYvDTUa