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

Unexpected condition clear #77

Open
Wesley-Vos opened this issue Feb 21, 2025 · 4 comments
Open

Unexpected condition clear #77

Wesley-Vos opened this issue Feb 21, 2025 · 4 comments

Comments

@Wesley-Vos
Copy link

Wesley-Vos commented Feb 21, 2025

Hi,

I'm using your integration but sometimes see an error in the log. It is about an unexpected condition: "clear".

I'm running HA 2024.2.4
with integration version 5.6.1
and the "Buienradar condition sensor" as source.

The error is:

Logger: custom_components.illuminance.sensor
Bron: custom_components/illuminance/sensor.py:461
integratie: Verlichtingssterkte (documentatie, problemen)
Eerst voorgekomen: 10:33:20 (3 gebeurtenissen)
Laatst gelogd: 16:43:27

Illuminance: Unexpected current condition: clear

Edit:
This is how the history graph looked like for today, also a bit strange because while it is 'Helder' (i.e. clear), the illumiance is way lower than when it is 'Bewolkt' (cloudy).

Image

If you need more info, please let me know!

Thanks!

@Wesley-Vos
Copy link
Author

Hmm, while checking the docs, I see that clear is not an official condition according to HA weather entity, is that the reason?

@pnbruckner
Copy link
Owner

Yes, that is the reason. It looks like the change to the buienradar integration in the 2023.6 release may have caused it to use this non-standard condition word. I'm not sure. I know I tested with that integration at some point in the past and it worked ok at that time.

You can make up for this by changing the fallback option. It defaults to 10 (dark), but if you change it to 1 (clear), it should compensate for the unexpected condition word.

@Wesley-Vos
Copy link
Author

I've checked the buienradar integration a bit more and it turns out that the weather entity (weather.buienradar) is returning the correct conditions for a weather entity. The condition sensor is returning the known conditions from buienradar itself, not necessarily the same condition names as HA.

The weather.buienradar entity can be used in the integration as well I found out so I think that the documentation of this integration can be updated, in that you should use the weather entity of the buienradar integration, instead of the condition sensor. :)

@Feriman22
Copy link

Feriman22 commented Feb 27, 2025

I have got similar errors in the HA log:

2025-02-27 17:58:56.782 ERROR (MainThread) [custom_components.illuminance.sensor] Illuminance: Unexpected current condition: mist
2025-02-27 18:08:56.803 ERROR (MainThread) [custom_components.illuminance.sensor] Illuminance: Unexpected current condition: light rain
2025-02-27 18:18:56.812 ERROR (MainThread) [custom_components.illuminance.sensor] Illuminance: Unexpected current condition: moderate rain
2025-02-27 19:58:56.805 ERROR (MainThread) [custom_components.illuminance.sensor] Illuminance: Unexpected current condition: light rain
2025-02-27 20:08:56.805 ERROR (MainThread) [custom_components.illuminance.sensor] Illuminance: Unexpected current condition: moderate rain

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

3 participants