-
Hi Klemens; Transfer of my PV-data stopped some time ago. It looks like it is due to the upgrade to a newer version that requires the confirmation that I accept the risks associated with writing. Error message as follows: Logger: homeassistant.components.automation.automatische_ubertragung_der_pv_werte_an_idm_wp Automatische Übertragung der PV Werte an IDM WP: Error executing script. Error for call_service at pos 1: Error rendering data template: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ states("sensor.power_solar_surplus")|float }}' but no default was specified I have so far not been able to figure out how to accept the writing risk. I do not see this option under the configuration page (Integrations, IDM Heatpump, Configuration) How do I need to proceed? Best, Kjartan |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
If you're using the UI to configure the script, you should see a Checkbox with the text "I accept the risks"/"Ich akzeptiere das Risiko". When using YAML you need to add the additional parameter That said, I believe there is a second error here your sensor |
Beta Was this translation helpful? Give feedback.
-
Thanks for the help. This took away both error messages and the values are now transferred. Very much appreciated. I added the acknowledge_risk to the script.yalm, but also tried to figure out how to do it through the UI. The "Further Configuration" link on the documentation section does not work, so I did not get further there. I saw that there is a possibility to set power in the automations UI for the heat pump, but this seemed to be limited to a constant value and not a variable. For that setting I found the check box. |
Beta Was this translation helpful? Give feedback.
If you're using the UI to configure the script, you should see a Checkbox with the text "I accept the risks"/"Ich akzeptiere das Risiko". When using YAML you need to add the additional parameter
acknowledge_risk: true
. Take a look at the snippet in #142 for an example.That said, I believe there is a second error here your sensor
power_solar_surplus
doesn't always have a value. In your example it wasunavailable
. Depending on your use case you may be able to use{{ states("sensor.power_solar_surplus")|float(0) }}
so0
is used as the default value forunknown
/unavailable
. I suspect that0
is the right default, but you might need a different value or may need to handle the case entirely sep…