home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.21k stars 30.23k forks source link

Vicare component - solar power sensor has no numeric state #65633

Closed Zahnweh closed 2 years ago

Zahnweh commented 2 years ago

The problem

First of all thanks for adding the new solars sensors!

But unfortunately 'sensor.vicare_solar_power_production' does not have a state that can be parsed as a number. When I try to add the sensor in my energy configuration it says:

Entität hat einen nicht numerischen Status Die folgenden Entitäten haben einen Zustand, der nicht als Zahl geparst werden kann: sensor.vicare_solar_power_production ([0, 0, 0.163, 0, 0, 0.049, 0, 0.035]

Bildschirmfoto 2022-02-04 um 09 26 30

)

What version of Home Assistant Core has the issue?

2022.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Viessmann Vicare

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vicare/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

vicare documentation vicare source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @oischinger, mind taking a look at this issue as it has been labeled with an integration (vicare) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

bairnhard commented 2 years ago

I hope, I am not getting this wrong. You get back all the data that Viessmann provides in their API. This data is probably not meant to be used in the energy configuration. HA's solar panel energy implementation is meant to be used for photovoltaic systems, not for Viessmann's hot water production.

Zahnweh commented 2 years ago

Good point. I already thought about that. But the data looks strange to me though as its '0, 0, 0.163, 0, 0, 0.049, 0, 0.035' and the unit is kWh. In my eyes that doesn't fit together.

oischinger commented 2 years ago

I would also expect a single numeric value. What does the data mean? Is it the last 8 power production measurements over time?

I fear that we either might need to change the unit or provide multiple sensors

Zahnweh commented 2 years ago

Yes. It's the last 8 measurements divided by commas.

image

oischinger commented 2 years ago

Then I'd suggest we just take the most recent value and suffix the sensor with _today.

Does that make sense?

Zahnweh commented 2 years ago

Sounds good. Let's give it a try.

oischinger commented 2 years ago

@bairnhard since you contributed the initial PR. What do you think? Any other suggestions?

oischinger commented 2 years ago

@woehrl01: Ideally we would implement an additional getter in PyVicare for the "Today" value. What do you think?

woehrl01 commented 2 years ago

@oischinger yes, that definitely makes sense.

oischinger commented 2 years ago

Looks like we already have getSolarPowerProductionToday and so on. It's coming to the HA integration with this PR: https://github.com/home-assistant/core/pull/63339

In that case I'd suggest we remove the sensor 'sensor.vicare_solar_power_production' and use only the today, week, months sensors

bairnhard commented 2 years ago

@bairnhard since you contributed the initial PR. What do you think? Any other suggestions?

Back online. Yes, makes sense. I can't test it, though because my solar system does not support these values...

My solar heating does not support these values and there's nothing I can do about it. I called Viessmann and they said, we need to find someone who gets a response from the API with values. As a gut feeling, I'd leave all values in and maybe document it properly, so people who only have that as a response from the Viessmann API have at least some data.

I assume it works since the HA logs respond properly and say, that my system doesn't support them.

smartmatic commented 2 years ago

I am facing the same issue and it would be very nice to get a solution as the data is available but not as a single value only as @Zahnweh already showed as a row of the solar power production of the last 7 days

HA Solar Panel Error

I guess the good point is that the first entry in this 7-days row is the latest one. So a formular which takes always the first value from the left side as the latest solar power value for the daily report would be great!

So in my example 28.1 is the newest value

Is that possible?

oischinger commented 2 years ago

I think this is resolved with the latest commit on this PR. there is now a "Solar power production today" sensor you could use. I'm also adding these sensors to the custom integration now: https://github.com/oischinger/ha_vicare/pull/92

smartmatic commented 2 years ago

I think this is resolved with the latest commit on this PR. there is now a "Solar power production today" sensor you could use. I'm also adding these sensors to the custom integration now: oischinger/ha_vicare#92

Ah ok, and the new "Solar power production today" should be already available via the Viessmann Integration? I don't have this entity

oischinger commented 2 years ago

You need to use the latest custom component or wait for the next home assistant release to get the new entity

smartmatic commented 2 years ago

Ah ok, i am new at Home Assistant so sorry for my questions. Can you please give me a hint how to integrate such custom component and how it works together with the offical integration once the HA update is released? Is it then necessary to remove the custom component? Thank you in advance for your support and patience!

oischinger commented 2 years ago

You can copy https://github.com/oischinger/ha_vicare/tree/master/custom_components/vicare to /config/custom_components/vicare/ and the custom component will replace the existing integration (after HA Core restart). When you want to switch back to the official integration you must remove that directory. An update to the next HA version won't do that for you.

github-actions[bot] commented 2 years ago

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 has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.