# \[APP\] Zooz - Let's build smarter tech together

**URL:** <https://community.homey.app/t/app-zooz-lets-build-smarter-tech-together/130214>\
**Category:** Apps\
**Tags:** app\
**Created:** [February 10, 2025, 1:56pm UTC](https://community.homey.app/t/app-zooz-lets-build-smarter-tech-together/130214 "2025-02-10T13:56:37Z")\
**Posts on this page:** 2\
**Page:** 4

<div class="post-metadata">

**Author:** ![Tycho](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tycho/32/16864_2.png) [@Tycho](https://community.homey.app/u/Tycho)\
**Post date:** [March 5, 2026, 12:19pm UTC](https://community.homey.app/t/app-zooz-lets-build-smarter-tech-together/130214/61 "2026-03-05T12:19:34Z")

</div>

It looks like there is a bug in handling brightness. I have a Zooz Outdoor Motion Sensor ZSE70. When there is direct sunlight on the sensor, it reports negative values like this:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/c/0c47d076a44b8e5d309337d81dd4d534bb201b24.png)

When there is no direct sunlight on the sensor, the values are normal and always positive.

---

<div class="post-metadata">

**Author:** ![Ken\_Hansen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ken_hansen/32/123364_2.png) [@Ken\_Hansen](https://community.homey.app/u/Ken_Hansen)\
**Post date:** [June 13, 2026, 3:39pm UTC](https://community.homey.app/t/app-zooz-lets-build-smarter-tech-together/130214/62 "2026-06-13T15:39:12Z")

</div>

Hi all,

Looking for confirmation or workarounds from anyone with multiple ZEN72 dimmers on Homey Pro. I’ve hit a reproducible issue on two different hubs and want to see if I’m alone here.

**The pattern:**

- First ZEN72 includes (after 2-3 retries). Shows as “Authenticated, Unauthenticated” security in Developer Tools.
- Every ZEN72 after that fails with “Unable to connect — Something went wrong while communicating with the device.”
- ZEN71 on/off switches include cleanly during the same session. So Z-Wave inclusion itself is working, just ZEN72 specifically that breaks.

**Confirmed on both:**

- Homey Pro Early 2023 (firmware 13.2.1)
- Homey Pro 2026 (firmware 13.2.1)

Same physical ZEN72 units that fail on the 2026 also fail on the 2023 when they’re not the first ZEN72 attempt on that hub. So it follows the hub state, not the device.

**Already tried:**

- Multiple factory resets of each ZEN72 (paddle reset confirms with proper LED pattern)
- Breaker power cycle of the switch
- S0 legacy pairing checked vs default S2
- 3-tap and 5-tap inclusion patterns (per Zooz docs)
- Provisioning list checked clean
- Run “Remove Unknown Nodes” between attempts
- Hub reboots (unplug 30 sec)
- Complete Z-Wave network factory reset on the 2026

**Other observation:**

The one ZEN72 that did include doesn’t show a status indicator dot on its device tile. Same issue happens with a ZEN71 if you set it as device class “fan” instead of “light”.

I have about 25 ZEN72s to deploy and currently blocked at 1 successful per hub. Filed a GitHub issue at [ZEN72 inclusion: only first ZEN72 per hub includes successfully; subsequent ZEN72s fail to include · Issue #99 · koktail-nl/com.getzooz.issues · GitHub](https://github.com/koktail-nl/com.getzooz.issues/issues/99) and contacted Zooz support in parallel.

Anyone else hitting this with ZEN72 specifically? Anyone found a workaround?

Thanks.

[Previous page](https://community.homey.app/t/app-zooz-lets-build-smarter-tech-together/130214.md?page=3)