Skip to content

fix: add 'far' movement state value to ZG-205W mmWave presence sensor#5411

Merged
make-all merged 1 commit into
make-all:mainfrom
robelmes:fix/zg205w-add-far-movement-state
Jun 25, 2026
Merged

fix: add 'far' movement state value to ZG-205W mmWave presence sensor#5411
make-all merged 1 commit into
make-all:mainfrom
robelmes:fix/zg205w-add-far-movement-state

Conversation

@robelmes

Copy link
Copy Markdown
Contributor

Summary

The ZG-205W (and ZG-205Z, which uses the same DPS mapping) mmWave presence sensor occasionally emits far as the DPS 116 value in addition to the already-mapped large_move, small_move, breathe, and none.

Problem

Without a mapping for far, tuya-local passes the raw string through to Home Assistant's enum sensor. HA then raises a ValueError on every update that sends this value:

ValueError: Sensor sensor.presence_sensor_office_pc_movement_state provides state value 'far',
which is not in the list of options provided

This produces repeated errors in the HA log and leaves the sensor in an unavailable/unknown state whenever the device reports far.

Fix

Add farFar to the DPS 116 mapping. Based on the sensor's near/far detection zones, this value appears to represent stationary presence detected at far range (beyond the active motion zone).

Testing

Observed on ZG-205Z sensors (same DPS layout as ZG-205W) running current firmware. After adding this mapping, the ValueError no longer appears in HA logs and the sensor reports Far correctly.

The ZG-205W/ZG-205Z mmWave presence sensor can emit 'far' as a DPS 116
value in addition to the existing large_move, small_move, breathe, none.

This value appears to represent stationary presence detected at far range
(beyond the active motion zone). Without this mapping, tuya-local passes
the raw 'far' string to HA, which raises a ValueError because 'far' is not
in the declared enum options, producing repeated errors in the HA log.

Observed on firmware version in use with ZG-205Z sensors (same hardware,
same DPS mapping).
@make-all make-all merged commit ad393ee into make-all:main Jun 25, 2026
4 checks passed
@github-project-automation github-project-automation Bot moved this from 👀 In review to ✅ Done in Tuya Local Jun 25, 2026
make-all added a commit that referenced this pull request Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants