[BUG] AVM Binding on openhab 4.3

Setup, Configuration and Use Installation
1
  • Platform information:
    • Hardware: rasperry pi 5, 64bit,
    • OS: Debian 12.9
    • Java Runtime Environment: Zulu 17
    • platform is used and what version_
    • openHAB version: 4.3
  • Issue of the topic: Fritz devices unknown

After the Fritzbox was upgraded to 8.0.1, the avm binding no longer works.
Automatic searching does not work either.
Manually creating the devices with the correct are leaves the status at unknown.
Interesting is that in the Fritzbox the devices are now called e.g. Fritz!Energy or Fritz!Connect
Does anyone have an idea?

2

While I noticed the binding might need to be turned off and on again in case the Fritzbox rebooted, it works here as before. When the Fritzbox reboots, the binding access lease is gone, so the binding must login again. That appears to not work automatically anymore under OH4.3.

3

Hello Thomas, I think there is a misunderstanding.
I reinstalled the binding (because it didn’t work), the status is . But the detection doesn’t work (I set the switch in the config).
Manual entry doesn’t help either. Booting the Fritzbox isn’t the solution either.
I think the binding has a problem with the new font of the device.
But unfortunately there is no one (developer) who can analyze the trace.

4

new insight

A completely new installation does not solve the problem.
The AVM adapters are not recognized.

5

Hi Joachim,

just tested this with a new Fritz Dect 200 (FRITZ!Smart Energy 200)

image
image915×425 21.3 KB

It’s instantly in the Inbox:

image
image752×368 14.3 KB

I didn’t add any Items, but the Thing is online:

image
image722×66 4.11 KB

So at least it isn’t a general problem with the Binding. Other AVM Items work without any issue.
I’m on openHAB 4.3.2 in Docker and the Fritzbox is on 8.0.2.

6

I also had problems with some old Magenta Power Switches. I was able to solve it by deleting the things, they were discovered and started working again with the previously linked items.

7

I have installed oh4 on a Debian 12.
Binding installed, nothing is found.

The same on a rasperberry 5.

What could it be?

8

2025-02-16 20:56:45.423 [DEBUG] [l.discovery.AVMFritzDiscoveryService] - Discovered unsupported device: [ain=xxxxxxxxxxx,bitmask=320,isHANFUNDevice=false,isHANFUNButton=false,isHANFUNAlarmSensor=false,isButton=false,isSwitchableOutlet=false,isTemperatureSensor=true,isHumiditySensor=false,isPowermeter=false,isDectRepeater=false,isHeatingThermostat=true,hasMicrophone=false,isHANFUNUnit=false,isHANFUNOnOff=false,isDimmableLight=false,isColorLight=false,isHANFUNBlind=false,id=49,manufacturer=AVM,productname=FRITZ!Smart Thermo 301,fwversion=05.21,present=1,name=FRITZ!DECT 301 UG Küche,battery=30,batterylow=1,null,null,null,[tist=42,tsoll=42,absenk=32,komfort=42,lock=0,devicelock=0,errorcode=0,batterylow=1,windowopenactiv=0,windowopenactiveendtime=0,boostactive=0,boostactiveendtime=0,battery=30,nextchange=[endperiod=1739736000,tchange=32],summeractive=0,holidayactive=0],[celsius=21.0,offset=-2.0],null,null,null,null,,null]

After I Switch To Debug Mode…

9

Only as a test: Is the device working in the Fritz Smarthome App?
I haven’t got a device like this. Only switches and security contacts.

10

Yes, it’s working fine with the avm smartphone app