-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show only direct connections #19
Comments
Maybe I spoke too fast: OpendataCH/Transport#216 |
So yeah, according to the reply in the ticket above the There's still the chance to keep the parameter in the library and do the filtering at this stage to kind of simulate the missing functionality in the API. Would you be willing to review a patch to do so? |
Ping @miaucl |
Hey guys, as you might know, it takes some time to integrate into HA and as it was a old integration, the focus lies first on clean up before new features are considered. But yes, this is already on my radar 👍 |
Great, if I can help somehow here I am. I'm specially interested in being able to filter out non-direct connections, preferably at HA level. I've seen a patch of yours has been recently merged in HA to have separate entities per departure. If each |
Hi,
Sorry for posting here stuff about the HA integration but I thought it'd be faster to reach you :)
Would it be feasible to patch the HA integration to configure a given connection to only show direct connections? This lib and the API seem to support it.
It does not seem complicated: maybe an extra
user_input
inconfig_flow
which would enable thedirect
parameter in theOpendataTransport
object. I don't have much experience touching the HA codebase but I can try.What do you think?
The text was updated successfully, but these errors were encountered: