BVG Public Transport Sensor for Berlin

Kraken · February 20, 2019, 9:28am

Hi,

I’ve created a custom component to display realtime departure times for stations within the BVG route network (including S-Bahn data). The component displays the time in minutes until the next departure, including delays. You can define a walking distance, so only departures that are “reachable” by you in a timely manner are displayed.

The component along with detailed instructions can be downloaded from here:

# Example configuration.yaml entry

sensor:
  - platform: bvgsensor
    name: U2 Rosa-Luxemburg-Platz
    stop_id: "900000100016"
    direction: "Pankow"
    walking_distance: 5

There is no custom component for the Berlin public transport up till now and I had same spare, time so I decided to create one.

Update: released version 0.3.5

you can now specify multiple directions, e.g. if your route is served by multiple lines with different directions
the component is now time zone aware (using the time zone from your HA config)
optimized logging
various bugfixes

Greetings from under the sea
Kraken

Aluavin · February 20, 2019, 11:04am

Very good idea. Will try on weekend. If you want a feature request: use vbb-hafas instead of “just” bvg since this one will get the data of sbahn and bvg in berlin.

Kraken · February 20, 2019, 12:01pm

thanks, apreciate your feedback!
As for the feature request, the sbahn is included in the data-feed, so you may use it right away
Will update the description acordingly.

der_heinrich · February 23, 2019, 6:49am

I would like to add the sensor to my ha (version 0.88). But it does not recognize the sensor?
I placed bvgsensor.py in /home/homeassistant/.homeassistant/config/custom_components/bvgsensor.py, changed permissions to homeassistant.homeassistant
My configuration.yaml:

platform: bvgsensor
name: Abfahrt Richtung Hackescher Markt
stop_id: “900000162001”
direction: “S Hackescher Markt”
walking_distance: 14
file_path: “/tmp/”

Any idea? Thanks for you help!
Heinrich

Kraken · February 23, 2019, 9:21am

It looks like the path for the custom_component is wrong. You would need to add the sensor folder…
the whole path would look something like this: ...../YOUR_CONFIG_PATH/custom_components/sensor/bvgsensor.py

let me know if that worked for you.

der_heinrich · February 24, 2019, 1:16pm

I adjust the path for the sensor file.
It is an ubuntu-server installation with the virtual environment --> https://www.home-assistant.io/docs/installation/raspberry-pi/

So my config path should be --> /home/homeassistant/.homeassistant

Now I got only warnings in the log-file:

2019-02-24 14:02:43 WARNING (SyncWorker_3) [custom_components.sensor.bvgsensor] No valid connection found. Please check your configuration.

2019-02-24 14:02:04 WARNING (SyncWorker_1) [homeassistant.loader] Integrations need to be in their own folder. Change sensor/bvgsensor.py to bvgsensor/sensor.py. This will stop working soon.

Now I added your example-config with rosa-luxemburg - but still not working.

Kraken · February 25, 2019, 5:24pm

I’ve just checked your configuration and your configured stop_id (900000162001) is “S Karlshorst” and from what I saw in the data feed there is no connection with an final destination to “S Hackescher Markt” …
If you want the departure times for the S3, please specify the final destination which would be “S Spandau”.

You can also specify multiple destinations if there is more than one connection you could use…

Hope that helps to get it working

Kraken · February 25, 2019, 5:26pm

The paths for custom components have changed with the Version 0.88.0, and can be ignored at the moment.

Kraken · February 25, 2019, 6:03pm

Update: while testing your config, I’ve found an issue regarding encoding. I will take a look and provide an updated version soon.

Kraken · February 28, 2019, 10:48am

hi @der_heinrich, i have just updated the code on github (v0.3.0). Please try the updated version and let me know if the problem still exists. I’ve tested it with the configuration below.

  - platform: bvgsensor
    name: Hackescher Markt
    stop_id: "900000162001"
    direction: "Spandau"
    walking_distance: 17
    file_path: "/tmp/"

der_heinrich · March 1, 2019, 10:12am

hi @Kraken,
it works now! thanks a lot!

Kraken · March 16, 2019, 8:59am

Updated to version 0.3.5:
you can now specify multiple directions, e.g. if your route is served by multiple lines with different directions

- platform: bvgsensor
    stop_id: your stop id
    direction: 
      - "destination 1"
      - "destination 2"

josef · March 16, 2019, 10:49am

Great component! When are you planning to migrate the component to HA > 0.89 because I really like to integrate it within my current setup.

Kraken · March 16, 2019, 1:10pm

I hope to find some time today

Kraken · March 16, 2019, 1:52pm

Fortunately it is pretty simple to get it up and running with 0.89 and beyond. Simply create a folder named bvgsensor within your custom_component folder and rename the file bvgsensor.py to sensor.py

.../conf/custom_components/bvgsensor/sensor.py

aschobba · December 8, 2019, 6:42pm

I’am getting following error… is the Integration still working?

Platform error sensor.bvgsensor - Integration ‘bvgsensor’ not found.

I used the instructions from github but with no luck.
filepath:
/config/custom_components/bvgsensor/sensor.py

Aluavin · December 31, 2019, 12:42pm

Had the same problem. easy to fix.
first restart the server without the sensor, but with the component, than after restart add the sensor => success

aschobba · January 1, 2020, 12:15pm

You mean copy the custom component to the folder restart and than add the sensor?
Or should I add something additional to the configuration.yaml to load the custom component?

Aleklu · January 16, 2020, 12:21pm

Im running into a similar problem: I have the sensor.py in the correct folder, “config\custom_components\bvgsensor\sensor.py”. Rights are set correctly as well. After restarting Hass.io I add

sensor:
  - platform: fritzbox_netmonitor
  - platform: bvgsensor
    stop_id: "900000162001"
    direction: "Spandau"

as the minimal configuration in my configuration.yaml. And then I run into “Platform error sensor.bvgsensor - Integration ‘bvgsensor’ not found.”

How can I tell the system that there is a new integration available? Do I need to add something under “discovery:” in my configuration.yaml?

Any pointers are very much appreciated!

saeris · January 30, 2020, 5:31pm

I tried investigating the issue but sadly didn’t figure it out.
Some of the things I tried:

create a manifest.json and __init__.py files as those seem to be needed by HA
add DOMAIN and DEFAULT_NAME
put the code into __init__.py to see if that changes anything
a few other small changes (like I noticed the add_entities was referencing Bvgsensor with a capital B and try small caps)

I didn’t make a github fork but here are the files I toyed around with… maybe someone else can see the light https://file.io/dpg5ju