Connection issue with Enode

I recently signed up for the annual subscription because I was impressed by the features. I have a trip to Switzerland coming up in May, and I’d like to plan it carefully.

Today I took a test drive from Jena to Göttingen and back, and there were so many issues that made using the app in the car impossible.

1. The battery level wasn’t updated during route planning. I’m connected via eNode. The battery was at 28% during preliminary planning, but was charged to 95% before the trip. I couldn’t update the live status, nor could I manually enter the battery level. Even canceling the route didn’t work. It kept saying the route was not feasible. So I couldn’t even train the system on the way there and had to fall back on Google Maps again.

On the return trip, the Derive status actually worked again, and we drove from Göttingen to Jena. Here, the next problem arose along the way: the map was much slower than our actual progress. We had long since reached the Eschwege area, but on the map we were still halfway between Göttingen and Eschwege. There was no way to update it to our current location. In Eisenach, I took a break, and during that break, the location arrow moved on its own—maybe it would have caught up with me in 30 minutes.

Are these issues known? Are there any bug fixes? I have to go to Switzerland at the end of May and would really like to use ABRP because the battery indicator and SOC estimate were very accurate and would make planning charging stops much easier.

But with these issues, the app is completely unusable.