Skip to content
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

Open
mr-p666 opened this issue Dec 9, 2024 · 6 comments
Open

Only the next departure per stop is displayed as a sensor #1

mr-p666 opened this issue Dec 9, 2024 · 6 comments
Assignees

Comments

@mr-p666
Copy link

mr-p666 commented Dec 9, 2024

I've configured two stops and wanted to receive three departures for each.
image

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.
image
image

@jozefKruszynski
Copy link
Owner

Hadn't seen this until now.
There will only ever be a single next departure shown as the sensor, the list of departures is only in the attributes.
The screenshot I have actually shows 4 separate "line headsigns combinations" so to speak.
Although they are all from a single stop that stop has 2 different lines the 26 and the 25 and each of those has 2 possible "headsigns".
This is the intended behaviour

@mr-p666
Copy link
Author

mr-p666 commented Dec 23, 2024

Ah, all right. Thanks for the clarification. I didn't realize it.
But then it would be great to see all selected departures as their own sensor and not just as an attribute, so you don't have to create multiple template sensors to extract the desired information from them.

@jozefKruszynski
Copy link
Owner

jozefKruszynski commented Dec 23, 2024

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.
Maybe I'll add it as an optional feature to create a sensor for each.

@mr-p666
Copy link
Author

mr-p666 commented Dec 23, 2024

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.
How about making it configurable as a checkbox below the RBL list? 😉

@jozefKruszynski
Copy link
Owner

How about making it configurable as a checkbox below the RBL 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.

@jozefKruszynski
Copy link
Owner

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 😉

@jozefKruszynski jozefKruszynski self-assigned this Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants