Senec and Tibber

[scottgoo]

I changed from Senec cloud to Tibber. Like to charge my senec battery when prices are low and get power from battery when prices are high.

I know the way to force a battery charge. Is there a way to pause charging then? And is there a way to block the battery from supplying the house when it is charged. Would be nice to keep the battery power for the very expensive times.

Thank you!

[bobthebuilder4711]

Sadly no.

If you know Modbus then you could engineer a device that replaces the Enfluri and would simulate energy flow from and into the grid to make your senec battery do what you want.

That would of course make the statistics on mein-senec.de or in the App totally useless. But you can always get the grid import and grid export from your digital energy meter and don't have to rely on senec for that, so Home Assistant would be able to display sane data.

But someone would have to know Modbus and would have to be willing to tinker with their senec battery.

[scottgoo]

Thanks a lot for your reply! Unfortunately I am not so big in modbus so I won’t manage to get things done this way.

[loeffelpan]

I use another "solution".
I tell an automation (not really, as I have to enable and adjust it manually regarding future prices and estimated pv energy) when to start charging to a specific soc and when to release its energy. Actually the automation is charging to that soc, stops there and restarts when soc is 10% below until release time is reached.

alias: "Tibber: PV-Batterie laden"
description: ""
trigger:
  - platform: time
    id: charge
    at: input_datetime.tibber_start
  - platform: numeric_state
    entity_id:
      - sensor.senec_battery_charge_percent
    below: input_number.tibber_target_soc
    id: recharge
    value_template: "{{ state.state|float(0) + 5 }}"
  - platform: numeric_state
    entity_id:
      - sensor.senec_battery_charge_percent
    above: input_number.tibber_target_soc
    id: stop
  - platform: time
    id: disable
    at: input_datetime.tibber_end
condition:
  - condition: state
    entity_id: input_boolean.tibber_active
    state: "on"
action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - charge
          - condition: numeric_state
            entity_id: sensor.senec_battery_charge_percent
            below: input_number.tibber_target_soc
        sequence:
          - service: switch.turn_on
            target:
              entity_id: switch.senec_safe_charge
            data: {}
          - service: input_boolean.turn_on
            data: {}
            target:
              entity_id: input_boolean.tibber_charging
      - conditions:
          - condition: trigger
            id:
              - recharge
        sequence:
          - condition: state
            state: "on"
            entity_id: input_boolean.tibber_charging
          - service: switch.turn_on
            target:
              entity_id: switch.senec_safe_charge
            data: {}
      - conditions:
          - condition: trigger
            id:
              - stop
        sequence:
          - condition: state
            state: "on"
            entity_id: input_boolean.tibber_charging
          - service: switch.turn_off
            target:
              entity_id: switch.senec_safe_charge
            data: {}
      - conditions:
          - condition: trigger
            id:
              - disable
        sequence:
          - service: switch.turn_off
            target:
              entity_id: switch.senec_safe_charge
            data: {}
          - service: input_boolean.turn_off
            data: {}
            target:
              entity_id:
                - input_boolean.tibber_active
                - input_boolean.tibber_charging
mode: single

[bobthebuilder4711]

I guess I'm too dumb to make any sense of that YAML. How do you make your senec power station stop charging at "Ladeziel"? Do you really restart the whole power station? And how do you then prevent it from discharging?

[loeffelpan]

I'll try a short description of that automation.

There are four triggers:

• start at start time
• recharge when soc is 5% below charging target (value_template is 5% above of the current soc and will trigger at 5% below)
• stop when soc = charging target
• disable at stop time

Start trigger will start charging with integrations safe charging switch and turn on a boolean helper.
Then stop trigger will turn off the switch when soc reached charging target.
From now the battery will discharge as usual as senec does not provide any possibility to hold soc or prevent discharging.
At 5% below charging target the recharge trigger starts charging again by turning on the safe charge switch. So the battery will oscillate e. g. between 65% and 70% soc until the disable trigger turns off the safe charging switch (if turned on) and disables the boolean helpers at stop time.

First boolean helper (_active) is for enabling the automation in general.
Second boolean helper is to prevent actions when soc crosses charging targets for any reasons without the automation running.

Feel free to ask any question.

[bobthebuilder4711]

So the battery will oscillate e. g. between 65% and 70% soc until the disable trigger turns off the safe charging switch (if turned on) and disables the boolean helpers at stop time.

Okay, that sounds like you're burning through cycles without this having enough benefit to justify the lost cycles.

[loeffelpan]

I don't think this is really relevant.
Those modules can make up to 12.000 cycles according to their data sheet. Even if you will do a full charge every day (that is one cycle and will likely not happen) the whole year, it will take over 30 years to make that amount of cycles.
Also I have 20 years of warranty, so I don't really care.

But indeed I would prefer a solution via modbus, too.

[mschmiedel]

[mschmiedel]

This switch I posted is btw outdated/not necessary, because the actual integration has this switch already as "senec_safe_charge", just an automation that controls this would be enough... :)