For my own use case I needed to extent the functionality a bit.
And I thought maybe those changes could be beneficial to the community.
I'm not quite sure if the config flow would need some sort of migration or if the defaults do suffice for that.
Any insight here would be greatly appreciated as this is my first work in the hassio ecosystem.
Currently the filter only apply to the data set and are not passed on to the actual "api" call as this is currently not supported.
But I assume the backend library needs a refresh in the future anyway as the DBahn is currently showing a warning to switch over to the new design, and therefore indirectly announces to discontinue this service.
Proposed Changes
Allow connections list to be filtered by product
I need to exclude ICE's from my filter list as those may not be covered by my ticket.
Set a maximum connection count to be available to a sensor
To limit the data amount in the sensor. I'm not quite sure if this is currently a real concern, but may be for the internal caching.
Allow to access connections list in sensor
I like to display a bit more data than only the next two departures.
FaserF
commented
7 months ago
Hello @FaserF
thanks for your integration!
For my own use case I needed to extent the functionality a bit. And I thought maybe those changes could be beneficial to the community.
I'm not quite sure if the config flow would need some sort of migration or if the defaults do suffice for that. Any insight here would be greatly appreciated as this is my first work in the hassio ecosystem.
Currently the filter only apply to the data set and are not passed on to the actual "api" call as this is currently not supported. But I assume the backend library needs a refresh in the future anyway as the DBahn is currently showing a warning to switch over to the new design, and therefore indirectly announces to discontinue this service.
Proposed Changes
Related Issues
resolves FaserF/ha-deutschebahn#12