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
Describe the bug
If I set up a sensor and "include tomorrow", it shows the next departure the day after as state, even if there are still many the same day. Only the day is wrong, the hour is correct. The data in the attributes (next_...) seem however correct.
If I set up the same sensor without including tomorrow, it's all correct (but at the end of the day, I don't have the next departure the day after then...)
Steps/data to reproduce the behavior, e.g.
url to the zip file: public transport (bus/tram) in Belgium's Walloon Region.
route_route_id: B0031-18821
origin_station_stop_id: Bottbru2
return
Release used
gtfs2 release 0.3.6, HA type: HAOS
Additional
From dev tools, faulty one (with include tomorrow):
It seems fixed, thanks for the swift reaction! I'll come back after today's last bus if the next one of tomorrow does not show as expected (but from the attributes, it already seems OK).
Thanks again for the quick and effective fix!
Describe the bug
If I set up a sensor and "include tomorrow", it shows the next departure the day after as state, even if there are still many the same day. Only the day is wrong, the hour is correct. The data in the attributes (
next_...
) seem however correct.If I set up the same sensor without including tomorrow, it's all correct (but at the end of the day, I don't have the next departure the day after then...)
Steps/data to reproduce the behavior, e.g.
Release used
gtfs2 release 0.3.6, HA type: HAOS
Additional
From dev tools, faulty one (with include tomorrow):
Correct one:
The text was updated successfully, but these errors were encountered: