Door Sensor showing as occupancy sensor

Configuration Z-Wave
,
1

I bought this ZWave door/window sensor called DWZWAVE2.5-ECO. I was able to pair it, and it shows up pretty fine on the HA dashboard. Once I switch on binary_sensor it showed up on Homekit too.

But the rub is it shows up as Occupancy Sensor on homekit. So each time I open the door, it shows as the room is occupied. What do I need to change to change this to a door open/close sensor?

Here is some info I thought would be helpful.
node name: Ecolink Door/Window Sensor
manufacturer name: Ecolink
product name: Door/Window Sensor
query stage: Complete
is awake: true
is ready: true
is failed: false
is info received: true
max baud rate: 40000
is zwave plus: true
capabilities: beaming, zwave_plus, routing
neighbors: 1
sentCnt: 28
sentFailed: 0
retries: 0
receivedCnt: 121
receivedDups: 2
receivedUnsolicited: 101
sentTS: 2020-07-11 15:24:05:780
receivedTS: 2020-07-11 20:31:23:162
lastRequestRTT: 21
averageRequestRTT: 21
lastResponseRTT: 32
averageResponseRTT: 154
battery level: 100
wake up interval: 14400
application version: 10.01

2

Show the status of the binary_sensor like you’ve done with the zwave parent device.

3

Sorry, how do I do that?

4

This sounds suspiciously like its a home kit problem as everything seems to be okay in HA.
I’d ask on the home kit forums if you are using home kit as your frontend and this is an issue for you.

Edit: I assume you have set the device class in HA to be: door ?

1 Like
5

[Noob alert]
Hello @Mutt , how do I set that.

6

How Noob is Noob ?
Have you got everything in your configuation.yaml or are you breaking out from that ?

You haven’t listed any useful entities so it’s hard to be specific.
I have one such sensor set like this : -

homeassistant:
  customize:
    binary_sensor.neo_drwinsen_ptiodr_sensor:
      device_class: door

This is in one of my package files but you would put it in your configuration.yaml
Note: you can ONLY have ONE homeassistant: header (unless you run packages) and under that only ONE customize: header (these headers are actually yaml ‘keys’ ).
But beneath that you can have multiple sensors to be customised.
This (as far as I’m aware) will not influence homekit at all.

1 Like
7

This is what I have:


# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

zwave:
 usb_path: /dev/ttyUSB0
 
zha:
 usb_path: /dev/ttyUSB1
 database_path: /config/zigbee.db
8

Okay, nothing there precludes putting it in your config.
It’s a fairly major (important) key, numerous other stuff goes under it, so I’d put this in at the top