https://github.com/amaximus/bkk-stop-card
Custom Lovelace card for Budapest Public Transportation custom component
https://github.com/amaximus/bkk-stop-card
bkk budapest homeassistant hungary lovelace-custom-card lovelace-ui transportation
Last synced: 6 months ago
JSON representation
Custom Lovelace card for Budapest Public Transportation custom component
- Host: GitHub
- URL: https://github.com/amaximus/bkk-stop-card
- Owner: amaximus
- Created: 2019-08-01T16:04:26.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2024-11-24T11:59:11.000Z (6 months ago)
- Last Synced: 2024-11-24T12:28:57.006Z (6 months ago)
- Topics: bkk, budapest, homeassistant, hungary, lovelace-custom-card, lovelace-ui, transportation
- Language: JavaScript
- Homepage:
- Size: 183 KB
- Stars: 13
- Watchers: 4
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
[](https://github.com/hacs/integration)
# Lovelace custom card for BKK Stop Information
This Lovelace custom card displays Budapest Public Transportation (BKK)
line information departing in the near future from a configurable stop.
This custom card depends on the BKK Stop Information custom component that you may find at
[https://github.com/amaximus/bkk_stop](https://github.com/amaximus/bkk_stop/).
Lovelace UI does not support platform attributes natively.
Inspired by [entity-attributes-card](https://github.com/custom-cards/entity-attributes-card)
on handling attributes in Lovelace, a Lovelace custom card was a dept and now made available for BKK Stop.
#### Installation
The easiest way to install it is through [HACS (Home Assistant Community Store)](https://github.com/hacs/frontend),
search for bkk and select BKK Stop Card from Plugins.
If you are not using HACS, you may download bkk-stop-card.js and put it into $homeassistant_config_dir/www.
#### Lovelace UI configuration
Configuration parameters:
---
| Name | Optional | `Default` | Description |
| :---- | :---- | :------- | :----------- |
| entity | **N** | - | name of the sensor of bkk_stop platform|
| hide_in_mins | **Y** | `false` | Hide in_minutes information|
| hide_at_time | **Y** | `true` | Hide at_time information|
| hide_predicted_at_time | **Y** | `true` | If set to false, this will show predicted times with an '(est.)' suffix, when estimated arrival times are available, otherwise it will show the time according to schedule |
| max_items | **Y** | `0` | Number of items to show. 0: no limit |
| name | **Y** | `` | If specified it will overwrite the card title/station name |
| layout_bpgo | **Y** | `false` | Use Budapest GO layout |
---
For yaml mode Lovelace dashboard add the lines below to your ui-lovelace.yaml. For non-yaml dashboard use: overview → edit dashboard → 3 dot again → raw edit and add the card info there.
The entity should be the sensor of bkk_stop platform you defined.
```
resources:
- {type: module, url: '/www/community/bkk-stop-card/bkk-stop-card.js'}
cards:
- type: custom:bkk-stop-card
entity: sensor.bkk7u
hide_in_mins: false # it makes sense to set this to false if hide_predicted_at_time is true, as in_mins is calculated from "scheduled" times
hide_at_time: false
hide_predicted_at_time: true
- type: custom:bkk-stop-card
entity: sensor.bkkxu
hide_in_mins: true
hide_at_time: true
hide_predicted_at_time: false
```
Lovelace UI:
