Presence Sensor | SNZB-06P in Cube

eWeLink CUBE
1

I just play around with Cube just recently, move some zigbee devices, especially Sonoff Presence Sensor (SNZB-06P), and here are my feedback:

  • Related the term: Use “Motion“ instead of “Presence“.

I understand that this point has already stated in the FAQ section in the product website. But still I need to add this feedback, because I prefer the term Presence instead of Motion and cube is created by sonoff themself. Hopefully it just translation which need improvement. There are 2 locations which bother me:

Screenshot from 2026-02-09 12-12-31
Screenshot from 2026-02-09 12-12-31505×263 11.4 KB

First in the basic info when I click the device.

Screenshot from 2026-02-09 12-13-55
Screenshot from 2026-02-09 12-13-55505×309 22.5 KB

Second when setting the scene.

The use of term “Motion” is confusing, prefer “Presence“.

  • Detection Period

In the cube, minimum detection period is 15 seconds. If I remember correctly, minimum detection period in the ewelink app is 10 seconds. When I try to update the detection period to unwanted value, error message shown is not clear. Better to shown clear error message and sync the minimum detection period between cube and ewelink app.

  • Motion / Presence Detection Behaviour

My presence sensor placement is in the bathroom, when someone enter the bathroom, I expect sensor can trigger the lighting immediately. Previously using ewelink app I encountered randomness which is: sometime sensor can trigger the light immediately (almost immediate when I step my foot to the bathroom), and sometime it can trigger with delay. Zigbee signal is not an issue (checked already). I assume because I use ewelink app and it can have connection issue to trigger the scene. Using same sensor configuration, I expect that when I use cube in my local it can remove the randomness and it did (so far: 1 week experimentation). But the issue right now: it consistently give delay (minimum 5 seconds). I have set the scene using motion detected without delay / duration. Hope that it can be triggered as quick as possible (1s still okay), because cube has already in local, signal is good, setting is checked with smallest detection period as possible.

Thank you.

1 Like
2

Sonoff lacks a coherent ecosystem vision. This is the company’s biggest problem. You can see it clearly in:

  • NSPanel Pro,
  • TRVZB,
  • Cube,
  • their Zigbee stack,
  • their MQTT implementation,
  • their translations.

Every product looks as if it were created by a different team, each with its own philosophy and vocabulary. That’s why (using a few selected examples):

  • TRVZB has “Frost Protection” translated in a way that makes no sense,
  • Cube uses “Motion” instead of “Presence”,
  • SNZB-03P has Occupancy instead of Motion
  • NSPanel Pro has “Scenes” that aren’t scenes,
  • eWeLink has “Scenes” that are actually automations.

This is not a coherent ecosystem. It’s a patchwork. You have to love or leave it :slight_smile:

Above all, it’s their rush that destroys them, and this is how they manage to ruin even the most promising hardware device right from the start. And I’m not saying this out of spite — quite the opposite. Sonoff/eWeLink will always have a special place in my heart, because that’s where my whole IoT adventure began. I still think that, setting aside the occasional lemons, their hardware lineup is genuinely interesting, and the price‑to‑build‑quality ratio is almost unbeatable. So no, I’m not another angry crusader on a mission to bash them. I’ve simply gained some perspective over the years, and the honeymoon phase is long over.

1 Like
3

I say the same thing. They make the device and it happens that it takes a long time for support to be added to other hubs.

1 Like