1.8.0: = EnergyInput Wh
2.8.0: = EnergyOutput Wh
1.7.0: = PowerInput W
2.7.0: = PowerOutput W
This is a good start:
The Start was ok, but my Result Not. Sorry, and please help me out.
Merry Christmas and Thank you in Advance!
Please post your configuration as plain text and not a screenshot.
Try this instead:
sensor:
- platform: rest
name: amis_energy_bezug
resource: http://192.168.1.20/rest
authentication: basic
username: admin
password: ****
value_template: "{{ value_json['1.8.0'] }}"
Changin the value_template to your correct Syntax and removing the other wrong staff helped!
THANK YOU!!
I’m experimenting with energy 2 power cónversion.
Since I couldn’t find an easy solution as it is possible converting power2energy using the sensor integration platform. I did try to make a calculation in template integration using the timestamp difference between 2 pulses. The value is strange and I don’t know what the value is representing.
nor I have an idea to solve this…
as said before.
It is so easy! Couldn’t believe it. Worked like out of the box 
Thank you!!
… I tried to copy the config out of the terminal emulation into this window, but this didn’t work.
Thats why the screenshot config… 
You might need to hold down shift, or something like that. What terminal emulator are you using?
I’m ussin the Unix .
Now I#m struggling with a problem that I got with the derivative integration.
espcially with the inverter sensors of the battery. When the battery gets empty, the inverter stops producing energy very fast. the entergy counter stops after high pulse level and the derivative sensor stops displaying the last (high) power value from the last energy value it received.
until next day when the batterie inverter starts again producing energy and let the counter increasing its value, the high power value is shown in lovelance.
another big problem what i encountered was after hass restart.
the timer for derivtive calculation semms to start immediatly and this genates sometimes very high values especially when the energy counter transmits increased values close after restart, because of the low time in between the values ! After a restart derivative calculation should start only after the first counter value received and the derivative calculation should decrease its value automtically after the energy does’nt increase after a time period.
Another question, How I ćan I display last period attribute of utilitymeter?
I believe the state of the derivative entity only updates when the source entity updates. You can’t really fix the derivative sensor without fixing it’s source.
Derivative sensors are updated upon changes of the source.
Derivative - Home Assistant
You could create a lovelace card like this:
type: entity
entity: sensor.kotlik_handledstarts_daily
attribute: last_period
name: Last period
or use a template sensor and state_attr.