All 3.4.0 users should update to 3.4.1, two regressions in the pye3dc library have been fixed, which have been introduced with 3.4.
If you’ve problems creating a diagnostic dump, please update to 3.4.2.
Update for HA 2023.11 compatibility, also takes care of an edge case with additional device identifiers when calling services.
Hi thorben,
is it normaly, that the connection between HA and S10 abort for minutes or one hour? All entities unaivailable. HA says reconfig but its better to wait and reload…
Hi Robelix,
This is probably the same issue as
Could you please check there and add comments or additional debugging data to it, if applicable?
Torben-without-the-H 
Sorry torben
Now i had to reconfig and for moment it runs.
I will send data.
I remember the problem is, since i have startet MariaDB…is this possible?
Round about two times a day connection between HA and S10 lost and the entities are not available. Sometimes i have to reconfig or reload, sometimes it heals alone.
Web Connection of S10 ist stable all time.
I posted data on github
Hi Torben,
first of all, thanks for your awesome work!
I’ve been using Thomas Spalingers GO-implementation of the RSCP API for some years now since I found it to be the most flexible around the time our system was installed. However, you integration will make things so much easier, especially maintenance.
At what rates do you read the current / daily data, is is 10 seconds / 5 minutes? It would be awesome if we could get parameters in future to pick ourselfs. Currently I’m using 15 minutes for daily sums and 5 seconds for the current data.
I’m using version 3.4.3 of your integration and according to your changelog, it should automatically pick up additional powermeters. However, we have two of those, and only one is picked up. Should I create a bug report so you can take a look?
I have no practical experience with HA+Mariadb. Out of my guts I’d say this should be unrelated to the underlying DB. Best thing you probably can do is to enable debug logging, maybe for additional subsystems apart of E3DC as well. Normally, if something drops out, you should get some hint in the logs.
Thanks, I’ll look at it in the next days as soon as I get around to it. I have not yet seen this behavior on my end, so I can’t look at it first-handed.
You’re welcome, thank you too for using it!
Currently, the realtime data is queried every 10s, the historical data approximately every minute.
If you want it configurable, create a Feature Request for it at Github shouldn’t be that hard to change.
Yes, please open a separate bug for it, don’t forget the diagnostic dump. I’m not sure if this is on my end, might be that we’ll have to forward it to the pye3dc base library.
Cheers, Torben
Hi @torben78 it seems that I am to dumb to get the services working. (Yes i was)
I tried to find a clue but in the end reinstalled cause i thought maybe the device can’t be identified … but simply i can’t get the services running, Integration just shows sensors but no services
attached device is an e3dc s10 pro compact
If you can hint me to any documentation it would be highly appreciated
Thank you
and as most of the time writing the ticket resolved my issue, service is prominent under Developer tools services, as it should be. Thanks
I have to correct myself. Two additional sensors have been created, they were just deactivated by default. 
However, there is an entity missing for the wallbox consumption sum (kWh). I will create an issue for it once we charged our car again.
You could send me a diagnostic dump in this respect. In theory, the latest changes should auto-detect all powermeters in the box. I’d like to have a glimpse on what’s going on there. Alternatively, the py3edc lib also has a testing script. As I rely on its autodetction, it might be worthwhile to investigate this on the whole toolchain.
There is an open issue for that already. Since I do not have a WB on my E3DC (I’ve opted for an OpenWB, which already has impressive HA Supprt), it is not on my top priority list. I plan to implement it, however I can’t give you an estimated date for it, especially, since it seems we still have a number of strange intermittent bugs in the integration. I’d like to look at these first before implementing new features.
Hello Torben,
really nice integration - worked out of the box.
Looking forward to the availiability of the E3DC Wallbox
Markus
For me the setup process does not seem to be working
Currently I get all my data via the Modbus Integration, but I wanted to try the integration to see how it compares.
Hi T1ppes,
Look at the log file, enable Debug-Logging for the component to get everything you’ve got. Create a GitHub Ticket with it and I’ll look into it.
Cheers, Torben
Hej Markus,
Thanks, that’s great to hear.
I can’t give you an ETA on the WB integration (I don’t have one to test this). Maybe over the christmas holidays. I’ll probably churn out a Beta implementation (that’s at least my plan) and then look out for early adopters willing to test this. Stay tuned.
Cheers, Torben
Hello guys
I would configurate the energy dashboard but u couldnt set the grid consumption, grid export and solar production. the sensores are not avaiable.
the description says they should be labeld as device_class enegry. but the all are ‘power’
why is this so? i cant use this plugin.
any andvise?
thanks
Trevor
Many thanks for this great integration, works perfectly! 