openchargingcloud / chargydesktopapp

The Chargy E-Mobility Transparency Application for Windows, Mac OS X and Linux (based on Electron)

ChargyTS Desktop App

Chargy is a transparency software for the validation of secure and transparent e-mobility charging processes, as defined by the German Calibration Law ("Eichrecht") in combination with the Alternative Fuels Infrastructure Regulation (AFIR) of the European Commission and the European Digital Quality Infrastructure. The software allows you to verify the cryptographic signatures of energy measurements within charge detail records and comes with a couple of useful extentions to simplify the entire process for endusers and operators.

Benefits of Chargy

1. Chargy comes with meta data. True charging transparency is more than just signed smart meter values. Chargy allows you to group multiple signed smart meter values to entire charging sessions and to add additional meta data like EVSE information, geo coordinates, tariffs, ... within your backend in order to improve the user experience for the ev drivers.
2. Chargy is secure. Chargy implements a public key infrastructure for managing certificates of smart meters, EVSEs, charging stations, charging station operators and e-mobility providers. By this the ev driver will always retrieve the correct public key to verify a charging process automatically and without complicated manual lookups in external databases.
3. Chargy is platform agnostic. The entire software is available for desktop and smart phone operating systems and .NET. If you want ports to other platforms or programming languages, we will support your efforts.
4. Chargy is Open Source. In contrast to other vendors in e-mobility, we belief that true transparency is only trustworthy if the entire process and the required software is open and reusable under a fair copyleft license (AGPL).
5. Chargy is open for your contributions. We currently support adapters for the protocols of different charging station vendors like chargeIT mobility, ABL (OCMF), chargepoint. The certification at the Physikalisch-Technische Bundesanstalt (PTB) is provided by chargeIT mobility. If you want to add your protocol or a protocol adapter feel free to read the contributor license agreement and to send us a pull request.
6. Chargy is white label. If you are a supporter of the Chargy project you can even use the entire software project under the free Apache 2.0 license. This allows you to create proprietary forks implementing your own corporate design or to include Chargy as a library within your existing application (This limitation was introduced to avoid discussions with too many black sheeps in the e-mobility market. We are sorry...).
7. Chargy is accessible. For public sector bodies Chargy fully supports the EU directive 2016/2102 on the accessibility of websites and mobile applications and provides a context-sensitive feedback-mechanism and methods for dispute resolution.

Editions, Versions and Milestones

Version 1.2.x of the Chargy Transparency Software was reviewed and certified by Verband der Elektrotechnik Elektronik Informationstechnik e.V. (VDE). If you are a charge point vendor and want to use this software to verify the compliance with the German Eichrecht you can talk to our partner ChargePoint and obtain the required legal documents.

Version 1.0.x of the Chargy Transparency Software was reviewed and certified by Physikalisch-Technische Bundesanstalt (PTB). If you are a charge point vendor and want to use this software to verify the compliance with the German Eichrecht you can talk to our partner chargeIT mobility and obtain the required legal documents.

If you need help with the Chargy Transparency Software or want to include your smarty energy meter or transparency data format, talk to us.

This software is also available as WebApp.

Future

The development of version v1.5 already started and will focus on enhanced security concepts, more digital certificates and pricing information.

Credits

• Christian Meusel for some more BSM validations.

Awards

The Chargy Transparency Software is one of the winners of the 1. Thuringia's Open-Source Prize in March 2019. This prize was awarded by Wolfgang Tiefensee, Thuringia’s Secretary of Commerce, in conjunction with the board of directors of the IT industry network ITNet Thuringia.

chargydesktopapp's Issues

Show user authorisation information within the overview of all charging processes

The PTB/CSA wants to see the user authorisation information within the overview of all charging processes (main screen, left side).

Background is that even a single ev driver might have different ways for authorisation: Multiple RFID cards, multiple eMA Ids, ...

Add support of an accessibility feedback mechanism for people with a disability

The EU directive 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies ( https://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX%3A32016L2102 ) defines an "accessibility" feedback mechanism for people with a disability. This is directive is transformed into local law e.g. in Thueringia in http://parldok.thueringen.de/ParlDok/vorgaenge/69750/1

There is already an optional feedback mechanism within the app, but this is focused on technical issues. This mechanism should be extended.

Make it more clear which data is regulatory important and which is just meta data

The PTB wants something like an optical divide or marks which parts of the shown data is regulatory important (German: "eichrechtlich relevant") and which is just meta data.

Show socket type, max energy, ...

Add socket type, max energy, ... to CTR data format and show it within the app (if present)...

Allow to select or drop multiple (charge transparency) files

I would like to request/propose a feature

As a user I want to select multiple charge transparency files at once. Such files could be different charging sessions and public key files. All data should be aggregated and merged.

Show which version of Chargy is certified with which version of a charging station/EVSE/smart meter

1. Regulators want the see which version of Chargy is certified with which version of a charging station, EVSE and smart meter.
2. Having something like a digital certificate for this would be positiv
3. This also means that they might allow us to release new minor versions of Chargy without recertifing Chargy with every type of charging stations in the market :)

CSA wants the meter status information decoded

The meter status information gives information about e.g. errors occured and the status of the internal clock.

Verify the application hash against the versions.json information

• Show if the application hash matches or not
• Show, but do not verify digital signatures

More information about charging session when clicking on a bubble within the map

End-Customers want more information about charging session when clicking on a bubble within the map, e.g. highlight/open the charging session and show its details.

VDE-Feedback and change requests on Chargy v1.1 (chargepoint)

1. Ids in the chargepoint format differ between different firmware versions. Therefore compare them case-insensitive. Let charge point define the default format for presenting those Ids within Chargy to the end user (e.g. 'all upper', 'all lower', ...).

Show software version of the charging station, EVSE and smart meter within a CTR

The regulators want to be able to see the software version of the...

1. Charging Station
2. EVSE (if it is not just a part of the charging station)
3. Smart Meter (if it is a device having its own regulations)

Add multi-language and localization support

Implement chart.js to visualize the charging curve

Already implemented within the ChargyMobileApp.

Improved security via digital certificates and a PKI

• Add Open Charging Cloud root certificate
• Make sure, that the versions.json is digitally signed by one or more organizations
• Verify the certificates/signatures of the entire versions.json
• Verify the certificates/signatures of a version
• Verify the certificates/signatures of a version package
• Verify the certificates/signatures of a energy meter public key
• Verify the certificates/signatures of another certificates/signature (build a chain/web of trust)
• Sign entire CTRs

MSIX windows version from the Microsoft Store can not verify the application hash

The installation path of the normal Windows version and the MSIX version are different.

Publication within the Microsoft Store

• First publication
• Refined publication

Certificates/signaturs for smart meter public keys

• Show all signers of a smart meter public key
• Verify certificates/signatures for smart meter public keys

EMP wants a dedicated documentation/example how to use Chargy as a library

• EMP already has some App
• EMP wants a dedicated documentation and examples how to use Chargy as a library
• Explanations how to use and verify the public keys and certificates

Support of tariffs and/or price infos

EMP wants to attach tariffs and/or price infos signed with his private key.
Tariffs for charging, parking, reservation, ...

Live-DVD: Disable autostart of removable media

The PTB want us to disable the autostart of removable media within the Linux Live DVD

Simon wants a directory of test data

Simon wants a directory of test data

Show digital certificates of energy meter public keys

Show digital certificates of energy meter public keys, but do not verify them

total_energy = 0.0 => Invalid transparency format!

I found a bug to report

Within the charge point data format the value "total_energy = 0.0" will be misinterpreted as a missing value (praise JavaScript magics!).

Expected behavior

Use another method to validate if all mandatory parameters exist and are well defined.

Change OBIS value format to e.g. "1-0:1.17.0*255"

Currently the "obis" code is represented as a array of bytes, e.g. "0100011100FF".
Of course the better representation would be: "1-0:1.17.0*255"

Publication within the Apple App Store

App Skins / White Label Features

Ein Charging Station Operator bzw. ein E-Mobility Provider könnte sich wünschen gewisse Farben und Texte der App nach seinem Corporate Design Vorgaben anzupassen:

1. Via dem Transparenzdatensatz, d.h. Anpassung erst nach Laden des Datensatzes
2. Via einer Zusatzdatei bei der Installation der Software (JSON, CSS), d.h. Anpassung nach Start der App

general flow

I have a question or need help

hello, come across this implementation and would like to ask you if you can explain more about general works as documentation is actually low.

In particular I cannot understand how data has to be certified and in which format ( all chargepoint uses different format? ) and what exactly the charging station need to create at the end of session to create the certified data.

For my understanding the software simply read a signed file sent from the station ( but I could be wrong) . So if have time can u better explain me this flow ?

Thanks !

Process .chargy file extentions/associations opened via this app

All charge transparency file names should have the extention .chargy
Open at least on Windows .chargy files via the Chargy Desktop App.

Allow to save the list of charging sessions as shown within the app

I would like to request/propose a feature

As a user I want to select multiple charge transparency records/files, to get a consolidated view of all my charging sessions and to save this list of charging sessions as shown within the app on my computer.

This means add a button or similar to the app which will store the given charging sessions using the Chargy data format.

Allow separate public key files as input

I would like to request/propose a feature

The public key of Chargepoint charging stations is not part of the charge transparency record, but an external file. Allow this file as additional input and merge it into the other charge transparency records.

Documentation of the software structure

