-
-
Notifications
You must be signed in to change notification settings - Fork 758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wallbox Pulsar: charger logic error: current mismatch #18974
Comments
Try |
thank you. It helped. |
So unfortunately the problem still persists. After some investigation I think that something (or the wallbox itself) is irregularly changing the charging current to 32A. Attached are the logs and trace. If anyone can, please look at the time between CET 2025/02/20 11:27:15 and 2025/02/20 11:27:45. I tried writing to Wallbox support, but they are not willing to look into their logs for me why this happened. They only tell me that they do not recommend this type of control :-/. at 2025/02/20 11:27:06 was current value 21.8A `[ocpp ] TRACE 2025/02/20 11:27:15 send sloupek: [2,"4046667528","SetChargingProfile",{"connectorId":1,"csChargingProfiles":{"chargingProfileId":30,"stackLevel":10,"chargingProfilePurpose":"TxDefaultProfile","chargingProfileKind":"Absolute","chargingSchedule":{"startSchedule":"2025-02-20T10:26:15Z","chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":21}]} } }] [ocpp ] TRACE 2025/02/20 11:27:16 recv sloupek: [3,"4046667528",{"status": "Accepted"}]` in next second it send meter current 21.8A:
10 second after it was 30.9
evcc-20250220-113340-trace.log |
Wallbox.com unfortunately has numerous issues with the ocpp implementation. It feels like each time they release a new firmware, they fix one thing but mess up two others. |
yes :-/ ... i was able to isolate problem - i can set value from 6A to 18A without problem. I case i set 19A or more, its set to 18A.... It looks like i will need to make custom charger through homeassistant and wallbox integration :-/. |
Quick fix: Just set Broken firmware will not get fixed by just using other software. |
yes, of course. But that's not a exactly right in this case. Because Homeassistant is using wallbox integration with their cloud... and max power regulation from their cloud is working.... so i can use HA as bridge between evcc and stupid wallbox cloud... |
Seems they really don't want.
Essentially means that they don't trust their smart charging implementation. Unfortunately nothing we could do. |
I tried downgrading to version 5 (5.13.17, which the charger originally came with). The issue remains the same. Can't change max charge value correctly. I find this strange—surely someone within the EVCC community must be using chargers from this manufacturer, and if this were an inherent feature, it would have been documented somewhere, right? I'm worried that I might be doing something wrong, but EVCC seems so straightforward that I have no idea where I could be making a mistake. :) |
Describe the bug
Hi, when I try charge with OCPP connected Wallbox Pulsar Max in Solar or Min+Solar mode, there are continuos errors in log like : charger logic error: current mismatch (got 32A, expected 16.2A)..
Are there probles on EVCC or Wallbox side? In wallbox app i can see requested value for some time (seconds...) for example 16A, but after some soconds is returned back to 32A.
I had isolated every possible other device, even disabled chargng station access to cloud. EVCC was the only thing that could communicate with the charger.
Maybe important: I cant set this in my app: Enable “Improved charger control” (Profile -> Experimental functions) (myWallbox app)
Steps to reproduce
...
Configuration details
Log details
What type of operating system or environment does evcc run on?
Linux
External automation
Nightly build
Version
0.200.1
The text was updated successfully, but these errors were encountered: