Multiple operators at same charge point
Some times, there are multiple operators at the same address.
For example, at the resting areas "Karlslunde Vest 1" and "Karlslunde Øst 1" in Karlslunde, Denmark, only E.ON charging stations are registered.
Since my charges at those areas gets tagged automatically with the E.ON chargers, I get "NaN" as price for those.
On both addresses, there are super chargers from "Ultra-Fast Charging Venture Scandinavia", but I can't add those manually.
Suggestion:
- Make it possible to add extra operators at same charge point
- If multiple operators are registered at same point, make it possible to switch between operators in charging details
-
The same issue now goes for both Clever and E.ON chargers on addresses "Servicevej 1, 4600 Køge" and "Servicevej 2, 4600 Køge".
There's also a Tesla SuC very close to these addresses - I can't charge there, so don't know if that one has the same issue.
0 -
I don't really understand the problem?
Why don't you just change the charging operator afterwards, if you charged using a different Operator than what Tronity has (wrongly) assumed and attached to the charge?0 -
@Olaf
There's a difference between Charge Point and Charge Rate. The Charge Rate I use supports charging at one charge operator (Charge Point). Often, there are 2 or more charging operators very close to each other.
When the wrong one is anticipated by Tronity based on GPS, it's currently not possible to change it.
I can change Charge Rate, but that would not reflect what actually happened and make it impossible to check with my charge bills.
My above example - I charged on a Clever stall with my Clever subscription. The Charging Rate is only set up for the Clever network charging on the Clever rate. Meaning that when Tronity thinks I charged on E.ON, it shows "NaN" as price - and also, it doesn't reflect reality.
0 -
Ok, I get it now. Thanks for the additional information.
If Tronity assumes the wrong operater AND you can't change it afterwards, this is a major flaw. I therefore just upvoted this feature to support its development.0
Please sign in to leave a comment.
Comments
4 comments