Fronius Wattpilot

Configuration
203

As an individual device, I added sensor.devicename_connection_charged

204

Hallo Martin,
thanks for your nice work and the integration.

I first wanted to open a new topic to post my issue, but then i thought it might be interesting to bring it forward here in your topicā€¦

I am in the situation that i have a Fronius inverter, the fronius wattpilot wallbox and a varta element backup which is a ac-system (was a wrong decission at the time, now i know better. :-)). The problem is, that the varta storage is not recogniced in the fronius app and therefore PV-excess charging is not possible.

Are you planning to integrate a feature in your integration, that involves also a battery storage and can handle this?

As an alternative to having it in the integration, it should be possible to handle this issue with automations. Do you agree? At least I managed to get access to the state of charge of my battery and the Amount of watt that go in / ot lf the battery via modbus.
But i run into issues when it comes to the communication with the fronius app and having a robust and reliable system. The fronius app somehow seems to overwrite the commands that come from home assistant.

Due to not knowing enough about whats going on in the background during the charging process and if i can damage somethin in the battery, car or inverter, i didnā€™t wanted to play around with this too much.

kind regards

206

Hi Martin,
Great integration. It appears to working fine on my end.
I am trying to dynamically set the charging amps of my wattpilot in response to available excess solar as reported by a sensor in the integration for my solar system. For the life of me I cannot find the ā€œnumberā€ to dynamically set the charging amps.
Should I be dynamically rather be using the [number.wattpilot_max_charging_current]. Or is this integration not the appropriate one to use for such a goal. Should I then look at an OCPP methodology? Iā€™m hoping the answer is within this integration where i have spend considerable time now :slight_smile:
Thanks in advance to you and this helpful community.
(wondering if Bernie drives a P2 - Iā€™ve seen that name around on Aus EV FB forums)

207

Hi Alex,
No, we have an Atto3 (3yo now & still brilliant).
I donā€™t do it dynamically myself but manually adjusting number.wattpilot_max_charging_current works as expected.

We have a 25kWh battery which smooths out the cloudy-day ups & downs of production so dynamic adjustment hasnā€™t been necessary thus far.

208

Thanks for the quick reply Bernie. Looks like I may need to look at an OCPP solution. Greetings from Brissy.

209

You can adjust the value with an automation. As a quick example

description: ""
mode: single
triggers:
  - trigger: numeric_state
    entity_id:
      - sensor.pvgenkw
    below: 8
conditions: []
actions:
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.q_watt_max_charging_current
    data:
      value: "25"

The sensor.pvgenkw is my PV generation. When it drops below 8kW, the charging current is set to 25A.
Youā€™ll just need a somewhat more complicated automation to have multiple steps up & down.

210

Apologies for dropping in here, but I noticed a few people in this thread have been looking for a feature like this (using the Wattpilot solar charging features like "Eco Mode" with data from Home Assistant).

I've just published a personal project called Wattpusher which sits between Home Assistant and a Fronius Wattpilot, emulating a fake solar inverter so that these Wattpilot features can be used:

This is a separate program not a Home Assistant addon or app - although it could maybe be converted to a Home Assistant app in the future.

Still very new, but I've been using it successfully for a couple of months now. (If anyone runs into any problems please open an issue on Codeberg, rather than dragging this thread off-topic. :slight_smile:)

PS Thanks for all your work on the wattpilot-ha integration, @mk-maddin! I use it every day and it's invaluable.

211

Hi @mk-maddin, once again thanks for this very useful integration.

For a long time, I've had a problem with a utility meter that's based on sensor.watt_totally_charged as source entity. The UM increases when HA restarts (sometimes).

I've added a comment to this Wattpilot issue as a result of suggestions from the community. Way out of my league but hopefully it can be fixed.