• The PTB wants a simple diagram on the software structure.
• Add this also to the git repository

Show name and version of the crypto software used

The PTB wants more information about which crypto software is used to verify the signatures.

Problem: Strictly speaking two software libs are used. One for SHA256 and one for ECC.

Add support for ALFEN transparency format

Some customers want to use Chargy for ALFEN charging stations

• Support ALFEN transport via chargeIT JSON container
• Support ALFEN transport via SAFE XML container
• Parse and display ALFEN transparency data
• Verify ALFEN signatures
• The format uses BigInt internally which is converterd to Number. Could this become an issue somewhen in the future?

Documentation of the Charge Transparency Records (CTR) Format

Document all the PTB relevant features of the Charge Transparency Records (CTR) Format.

Add support for Mennekes transparency format

Some customers want to use Chargy for Mennekes charging stations

• Documentation of the Mennekes "metra"-XML received
• Support Mennekes transport via metra XML
• Support Mennekes transport via chargeIT JSON container
• Parse and display Mennekes transparency data
• Verify Mennekes signatures

Add support for the SAFE XML and Open Charge Metering Format (OCMF)

Some customers want to use Chargy for charging stations using the OCMF v1.0 format

• Support OCMF transport via chargeIT JSON container
• Support OCMF transport via SAFE XML container
• Parse and display OCMF transparency data
• Verify OCMF signatures

Additional meta data for SAFE XML

Add Chargy's additional meta data, e.g. geo coordinates of the EVSE, to the SAFE XML using an OCC namespace.

Publication within the Ubuntu Software-Center or Debian Repository

Show Software Identification

The PTB wants that the software version and its hash value, as printed on the "Baumusterprüfbescheinigung" is shown in the software.

Add "Chargy Transparenz Software" to favorite app on Linux Live CD (Ubuntu with Gnome desktop)

gsettings get org.gnome.shell favorite-apps
['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 'chargytransparenzsoftware.desktop']

Extend measurement verification interface...

Extend measurement verification interface to allow results like: (In)ValidStartValue, (In)ValidIntermediateValue, (In)ValidStopValue and StartValue, IntermediateValue, StopValue (without any verification at all) as this is assumed to be more userfriendly

Reimplement EMH to support additional EC curves

Support not only secp192r1, but also secp256r1, secp384r1 and secp521r1 for the EMH EDL40++ format.

A broken file within a list of files is ignored

When multiple transparency files are load but some of them are broken (invalid transparency format) then those files are ignored and not shown. VDE would like to get an error message instead.

Expected behavior

Add an item "$filename: Invalid transparency format" to the list of loaded charging sessions.

Add a "update available"-notification mechanism

• Add a "update available"-notification mechanism to notify the user that a new version of the software is available.

• Show a little red icon when the current version of the software is out of date

• Do not install anything automagically, as PTB is not a fan of this (at the moment)

• Use GitHub for serving the version file, as we do not have access to any logfiles (privacy)

PTB whats the TS to calculate and show the differences of time, consumption, ...

PTB whats that the TS calculates and shows the differences of time, consumption, ...

Allow compressed archives as input files and merge their content

I would like to request/propose a feature

Chargepoint charge transparency records are TAR archives compressed via BZIP2. Allow at least BZIP2, GZIP, ZIP files as input. Extract and merge the content of those compressed archives.

A user should also be able to put several charge transparency records/files (and public key files) into a single TAR/ZIP archive and open this file directly.

Chargy should also support archive files within other archive files, as e.g. Chargepoint charge transparency files are tar.bz2-archives and users might want to combine multiple into a single ZIP-archive.

The electron.asar file no longer exists.

Version 7.0.0 of electron remarks: "The electron.asar file no longer exists. Any packaging scripts that depend on its existence should be updated. #18577"
https://github.com/electron/electron/releases/tag/v7.0.0
electron/electron#18577

This file is used to calculate the application hash value, a PTB feature.

Good and bad examples for charge transparency records

Create and update the list good and bad examples for charge transparency records

1. For test cases
2. Showing different (optional) features

Implement legacy TRuDI-style software-crypto-selfcheck

The PTB want a TRuDI-style self check of "all" files. This means to enumerate all files, calculate the SHA256 hash over all those files, calculate a common hash value and compare it with the stored value. If both are the same the software was not modified.

Strictly speaking this is an obsolete security feature. To make if at least a bit useful we additionally will sign the common hash value with the GraphDefined/OCC private key and verify this signatures via its public key.

Add support for chargepoint charge transparency records

Chargepoint sent a first specification of their approach to the German Eichrecht, which uses charging stations crypto keys instead of smart meter crypto keys. This requires some changes within the internal data processing.

• Support the chargepoint charge transparency record format
• Support of secp224k1 signatures
• Support of secp256r1 signatures