AVM lately released firmware 8.0 for several box types. Has anyone already tried to use the binding with this firmware? Any hints or trouble?
I don’t want to upgrade my box and then run into trouble…
No issues on my side
2 Likes
For me too. All works fine.
1 Like
Same here, 7590AX² but no problems before and after upgrading to v8.0…
1 Like
I control my heating system (DECT 301/302) via OpenHAB and trigger templates to change heating schemes. Do you use something similar?
I have three Fritz! boxes in a mesh network. Two are running firmware 8.0. The primary Fritz!Box for AVM’s Smarthome products for openHAB is still running version 7.56. I have already upgraded the 7590 to version 8 several times with the result that no AVM Think was accessible via openHAB. In the end, the only option so far has been to downgrade to 7.56 so that everything works smoothly again. Even individual DECT 200 sockets to which I have assigned a different Fritz!Box (firmware 8.0) as a bride cannot be switched. If I reassign the socket to the box with the 7.56 firmware, I can switch it again. I have not yet found a solution…
Hi, same for me. No Smarthome-Thing (3x FRITZ!DECT 302, 1x 440) is working any more (Status: Gone) Fritzbox itself seems to work, at least the status is online. If I don’t find a solution or workaround I have to downgrade again.
edit: After Upgrade to 4.3.1 with reboot of Server the things are working again 
Hi,does this mean that firmware 8.0 is now running and the Smarthome products communicate with openhab? If that’s the case, then I’ll upgrade my last box too.
At least it works in my smarthome network with OpenHAB 4.3.1 and FritzOS 8.01
Hm, FritzOS 8.01? Where can I find this version? I still have 8.00.
It has not been rolled out for all Fritz!Box types.
Thanks for the Information.
After upgrading to FritzOS 8.02 and restarting openhab, communication is now running without any problems. 
Same here. I’m still on OH 2.5 and after update to fritzOS 8.02 no issues. Both bindings fritzboxtr064 and avmfritz are working.
Just a hint. Sometims, if you reboot the fritzbox, it is needed to reboot OH too. Because avmfritz binding cannot connect again. Cannot be solved by rebooting the binding, OH needs to be rebooted
Just updated to FritzOS 8.02 (from 8.0) and had to reboot OH (4.3.2) to get the communication back. Don’t think I had to do that for any update before.
I updated my FRITZ!Box 7590 to FRITZ!OS 8.02 and experienced connection issues.
The details and my solution:
Environment:
openHAB 4.3.2
Ubuntu 24.04.2 LTS on x86_64
OpenJDK 64-Bit Server VM version 17.0.14+7-LTS
I have been controlling and recording the room temperature via AVM radiator controllers FRITZ!DECT 301 and FRITZ!DECT 302 and the corresponding openHAB AVM FRITZ! binding for years.
After the last update of my FRITZ!Box 7590 to FRITZ!OS 8.02, the connection from the radiator controllers to openHAB no longer worked reliably.
The connection was lost after every hour.
Restarting the bundle via openhab-cli console (bundle:restart org.openhab.binding.avmfritz) was able to revive the connection for one hour at a time.
I do not believe that the FRITZ!OS 8.02 version was the root cause of the phenomenon.
Presumably, the restart of the FRITZ!Box associated with the update merely brought the phenomenon to light.
The root cause is more likely to be an update of openHAB or at OS level, which only had an effect after the FRITZ!Box was restarted (I rarely do this).
When investigating the problem, I noticed:
1. Discovery
There were the following messages in the logs (which I had not observed before):
/var/log/openhab/events.log
[INFO ] [openhab.event.InboxRemovedEvent ] - Discovery Result with UID 'avmfritz:fritzbox:192_168_0_1' has been removed.
[INFO ] [openhab.event.InboxAddedEvent ] - Discovery Result with UID 'avmfritz:fritzbox:192_168_0_1' has been added.
/var/log/openhab/openhab.log
[INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'avmfritz:fritzbox:192_168_0_1' to inbox.
I configure openHAB completely via files.
The corresponding ‘Thing’ was already available, albeit under a different UID.
To avoid this effect, I deactivated Discovery:
In /etc/openhab/services/runtime.cfg I added:
discovery.avmfritz:background=false
This measure had no effect on the stability of the connection.
2. Timeout
In the post there is a reference to unfortunate timeout values in the default of the AVM FRITZ! Binding.
I have therefore adjusted my configuration.
Before
Bridge avmfritz:fritzbox:7590 "FRITZ!Box 7590" @ "Keller:Netzwerkschrank" [ ipAddress="192.168.0.1", password="...", user="xxx" ] {
Thing FRITZ_DECT_301 099950228106 "FRITZ!DECT 301 Vorratsraum" @ "Keller:Vorratsraum" [ ain="099950228106" ]
...
After
Bridge avmfritz:fritzbox:7590 "FRITZ!Box 7590" @ "Keller:Netzwerkschrank" [
ipAddress="192.168.0.1",
password="...",
user="xxx",
pollingInterval=60,
asyncTimeout=15000,
syncTimeout=10000
] {
Thing FRITZ_DECT_301 099950228106 "FRITZ!DECT 301 Vorratsraum" @ "Keller:Vorratsraum" [ ain="099950228106" ]
...
This measure had no effect on the stability of the connection.
3. Events on FRITZ!Box
On the FRITZ!Box: System > Events in the System tab
I noticed the following messages (192.168.0.194 is the computer on which I am running openHAB).
With an active, working connection
Login of the user xxx to the FRITZ!Box user interface from IP address 192.168.0.194.
If the connection is faulty
13.02.25 13:29:20 User xxx logs on to the FRITZ!Box user interface from IP address 2001:16b8:b58b:3a00:e498:4bcd:c283:7fe3.
13.02.25 13:29:21 Login to the FRITZ!Box user interface from IP address 192.168.0.194 failed (invalid session ID). To be on the safe side, all still valid sessions to IP address 192.168.0.194 are terminated.
I have set the log level for the bundle to DEBUG in openHAB via openhab-cli console:
log:set DEBUG org.openhab.binding.avmfritz
In openhab.log with active, working connection
2025-02-13 13:49:30.524 [DEBUG] [al.handler.AVMFritzBaseBridgeHandler] - Poll FRITZ!Box for updates avmfritz:fritzbox:7590
2025-02-13 13:49:31.343 [DEBUG] [nal.hardware.FritzAhaContentExchange] - HTTP response: 200
2025-02-13 13:49:31.361 [DEBUG] [nal.hardware.FritzAhaContentExchange] - HTTP response: 200
2025-02-13 13:49:31.378 [DEBUG] [nal.hardware.FritzAhaContentExchange] - GET response complete: <devicelist version="1" fwversion="8.02"><device identifier="08761 0007822" id="16" functionbitmask="35456" fwversion="04.25" manufacturer="AVM" productname="FRITZ!DECT 200"><pr ...
In openhab.log if the connection is faulty
2025-02-13 12:17:06.176 [DEBUG] [al.handler.AVMFritzBaseBridgeHandler] - Poll FRITZ!Box for updates avmfritz:fritzbox:7590
2025-02-13 12:17:08.065 [DEBUG] [nal.hardware.FritzAhaContentExchange] - HTTP response: 403
2025-02-13 12:17:08.066 [DEBUG] [nal.hardware.FritzAhaContentExchange] - HTTP response: 403
The IPv6 address in the FRITZ!Box events had surprised me.
So I deactivated IPv6.
a.)
in openHAB-GUI: Settings > Network (“Show advanced” if necessary)
I stopped openHAB: sudo systemctl stop openhab and
cleared the cache: sudo openhab-cli clean-cache
b.)
I disabled IPv6 at OS level to be on the safe side (see e.g. How to Disable IPv6 in Ubuntu 24.04. Since I am with Ubuntu 24.04 I had to have @reboot /usr/bin/sleep 15 && /usr/sbin/sysctl --system in the root crontab as mentioned in the link.)
I also checked “Einzelne IP-Adresse pro Interface” in openHAB-GUI: Settings > Network (“Show advanced” if necessary)
I restarted openHAB: sudo systemctl start openhab
Since this measure, deactivation of IPv6, the connection between FRITZ!Box 7590 with FRITZ!OS 8.02 and the openHAB AVM FRITZ! Binding is stable again.