Closed ojarosch closed 3 years ago
Hey there @cgtobi, mind taking a look at this issue as its been labeled with an integration (rmvtransport
) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
Thanks for reporting this. I was able to reproduce the bug and fix it.
The problem
The given results ignore configured parameters. I'm looking for the next departures of RB67, RB68 or RE60 from Frankfurt Central Station, which target either Mannheim or Heidelberg. I instead receive data from completly different lines which to not meet any of the given parameters, see example data below. RE70 for exaple does not even target Mannheim, even though the received data states it. I even got data from an ICE, which explicitly not asked for. Sometimes duplicate data is given. E.g. the same departure is given as RB67 aswell as RB68. According to the RMV-Website and/or App, there is only one departure at the given time.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information