core: Error configuring Luftdaten.info Sensor ID via Frontend
Home Assistant release with the issue: 0.84.6
Last working Home Assistant release (if known): 0.83.x
Operating environment (Hass.io/Docker/Windows/etc.): hass.io on Raspi3
Component/platform: Luftdaten: https://www.home-assistant.io/components/luftdaten/
Description of problem: I had some problems showing my Luftdaten.info sensors. After deleting them on the frontend I am not able to re-enter my values. When I try to add an sensor I always get the message (German hass.io):
“Keine Kommunikation mit Lufdaten API möglich” (Luf-t-daten is misspelled here)
The message is shown VERY fast, so I think there is no “real” try to connect… In my opinion it is too fast for every “DNS or something” timeout…
The Logfiles says: ERROR (MainThread) [luftdaten] Can not load data from luftdaten.info
I am sure my sensors and the Luftdaten API is working, I can see all data via Browser.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
YAML Config is disabled - using frontend only!
Traceback (if applicable):
Additional information: I know about problem #19591 and I have the same problem. With both issues Luftdaten in unusable for me in 0.84.6 now.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 24 (11 by maintainers)
Commits related to this issue
- Remove duplicate Luftdaten config entries. This fixes #18838, and also fixes the root cause of #19981 and #19622. — committed to jvanderneutstulen/home-assistant by jvanderneutstulen 5 years ago
- Remove duplicate Luftdaten config entries. This fixes #18838, and also fixes the root cause of #19981 and #19622. — committed to jvanderneutstulen/home-assistant by jvanderneutstulen 5 years ago
- Remove duplicate Luftdaten config entries. This fixes #18838, and also fixes the root cause of #19981 and #19622. — committed to jvanderneutstulen/home-assistant by jvanderneutstulen 5 years ago
- Remove duplicate Luftdaten config entries. This fixes #18838, and also fixes the root cause of #19981 and #19622. — committed to jvanderneutstulen/home-assistant by jvanderneutstulen 5 years ago
- Change sensor_id to int and remove duplicate Luftdaten config entries. This fixes #18838, and also fixes the root cause of #19981 and #19622. — committed to jvanderneutstulen/home-assistant by jvanderneutstulen 5 years ago
- Fix duplicate luftdaten entities (#20226) * Use same data schema for configflow, make sensor_id a positive integer. * Change sensor_id to int and remove duplicate Luftdaten config entries. This... — committed to home-assistant/core by jvanderneutstulen 5 years ago
I got the following response :
As test/workaround I changed the luftdaten api url in the library and pass it through a proxy which alters the User-Agent. In the last couple of days I see a normal request rate at 1 request every 10 minutes, which is the default for the integration. (running HA 0.84.6)
Interesting catch and I just sent an email to Jan from the luftdaten.info project to see if there are any specific reasons for this.
It seems as they have blacklisted 0.85 too… Probably caused by the issue in #18838 😦
The manual configured one worked so well for months 😦
One more…
Home Assistant is actually documented as a PlugIn on the luftdaten.info page, see https://luftdaten.info/faq/#toggle-id-8
@mattsches Ah, thanks! Now I understand the whole chain. I think I can wait for 0.85. I cannot find a hook to this error for the moment, and with a fix in 0.85 there is no need to go deeper. 😃
For me this was another chance to get deeper into the ha universe… thanks, great community!