Map magnet sensor to light switch

[350d]

There is a clever solution available to use window/door sensor as smart light switch where some alias workaround needed to convert sensor to switch. Home Assistant example:

- alias: Light switch
  trigger:
    platform: state
    entity_id: binary_sensor.door_window_sensor_158d000xxxxxc2
  action:
    service: light.toggle
    entity_id: light.somelight

Please help me to remap magnet sensor to light switch device via miot plugin config.
Also I have no idea how to use device events instead of polling to prolong device battery life.
My device properties:

NAME:     Light switch Virtual
ID:       lumi.158d00016cd97a
MODEL:    lumi.sensor_magnet.v2

PROPS:

magnet-sensor:contact-state

EVENTS:

magnet-sensor:close
magnet-sensor:open
magnet-sensor:door-not-closed
battery:low-battery

I've connected this device via Mi Hub v3 and tried to configure it like this:

                {
                    "name": "Light switch Virtual",
                    "ip": "hubiphere",
                    "token": "hubtokenhere",
                    "deviceId": "lumi.158d00016cd97a",
                    "model": "lumi.sensor_magnet.v2",
                    "pollingInterval": 3600,
                    "deepDebugLog": true,
                    "micloud": {
                        "username": "loginhere",
                        "password": "passwordhere"
                    },
                    "buzzerControl": false,
                    "ledControl": false,
                    "childLockControl": false,
                    "modeControl": false,
                    "propertyMonitor": [
                        {
                            "property": "magnet-sensor:contact-state",
                            "name": "Link magnet sensor state to switch position",
                            "linkedProperty": "switch:on",
                            "linkedPropertyValue": 1
                        }
                    ]
                }

but it doesn't work and no devices showed up in HomeKit.

homebridge log:

[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Got device configuration, initializing device with name: Light switch Virtual
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Model known: lumi.sensor_magnet.v2!
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Initializing device!

[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Initializing device services
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Device services: [
  "magnet-sensor",
  "battery"
]
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Initializing device properties
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Device properties: [
  "magnet-sensor:contact-state"
]
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Initializing device actions
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Successfully created a ContactSensor device! It is a Xiaomi Mi Door and Window Sensor.
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Initializing accessory!
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Accessory successfully initialized!
[15/10/2023, 19:18:28] [miot] [Light switch Virtual] Registering 1 accessories!
[15/10/2023, 19:18:29] [miot] [Light switch Virtual] Everything looks good! Initiating property polling!
[15/10/2023, 19:18:29] [miot] [Light switch Virtual] Log in to MiCloud!

[merdok]

You have to run homebridge in debug mode and see what the debug log says.

Your first objective should be to make the device appear. You can try to specify the token and ip of the gateway (Hub), but the model and deviceId needs to be that of the contact sensor.

If you want your device to appear as a light switch then you have to find a light switch model and use that instead. Be aware that in that case the plugin will fetch the invalid metadata hence the properties might not work. You would need to go the miot metadata cache which should be in the homebridge config directory and manually adjust the properties there so that they match the contact sensor.

It might work, but it is all based just on theory, so you have to try it out and play with it.

[350d]

Device connected via hub with hub token/ip already visible in HK. Lets try to configure it with custom mappings in config - is this possible via config only or I need to edit cache files?

[merdok]

what you put in the config is validated against the miot spec (cached files), so you would need to adjust the cache files to fake the device capabilities.