We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Home Assistant release (hass --version): 0.51.2
hass --version
Python release (python3 --version): Python 3.4.2
python3 --version
Component/platform: Raspberry Pi 3 (Hassbian)
Description of problem: The sensor doesn't update it's state after some hours.
Expected: State should update and always show the next possible connection.
Problem-relevant configuration.yaml entries and steps to reproduce:
configuration.yaml
sensor: - platform: swiss_public_transport from: 8507493 to: 8507000
Additional info: Due to a change in the http://transport.opendata.ch/ API, there are now only 1000 Requests allowed per day. See here
The Sensor updates its state every minute, therefore it will stop updating itself after 16 hours (if you only have one sensor).
Maybe it would make sense to not update it until the current state "next departure" (timestamp) has passed?
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Home Assistant release (
hass --version
):0.51.2
Python release (
python3 --version
):Python 3.4.2
Component/platform:
Raspberry Pi 3 (Hassbian)
Description of problem:
The sensor doesn't update it's state after some hours.
Expected:
State should update and always show the next possible connection.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Additional info:
Due to a change in the http://transport.opendata.ch/ API, there are now only 1000 Requests allowed per day. See here
The Sensor updates its state every minute, therefore it will stop updating itself after 16 hours (if you only have one sensor).
Maybe it would make sense to not update it until the current state "next departure" (timestamp) has passed?
The text was updated successfully, but these errors were encountered: