home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
69.75k stars 28.91k forks source link

Fronius Smart Meter missing after adding BYD Battery #119151

Closed LDprg closed 16 hours ago

LDprg commented 3 weeks ago

The problem

I have a Fronius Gen 24 with two Smart Meters and a BYD Battery. The two Smart Meters were working fine until I added the BYD Battery recently. One of the two Smart Meters suddenly disappeared (other one and the battery working fine).

On the Fronius Gen24 itself everything is working as expected.

What version of Home Assistant Core has the issue?

core-2024.6.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Fronius

Link to integration documentation on our website

https://www.home-assistant.io/integrations/fronius

Diagnostics information

Couldn't download any, hitting the button just does nothing.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Couldn't find any suspicious logs from Fronius Integration.

Additional information

No response

home-assistant[bot] commented 3 weeks ago

Hey there @farmio, mind taking a look at this issue as it has been labeled with an integration (fronius) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `fronius` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign fronius` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


fronius documentation fronius source (message by IssueLinks)

farmio commented 3 weeks ago

Hi 👋! Can you add some information about your system and a diagnostic download?

LDprg commented 3 weeks ago

@farmio I cant download diagnostic of the whole fronius integration since clicking the download button doesn't start any download. I tried different browsers, but no success. However the independent devices work.

But here are my Fronius specs: Fronius Gen24 10 Fronius Gen24 4 (because the Gen23 10 couldn't handle the produced power on it own ) 2* Smart Meter TS 65A-3 (one for Battery and one for Heatpump) BYD HVM Battery 11kWh

Here are the device diagnostics (The smart meter from the heatpump missing, since as mentioned it isn't available since adding the battery) config_entry-fronius-d81e9a6045d9375078f2cfeb03976464 (2).json config_entry-fronius-d81e9a6045d9375078f2cfeb03976464 (1).json

config_entry-fronius-e1fb34e8f8ac551f682c06b570102cc3 (2).json config_entry-fronius-e1fb34e8f8ac551f682c06b570102cc3 (1).json config_entry-fronius-e1fb34e8f8ac551f682c06b570102cc3.json

LDprg commented 3 weeks ago

Here are also my system info:

Version     core-2024.6.1
Installationstyp    Home Assistant Container
Entwicklung     false
Supervisor  false
Docker  true
Benutzer    root
Virtuelle Umgebung  false
Python-Version  3.12.2
Betriebssystemfamilie   Linux
Betriebssystem-Version  6.8.5-zabbly+
CPU-Architektur     x86_64
Zeitzone    Europe/Vienna
Konfigurationsverzeichnis   /config
farmio commented 3 weeks ago

Oh, there seems to be a bug with diagnostics downloads currently https://github.com/home-assistant/frontend/issues/21061

The second batch of diagnostics you uploaded seem to see 2 meter devices. I can't see (it's redacted) if they maybe have similar serial numbers - which would be odd, but would explain why only one is seen.

LDprg commented 3 weeks ago

Oh, there seems to be a bug with diagnostics downloads currently https://github.com/home-assistant/frontend/issues/21061

The second batch of diagnostics you uploaded seem to see 2 meter devices. I can't see (it's redacted) if they maybe have similar serial numbers - which would be odd, but would explain why only one is seen.

I mean they have been working before in homeassitant. And in the Fronius UIs both Smartmeter work as expected. Just they that one is not visible.

Also I checked, I accidentally downloaded and uploaded the diagnostic from the smartmeter that works twice. So they are actually the same file and smartmeter. I couldn't download the diagnostic of the not visible Smartmeter because well it is not visible and therefore the menue is missing.

crallian commented 3 weeks ago

I think I have the same issue, Gen24 with BYD battery. Single Smart Meter TS 65A-3. Smart meter data not visible anymore in HA after upgrade from 2024.3 to 2024.6.2

LDprg commented 3 weeks ago

@farmio I got the problem solved. The issue is that when adding the battery the integration resets all the names. My first smartmerter had the default name, but the second was renamed. So the second smartmeter got reseted and had the default name with a number afterwards, Because of the similar names I didn't noticed that it still existed.

The Integration shouldn't rename Smart Meters that didn't change when reinitializing the device because of another added component.

farmio commented 3 weeks ago

I have no explanation for why that happened. The changed name is stored in HAs internal device registry entry - which is linked to the device by its serial number. So if you didn't remove and re-add the integration these changes shouldn't be touched by adding another device.

issue-triage-workflows[bot] commented 1 week ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.