Vlaams Verkeerscentrum Integration 🇧🇪

Share your Projects! Custom Integrations
, , ,
1

Hi all! :wave:

I’ve developed a new integration: the Vlaams Verkeerscentrum Integration :belgium:

This integration provides real-time travel time sensors for specific routes in Belgium, using data from the Vlaams Verkeerscentrum platform (verkeerscentrum.be). It pulls travel times from their website, enabling you to monitor traffic conditions and plan your trips more efficiently.

Key Features:

  • Real-time Travel Times: Stay updated with travel times for your predefined routes.
  • Customizable Trajectories: Easily configure which routes you want to monitor.
  • Alerts and Automations: Use Home Assistant’s features to get notifications about delays or travel changes.

Feedback, suggestions, and ideas for improvements are welcome!

You can check out the repository here: GitHub - studiojw/vlaams-verkeerscentrum-ha: This integration for Home Assistant provides real-time travel time sensors for specific trajectories in Flanders, Belgium, as defined on the Vlaams Verkeerscentrum platform.

2 Likes
2

Awesome, was looking for this since a while.

Is it just me, or do you also regularly see ‘unknown’ as travel time? A few minutes later it shows a time again. I suppose it may have something to do with the polling interval.

3

Hi Michel,

I don’t have this issue. How does your chart looks like on the History page? Do you see any gaps?

Feel free to share the trajectory, I can monitor it for a few days to see if I encounter the same problem.

4

Hello,

I reinstalled the integration and the problem seems to be fixed!

5

Nope, problem returned. It seems as if it displays ‘unknown’ when there’s heavy traffic. Perhaps the api is throttled?

Route Antwerp-Lummen

6

Hi! Thanks for flagging this.

I did some digging, and it seems the Vlaams Verkeerscentrum website itself has been acting up. For instance, when I check my personal trajectories, I sometimes see routes that aren’t mine at all. After refreshing, they eventually show the correct ones. Since the integration pulls data directly from this page, these issues likely explain why you’re seeing ‘unknown’ travel times. Unfortunately, until Vlaams Verkeerscentrum fixes this on their end, there’s not much we can do to stabilize it within the integration.