AVM FRITZ!SmartHome - Missing Entitäten Fritz Zigbee Devices

Peter1980FFM commented 9 months ago

The problem

Hi have some Zigbee devices in my Fritzbox and in Home Assistant not all Entitäten are Show.

What version of Home Assistant Core has the issue?

core-2023.12.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

AVM FRITZ!SmartHome

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 9 months ago

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

Code owner commands

Code owners of `fritzbox` 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 fritzbox` 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)}}

fritzbox documentation fritzbox source _{^{(message by IssueLinks)}}

mib1185 commented 9 months ago

Hi @Peter1980FFM

please enable debug logging, restart HA and provide the home-assistant.log. To do so add the following to your configuration.yaml:

logger:
  default: info
  logs:
    homeassistant.components.fritzbox: debug
    pyfritzhome: debug

Further if possible please download and provide the diagnostics data for this integration.

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

Peter1980FFM commented 9 months ago

@mib1185 Danke für die Schnelle Antwort home-assistant_fritzbox_2023-12-31T12-28-35.419Z.log Ich hoffe das ist das Richtige :-)

Peter1980FFM commented 9 months ago

FYI Template i have crate in the Fritz Device are show. Only the Groups of Devices are missing

mib1185 commented 9 months ago

the logfile is good 👍 please also provide the diagnostics data

Peter1980FFM commented 9 months ago

config_entry-fritzbox-76a34de47a331963a19f9a3241f29eef.json.txt now the Device Diagnostic. So i have to create a issue by pyfritzhome?

mib1185 commented 9 months ago

sorry for the confusion ... i've moved the part about the Fritz Smart Gateway into #106766 and we should keep this both issues separated, because in #106766 it is about the support of the new Fritz Smart Gateway and here in #106767 it is about the support of groups from the Fritz!Box itself. For both the pyfritzhome needs to be extended to support it.

So we need two new feature requests in pyfritzhome

support for group (_see chapter 3.2 in avm api docs_)
support for zigbee units (_see chapter 1.2 in avm api docs_)

Peter1980FFM commented 9 months ago

I have open it

HelgeGitHub commented 8 months ago

Here is the debug log for "AVM FRITZ!SmartHome - Aeotec Water Leak Sensor - Samjin water - missing battery value/level and SW version (see also Issue #107526)" debug_log_AVM FRITZ!SmartHome - Aeotec Water Leak Sensor - Samjin water (was Issue #107526).txt

It seems, as already seen in the config file: There are two entries for each zigbee device having different device IDs, where the second one is derived from the first by an appended "01". The first one contains all device information and the second one the operational information.

The same situation I found for my Telecom motion detector. But in this case the second device ID was extended by "-1" at the end. debug_log_AVM FRITZ!SmartHome - telecom motion detector.txt

config_entry-fritzbox-SmartHome - telecom motion detector.json.txt

mib1185 commented 8 months ago

thanks @HelgeGitHub if you are interested, in chapter 1.2 in the avm api docs you'll find the explanation how these IDs are build

issue-triage-workflows[bot] commented 5 months 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.

Peter1980FFM commented 5 months ago

Hello when will the Fully Implementation in Home Assistent? Party Implemation Done

issue-triage-workflows[bot] @.***> schrieb am Mo., 8. Apr. 2024, 11:07:

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.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/106767#issuecomment-2042240679, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKZLJW6JEM3ZR6NIGRD7IVDY4JM4BAVCNFSM6AAAAABBIFJ5ACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSGI2DANRXHE . You are receiving this because you were mentioned.Message ID: @.***>

HelgeGitHub commented 5 months ago

As mentioned above the issue "AVM FRITZ!SmartHome - Aeotec Water Leak Sensor - Samjin water - missing battery value/level and SW version (see also Issue https://github.com/home-assistant/core/issues/107526)" is solved: Battery level and SW version are provided.

But the issue for the "Telecom motion detector" is still not solved (same situation as before). HA shows the values of device "11324 0870192-1" instead device "11324 0870192"

config_entry-fritzbox-a09bba0e0cf1cfa300a3ed0cb50ab9f8.json

mib1185 commented 5 months ago

Hi @Peter1980FFM unfortunately the full support needs some more changes in the integration, especial the logic how devices and sub-devices are merged and this without breaking existing HA setups ... did just not find the time to do this

issue-triage-workflows[bot] commented 2 months 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.

home-assistant / core