Closed hudecitydave closed 5 years ago
Hey there @fabaff, mind taking a look at this issue as its been labeled with a integration (luftdaten
) you are listed as a codeowner for? Thanks!
This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Home Assistant release with the issue: 0.95.4
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
arch | x86_64 dev | false docker | true hassio | true os_name | Linux python_version | 3.7.3 timezone | Europe/Berlin version | 0.95.4 virtualenv | false
Component/platform: https://www.home-assistant.io/components/luftdaten/ Configured via frontend
Description of problem:
Randomly my sensors switch to the state "unknown" in the frontend, the following is happening in the log:
Sometimes it is possible to restart ha, sometimes I have to delete and reconfigure the sensors via frontend.
For me, my sensors are working well via direct API call: https://api.luftdaten.info/v1/sensor/8608/