Fritz!box sockets switch very slowly

[t785634]

The problem

If I want to switch on a Fritz!Box socket via Home Assistant, it takes a very long time until it is switched on and the entity is updated.

What version of Home Assistant Core has the issue?

core-2024.2.5

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]]

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]

What do you mean with "very long"? Further is there a delay between toggle the switch in HA and the real devices switches?

[Rincewind77]

Maybe that's the same issue as I have:

The problem

I have a FRITZ!DECT 200 running on a FritzBox 4060.

When I activate the switch in HA, the physical and the graphical switch get activated. But after 1-2 seconds, the graphical switch in HA toggles back to disabled, but the physical switch stays active. When I then activate the graphical switch in HA again, it stays activate as well as the physical switch.

Disabling the switch later on, behaves the same, just the other way around.

What version of Home Assistant Core has the issue?

I have fresh installed version 2024.3.3.

What was the last working version of Home Assistant Core?

As I am new to Home Assistant, it never worked for me.

What type of installation are you running?

Standard Home Assistant OS on a Raspberry Pi 5.

Please let me know what other information I can provide to help you here.

[t785634]

The delay is as rincewind77 describes it. „When I activate the switch in HA, the physical and the graphical switch get activated. But after 1-2 seconds, the graphical switch in HA toggles back to disabled, but the physical switch stays active.“ After 30 seconds later the graficial switch in HA entity goes back to the on state as it is the real switch.

[Just-Zuul]

Have the same Problems like rincewind77 described. FritzBox 7590 with Fritz Dect 200 and 210 (6 Devices)

Also the refresh of the Values (actual Watts) some Times refresh in 5 to 10 Seconds - Sometimes in 5 - 30 Minutes (??)

Actual HA running in a virtual Maschine on a Synology NAS - all Ressources (CPU RAM) are enough free Space.

[mib1185]

Hi @t785634

please enable debug logging, toggle the switch in HA, wait ~90s and than provide the log file (will automatically be downloaded when disabling debug logging).

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.

thx 👍

[Rincewind77]

I ran the debug procedure on my HA. Please find the debug logs attached. home-assistant_fritzbox_2024-04-02T16-43-04.487Z.log

[issue-triage-workflows[bot]]

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.

[t785634]

For me the problem was not solved with version 2024.4.3

[Rincewind77]

Updating to version 2024.4.3 did also not fix the problem for me.

[mib1185]

@Rincewind77 the provided log does not met the requested log in https://github.com/home-assistant/core/issues/113749#issuecomment-2030544613 - it does not show any switch toggle action

[mib1185]

@t785634 do you mind to also provide the requested debug log?

[Rincewind77]

@mib1185 sure, attached the latest log. I hope I did it correct this time. I talk about a "FRITZ!DECT 200" switch btw.

home-assistant_fritzbox_2024-04-23T17-29-34.044Z.log

[issue-triage-workflows[bot]]

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.

[Rincewind77]

With version 2024.5.2 I still have the same issue.

[julian-vl]

I also have this issue. For me it also leads to the problem, that a script that turns multiple devices on or off doesn't work reliably with the FRITZ device.

[t785634]

@t785634 do you mind to also provide the requested debug log?

Do you still need my log or do you use rincewind77s log?

[issue-triage-workflows[bot]]

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.

[Rincewind77]

With version 2024.5.5 I still have the same issue.

[issue-triage-workflows[bot]]

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.

[BigAl66]

Before I used Home Assistant I wrote my own tool to set and display the state of the FritzBox devices. My tool polls every 5 seconds the state of the devices. When I trigger a device, I force the local state to the new state and reset the timer for the polling. After 5 seconds the next poll will be executed and the state is all the time correct. This worked perfectly.

Now using Home Assistant I have the same problem that many users have. I trigger the switch and it jumps back to its old position. After 30 seconds the new position is shown. I think the time between activating the device and polling the status is just too short. It would be nice if this time could be configured.

This belongs for me only to the status update. As soon I trigger a switch it is immeditaly activated / deactivated.

[t785634]

@mib1185 Do you still need my log or do you use rincewind77s log? Because the issue is labeled with [needs-more-information]

[BigAl66]

@mib1185 Do you still need my log or do you use rincewind77s log? Because the issue is labeled with [needs-more-information]

In the meantime I replaced all my sockets with Tasmotas. So the problem is gone. Thank you!

[issue-triage-workflows[bot]]

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.

[Rincewind77]

With version 2024.7.2 I still have the same issue.

[t785634]

Is it possible to increase the update interval?

[issue-triage-workflows[bot]]

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.

[Rincewind77]

With version 2024.7.4 I still have the same issue.

[issue-triage-workflows[bot]]

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.

[mib1185]

in progress