Yup, entirely as expected. Just done so and it’s now set itself up, and working fine.
I do of course disable it when not in use, hence why it hadn’t been picked up yet.
So I’m now back up and running again, with only difference being the lack of port forwarding control (which I wasn’t currently using anyway). And the old custom component is now binned.
False 
Check better both the documentation and the entities created.
Old custom integration from 2021.7 on is completely redundant and no more developed.
Simone
Check better under the entities created 
They are just disabled by default, but they are there.
Simone
@chemelli - yes, found them all now and everything I had with the old custom component I now have with your new integration. The old CC is removed completely and my set-up is up and running fine again.
Thanks for all your work on the integration (and the transition from the old CC to it), highly appreciated 
Concerning the port forwarding - is that still limited to just the ports going to the HA device IP address as it was in the old CC? I don’t see any at the moment, but I don’t have any ports forwarded to the HA device, only to others on my network.
Port forwarding control? I don’t see that
yes, unfortunately it’s a limit of AVM api implementation.
Simone
If the destination devices is the HA server, then you should have them. If not open a issue.
If the destination is another, you cannot get them created as per AVM api limitation.
Simone
It was working with the custom_component. I generally don’t enable UPnP though so maybe that is the issue? The docs are a little light on for this…
Nope, it wasn’t. As I wrote it’s a AVM api limit.
Simone
Opened a PR to improve documentation: Add Fritz missing info for device profiles and port forwards by chemelli74 · Pull Request #18431 · home-assistant/home-assistant.io (github.com)
I just remember everyone that all of us can improve docs easily
Simone
@chemelli do you think it worth adding a note about the incompatibility with the older custom component too, or would it be fine to just let that one die off naturally?
Just thinking for anyone else who still has it installed like I did, and would need to remove it now that its functionality is fully depreciated and incorporated into the integration.
I’m fine to PR the docs change if it’s worthwhile.
Custom components are not port of Home Assistant Core and will not be referenced.
We are working on an update of the custom components that will fire a notification so all users will be informed.
Simone
Fair enough, sounds fine to me.
Just don’t want others to hit the same issue I did last night, as that was most frustrating as it look a lot of functionality down due to the breakage of data flow from the router.
That is true but you need to know the option actually exists to improve/add to the docs. I only knew this existed because of the old custom component - the HA docs don’t even mention it.
I don’t understand what you mean by API limit.
I do understand you can only enable/disable port forwards for the device running Home Assistant (I see that from the custom component docs)
On a dev instance of HA with port forwards I DO see that switch but I have only port 80 forwarded on that instance and it’s a http forward. On my main production HA instance I don’t see the switch at all BUT it is only opening ports to the public IPv6 address of the device and it’s https not http - is that why? I also don’t enable the “Allow Independent Port Sharing” for any device as I’ve always thought that was a security risk? It doesn’t seem necessary to enable that on my dev instance but the docs for HA don’t say so I don’t know!
So I guess I’m asking does the port forwards switch only appear if you have http forwards configured? Does Independent port sharing need to be configured?
Good morning, I have Fritzbox 7590 plus 1750e repeater plus 3000 repeater, all in a mesh setup. I need to track with router source 2 smartphones, I did all the things required passing from old custom integration to the new official one, i.e. removing old yaml config, adding new discovered integrations, enabling smartphones device tracker found, setting a 15 sec period to consider home, BUT my phones that are connected to my wifi ARE ALWAYS SEEN NOT HOME!!!
EDIT: after abiliting specific log, I don’t see any error or warning about fritzbox device_tracker, it simply doesn’t work in my setup and I can’t figure how to solve
I have switches for all my ports, not only for https.
IIRC, there is not yet support for port-ranges.
I don’t have independent port sharing enable for that device.
Simone
Open a issue on GitHub and attach debug log.
Simone
Are they only for IPv4 forwards though? I only have ports opened to the IPv6 address of HA.
We can try to check if something appears in debug logs, add the following to configuration.yaml , restart HA, and post the logs near the error:
logger:
default: warning
logs:
homeassistant.components.fritz: debug
fritzconnection: debug
fritzprofiles: debug
Note: logs may be hard to read here, it is better to use a service such as https://pastebin.com/ for uploading the log.
About what issues are we even talking about here? Or is this for all “new” problems?
If so, I already answered in the Github issue for the “connection pool error”. But to bring it up here as well, here is the link to pastebin: