Why “presence” is N/A
This specific Tuya firmware does not publish a boolean presence state at all.
What it does expose:
target_distanceradar_sensitivitydetection_range- link quality, etc.
What it does not expose:
presence: true/falseoccupancy- any binary motion/presence cluster
So Zigbee2MQTT shows:
Presence → N/A
because there is literally no Zigbee attribute to map.
This isn’t a UI bug.
It’s not a Zigbee2MQTT config issue.
It’s not your coordinator.
It’s Tuya shipping a “presence sensor” that only reports raw radar metrics.
Why Tuya does this (the annoying truth)
Tuya expects:
- their cloud
- or their proprietary gateway
to derive presence from radar data.
In other words:
“We’ll sell you the hardware, but the meaning lives elsewhere.”
Classic Tuya.
What Zigbee2MQTT can’t magically invent
Z2M can:
- expose attributes
- convert known clusters
It cannot:
- infer semantics the device never publishes
Hence: Presence = N/A forever, unless firmware changes.
What people actually do in practice
You have three realistic options:
1. Derive presence yourself (works well)
Create presence logic from target_distance + time.
Example logic:
target_distance > 0for ≥ N seconds → presence = truetarget_distance == 0for ≥ M seconds → presence = false
This is exactly what Tuya’s cloud does anyway.
In Symcon / HA / Node-RED this is trivial and reliable.
2. Flash alternative firmware (usually not possible)
Some Tuya mmWave devices can be reflashed (ESP-based).
This one is not realistically flashable.
3. Buy a sensor that actually exposes presence
Devices that do expose real presence over Zigbee:
- Aqara FP2 (not Zigbee, but works properly)
- Some newer Tuya models with updated firmware (hit-or-miss)
- Z-Wave mmWave sensors (ironically much saner)
Bottom line
No joke.
No misconfiguration.
Just Tuya being Tuya.
You bought a radar that can detect presence,
but you did not buy a Zigbee device that admits it detected someone.
If you want, I can:
- sketch a clean Symcon logic block for presence inference
- suggest mmWave models that actually expose
presence - help you normalize this across your Zigbee fleet so it doesn’t feel like a hack
You’re right to be annoyed — this one earns the eye-roll. ![]()


