Add: powerd load via Homeassitant/MQTT

[mkrasselt1]

My smart home features a heat dump controlled via esphome modbus (realys board switching resistive heaters in my water tank) that can take remaining solar power and use it to "charge" the water tank

It would be great if the homeassitant integration of this software offered a event to turn on additional loads (or to reduce them) or if evcc itself could send mqtt messages to controll loads (mine also feature a meter so that used power is available)

Right now i am using a vm emulating a shelly device to be controlled via evcc and read back into homeassitant which uses esphome again to controll the loads but its a pain.

[andig]

You can already do this by creating a custom charger.

[mkrasselt1]

i looked into it, and its almost as complicated - i would need to add the complete availableCurrent to active switches logic(enable additional heat-strips when (actual Power<available Power) then enable (available Power-actual Power)/power per Strip ect... in homeassitant, only based on the amperage limit given by evcc ... which is basicaly the same setup as i have right now.

i was thinking of something like a list of "chargers" with a given fixed load each and evcc turning them on whenever there is power to spare...

[VolkerK62]

you can use a few chargers, but every charger has got its own loadpoint.
you can fix the needed power by using the same current for min and max.
and by using different priority and enable/disable delay you can influence the start/stop sequence.

should be possible by using a switchsocket custom charger with mqtt

[mkrasselt1]

i tried adding it using this config:

vehicles:
  - name: heizung
    type: custom
    title: Heizlüfter
    icon: waterheater
    phases: 
      source: mqtt
      topic: esphome/heizstabsteuerung/enable/phases
    onIdentify:
      mode: pv
#      minSoC: 45
#      targetSoC: 55
#    soc:           # SoC = Wassertemeratur
#      source: mqtt
#      topic: esphome/heizstabsteuerung/temperature
#    onIdentify:
#      targetSoC: 23

loadpoints:
  - title: Heizstabsteuerung
    charger: esphome1
    vehicle: heizung
    mode: pv
    phases: 
      source: mqtt
      topic: esphome/heizstabsteuerung/enable/phases
    mincurrent: 8
    maxcurrent: 8
    resetOnDisconnect: true
#    soc:
#      poll:
#        mode: connected
#        interval: 10m
#      estimate: false
    enable:
      threshold: -1500
      delay: 30s
    disable:
      threshold: 300
      delay: 10s
#    guardduration: 10m

chargers:
  - name: esphome1
    type: custom
    standbypower: -1
    integrateddevice: true
    icon: waterheater
    heating: true
    enable:
      source: mqtt
      topic: esphome/heizstabsteuerung/enable
      payload: 2
    maxcurrent:
      source: mqtt
      topic: esphome/heizstabsteuerung/enable/current
    phasesActive:
      source: mqtt
      topic: esphome/heizstabsteuerung/enable/phases
    status:
      source: mqtt
      topic: esphome/heizstabsteuerung/enable/state
    enabled:
      source: mqtt
      topic: esphome/heizstabsteuerung/enable/enabled

it says that integrated, heating ect is not available

[VolkerK62]

standbypower ist not possible with custom charger. This is only a featur for switchsockets.

Try it this way

features:
- integrateddevice
- heating

[VolkerK62]

Ich mach mal auf deutsch weiter.

Wozu das Vehicle?
Ich nehme an das bei phases kein Plugin funktioniert.
Und wenn es integrated ist, brauchst du auch kein onIdentify.
Vehicle nimmt man in so einem Fall eigentlich nur, um den soc (Temperatur) in den Loadpoint zu bekommen.
Das geht bei einem Custom Charger aber auch mit dem Parameter soc:

Am Loadpoint werden phases, mincurrent, maxcurrent in der yaml ignoriert. Die sind im UI (loadpoint settings) einzustellen.
resetOnDisconnect ist schon seit längerem deprecated.

phasesActive am Charger dürfte auch nciht funktionieren.