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
I tried to setup a sensor for this service but it always sets the direction in the outbound direction.
VLine service, Geelong - Melbourne line, Melbourne direction, From Wyndham Vale Railway Station.
It tells me that:
Created configuration for Geelong - Melbourne line to Geelong from Wyndham Vale Railway Station.
It doesn't matter if I choose the Melbourne or Geelong direction it will always create the sensors in the Geelong direction.
The actual sensors show the direction ID as 21, where it should be 0 for inbound.
The text was updated successfully, but these errors were encountered:
Can confirm, also having the same issue for Traralgon line (VLine). No matter the selection of the directional selection on the GUI it always generates sesnors for outbound travel towards Traralgon.
Similar to issue #18 ... there's something fishy going on with return values when they are 0. Maybe it's interpreting it as none?
In any case, I was able to fix this by changing line 117-119 in config_flow.py
from:
data_schema = vol.Schema({
vol.Required(CONF_DIRECTION, default=next(iter(self.directions))): vol.In(self.directions),
})
to:
data_schema = vol.Schema({
vol.Required(CONF_DIRECTION, default=0): vol.In(self.directions),
})
Also seeing this same issue on VLine for 'Seymour - Melbourne via Broadmeadows'. Exactly as @OppyLock described; no matter which direction I choose, it always creates one to Seymour rather than to Melbourne.
I tried to setup a sensor for this service but it always sets the direction in the outbound direction.
VLine service, Geelong - Melbourne line, Melbourne direction, From Wyndham Vale Railway Station.
It tells me that:
Created configuration for Geelong - Melbourne line to Geelong from Wyndham Vale Railway Station.
It doesn't matter if I choose the Melbourne or Geelong direction it will always create the sensors in the Geelong direction.
The actual sensors show the direction ID as 21, where it should be 0 for inbound.
The text was updated successfully, but these errors were encountered: