Problems with esphome / D0 Read Head after power failure

Hello everyone,

I have a problem with my D0 read head connected to an esp and integrated into hassio via esphome.
Yesterday there was a power failure for ~15min in the whole town. Since then the fuinction is limited. (I have now also updated esphome today in the hope that this will solve it - unfortunately without success)

What I don’t understand is that only the status “active power” is no longer transmitted.
The other values are transmitted:

Does anyone have any idea what I can do to solve the problem?
Unfortunately, the wallbox control is dependent on the active power status ;(

Log:

(..)

[19:51:16][D][d0:058]: OBIS info:
[19:51:16][D][d0:063]: 1-0:0.0.0*255 = 1EBZ0100791128
[19:51:16][D][d0:063]: 1-0:96.1.0*255 = 1EBZ0100791128
[19:51:16][D][d0:063]: 1-0:1.8.0*255 = 014967*kWh
[19:51:16][D][d0:063]: 1-0:1.8.1*255 = 000001*kWh
[19:51:16][D][d0:063]: 1-0:1.8.2*255 = 014966*kWh
[19:51:16][D][d0:063]: 1-0:2.8.0*255 = 053473*kWh
[19:51:16][D][d0:063]: 1-0:96.5.0*255 = 001C0104
[19:51:17][V][sensor:043]: 'Total energy': Received new state 14967.000000
[19:51:17][D][sensor:093]: 'Total energy': Sending state 14967.00000 kWh with 2 decimals of accuracy
[19:51:17][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[19:51:17][V][json:058]: Size after shrink 84 bytes
[19:51:17][V][text_sensor:013]: 'Total energy string': Received new state 014967*kWh
[19:51:17][D][text_sensor:064]: 'Total energy string': Sending state '014967*kWh'
[19:51:17][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[19:51:17][V][json:058]: Size after shrink 92 bytes
[19:51:17][V][sensor:043]: 'Energy Export': Received new state 53473.000000
[19:51:17][D][sensor:093]: 'Energy Export': Sending state 53473.00000 kWh with 2 decimals of accuracy
[19:51:17][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[19:51:17][V][json:058]: Size after shrink 84 bytes
[19:51:17][D][d0:058]: OBIS info:
[19:51:17][D][d0:063]: 1-0:0.0.0*255 = 1EBZ0100791128
(..)

yaml.

external_components:
  - source:
      type: git
      url: https://github.com/BMOD89/esphome_compontens
      ref: main
    components: [ d0 ]


esphome:
  name: strom-keller
  platform: ESP8266
  board: nodemcuv2
  includes:
    - uart_read_line_sensor.h

# Enable logging
logger:
  level: VERBOSE
  baud_rate: 0


# Enable Home Assistant API
api:



ota:
  password: "."

wifi:
  networks:
  - ssid: "xxx"
    password: "xxx"



  # Enable fallback hotspot (captive portal) in case wifi connection fails

time:
  - platform: homeassistant

captive_portal:

web_server:
  port: 80
  
d0:
  id: myd0
  uart_id: uart_bus

uart:
  id: uart_bus
  tx_pin: GPIO1
  rx_pin: GPIO3
  baud_rate: 9600
  data_bits: 7
  parity: EVEN
  stop_bits: 1

sensor:
  - platform: d0
    name: "Total energy"
    server_id: "01 00 01 08 00 FF"
    obis_code: "1-0:1.8.0*255"
    unit_of_measurement: kWh
    accuracy_decimals: 2
    device_class: energy
    state_class: total_increasing
#    filters:
#      - multiply: 0.0001

  - platform: d0
    name: "Energy Export"
    obis_code: "1-0:2.8.0*255"
    unit_of_measurement: kWh
    accuracy_decimals: 2
    device_class: energy
    state_class: total_increasing
#    filters:
#      - multiply: 0.01

  - platform: d0
    name: "Active power"
    obis_code: "1-0:16.7.0*255"
    unit_of_measurement: W
    accuracy_decimals: 1
#    filters:
#      - multiply: 0.1

text_sensor:
  - platform: d0
    name: "Manufacturer"
    obis_code: "129-129:199.130.3*255"

  - platform: d0
    name: "Total energy string"
    obis_code: "1-0:1.8.0*255"

You may need to ask the author of the custom component.

Maybe it is not the ESP, but the D0 that is the issue or the connection between them.