You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wanted to start a Discussion with people who follow along to see what we should focus on next in terms of the long term requirements of the integration.
A couple of things on my wish list so far are:
An overhaul of the config_flow, can we integrate a more user friendly setup, can we do a similar style as TripView where we can select from a list (by suburb/route/stop) or via a map with station markers?
List stops by stopping order
add route number and sort by it for Trams and Bus services
Integrate Route Direction as part of the Service List
Add support to see all services from a stop/platform/direction (and optional to specific location), e.g. currently if I took a train from Parliament to Collingwood, there are two lines that go between those stops, and I want to integrate that into a single sensor rather then two different line sensors.
Combined multi stop/multi mode routes (for the purpose of being able to see a estimated arrival time to a known destination if you got this service)
The text was updated successfully, but these errors were encountered:
If we could somehow get disruptions into the integration, that would be great.
Yip sure thing, there is a pull request #25 by arunsudhakar so we should at least be able to get the disruptions pulled in, but I think we want to add some filters etc so you only get relevant disruptions
I have just installed this (after a it of a wait for a PTV key, of course) and it's great. I too would love to be able to get disruption info; it's a logical next feature because the timetable info can effectively be incorrect if you aren't made aware of a disruption.
If there's any way I can assist with testing or similar I will try!
Just wanted to start a Discussion with people who follow along to see what we should focus on next in terms of the long term requirements of the integration.
A couple of things on my wish list so far are:
The text was updated successfully, but these errors were encountered: