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

value not float leading to unknown state of entities #16

Open
wagnst opened this issue Aug 21, 2024 · 0 comments
Open

value not float leading to unknown state of entities #16

wagnst opened this issue Aug 21, 2024 · 0 comments

Comments

@wagnst
Copy link

wagnst commented Aug 21, 2024

as mentioned already in #11
i am seeing regular issues with the integration leading to NaN data in HA:

2024-08-21 17:55:04.450 WARNING (SyncWorker_7) [custom_components.dhmz.weather] Unknown DHMZ weather symbol: None
2024-08-21 17:55:04.453 WARNING (MainThread) [custom_components.dhmz.weather] Temperature - value not float: 
2024-08-21 17:55:04.453 WARNING (MainThread) [custom_components.dhmz.weather] Humidity - value not float: 
2024-08-21 17:55:04.453 WARNING (MainThread) [custom_components.dhmz.weather] Pressure - value not float: 
2024-08-21 17:55:04.453 WARNING (MainThread) [custom_components.dhmz.weather] Wind speed - value not float: 

image

i'm not sure what happens, but visiting the site itself, i see it as available, e.g. via the website or via the XML api for the bespoke dataset.

is there any idea what is happening here? Are they rate limiting requests? If yes maybe instead it could just be skipped to write data to the entity for that occasion so the entities don't report Unknown?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant