The 22,10€ comes from the entry exit matrix Italy_NorthWest:
This price is correct if you drive through another (way longer) route that does not go through any other toll booths.
In the same matrix, there would be the combinations for the subtrip #1:
And for the subtrip #3:
So I guess now you’re computing the price by taking the first and the last segment that belongs to a price matrix and retrieving the price, but that’s not correct. Ain - Aout - … other toll-free segments … - Bin - Bout <- Your computed price: Ain to Bout
You need to scan all segments of the route and sum all different subsection.
Ain - Aout - … other toll-free segments … - Bin - Bout <- The right price: Ain to Aout + Bin to Bout
Not having anything better to do, for celebrating the 1st birthday of this bug, I’ve checked and fixed all the broken toll-segments we had in Italy and thoroughly checked this route again (now, due to a closure, the route goes through the Toll-free highway A50, but the wrong Waze-computed price, of course, does not change).
Now I am 99,9% confident this is not a configuration error but an actual bug.
The boring Data for Nerds
serverUniqueId: “m4207711124845261017”
There are 2 possible toll routes, one through the A4 (6,90€) and one through the new A35 (11,20€). The price of the A35 is about twice the price of the A4.
When driving through the A35, you get two “barriers” (toll-booths) to pay (A4 Castegnato and A35 Chiari Est).
Waze prices:
Through A4: 6,90€ (correct)
Through A35: 6,90€ (wrong, should be 11,20€, 4,30€ off).
You sure? I am still seeing it on RBS. I still get a cash price from Clearville to Albrightsville, PA of $56.10, the same one I mentioned in Discord. If the bug were fixed, it would show $24.40.