-
Notifications
You must be signed in to change notification settings - Fork 2
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
Only the next departure per stop is displayed as a sensor #1
Comments
Hadn't seen this until now. |
Ah, all right. Thanks for the clarification. I didn't realize it. |
My goal with this integration was specifically to avoid having each departure as its own sensor. I wanted a single sensor with all departures as an list in an attribute. We'll see though, I understand why you would want a sensor for each. |
But creating multiple template sensors isn't great either. Sorry, but I don't see any benefit in having everything except the next departure in the attribute list. |
See my comment above yours. The benefit as I see it, is to avoid creating hundreds of sensors that are short lived and thrown away within a few minutes of being created. But as I said, I can see why you would want each as a new sensor. |
Having said all that, I guess it shouldn't be too difficult to create as many sensors for each stop as requested in the slider, and update all of these so that there are only ever 3 if you selected 3. I might reconsider the whole setup 🤣 This is why it's good to have other people's opinions 😉 |
I've configured two stops and wanted to receive three departures for each.
Unfortunately, unlike your screenshot, I only have one sensor with the next departure of each stop, while the list of selected departures is in the attribute list of the sensors.
The text was updated successfully, but these errors were encountered: