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
When using multiple departure sensors in a single card, how can I determine which sensor each departure belongs to? It seems that show_entity_name becomes disabled. However, show_entity_name (or show_sensor_name) would be useful when using multiple sensors. Just thinking out loud—there's probably a good reason why show_entity_name is disabled.
I'm thinking maby put the name for each group in front of each departure name.
The text was updated successfully, but these errors were encountered:
The reason why the show_entity_name is disabled in multi-entity mode is to get a consistent "timetable-like feeling" where all the departures are sorted by the expected time.
@fl0om, please describe your use case for displaying each sensor's name in one timetable.
I'm sorry, I thought this was the purpopse of multi entity mode. If not, then I'm not sure how to use it. I want a timetible-like feeling, but it get confusing when I can not see the name of each entity. I will use separate cards for each entity instead.
I am also experiencing the same problem. The recent update to the card seems to have lost the line graphic in the output table. This post shows the problem with pictures.
The recent update to HA-LondonTfL v0.4.8 integration has fixed the above problem for me, Bus numbers and DLR platforms are now showing in the card dashboard.
When using multiple departure sensors in a single card, how can I determine which sensor each departure belongs to? It seems that show_entity_name becomes disabled. However, show_entity_name (or show_sensor_name) would be useful when using multiple sensors. Just thinking out loud—there's probably a good reason why show_entity_name is disabled.
I'm thinking maby put the name for each group in front of each departure name.
The text was updated successfully, but these errors were encountered: