Koenkk / Koenkk/zigbee2mqtt

ROBB ROB_200-070-0 does not report Occupancy

Open
#32,721 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

problem
Dominant language
TypeScript
Stars
15.7k
Forks
2k
Avg merge
18h 55m
Merged PRs (30d)
35

Description

What happened?

ROBB ROB_200-070-0 reports Occupancy as Unknown or Unavailable. As a motion sensor, this is a critical component of this device.

What did you expect to happen?

Occupancy should be reported as True or False

How to reproduce it (minimal and precise)

Pair the device to Z2M and see the sensor state for Occupancy.

Zigbee2MQTT version

2.13.0

Adapter firmware version

EmberZNet Revision: 7.5.1 [GA]

Adapter

Silicon Labs MGM210P (Home Assistant Yellow)

Setup

As a Home Assistant Add-on on Home Assistant Yellow (RPi 5 CM)

Device database.db entry

No response

Debug log

No response

Notes

Z2M shows these State:

{
"alarm_1": true,
"alarm_2": false,
"battery": 100,
"battery_low": false,
"humidity_4": 61,
"illuminance_5": 231,
"linkquality": 116,
"occupancy_1": true,
"tamper": false,
"temperature_3": 23.3,
"identify": null,
"occupancy": null
}

However, it seems the Home Assistant entity for Occupancy uses "occupancy" instead of "occupancy_1".

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the device definition or converter for ROBB ROB_200-070-0 and inspect how its occupancy exposures are mapped. Reproduce the paired-device state showing occupancy_1 alongside occupancy, then update the mapping so the Home Assistant Occupancy entity reports the device's true or false occupancy state and verify the reported state.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.