Hello Torben,
many thanks for the great E3DC integration !!!
Is it possible to set a discharge block for the battery via the integration?
I also have an E3DC S21X home power station and am currently asking myself whether it is possible, for example, if the sun is no longer shining and I have charged my battery via my dynamic tariff, but at some times it is still cheaper to draw the electricity directly from the grid and not to discharge the battery with losses first. Is there a setting here, i.e. if no electricity can be generated via solar, the battery should not be drained. For example, if the dynamic current is at 15 ct for 3 hours and the battery is full, it makes no sense to discharge the battery with losses, but only to draw power directly from the grid. Later, when the grid electricity is more expensive again, the battery is discharged again.
Hey,
did anyone solve this issue? Having the same issue with latest hass version:
2024-10-14 13:20:29.766 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store/repositories - https://github.com/torbennehmer/hacs-e3dc.git is not a valid add-on repository
Hi all,
thanks for the Kudos, even though I tend to react only slowly (real life, as it is). I really appreciate that! Thanks for using my tool!
E3DC does not give us Today-Sensors for everything, unfortunately. The todays you’ve got are queried from its internal time series database, right now, no other sensors are made available there, directly from E3DC. The only thing you could do is create your own template sensor using the Rieman Integration integration (no typo ;-)), which can sumup such measurements. Doing this ourselves is non-trivial, as we’d have to integrate the values over time as well. This is why I haven’t done it yet.
The difference between “additional” and “additional production” has a similar reason. One of it is a default, nondescript sensor, the other one is directly related to the power meter API. Right now, we provide both. The power meter API is the more sophisticated, but those are - again - not in the internal Time Series DB, so no history. I think in current setups, the old-style sensors are disabled by default, only kept for backwards compatibility.
You may want to use the actions/services to set power limits, as described in the README.md. With them, you can block E3DC from discharging (or even charging, if you’d want that). I am using this approach to prevent E3DC discharging the battery when I’m using cheap grid power from Tibber to charge my car, basically looking something like this (YAML mode, for easier transportation into the forum):
alias: "Wallbox aktiv: S10 Entladung sperren"
description: ""
trigger:
- type: power
platform: device
device_id: 5410...
entity_id: f8da...
domain: sensor
above: 3.8
for:
hours: 0
minutes: 0
seconds: 10
condition: []
action:
- service: e3dc_rscp.set_power_limits
data:
device_id: b004...
max_discharge: 0
mode: single
To clear the limits again, there is another action to clear the limits, basically:
- service: e3dc_rscp.clear_power_limits
data:
device_id: b004...
Using this approach, you can do just about anything except charging the battery from the grid (manual charging does this, but handle with care, again, check README.md for details).
Can you please file an issue, including HACS/HA debug logs of the attempt.
I’ll check this against current HACS/HA, there has been some change here, which I haven’t validated so far. I’m in the process of upgrading to latest HA, but not yet finished, as there were a number of dev blogs I still have to go through before commiting.
But please create the issue, so you’ll be informed when I’ve got something new there, it also reminds me of testing this. 
Torben
Many Thanks for your feedback, I’ll try and come back.
Another question, is it possible to output the values of the individual solar production trackers 1-3?
What do I have to do for this?
I cant connect correctly to my E3DC.
I get this error: Einrichtungsfehler, wird erneut versucht: Configuration not yet ready: Fatal error when talking to E3DC
Any Idea?
The integration currently does not support this, it would need a code change. PRs are always welcome, please check the GitHub page for that, Thanks!
Without further information, I can’t say anything. Check your debug logs. Please head to our Discussions on GitHub for further discussions, do not open an issue for support requests.
Best bets: Wrong account data or RSCP key.
Torben
I installed the E3DC-Integration (version v3.8.0) for the first time and it seems to work without any problems. This is very important for my home automation projects.
Thank you very much Torben for this great work!
Hey Torben,
I´ll get the following Error
2024-11-23 15:28:10.987 DEBUG (SyncWorker_6) [custom_components.e3dc_rscp.e3dc_proxy] Fatal error when talking to E3DC: 11 is not a valid PowermeterType
Hi @Yosberto
Please create an issue at the GitHub page, if the integration allows you to, attach a dignostic dump as well. We might have to test a bit around this, as we are unaware of this powermeter type. Could be, that we’ve to forward this to pye3dc.
Also add all known information to your unit to the issue, as I’m not sure what actual setup you’re using there.
Torben