I like the new consumption report (charging robot individual) directly out of the Easee app.
All charging sessions are displayed, but the report misses the important column of the used Easee Key for each charging session.
Could you add this column to the report?
It would be helpful to know who did the charging session.
Additionally, it would be absolutely amazing to have the possibility to choose in the Easee App, which type of report is requested for. So the same possible selections, that are already available in the Easee Cloud. Reports per Easee Key, per Charger, etc.
Activity Newest / Oldest
So what is the timeline to implement the column of the specific easee key that was used for the individual charging session in the report that is created within the app?
The original request was created almost exactly a year ago and is now in status "planned" for several months.
When can I see this rather small adjustment appearing on my app experience?
Is it also planned to implement the same report types within the app, that are already available in the cloud for more than a year?
Can you provide an update on this feature, as it is needed for me too as we use the chargers at our offices and our accountant says we need to monitor use so we can calculate the “benefit” tax and enforce a fair use policy. I can’t be the only person who needs this.
When you filter your Consumption by Easee Key(s), the resultant PDF report generated, will only include those selected keys' consumption.
The Easee Key filtering option can be enabled if you click the Filter icon button right below the document icon button.
This will obviously be for the selected Charger only.
We might soon open up for similar consumption functionality at the Charge site level (meaning the same thing would be possible, but for all chargers on the Charge site).
Would it be possible to adjust the permission levels so that Admin users can filter all Easee Keys? Right now, I can only see my own key, which makes filtering almost pointless.
It would be great to have the possibility to create the same categories of reports as via easee.cloud (on a Site-Level). Then there would also be the possibility to create reports that contain the so important Easee Keys and allow the easy calculation of the individual user consumption.
Not sure I fully understand why you would need to see someone else's keys to do this.
Would it not be sufficient to be able to filter or break it down by user instead?
If I want to create a report of the consumption of this user and send it to the user to process payments, etc., then I need to be able to filter for all users.
Why else would I need permission levels? Admin should see all users in my opinion.
If I filter by Key or by User is both fine for me, but maybe people have multiple Keys per User and need the filtering on Key level.
But again, this is all possible on the cloud site, so why not offer the same functionality in the app.
Yeah, i totally agree, I'm just wondering what would be better.
How do you know which keys belong to which user?
Well I can't speak for everyone, but my Easee Key ist just called "Fabian". If people use multiple keys, they could call them "Fabian - Work" or "Fabian - Private".
I think this would not be a problem, as Users can name the Keys how they like.
Any updates on this topic?
At least the app now supports filtering for easee keys, but still no implementation in the reports or possibility to create the same categories of reports as via easee.cloud
Also the filtering in the app only shows easee keys of the user of the app, not all easee keys, even for me as admin. If I only see my key, filtering is almost pointless.
Should also be quick and easy to implement - Why no implementation yet?
We just got our second EV today. So this is something really important to be added. We also would like to add a 3 key when a friend comes and visit. So that he can charge and we still know which consumption belog to which car. 👍🏻
Thank you for your input. This is already in our plans and should hopefully be released within the next three months :)
Status changed to: Planned