Mirabella Genio Door & Window Sensor I002575 HKWL-DWS02W

Tags: #<Tag:0x00007f77fa545370>
#1

I have seen a few people trying to get the Mirabella Genio Door & Window Sensor working with home assistant without success, myself included. I am creating this topic to track the progress of this integration.

Model: HKWL-DWS02W
Item: I002575

Mirabella Genio Smart Home
#2

I have it running with ESPhome, although response time is terrible at between 5 and 10 seconds.
Probably fine for windows or garage doors, but for a standard door that can be opened and closed within this time, almost useless as the open / close will be missed.

I plan to use mine on a sliding wardrobe door to toggle a light strip.

Esphome config here:

Sensor must be put in to pairing mode to keep it awake for the flash

#3

I bricked mine trying to follow a guide on tasmota website and have tried to reflash it with a serial connection but it doesn’t want to work.

#4

Nice @jivesinger I am giving this a go now. If it is possible with esphome then it should be possible with Tasmota you would think.

#5

Sounds like it was faulty when you bought it @a_lunatic, need to take it back in and get it replaced :wink:

#6

So I flashed it with ESPhome as suggested and it will not connect to my access point. Wifi details are correct, and I tested a non flashed one with the AP so I know it works.

I also enabled the Captive Portal and that is not coming up after the 1minute wait ether. So I am not sure how to recover the device without opening it up.

esphome:
  name: door
  platform: ESP8266
  board: esp01_1m
  arduino_version: 2.5.1
  board_flash_mode: dout
  includes:
    - sb1_uart.h

wifi:
  ssid: 'SSID'
  password: PASSWORD
  fast_connect: true
  ap:
    ssid: "doorsensor Fallback Hotspot"
    password: "W1PBGyrokfLz"

captive_portal:

mqtt:
  broker: ''
  username: USERNAME
  password: PASSWORD
  birth_message:
  shutdown_message:
  will_message:

uart:
  - tx_pin: 1
    rx_pin: 3
    baud_rate: 9600
    id: uart0

ota:

logger:
  level: INFO
  hardware_uart: UART1

sensor:
  - platform: wifi_signal
    name: "Door WiFi Signal"
    update_interval: never
    expire_after:
    filters: []
  - platform: adc
    name: "Door Battery"
    update_interval: never
    expire_after:
    pin: VCC
    filters: []

binary_sensor:
  - platform: template
    id: door
    name: "Door Closure"
    filters: []
    device_class: door
    lambda: "return {};"

custom_component:
  - id: sb1_uart
    lambda: |-
      auto component = new SB1UARTComponent(id(uart0), id(door));
      return {component};
#7

So I got it connected, I think my issue was the fast_connect: true however I’m not 100%.

The captive_portal: still isn’t working ether.

At the end of the day these door sensors just kinda suck. To be fair they seemed okay running the default firmware but no good if you want to flash them.

#8

It doesn’t work because the ESP is only awake for a few seconds. If it did work your batteries would be flat within hours.

What sort of delay are you getting between activating the sensor and seeing that reflected in Home Assistant ?

#9

Sorry, by captive_portal I mean the fall back AP mode. Where if your device dose not connect to the WI-FI network within 1 minute it starts its own AP you can connect to and reconfigure the WI-FI credentials.