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 have updated NationalRailTimes to the latest available version
I did a search to see if there is a similar issue.
Current Behavior
Invalid configuration error when trying to configure via yaml.
Invalid config for [sensor.nationalrailtimes]: [destination] is an invalid option for [sensor.nationalrailtimes]. Check: sensor.nationalrailtimes->destination. (See ?, line ?).
Expected Behavior
Configuration pass
Steps To Reproduce
Try to add the following to your configuration.yaml:
This is a known issue I too have been suffering from, and I'm completely onboard with this. Certainly needs further investigation.
Frankly, there are a number of issues with this component I have around this area too... such as lack of editing, and the API key request every time a new station is added...
This component could to with a refactor. As much as I would like to, I just don't have the time to get deep into fixing this one right now.
Requirements
Current Behavior
Invalid configuration error when trying to configure via yaml.
Expected Behavior
Configuration pass
Steps To Reproduce
Try to add the following to your configuration.yaml:
api_key: YOUR_KEY
arrival: LBG
destination: CHX
time_offset: 15
Context
No response
Environment
No response
Anything else?
Is it possible that this is caused by PLATFORM_SCHEMA (in sensor.py) not including destination?
The text was updated successfully, but these errors were encountered: