Entities#
Below is the list of entities that will be created with each instance of the integration.
Next Bus#
sensor.first_bus_<<NAME_OF_SENSOR>>_next_bus
This will provide the number of minutes until one of the specified buses (or any if no specific buses were specified) reach the bus stop. If there is no known next bus, then none
/unknown
will be returned.
The sensor will pull the latest times for the stop every 5 minutes. This is done so that the unofficial API isn't hammered and support is taken away, and I felt 5 minutes was long enough so that information wasn't too stale. This means that there is a chance that the time won't reflect the times on the app/website if they are updated within this 5 minute timeframe.
The following attributes are available in addition
Attribute | Type | Notes |
---|---|---|
service_ref |
string |
The internal reference for the service |
service_number |
string |
The name/number of the next bus |
destination |
string |
The destination of the next bus |
due |
datetime |
The timestamp of when the next bus is due |
is_live |
boolean |
Determines if the bus is being tracked (true ) or is from the timetable (false ) |
stop |
string |
The ATCO code of the bus stop that is being tracked |
buses |
list |
The collection of known upcoming buses for the stop, filtered to the selected buses if configured. |
data_last_updated |
datetime |
The timestamp when the underlying data was last updated |
For each bus in buses
, you can find the following attributes
Attribute | Type | Notes |
---|---|---|
service_ref |
string |
The internal reference for the service |
service_number |
string |
The name/number of the next bus |
destination |
string |
The destination of the next bus |
due |
datetime |
The timestamp of when the next bus is due |
is_live |
boolean |
Determines if the bus is being tracked (true ) or is from the timetable (false ) |