-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature Request: Template Support #21
Comments
Hi @marcelvandorp, thank you for your message. |
Template are indeed currently not supported. For now, I do suggest going with a template sensor. |
Also having separate consumption and production sensors here. |
@nonplusnl a workaround right now would be to create template sensors, which do the math for you: |
It actually gives you a bit more to work with if you create template sensors like that.. The latter I take by pulling the sensor.solaredge_ac_power directly from the solaredge pv ac power generation (modbus over tcp sensor on the pv setup) and comparing it against the power meter P1 power consumption and generation counters live The full configuration.yaml entries I use for these: `template:
|
Hi,
I have a feature request:
I see that negative values will show the animation from right to left (as expected). My DSMR has two sensors per line: Power Consumption and Power Production. Both are positive values. But When I have Production, I do not have Consumption and vice versa
Is there a way to display the results of the calculation: Consumption-Production? That is: with Consumption this is a positive value, and with Production this is a negative value. This way the animation shows exactly the flow of energy as it occurs.
I tried a template, but this isn't recognized (or I do something wrong).
This is a simple test config that works:
But if I change the power line to use a template, like this:
- power: "{{ states('input_number.schuiver') }}"
It doesn't show anything. This line only uses a template to retrieve the value, no calculations are done (yet)
I am aware I can solve this with a template sensor, but I believe a solution in this card is the cleaner solution.
The text was updated successfully, but these errors were encountered: