-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional Production not enabled automatically if present #43
Comments
Please add a diagnostics dump. If you don't want to upload it here, you can use https://kurzer.link/e3dcrscp as an alternative. |
Found it… It was disabled… I have enabled it and now it is visible. Sorry – My fault! Great stuff!!!
Von: torbennehmer ***@***.***>
Gesendet: Mittwoch, 9. August 2023 10:44
An: torbennehmer/hacs-e3dc ***@***.***>
Cc: Marco Vögele ***@***.***>; Author ***@***.***>
Betreff: Re: [torbennehmer/hacs-e3dc] Additional Production (Issue #43)
Please add a diagnostics dump. If you don't want to upload it here, you can use https://kurzer.link/e3dcrscp as an alternative.
—
Reply to this email directly, view it on GitHub<#43 (comment)>, or unsubscribe<https:/notifications/unsubscribe-auth/A7G547U5YS7A72NEURQYR53XUNEWHANCNFSM6AAAAAA3I7LLUE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@MarcoAVoegele Yes, that's true, those sensors are not active by default. Please drop me a diagnostic dump nevertheless: I'd like to check if I can automatically enable the sensor in some way. To get into this, I'd need that dump, my own unit does not have an additional source, thus I cannot really analyze this no my end. |
Hi, yes I can do it. What do I need to do, so that you get the required information?
Von meinem iPhone gesendet
Am 09.08.2023 um 19:36 schrieb torbennehmer ***@***.***>:
@MarcoAVoegele<https:/MarcoAVoegele> Yes, that's true, those sensors are not active by default. Please drop me a diagnostic dump nevertheless: I'd like to check if I can automatically enable the sensor in some way. To get into this, I'd need that dump, my own unit does not have an additional source, thus I cannot really analyze this no my end.
—
Reply to this email directly, view it on GitHub<#43 (comment)>, or unsubscribe<https:/notifications/unsubscribe-auth/A7G547SXEJINCJ5B5EXEOIDXUPDA5ANCNFSM6AAAAAA3I7LLUE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
It does not download the file…
***@***.***
Von: torbennehmer ***@***.***>
Gesendet: Mittwoch, 9. August 2023 19:55
An: torbennehmer/hacs-e3dc ***@***.***>
Cc: Marco Vögele ***@***.***>; Mention ***@***.***>
Betreff: Re: [torbennehmer/hacs-e3dc] Additional Production not enabled automatically if present (Issue #43)
Go to the device in the HA setup, klick the tripledot menu and download the diagnostics dump from there. It'll contain a lot of information queried from the unit, that give me an impression how it reacts to API calls.
[Das Bild wurde vom Absender entfernt. image]<https://user-images.githubusercontent.com/2812067/259502314-16514e44-0de8-46be-87a2-98d2f41e330b.png>
—
Reply to this email directly, view it on GitHub<#43 (comment)>, or unsubscribe<https:/notifications/unsubscribe-auth/A7G547UG4PTU5Q3IS75NOILXUPFGRANCNFSM6AAAAAA3I7LLUE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Please check if you're using the latest version of the integration. |
Release 3.4 should add all additional productions as their own powermeters. Please validate this against your requirements. If it works, it would be great if you could send me one final diagnostics dump, I'll probably deprecate the old sensors at this point, but I'd like to verify if possible. |
We had the same issue until I found the disabled entity. However, here's the requested dump. |
System Health details
./.
Checklist
Describe the issue
There is no "sensor.s10e_pro_additional_production" or similar showing up in entities, although there is an E3DC external inverter with additonal 2 strings installed.
Reproduction steps
...
Debug logs
Diagnostics dump
No response
The text was updated successfully, but these errors were encountered: