Skip to content

fermartv/emt_madrid

Repository files navigation

Please ⭐ this repo if you find it useful

EMT Madrid bus platform for Home Assistant

This is a custom sensor for Home Assistant that allows you to have the waiting time for a specific Madrid-EMT bus stop. Each sensor will provide the arrival time for the next 2 buses of the line specified in the configuration.

Thanks to EMT Madrid MobilityLabs for providing the data and documentation.

Example Example attributes

Prerequisites

To use the EMT Mobilitylabs API you need to register in their website. You have to provide a valid email account and a password that will be used to configure the sensor. Once you are registered you will receive a confirmation email to activate your account. It will not work until you have completed all the steps.

Manual Installation

  1. Using the tool of choice open the directory for your HA configuration (where you find configuration.yaml).

  2. If you do not have a custom_components directory there, you need to create it.

  3. In the custom_components directory create a new directory called emt_madrid.

  4. Download all the files from the custom_components/emt_madrid/ directory in this repository.

  5. Place the files you downloaded in the new directory you created.

  6. Restart Home Assistant

  7. Add emt_madrid sensor to your configuration.yaml file:

    # Example configuration.yaml entry
    sensor:
      - platform: emt_madrid
        email: !secret EMT_EMAIL
        password: !secret EMT_PASSWORD
        stop: 72
        lines: 
          - "27"
          - "N26"
        icon: "mdi:fountain"

Configuration Variables

email:
(string) (Required)
Email account used to register in the EMT Madrid API.

password:
(string) (Required)
Password used to register in the EMT Madrid API.

stop:
(integer) (Required)
Bus stop ID.

lines:
(list) (Optional)
One or more line numbers.

icon:
(string) (Optional)
Icon to use in the frontend. Default value: "mdi:bus"

Sensors, status and attributes

Once you have the platform up and running, you will have one sensor per line specified. If no lines were provided, it'll create a sensor for each line in that stop ID. The name of the sensor will be automaticalle generated using the following structure: Bus {line} - {stop_name}.All the sensors will update the data automatically every minute and you should have the following data:

state:
(int)
Arrival time in minutes for the next bus. It will show "unknown" when there are no more buses coming and 45 when the arrival time is over 45 minutes.

Attributes

next_bus:
(int)
Arrival time in minutes for the second bus. It will show "unknown" when there are no more buses coming and 45 when the arrival time is over 45 minutes.

stop_id:
(int)
Bus stop ID given in the configuration.

stop_name:
(int)
Bus stop name from EMT.

stop_address:
(int)
Bus stop address from EMT.

line:
(int)
Bus line.

destination:
(int)
Bus line last stop.

origin:
(int)
Bus line first stop.

start_time:
(int)
Time at which the first bus leaves the first stop.

end_time:
(int)
Time at which the last bus leaves the first stop.

max_frequency:
(int)
Maximum frequency for this line.

min_frequency:
(int)
Minimum frequency for this line.

distance:
(int)
Distance (in metres) from the next bus to the stop.

Second bus sensor

If you want to have a specific sensor to show the arrival time for the second bus, you can add the following lines to your configuration.yaml file below the emt_madrid bus sensor. See the official Home Assistant template sensor for more information.

# Example configuration.yaml entry
template:
  - sensor:
      - name: "Siguiente bus 27"
        unit_of_measurement: "min"
        state: "{{ state_attr('sensor.bus_27_cibeles_casa_de_america', 'next_bus') }}"

Roadmap

  1. Move to fully async component.
  2. Add unique_id to allow modifying sensor names.