Hi James. Did you get your problem solved? I seem to be having the same issue. Also with a gmail account…
use the E-mail to login to the app. And then you should be fine.
I also wonder where added_range is calculated. In which upstream library is it? I did not find it in GitHub - cliviu74/wallbox: Python Module interface for Wallbox EV chargers api
It simply does not work with a Google account. I deleted my account and created an new wallbox one with an outlook e-mail adress. And it instantly worked now. 
1 Like
I updated my Walbox Pulsar Plus to 6.7.33 and I’m seeing data every 30 seconds, and then the data is unavailable for 30 seconds, and so on.
Is anyone else experiencing this? I’ve already reported it to Wallbox support.
Perhaps an integration adjustment is needed since 6.7.33?
Antwoord van Wallbox support:
API Service Update - Juni 2025
Onderwerp: Verbeteringen in API-prestaties en nieuw gebruiksbeleid
We hebben onlangs ongewoon hoog en inefficiënt verkeer naar onze API geïdentificeerd, met name van bepaalde third-party services zoals Home Assistant. Dit heeft af en toe de prestaties en betrouwbaarheid voor andere gebruikers beïnvloed. Om dit aan te pakken, rollen wij de volgende updates uit:
Wat is nieuw
- Geüpgradede API-infrastructuur om beter om te gaan met gelijktijdige verzoeken en om langdurige schaalbaarheid te garanderen.
- Nieuw gebruiksbeleid gericht op het bevorderen van rationele en duurzame integratiepatronen op externe platforms.
- Verbeterde rate-limiting-logica – het huidige systeem zal worden aangepast om meer gebalanceerde toegang te bieden zonder de algehele stabiliteit in gevaar te brengen.
Waarom dit belangrijk is
Sommige integraties, door inefficiënt polling of overbodige verzoeken, hebben een buitensporige belasting van onze servers veroorzaakt. Ons nieuwe systeem zal helpen deze problemen te minimaliseren terwijl we open, flexibele integratie blijven ondersteunen.
Wat u moet doen
Als u een integratie met onze API onderhoudt (bijv. via Home Assistant), raden we sterk aan uw implementatie te herzien om ervoor te zorgen dat deze in overeenstemming is met de nieuwe richtlijnen. Vermijd onnodig of frequent polling. Overweeg waar mogelijk caching, event-based logica of batching te gebruiken.
Wanneer
Deze wijzigingen worden geleidelijk uitgerold vanaf 18 juni 2025.
Voor ontwikkelaars: gedetailleerde technische documentatie en bijgewerkte rate-limieten zullen binnenkort beschikbaar zijn in het Developer Portal.
Dank u voor uw medewerking en inzet voor verantwoordelijk gebruik.
— Het API-team
You can configure the Wallbox with OCPP and get an update each seconds with the sample interval setting.
Nice tip [lostOzone], thanks!
Does the charger provide SoC (state of charge of battery)?
I would like to make automation that will stop chargimg the car when it reaches 80%.
@nicko9 - This question has been answered many times already.
AC chargers do not have any ability to determine SoC of the car. The Type 1 or Type 2 connection is very simple - essentially analog - and no provision has been made for communicating SoC. You will need to get this information from your car.
Fortunately, my Kia EV5 has a setting to limit charge to 80%, or any other value I choose. My previous Nissan Leaf did not have this setting, so I made a kWh limit on my charging dashboard to do the same thing.
1 Like
You can use the manufacturer Cloud. Or get a WiCAN Pro if your car is supported. This device can give the SoC using OBD and WiFi.
1 Like
Thanks! Thread spanned over 4 years, so I wasn’t sure if something was changed. I guess I’ll calculate time 
1 Like
hello everyone, for information, i’m currently working on an integration for people using a Morec type box which work with local UDP network protocol (no cloud but the application evsemaster).
it’s almost working, when i finish my test i will publish it and keep you inform here
hope it will help some of you too
1 Like
Hi all,
Sharing a Home Assistant integration I built for chargers that use the EVSE Master (EVSEMaster) mobile app protocol over local UDP.
Tested with a MOREC 7 kW wallbox (single‑phase) that speaks this protocol.
Project:
- Repository: GitHub - Oniric75/evsemasterudp: Home Assistant integration for EVSE Master UDP protocol chargers
- License: MIT (NOTICE + attribution to the original reverse‑engineering reference)
Support the Project
If this integration helps you, please star the repository — it really boosts visibility and encourages future improvements: GitHub - Oniric75/evsemasterudp: Home Assistant integration for EVSE Master UDP protocol chargers
Thank you!
What it provides:
- Explicit Start / Stop charge buttons (no ambiguous toggle)
- Charge status sensor with states:
charging,soft_protection,not_charging - Sensors: current (A), voltage (V), power (W), cumulative energy (kWh), internal / external temperatures, meta operating state (idle / charging / plugged / offline / error)
- Configurable maximum current (amps) setting
- Optional soft protection delay between stop → new start to reduce mechanical relay wear
Basic HACS install:
- In HACS → Integrations → Custom repositories → add:
GitHub - Oniric75/evsemasterudp: Home Assistant integration for EVSE Master UDP protocol chargers (type: Integration) - Install “EVSE Master UDP”
- Restart Home Assistant
- Add the integration (provide charger password if required)
Minimal example automation (start at night):
alias: Start EVSE at 23:30
trigger:
- platform: time
at: "23:30:00"
condition: []
action:
- service: button.press
target:
entity_id: button.evsemaster_demarrer_charge
mode: single
And to stop at 06:30:
alias: Stop EVSE at 06:30
trigger:
- platform: time
at: "06:30:00"
action:
- service: button.press
target:
entity_id: button.evsemaster_arreter_charge
Disclaimer:
Use at your own risk; no guarantee of correctness or suitability for all hardware variants. Monitor behavior the first times you run automated starts/stops.
If your charger also uses the EVSEMaster UDP protocol (often seen with some generic / OEM white‑label units), this may save you time. Feedback or protocol observations welcome. ``````
1 Like
Hi, I would like to share a custom integration I made to monitor solar coverage when charging EV (or consumption of other devices) to gather insights on solar coverage. I’m using for some years template sensors to achieve this, but made instead a custom component that is publicly available. The accumulated data should be (very) persistent and survive restarts and updates etc.
if anyone is interested, here is the link to my repo. (yet to be tested long-term)
1 Like
HI all,
I was wondering if anyone could confirm if the internal workings between different Wallbox models are the same regarding the lock.
for my Copper SB, when lock is locked and cable gets plugged in, charging won’t start (charging enable = off). only when lock is unlocked, charging starts.
once charging started (charging enable = on), lock can be locked again and charging continues.
is this the same for all models?
Same on Pulsar
ok perfect, thanks for the confirmation!
if anyone is interested, I made a custom integration for smart EV charging.
more info:
can anyone confirm when using a Wallbox charger with a socket and the lock is locked, can you still plug in a cable into the wallbox or does the lock prevent this?