Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Unable to setup via configuration.yaml #2

Open
2 tasks done
ReX1983 opened this issue Jan 28, 2023 · 1 comment · May be fixed by #6
Open
2 tasks done

[Bug]: Unable to setup via configuration.yaml #2

ReX1983 opened this issue Jan 28, 2023 · 1 comment · May be fixed by #6
Labels
bug Something isn't working

Comments

@ReX1983
Copy link

ReX1983 commented Jan 28, 2023

Requirements

  • 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:

  • sensor:
    • platform: nationalrailtimes
      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?

@ReX1983 ReX1983 added the bug Something isn't working label Jan 28, 2023
@crismc
Copy link
Owner

crismc commented Apr 8, 2023

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.

@terricain terricain linked a pull request Nov 18, 2023 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants