Skip to content

Streamlined Monitoring of Multiple Lines

Latest
Latest
Compare
Choose a tag to compare
@fermartv fermartv released this 04 Jul 21:14
· 1 commit to master since this release
2.0.0
f394609
This commit was created on GitHub.com and signed with GitHub鈥檚 verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

馃ぉ NEW FEATURES 馃ぉ

  • Multiple lines for a single stop are now supported. This allows for a more efficient use of the API and server resources when monitoring several lines for a single stop.
  • Additional information has been added to attributes, such as service start and end time, stop name and address, and many more.
  • Overall code and tests have been improved.

鈿狅笍 BREAKING CHANGES 鈿狅笍
If you were using previous versions of this component, please make the following changes:

  • The name parameter in the config is no longer supported. It should be removed as the sensors will now be named automatically.
  • The line parameter is now called lines and should be provided as a list of lines. You can either remove it to get a sensor for each line that goes through that bus stop or include a list of lines that you wish to monitor.
  • The stop parameter now expects an integer value.

If your previous configuration looked like this:

sensor:
  - platform: emt_madrid
    email: !secret EMT_EMAIL
    password: !secret EMT_PASSWORD
    stop: "72"
    line: "27"
    name: "Bus 27 en Cibeles"
    icon: "mdi:fountain"

  - platform: emt_madrid
    email: !secret EMT_EMAIL
    password: !secret EMT_PASSWORD
    stop: "72"
    line: "N26"
    name: "Bus N26 en Cibeles"
    icon: "mdi:fountain"

You should change it to this:

sensor:
  - platform: emt_madrid
    email: !secret EMT_EMAIL
    password: !secret EMT_PASSWORD
    stop: 72
    lines: 
      -  "27"
      -  "N26"
    icon: "mdi:fountain"

馃敡 HOW TO UPDATE 馃敡
To update to the latest version, please follow the steps below:

  1. Download and extract the Source code (zip) file located below these release notes.
  2. Using your preferred tool, open the directory for your Home Assistant configuration, where you can find the configuration.yaml file.
  3. If you don't already have a custom_components directory in your configuration directory, create one.
  4. Within the custom_components directory, create a new directory named emt_madrid.
  5. Download and save all the files from the custom_components/emt_madrid/ directory in the downloaded Source code.
  6. Place the downloaded files into the newly created emt_madrid directory.
  7. Restart Home Assistant to apply the changes.
  8. Update your configuration as indicated above.
Assets 2