Adding initial Wallbox implementation#81
Conversation
dirkgroenen
left a comment
There was a problem hiding this comment.
A few minor remarks, but I'll help you to fix those and have a look at the failing tests as well.
…ration, and lint - MaxChargerLimit now uses `max_available_power` sensor (hardware max) instead of reusing the `maximum_charging_current` number entity - has_synced_phase_limits returns True (single global current = synced) - car_connected includes all connected statuses (Scheduled, Waiting, WaitingInQueue*, WaitingMid*) - can_charge includes Discharging to fix hierarchy violation - Register CHARGER_DOMAIN_WALLBOX in config_flow device filter - Add # noqa: TID252, fix D213 docstrings, msg pattern for ValueError, remove unnecessary try/except in set_current_limit - Rewrite tests: correct Phase import, dedicated is_charger_device tests, exhaustive status coverage, float parsing, has_synced test
|
@safinea are you in the ability to test the current branch with your wallbox to see if all is working correctly? Should be in a ready-to-merge state now. |
|
Testing is underway, although 'faking' a high current use may be difficult. Initial results are promising. |
Hi, also downloaded and replaced the branch files and get this: Config-flow kon niet geladen worden: {"message":"Invalid handler specified"} |
|
@AOskam if you have HACS you can install a specific version by running the following service action (Via HASS -> Developer Tools -> Actions) action: update.install
data:
version: 8eb3fb5a36cb5f29ffa499296d172a5a668997f0
target:
entity_id: update.evse_load_balancer_updateThat should install the latest commit from this branch. Would you mind giving that a try to see if it wasn't something in the copy-pasting of the files that went wrong? Also please provide me with full logs (or your terminal output) such that I can see where the issue is happening. |
Ah, didn't know that :). Install went fine now. Wallbox was detected and configurable, will charge the car this evening and see if it responds properly. Using DSMR and a Pulsar plus charger. Thanks |
|
some issues, do not get the available current sensor at the moment. Logger: homeassistant.components.sensor Error adding entity sensor.evse_load_balancer_available_current_l1 for domain sensor with platform evse_load_balancer |
|
and: Logger: homeassistant Error doing job: Exception in callback _TrackTimeInterval._interval_listener() (task: None) |
|
Also the integration hang on "waiting for charger" when it started up. When the charger definition changed, it did not switch. Only after reloading the integration it changed to "monitoring loads", however because of the sensor config fault it is not functioning i guess. Not good at coding myself, so cannot help you with that ;). |
|
@AOskam it seems like the DSMR meter has an issue finding the Voltage entity. Which DSMR version are you using? It might be that there is a different entity name being used. Also please check if your DSMR integration is indeed exposing Voltage entities for all three phases L1/L2/L3. |
|
@dirkgroenen FWIW, I'm using "dsmr_version": "5" according to the diagnostics. The DSMR meter is showing the current per the 3 phases, but the EVSE load balancer was giving "Unavailable" for the available current sensors. DSMR sensors are |
|
Good to hear @safinea 🙌 Looking forward hearing whether the wallbox implementation works |
Added Wallbox charger implementation, plus a simple test file.
Code is untested and is submitted as is.