-
Notifications
You must be signed in to change notification settings - Fork 10
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
Missing current temperature sensors 'unknown' #51
Comments
Hi, I had the same issue, and found your issue whilst looking for a resolution myself. My issue was caused by using "current" as the timestep for the current conditions, I set mine to "1m" and my sensors started working rather than being sat as "unknown". I can't see anything drastically different with your config that should cause you issues, the only thing I can see is that you have a mix of v3 and v4 sensor names... I've tried to align mine to the raw Climacell names, whether that has any bearing? In case it helps, my (now working) config is below (just note I prefix the sensors with "daily" or "current" - if you copy and paste and want to maintain your current naming convention, make sure you remove these!):
|
Wow @Mobbsey that fixed it. I didn't realize I had a mix (I clearly missed those from the documentation), I just cleaned my config updating the fields using your example and all the sensors are back. Thanks a lot! |
Hi,
Today I made the update to Climacell API v4 and updated the fields but I can't get the current temperature sensors to work.
In HA Developer Tools I get the sensors but they display 'unknown' value. This does not happen to all but just the current measurements as the others appear (for example
sensor.cc_climacell_temperature = 'unknown'
butsensor.cc_climacell_temperature_0d
returns a value.This makes me think I'm missing something for the current weather conditions or that my config is wrong.
The text was updated successfully, but these errors were encountered: