I think you still have the old custom components FRITZ!Box Tools
As the issue on GitHub shows, it installs incompatible dependencies.
Simone
1 Like
@chemelli Yes I do, as the new integration doesnāt yet provide control over profiles which the old custom component did - at least last time I tested it.
Iāve just stripped that out to test if it helps, and so far itās looking promising.
Does the integration now provide that control too, so the old custom component can be binned?
OK removing the old custom integration and reinstalling the AVM one has got things back up and running.
But my set-up was using the profile and wifi controls from the old custom integration, which are missing from the new one.
@chemelli is there any plan to include that functionality into the new integration, so the full functionality is available again? My set up was rather relying on being able to switch access profiles and wifi on/off via HASS and Iād rather not have to work out a new solution for thatā¦
Can you give me a link to the GH issue so I can look at it?
The new one is missing profiles (which I never used) and port-forwarding which I did but WiFi is there as per the defunct CC nowā¦
Iāve found profiles now in the new integration, but I canāt see wifi switches for guest, 2.4GHz and 5.0 GHz. What entities are they?
Edit - never mind, found the normal wifi ones. Guest is missing, but itās currently disabled so probably hasnāt been found yetā¦
If itās disabled you need to enable itā¦
EDIT I do see profiles but no port forwarding controlā¦
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
1 Like
@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?