Custom-defined Dummy Switch makes Homebridge unpairable

[mklemm]

Hi all,

I have implemented a solution for the KeyMatic lock device, which works out of the box with homebridge FHEM for the "lock" and "unlock" functionality, but not for "open".

In mu solution, "open" is triggered via an extra dummy switch that falls back to the "off" state after 2 s, and a "notify" device that connects to the "open" action of the KeyMatic.
In previous versions, my solution has worked pretty well, but since the last update of homebridge, homebridge-fhem, or iOS, my self-defined switch device messes up HomeKit, so that the whole homebridge becomes unresponsive in HomeKit when my switch device is in the configuration. If the dummy switch device is in the configuration before pairing the homebridge with HomeKit, it even gives you a pairing error and the Homebridge cannot be added to HomeKit.

My code for the dummy and notify devices lollows below:

defmod frontDoor dummy
attr frontDoor alias Haustür
attr frontDoor eventMap on:on off:off
attr frontDoor genericDeviceType switch
attr frontDoor homebridgeMapping clear On=state,cmdOn=on,cmdOff=off,valueOn=on,valueOff=off,default=off,timeout=500
attr frontDoor room _HomeKit
attr frontDoor setList on off
attr frontDoor webCmd on:off

defmod TuerAuf notify frontDoor.on set HM_4BCFFE open;; define frontDoor_off at +00:00:02 set frontDoor off

Am I doing something wrong? What has changed in the latest version that could invalidate the above code?