Hey there. Good work so far.
Just one additional question:
How can I get statistics for the following sensor:
sensor.e3dc_power_consumption_house
I can’t insert the sensor in a Statistics graph card.
Hey there. Good work so far.
Just one additional question:
How can I get statistics for the following sensor:
sensor.e3dc_power_consumption_house
I can’t insert the sensor in a Statistics graph card.
cool, thanks for this integration. I always wanted to do the same thing, but never really found the time for it.
Since I didn’t want to spam your Github repo with a ticket for just a simple question, I thought I’d ask here. Why are the web interface credentials needed? I personally would prefer local communication only, but web credentials are mandatory in the setup wizard.
HI @da-anda
This is a limitation of the E3DC authentication. While it is online, it will always authenticate against E3DC cloud services. Everything else (the complete communication) is executed locally, I do not use the cloud client. The auth-relay is done by the E3DC unit, not my lib, to my knowledge there is no way around it. Pure local authentication is only possible in offline mode when the net is down.
We can have further disucssions in the topic of the integration, if you like:
Also, more details regarding the authentication are available on the pye3dc lib’s readme:
Hi,
after update to HA 2025.8 the custom integration from 2022 didn´t work anymore an also all devices were not loaded.
After some changes in the yaml files, it works again… It seems, that only one change in the sensor.yaml fix it.
I had to delete
The mistake was, that I already had an entry sensor.e3dc_external_power in modbus.yaml
The RCSP variant by Torben Nehmer is cool and basically works as well (except for the external solar source). However, what bothers me about this variant is that I only receive an update every 30 seconds, not live… that’s why I continue to use the Modbus variant.