3

Utilize Data from Electrify America's Network Status Page

  • Live

K
K.W.

Please incorporate the data that EA posts publicly on their Network Status page: cloud.email.electrifyamerica.com/network-and-planned-maintenance

I realize EA does not make this data convenient to access via API. However, I really would like to see ABRP scrape the publicly-available EA network status page so that ABRP can avoid routing to chargers that are totally 100% offline as posted by EA.

Example: ABRP is currently routing to an EA charger in Flagler, CO which is totally offline for upgrades. This information is publicly posted on EA's Network Status page and should be incorporated by ABRP.

From EA's Network Status page:
Upcoming Station Upgrade: Unavailable beginning on the following date while legacy hardware is upgraded to the newest generation of chargers.
July 24, 2024
I-70 Diner (Station 100158) at 17044 CR-5, Flagler, Colorado 80815

Ideally, ABRP would scrape the EA network status page and and then mark the station as temporarily unavailable or something and (most importantly) not route people there. Once the location is removed from the EA network status page, ABRP can resume routing people to that station.

Currently, if I didn't check EA's Network Status page before going on this hypothetical trip and instead just trusted ABRP's routing, I would arrive with 10% SoC to this totally offline EA station. I would be totally stranded, as the nearest other DCFC is in Limon, CO - 35 miles away.

A

Activity Newest / Oldest

D

dlu

It would also be *very* nice to have a "out of service charger" feature in ABRP -- what I would like to see is a way to mark a charger (either an individual charger or the whole station) as out of service when you get there and discover that you can't charge. This information could be propagated in real-time so that other folks would be able to route around it. One way to do this would be to push out a "charger status update" so that there would be a warning that anyone navigating to the charger could see.

Since there is a potential security risk in allowing this (stations could be maliciously marked as down) it would be important to require some authentication when accepting an out of service update (so that a bad actor could potentially be held accountable) and it would also be wise to have the update trigger a message to the station operator to tell them that you received a out of service message. Part of "authenticating" down station messages could be to require that the app reporting actually be at the station -- or at the very least to have navigated to the station very recently.


Avatar

Bo_ABRP

Status changed to: Live

Avatar

Bo_ABRP

This is great input, thank you! We have deployed parsing of this data so that ABRP now shows the stations which are claimed (by EA) to be unavailable as such.
Please let us know how this works in practice - is the EA page correct?


  • Avatar
  • D