-
-
Notifications
You must be signed in to change notification settings - Fork 641
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
easee invalid Status 403, no matching rate, max charge current, invalid status #16085
Comments
Die Fehlermeldung kommt von Easee |
Easee API appears to be down |
Still down, FYI |
Same here |
guess we have to wait |
bei mir auch.... es nervt...entweder ist irgendwas mit dem Cupra (VW) Server, dann Datenschutzeinstellungen und jetzt auch noch Easee |
Ja, oder evcc mit dem Lizenz Token. Komisch ist, wenn beides gleichzeitig passiert. |
Ich leide auch darunter. Gestern wurden 15 % Solarenergie verbraucht :( bei 40 kW |
ok ich habe das gleich Problem. Die Wallbox lässt sich also über die App überhaupt nicht mehr steuern. Lädt munter vor sich hin. also kann man nur über Easee beenden oder? |
richtig. |
.. auch die easee app spinnt, hängt immer wieder. |
OK. Dann muss ich das Auto immer abstecken...das blöde bluelink funktioniert nicht immer in der Garage |
hab das gleiche Problem. Ist doch beschissen, wenn man abhängig von irgendeiner Cloud ist. |
Easee don't even let OCPP work without using the Easee API. |
So theres no possibility? |
It's unlikely that Easee Wallboxes are running Modbus. Bluetooth would require having the evcc server being within Bluetooth range (which sort of defeats the object) plus a lot of work to reverse engineer the app. In theory, it should be possible to spoof the Easee server for local control but, ideally, Easee should allow local OCPP control like other manufacturers.
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: unstressable ***@***.***>
Sent: Sunday, September 15, 2024 10:02:03 PM
To: evcc-io/evcc ***@***.***>
Cc: pmknowles ***@***.***>; Comment ***@***.***>
Subject: Re: [evcc-io/evcc] easee invalid Status 403, no matching rate, max charge current, invalid status (Issue #16085)
have the same problem. Can't you integrate the Easee locally to prevent such things from the outset?
It sucks when you're dependent on any cloud.
Easee don't even let OCPP work without using the Easee API.
So theres no possibility?
Nor Modbus TCP?
Bluetooth?
—
Reply to this email directly, view it on GitHub<#16085 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI5KPM26GTGQAPQF3NKSO33ZWXYUXAVCNFSM6AAAAABOFI53XWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJRG44TAMRVGM>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Me too! |
Describe the bug
Seit heute Nachmittag bekomme ich plötzlich folgende Fehlermeldungen, ohne etwas anderes konfiguriert zu haben. Heute morgen lief die Ladung noch problemlos:
Steps to reproduce
...
Configuration details
Log details
What type of operating system are you running?
Linux
Nightly build
Version
0.130.9 and 0.130.8 beide Fehlerhaft
The text was updated successfully, but these errors were encountered: