AVM FRITZ!Box Tools: no Wifi on/off switches in Access Point mode

[fplanque]

The problem

When the integration handles a Fritzbox configured as a router, there are switches like switch.fritz_box_7490_wi_fi_network_name that allow to turn the radios on and off (2 switches, one for 2.4 and one for 5 GHz)

But when the integration handles an (additional) Fritzbox that is configured as a WiFi access point (not router, just connecting to existing network through LAN1 and provding a WiFi access point), then those switches are not present.

I can't think of any reason why those switches would not be exposed by fritz!os in that case, therefore I believe it is an oversight in the integration. Am I mistaken?

What version of Home Assistant Core has the issue?

core-2024.5.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!Box Tools

Link to integration documentation on our website

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

Diagnostics information

{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2024.5.5",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.12.2",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/Luxembourg",
    "os_name": "Linux",
    "os_version": "6.6.29-haos",
    "supervisor": "2024.05.1",
    "host_os": "Home Assistant OS 12.3",
    "docker_version": "25.0.5",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {
    "omada": {
      "documentation": "https://github.com/zachcheatham/ha-omada",
      "version": "0.4.0-beta.1",
      "requirements": []
    },
    "hacs": {
      "documentation": "https://hacs.xyz/docs/configuration/start",
      "version": "1.34.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    }
  },
  "integration_manifest": {
    "domain": "fritz",
    "name": "AVM FRITZ!Box Tools",
    "codeowners": [
      "@mammuth",
      "@AaronDavidSchneider",
      "@chemelli74",
      "@mib1185"
    ],
    "config_flow": true,
    "dependencies": [
      "network"
    ],
    "documentation": "https://www.home-assistant.io/integrations/fritz",
    "iot_class": "local_polling",
    "loggers": [
      "fritzconnection"
    ],
    "requirements": [
      "fritzconnection[qr]==1.13.2",
      "xmltodict==0.13.0"
    ],
    "ssdp": [
      {
        "st": "urn:schemas-upnp-org:device:fritzbox:1"
      }
    ],
    "is_built_in": true
  },
  "data": {
    "entry": {
      "entry_id": "6b95b9bf47f54553704833d0911c3d99",
      "version": 1,
      "minor_version": 1,
      "domain": "fritz",
      "title": "FRITZ!Box 7490 K3",
      "data": {
        "host": "192.168.178.40",
        "password": "**REDACTED**",
        "port": 49000,
        "username": "**REDACTED**"
      },
      "options": {
        "consider_home": 5,
        "old_discovery": false
      },
      "pref_disable_new_entities": false,
      "pref_disable_polling": false,
      "source": "user",
      "unique_id": null,
      "disabled_by": null
    },
    "device_info": {
      "model": "FRITZ!Box 7490",
      "unique_id": "5C4979XX:XX9",
      "current_firmware": "7.57",
      "latest_firmware": "",
      "update_available": false,
      "connection_type": "WANPPPConnection",
      "is_router": false,
      "mesh_role": "slave",
      "last_update success": true,
      "last_exception": null,
      "discovered_services": [
        "any1",
        "WANCommonIFC1",
        "WANDSLLinkC1",
        "WANIPConn1",
        "WANIPv6Firewall1",
        "DeviceInfo1",
        "DeviceConfig1",
        "Layer3Forwarding1",
        "LANConfigSecurity1",
        "ManagementServer1",
        "Time1",
        "UserInterface1",
        "X_AVM-DE_Storage1",
        "X_AVM-DE_WebDAVClient1",
        "X_AVM-DE_UPnP1",
        "X_AVM-DE_Speedtest1",
        "X_AVM-DE_RemoteAccess1",
        "X_AVM-DE_MyFritz1",
        "X_VoIP1",
        "X_AVM-DE_OnTel1",
        "X_AVM-DE_Dect1",
        "X_AVM-DE_TAM1",
        "X_AVM-DE_AppSetup1",
        "X_AVM-DE_Homeauto1",
        "X_AVM-DE_Homeplug1",
        "X_AVM-DE_Filelinks1",
        "X_AVM-DE_Auth1",
        "X_AVM-DE_HostFilter1",
        "X_AVM-DE_USPController1",
        "WLANConfiguration1",
        "WLANConfiguration2",
        "WLANConfiguration3",
        "Hosts1",
        "LANEthernetInterfaceConfig1",
        "LANHostConfigManagement1",
        "WANCommonInterfaceConfig1",
        "WANDSLInterfaceConfig1",
        "X_AVM-DE_WANMobileConnection1",
        "WANDSLLinkConfig1",
        "WANEthernetLinkConfig1",
        "WANPPPConnection1",
        "WANIPConnection1"
      ],
      "client_devices": [
        "**REDACTED**",
        "**REDACTED**"
      ],
      "wan_link_properties": {
        "NewWANAccessType": "Ethernet",
        "NewLayer1UpstreamMaxBitRate": 512,
        "NewLayer1DownstreamMaxBitRate": 1024,
        "NewPhysicalLinkStatus": "Up",
        "NewX_AVM-DE_DownstreamCurrentUtilization": "0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0",
        "NewX_AVM-DE_UpstreamCurrentUtilization": "0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0",
        "NewX_AVM-DE_DownstreamCurrentMaxSpeed": 0,
        "NewX_AVM-DE_UpstreamCurrentMaxSpeed": 0
      }
    }
  }
}

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

drag & drop of diagnostics did not work

[home-assistant]

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

Code owner commands

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

---

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

[chemelli74]

Hi @fplanque, your device is in

"mesh_role": "slave",

this means that the on/off is created only for the master.

[fplanque]

@chemelli74 thank you, do you know how to change from slave to master?

in the fritzbox UI I unchecked "Switching wireless devices automatically between the 2.4-GHz and the 5-GHz frequency bands and between multiple FRITZ! products in the Mesh" both on the router and on the AP, I then rebooted the AP and re-registered it anew in Home Assistant. The diagnostics file still shows mesh_role": "slave",. Can I switch it to master?

[chemelli74]

The status depends on the mesh configuration. Is not something you can manually change.

[fplanque]

Ok, once I turned on WiFi radios, I did see the Mesh configuration (it is hidden when radios are off).
When I changed the Wifi Mesh UI setting to master, it reconfigured the whole FritzBox as an internet router and no longer a standalone access point.
So from the fritzbox UI, it seems the router/no router and the mesh master/slave configurations are interlinked...

Yet, from the Home Assistant Integration diagnostics file, there seem to be 2 distinct properties:

      "is_router": false,
      "mesh_role": "slave",

Can you shed some light on that?

Do you know if these two properties can be set independently somehow (so 4 states total, not just 2) ?

Thank you.

[mib1185]

Hi @fplanque
i think these are question for the manufacturer AVM.
Nevertheless, as long as a fritzbox is a mesh slave, it is steered from the mesh master, therefore we do not create wifi switches for those devices in HA.

[fplanque]

@mib1185 you say:

therefore we do not create wifi switches

So it is your decision -- when developing the integration -- to intentionally not create the switches?

I want to strongly make the case that, if those switches can be created, they definitely should be created. And this for the following reasons:

1. When I have my second fritzbox as a mesh slave, I still can manually turn the radios on/off in the (slave) fritzbox UI. (But I'd like to do this in in home assistant which is both more convenient and also allows to automate turning off when tasks that require wifi are finished for the day).
2. When I have my second fritzbox as a mesh slave (still) and I actually switch the radios on/off on my first (master) fritzbox, those master switches impact only the master. Those switches on the master do not control the radio on/off of the slave.

I think, this proves that, even if many wifi settings are steered by the mesh master, the fact that a slave has its radios on or off is not steered by the master.

I tested this again today. I could post a dozen screenshots but I don't think it brings much more than what I explain.

So, if you can create those switches also for the slave, please please do.

Now, if you can't, please confirm clearly that it is AVM who has chosen not to expose this function when the fritzbox is a slave. In that case I will definitely enquire by AVM (But at this point you seem to say it is you/devs of the integration who deciced to not create the swicthes.)

Thank you.

[fplanque]

@mib1185

Can you please confirm that there is no point in me contacting AVM about exposing the wifi radio switches (in the context of fritzbox used as Access Point) because these switches are already exposed by the fritzbox and it's just the HA integration that is not "passing them through" to HA?

Also, if you do have a setup where the slave radios are actually controlled by the master whereas they are not for me, I believe there are actually 3 modes:

• Mesh Master
• Mesh Slave (as you describe it)
• Independent access point (as I have it setup)

I believe that 3rd "Access Point" mode is enabled through this screen:

Notice I have "other internet service provider" on my "slave/AP" fritzbox.
I (purposedly) did not select "existing connection over LAN".
In my config, the slave fritzbox "connects" to the master only by requesting a DHCP config. Very minimalistic.
In the other "existing connection" config (which I personally don't want), I understand there may be a PPPoE passthrough tunnel, which indeed would allow the master to control the slave in all sorts of ways...

EDIT 2024-01-04: I tried a setup with a second fritzbox connected as "existing connection over LAN". What this does is that it makes the second fritzbox act as its own router with its own subnet like 192.168.188.x instead of 192.168.178.x . I believe this actually totally prevents any meshing between the first and the second fritzbox. Therefore I no longer believe this setting to be relevant to my situation and there may indeed be only 2 cases: meshed and not meshed.

There is definitely a setup possible where the master does not control the slave and where turning the master radios on/off does not impact the slave radios. There may be more master/slave things not working in this "AP mode" but it doesn't matter to me, it is really the scenario that I want to use my fritzboxes by: independently control which floors of the house have wifi on or off. For example: at night I like the wifi next to the bedrooms off while I still may need to use the wifi in the basement.

Can you please enable the missing switches somehow? (even if they have to be hidden under some advanced config option)

Thank you.

PS: all boxes on FRITZ!OS: 7.57

[issue-triage-workflows]

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.

[fplanque]

@mib1185 Could you please reply? (Even if it's "I don't know" or "I don't have time to look into it")
Thank you.