openchargingcloud / chargydesktopapp Goto Github PK
View Code? Open in Web Editor NEWThe Chargy E-Mobility Transparency Application for Windows, Mac OS X and Linux (based on Electron)
License: GNU Affero General Public License v3.0
The Chargy E-Mobility Transparency Application for Windows, Mac OS X and Linux (based on Electron)
License: GNU Affero General Public License v3.0
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']
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.
All charge transparency file names should have the extention .chargy
Open at least on Windows .chargy files via the Chargy Desktop App.
The regulators want to be able to see the software version of the...
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.
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)
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
EMP wants to attach tariffs and/or price infos signed with his private key.
Tariffs for charging, parking, reservation, ...
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, ...
Create and update the list good and bad examples for charge transparency records
The meter status information gives information about e.g. errors occured and the status of the internal clock.
Within the charge point data format the value "total_energy = 0.0" will be misinterpreted as a missing value (praise JavaScript magics!).
Use another method to validate if all mandatory parameters exist and are well defined.
Add Chargy's additional meta data, e.g. geo coordinates of the EVSE, to the SAFE XML using an OCC namespace.
Add socket type, max energy, ... to CTR data format and show it within the app (if present)...
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.
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:
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.
Add an item "$filename: Invalid transparency format" to the list of loaded charging sessions.
The installation path of the normal Windows version and the MSIX version are different.
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.
The PTB wants that the software version and its hash value, as printed on the "Baumusterprüfbescheinigung" is shown in the software.
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.
Some customers want to use Chargy for Mennekes charging stations
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.
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.
The PTB want us to disable the autostart of removable media within the Linux Live DVD
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.
Support not only secp192r1, but also secp256r1, secp384r1 and secp521r1 for the EMH EDL40++ format.
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"
Some customers want to use Chargy for ALFEN charging stations
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 !
PTB whats that the TS calculates and shows the differences of time, consumption, ...
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.
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.
Some customers want to use Chargy for charging stations using the OCMF v1.0 format
Document all the PTB relevant features of the Charge Transparency Records (CTR) Format.
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.
Simon wants a directory of test data
Show digital certificates of energy meter public keys, but do not verify them
Already implemented within the ChargyMobileApp.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.