#ocpp — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ocpp, aggregated by home.social.
-
"The EV charging industry has well-established security standards. OCPP (Open Charge Point Protocol) provides clear guidelines for securing the communication channel between EV Chargers and the Charging Station Management System (CSMS): use VPNs or Private APNs, implement OCPP Security Profile 2 or higher, enforce TLS mutual authentication etc. When properly configured, these measures make it significantly harder for threat actors to compromise the management channel.
But what about the other side of the charger?
While the industry has focused on securing the backend communication, the attack surface exposed through the CCS2 charging plug remains largely untested.
Every time an EV connects to a charger, it establishes an IP network over Power Line Communication (PLC). This network was designed for V2G protocols. But we also discovered other EV charger operating system services listening on these network interfaces.
From a traditional IT security perspective, think of this attack vector as analogous to an attacker having a port in the corporate LAN. The scenario is identical, except the port isn't an RJ45 jack in the office, it's a CCS2 connector in a parking lot.
This has profound implications: compromised EV chargers can serve as a foothold into CPO (Charge Point Operator) private networks. Since chargers often connect to backend systems via VPN or Private APN infrastructure, an attacker with access to a charger could potentially pivot to back-office systems, billing platforms, or other critical infrastructure."
https://www.saiflow.com/blog/the-hidden-ccs2-attack-surface-on-ev-chargers
-
"The EV charging industry has well-established security standards. OCPP (Open Charge Point Protocol) provides clear guidelines for securing the communication channel between EV Chargers and the Charging Station Management System (CSMS): use VPNs or Private APNs, implement OCPP Security Profile 2 or higher, enforce TLS mutual authentication etc. When properly configured, these measures make it significantly harder for threat actors to compromise the management channel.
But what about the other side of the charger?
While the industry has focused on securing the backend communication, the attack surface exposed through the CCS2 charging plug remains largely untested.
Every time an EV connects to a charger, it establishes an IP network over Power Line Communication (PLC). This network was designed for V2G protocols. But we also discovered other EV charger operating system services listening on these network interfaces.
From a traditional IT security perspective, think of this attack vector as analogous to an attacker having a port in the corporate LAN. The scenario is identical, except the port isn't an RJ45 jack in the office, it's a CCS2 connector in a parking lot.
This has profound implications: compromised EV chargers can serve as a foothold into CPO (Charge Point Operator) private networks. Since chargers often connect to backend systems via VPN or Private APN infrastructure, an attacker with access to a charger could potentially pivot to back-office systems, billing platforms, or other critical infrastructure."
https://www.saiflow.com/blog/the-hidden-ccs2-attack-surface-on-ev-chargers
-
Today in "teaching math to sand was a mistake": SteVe reports a -5.4kWh charge, because, uhm, apparently it started the charge at 0, but also at -22kWh?!
As the "Start value" (0) is reported in the CSV export, but not the initial value (-22kWh), now it looks like I need to grab each individual transaction in order to calculate correct numbers. WTF.
-
Today in "teaching math to sand was a mistake": SteVe reports a -5.4kWh charge, because, uhm, apparently it started the charge at 0, but also at -22kWh?!
As the "Start value" (0) is reported in the CSV export, but not the initial value (-22kWh), now it looks like I need to grab each individual transaction in order to calculate correct numbers. WTF.
-
Основы Product Security для автомобилей и зарядных станций: термины, архитектура, фреймворки и практические кейсы
Современный автомобиль и зарядная станция — это уже не просто железо, а сложные программно-аппаратные продукты. В статье разбираю базовые термины, архитектуру, trust boundaries, OTA, типовые риски и ключевые фреймворки с точки зрения Product Security.
https://habr.com/ru/articles/1053540/
#product_security #automotive_security #EV #EVSE #OCPP #OTA #ECU #SBOM #secure_SDLC #DevSecOps
-
I'm trying to be more social and invite more spontaneity and serendipity into my life (mostly because I like S-words?), therefore...
if anyone would be interested in hopping into a brief audio call sometime to talk about any of the geeky topics below, totally informal and improvised, let me know! We could do it cameras off via Signal or Google Meet. We could limit it to 2 to 4-5 folks at once. I would herd the cats.
#DCC TTRPG (#DungeonCrawlClassics)
software performance optimization (especially latency & throughput, and hosting cost minimization)
#Paranoia TTRPG
#HHGG The Hitchhiker's Guide to the Galaxy
-
CW: CW Elektroauto
"wir möchten Sie darüber informieren, dass die Betrags-Reservierung vom 30.12.2025 10:53 aufgehoben wurde. Es erfolgt keine Abbuchung."
Klar, dass die Energiepreise hoch sein müssen, wenn Vorgänge tumb verloren gehen (#OCPP ist wirklich ein Paradebeispiel für RFC 1925) und nicht abgerechnet werden können. 🤷♀️
-
CW: CW Elektroauto
"wir möchten Sie darüber informieren, dass die Betrags-Reservierung vom 30.12.2025 10:53 aufgehoben wurde. Es erfolgt keine Abbuchung."
Klar, dass die Energiepreise hoch sein müssen, wenn Vorgänge tumb verloren gehen (#OCPP ist wirklich ein Paradebeispiel für RFC 1925) und nicht abgerechnet werden können. 🤷♀️
-
sighs
WAS looking at Grizzl-E car chargers for the new house, have one mini for reasons, and it works with #HomeAssistant in custom OCPP mode just fine.
Was having a slight issue, looked like a firmware upgrade might sort it, so flipped it back to their app updated, it started behaving the way I expected, great!
Went to flip it back to HASS as my #OCPP provider aaaand, what the heck is this login nonsense? Did I set a password? Nothing in the password vault, start searching...
They made it a premium feature worth about 50% of the cost of the charger!
What the frell‽
Needless to say I'm a smidge unimpressed. Grizzl-E / United Chargers are now 110% out of the running for the new house, and I've sent a polite nasty-gram their way asking for the feature to be restored since I was using it.
sighs
That's not the way you win customers, that's for sure
-
sighs
WAS looking at Grizzl-E car chargers for the new house, have one mini for reasons, and it works with #HomeAssistant in custom OCPP mode just fine.
Was having a slight issue, looked like a firmware upgrade might sort it, so flipped it back to their app updated, it started behaving the way I expected, great!
Went to flip it back to HASS as my #OCPP provider aaaand, what the heck is this login nonsense? Did I set a password? Nothing in the password vault, start searching...
They made it a premium feature worth about 50% of the cost of the charger!
What the frell‽
Needless to say I'm a smidge unimpressed. Grizzl-E / United Chargers are now 110% out of the running for the new house, and I've sent a polite nasty-gram their way asking for the feature to be restored since I was using it.
sighs
That's not the way you win customers, that's for sure
-
OpenOCPP - Open-source embedded software for EV chargers.
-
OpenOCPP - Open-source embedded software for EV chargers.
-
CW: CW OCPP
"Ich brauche bis 31. Mai die Privatentnahmen an der geschäftlichen #Wallbox sonst kommen wir in die Hölle und DU ZUERST!" Na gut. Mitten drin grausame Differenz zwischen Zähler und Ladevorgängen. Stellt sich raus, wenn am Monatsletzten abends angeschlossen wird, läuft zwar der Zähler (klar), aber der Ladevorgang zählt in den Monat, wo der Stecker rausgezogen wird, weil dann erst die #OCPP-Transaktion abgeschlossen wird. ☝️Immer noch mit shOCPP, Ehrensache. 🤡 https://github.com/mschmitt/shocpp
-
CW: CW OCPP
"Ich brauche bis 31. Mai die Privatentnahmen an der geschäftlichen #Wallbox sonst kommen wir in die Hölle und DU ZUERST!" Na gut. Mitten drin grausame Differenz zwischen Zähler und Ladevorgängen. Stellt sich raus, wenn am Monatsletzten abends angeschlossen wird, läuft zwar der Zähler (klar), aber der Ladevorgang zählt in den Monat, wo der Stecker rausgezogen wird, weil dann erst die #OCPP-Transaktion abgeschlossen wird. ☝️Immer noch mit shOCPP, Ehrensache. 🤡 https://github.com/mschmitt/shocpp
-
Wenn ich die #EVbox #Elvi mit dem Cloud-Backend von Everon verbinde, funktioniert sie zuverlässig.
Verbinde ich sie mit #evcc via #ocpp, bricht die Verbindung relativ häufig ab und baut sich auch nur dann wieder auf, wenn ich die #Wallbox hart neustarte.
Blöderweise gibt es nur Support, wenn ich die Wallbox mit dem offiziellen Backend verbunden habe - was mir ja herzlich wenig hilft.
-
#SolarEdge have told me they don't support "third party" (#EV charge points. Mine is an MG (Aurora) ChargeHub.
To control it, I _think_ I need an #OCPP server. Here's one: https://github.com/c-jimenez/open-ocpp
For that OCPP server to work, it will need to interrogate the SolarEdge control box to ask when it is "exporting", that is, has surplus energy that would be better stored in the car.
A problem: that #SolarEdge controller seems network-hardened, and rather determined to only send out only to SolarEdge servers, not to talk with anything on the local net at all.
Anyone out there done this already? I'd love a pointer or two.
#solar #charging -
#SolarEdge have told me they don't support "third party" (#EV charge points. Mine is an MG (Aurora) ChargeHub.
To control it, I _think_ I need an #OCPP server. Here's one: https://github.com/c-jimenez/open-ocpp
For that OCPP server to work, it will need to interrogate the SolarEdge control box to ask when it is "exporting", that is, has surplus energy that would be better stored in the car.
A problem: that #SolarEdge controller seems network-hardened, and rather determined to only send out only to SolarEdge servers, not to talk with anything on the local net at all.
Anyone out there done this already? I'd love a pointer or two.
#solar #charging -
@selea you go with smart one if you want to modulate the charge current : to not overload main fuse or to track your solar production and prevent import from the grid when charging. If you have #homeassistant there is an #ocpp hacs module, connect the charger to it and feel free to cut internet access to the charger, having it receive instructions from HA. I think only firmware upgrades may then require big bad internets.
-
@selea you go with smart one if you want to modulate the charge current : to not overload main fuse or to track your solar production and prevent import from the grid when charging. If you have #homeassistant there is an #ocpp hacs module, connect the charger to it and feel free to cut internet access to the charger, having it receive instructions from HA. I think only firmware upgrades may then require big bad internets.
-
Alter Schwede, ist die #goeCharger-Firmware unangenehm, und das an einem Sonntagmorgen, und das ist noch die alte #OCPP-Version 1.6. 🤕 https://github.com/goecharger/go-eCharger-API-v2/issues/176#issuecomment-1722433582
-
Alter Schwede, ist die #goeCharger-Firmware unangenehm, und das an einem Sonntagmorgen, und das ist noch die alte #OCPP-Version 1.6. 🤕 https://github.com/goecharger/go-eCharger-API-v2/issues/176#issuecomment-1722433582
-
#OCPP innerhalb eines Ladeparks, alle Charger authentisieren gegen das lokal zentrale Kreditkartenterminal, ergibt total Sinn. Alle per Internet M2M-IOT-SIM irgendwohin, wo soll sie denn herkommen, die Zuverlässigkeit?
-
#OCPP innerhalb eines Ladeparks, alle Charger authentisieren gegen das lokal zentrale Kreditkartenterminal, ergibt total Sinn. Alle per Internet M2M-IOT-SIM irgendwohin, wo soll sie denn herkommen, die Zuverlässigkeit?
-
Die gefürchtete #OCPP-1.6-Implementation in #Bash ist öffentlich und ich beginne zu verstehen, warum Ladesäulenfreischaltung ein einziges Dumpsterfire ist. Alle Charger halten 24x7x365 einen Socket zur zentralen Instanz offen und die muss lückenlos deren Status tracken, in Echtzeit im Verbund mit drölfzig Roamingsystemen. So sehr ich gegen mancher Leute Girocard-Fetisch bin, ich hab keine Ahnung, wie das mit dem Laden anders skalieren soll. https://github.com/mschmitt/shocpp #Elektroauto #Elektromobilität
-
Die gefürchtete #OCPP-1.6-Implementation in #Bash ist öffentlich und ich beginne zu verstehen, warum Ladesäulenfreischaltung ein einziges Dumpsterfire ist. Alle Charger halten 24x7x365 einen Socket zur zentralen Instanz offen und die muss lückenlos deren Status tracken, in Echtzeit im Verbund mit drölfzig Roamingsystemen. So sehr ich gegen mancher Leute Girocard-Fetisch bin, ich hab keine Ahnung, wie das mit dem Laden anders skalieren soll. https://github.com/mschmitt/shocpp #Elektroauto #Elektromobilität
-
CW: KFZ Elektroauto
"Schau genau auf den Bildschirm, ich gehe jetzt und ziehe das Auto raus, und dann siehst du hier im Log hoffentlich, wie der Abrechnungsdatensatz vorbeiscrollt." (...) "Da kam eine Zeile, war das etwa alles?" - "JA GEIL ODER?!? ES FUNKTIONIERT!!!!" (Bin mit einer Banausin verheiratet ❤️.) #OCPP #Elektroauto
-
CW: KFZ Elektroauto
"Schau genau auf den Bildschirm, ich gehe jetzt und ziehe das Auto raus, und dann siehst du hier im Log hoffentlich, wie der Abrechnungsdatensatz vorbeiscrollt." (...) "Da kam eine Zeile, war das etwa alles?" - "JA GEIL ODER?!? ES FUNKTIONIERT!!!!" (Bin mit einer Banausin verheiratet ❤️.) #OCPP #Elektroauto
-
Jetzt hab ich meine eigene #OCPP-Implementation programmiert, weil alle OCPP-Implementationen Schmutz sind, und muss am Ende feststellen, dass meine Implementation genauso Schmutz ist. Nirgends integrierbares Industrieprotokoll, das immer über alle denkbaren Layer hinweg in einem Guss durchimplementiert werden muss.
-
Jetzt hab ich meine eigene #OCPP-Implementation programmiert, weil alle OCPP-Implementationen Schmutz sind, und muss am Ende feststellen, dass meine Implementation genauso Schmutz ist. Nirgends integrierbares Industrieprotokoll, das immer über alle denkbaren Layer hinweg in einem Guss durchimplementiert werden muss.
