[avmfritz] add door/window contact AVM FRITZ!DECT 350

[Giga522 (Jan)]

Are there any plans to add the door/window contact AVM FRITZ!DECT 350?

Different door contacts (from other manufacturers) are already integrated but will the AVM Fritz!Dect 350 device be natively integrated? Battery level additionally to the state would be awesome.

Thanks in advance!

I already opened an issue at GitHub.

https://github.com/openhab/openhab-addons/issues/16340

[sihui]

@Giga522

Are there any plans to add the door/window contact AVM FRITZ!DECT 350?

Did you find a way to integrate the sensor into openHAB?

[Giga522 (Jan)]

Yes, the original binding AVM FRITZ! supports it as HAN-FUN contact sensor.
It is only not mentioned.

[sihui]

@Giga522

Yes, the original binding AVM FRITZ! supports it

Thanks a lot, need to buy one now …

[MorsRene (Rene)]

Hi together,

What a pitty.

It works in the Fritz!Box! - Open and Close are recognized there.
But it doesn’t work in openHAB.

My openHAB Test-Script renders some Debug Output:

Debug Fensterkontakt_Schlafzimmer_FRITZSmart_Control_350_HANFUN_Kontakt_TurFensterZustand (Fensterkontakt_Schlafzimmer_FRITZSmart_Control_350_HANFUN_Kontakt_TurFensterZustand (Type=ContactItem, State=NULL, Label=Tür-/Fenster-Zustand, Category=Contact, Tags=[Point], Groups=[Schlafzimmer])) Wert: NaN uninitialized: true State: NULL rawState: NULL type: Contact

so it always says: Uninitialized

I tried adding a “-1” to the AIN

22:40:03.284 [DEBUG] [rnal.handler.AVMFritzBaseThingHandler] - Update thing 'avmfritz:HAN_FUN_CONTACT:192_168_178_1:f7751ccb77' with device model: [ain=15282 0274179-1,bitmask=8208,isHANFUNDevice=false,isHANFUNButton=false,isHANFUNAlarmSensor=true,isButton=false,isSwitchableOutlet=false,isTemperatureSensor=false,isHumiditySensor=false,isPowermeter=false,isDectRepeater=false,isHeatingThermostat=false,hasMicrophone=false,isHANFUNUnit=true,isHANFUNOnOff=false,isDimmableLight=false,isColorLight=false,isHANFUNBlind=false,id=2002,manufacturer=AVM,productname=FRITZ!Smart Control 350,fwversion=0.0,present=1,name=FRITZ!Smart Control 350 #21,battery=null,batterylow=null,null,null,null,null,null,null,[state=0],null,null,[],[etsideviceid=36,unittype=514,interfaces=256]]

and I tried without the “-1”
21:57:47.133 [DEBUG] [rnal.handler.AVMFritzBaseThingHandler] - Update thing 'avmfritz:HAN_FUN_CONTACT:192_168_178_1:f7751ccb77' with device model: [ain=15282 0274179,bitmask=1,isHANFUNDevice=true,isHANFUNButton=false,isHANFUNAlarmSensor=false,isButton=false,isSwitchableOutlet=false,isTemperatureSensor=false,isHumiditySensor=false,isPowermeter=false,isDectRepeater=false,isHeatingThermostat=false,hasMicrophone=false,isHANFUNUnit=false,isHANFUNOnOff=false,isDimmableLight=false,isColorLight=false,isHANFUNBlind=false,id=36,manufacturer=AVM,productname=FRITZ!Smart Control 350,fwversion=03.58,present=1,name=FRITZ!Smart Control 350 #21,battery=90,batterylow=0,null,null,null,null,null,null,null,null,null,[],null]

@Giga522 : Do you have any hints for me?

[Giga522 (Jan)]

Hi, maybe you have space between the numbers?

Right:
AIN:123456-1,
Wrong:
AIN:123 456-1

You do not need a script for checking. You can directly see the state of your item at the main ui under your DECT350 thing.

[MorsRene (Rene)]

@Giga522 yes, I know , but it is like this:

1. I have no space in the AIN
2. Using -1 or not at the end leads to a Thing which is “Online”, but nevertheless has an uninitialized state
3. The automatic discovery doesn’t work, so I added manually.

[MorsRene (Rene)]

Here some Screenshots.
As you see only NULL is returned as state

[Giga522 (Jan)]

Ok, it seams right but under your thing channel you need a contact item. There is the state saved. A thing alone won’t represent the state of the sensor.

[MorsRene (Rene)]

Now it works,
Thanks for your help.

[Giga522 (Jan)]

You are welcome, you can mark the answer with a like for other people, who may have the same problem.