# \[Abandoned\] deCONZ

**URL:** <https://community.homey.app/t/abandoned-deconz/29390>\
**Category:** Apps\
**Tags:** app, zigbee, devices\
**Created:** [May 5, 2020, 9:57am UTC](https://community.homey.app/t/abandoned-deconz/29390 "2020-05-05T09:57:44Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![MadMonkey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/madmonkey/32/22606_2.png) [@MadMonkey](https://community.homey.app/u/MadMonkey)\
**Post date:** [May 28, 2020, 5:21pm UTC](https://community.homey.app/t/abandoned-deconz/29390/82 "2020-05-28T17:21:32Z")

</div>

Hey @Skorpion  
Thx, I think that was a misstake, I’ll include the quadrupple press in the next release😀

---

<div class="post-metadata">

**Author:** ![MadMonkey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/madmonkey/32/22606_2.png) [@MadMonkey](https://community.homey.app/u/MadMonkey)\
**Post date:** [May 31, 2020, 11:02am UTC](https://community.homey.app/t/abandoned-deconz/29390/83 "2020-05-31T11:02:21Z")

</div>

The next minor update is out!

---

<div class="post-metadata">

**Author:** ![Skorpion](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/skorpion/32/275_2.png) [@Skorpion](https://community.homey.app/u/Skorpion)\
**Post date:** [May 31, 2020, 5:48pm UTC](https://community.homey.app/t/abandoned-deconz/29390/84 "2020-05-31T17:48:31Z")

</div>

Great! 👍

---

<div class="post-metadata">

**Author:** ![Skorpion](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/skorpion/32/275_2.png) [@Skorpion](https://community.homey.app/u/Skorpion)\
**Post date:** [June 4, 2020, 11:30am UTC](https://community.homey.app/t/abandoned-deconz/29390/85 "2020-06-04T11:30:09Z")

</div>

Wanted to make a PR for the triple press of the Symfonisk Remote, but unfortunately I’m currently facing some problems with composing the code, so I can’t test it on my Homey.

Can you add this in a coming release? @MadMonkey

---

<div class="post-metadata">

**Author:** ![MadMonkey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/madmonkey/32/22606_2.png) [@MadMonkey](https://community.homey.app/u/MadMonkey)\
**Post date:** [June 4, 2020, 12:03pm UTC](https://community.homey.app/t/abandoned-deconz/29390/86 "2020-06-04T12:03:15Z")

</div>

Hey @Skorpion

Yes sure no problem. I think i’ll improve the symfonisk driver anyways a bit, I am thinking about a built in throttling/debounce mechanism

---

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [June 5, 2020, 8:30pm UTC](https://community.homey.app/t/abandoned-deconz/29390/87 "2020-06-05T20:30:31Z")

</div>

It was quite the job, but I finally migrated almost every Zigbee device to Deconz 😃

I have now 33 working devices 🎉 🎉.

**Only two weird problems:**

- One Aqara Lights Sensor does not show up in Phoscon. But it does display in de Deconz VLC and this Homey Deconz app detects it without any problems.
- I can’t seem to detect one Aqara motion sensor in the Phoscon Homey App (I’ve 8 other (same) motion detectors running fine). This sensor was working fine with the Homey Xiaomi app. And it does get detected inside Phoscon. Only the Deconz Homey app won’t detect it. I’ve removed and readded the battery in the sensor, restarted the Deconz docker, restarted Homey, restarted Deconz app, removed and re-added the sensor back inside Phoscon, try to readd it inside Homey Deconz app.

Don’t know what to do with this sensor.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [June 6, 2020, 6:42am UTC](https://community.homey.app/t/abandoned-deconz/29390/88 "2020-06-06T06:42:58Z")

</div>

> [@Satoer](#):
>
> One Aqara Lights Sensor does not show up in Phoscon. But it does display in de Deconz VLC and this Homey Deconz app detects it without any problems.

I think you mean the illumination sensor? And do you mean that other sensors of the same brand/model _do_ show up in Phoscon?

I have two Aqara illumination sensors, and they don’t show up in Phoscon either. I believe that’s normal.

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [June 6, 2020, 7:29am UTC](https://community.homey.app/t/abandoned-deconz/29390/89 "2020-06-06T07:29:49Z")

</div>

> [@robertklep](#):
>
> I have two Aqara illumination sensors, and they don’t show up in Phoscon either. I believe that’s normal.

All my Aqara body and illumance sensors, both first and second gen, show up in my Phoscon install.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [June 6, 2020, 7:37am UTC](https://community.homey.app/t/abandoned-deconz/29390/90 "2020-06-06T07:37:05Z")

</div>

This one?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/6/b6c4f154a9c9fc4a7340981d4d46218d53924d13.jpeg)

Although I was mistaken, it’s not an Aqara device but MiJia.

---

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [June 6, 2020, 7:39am UTC](https://community.homey.app/t/abandoned-deconz/29390/91 "2020-06-06T07:39:38Z")

</div>

> [@robertklep](#):
>
> I think you mean the illumination sensor?

> [@robertklep](#):
>
> This one?

Yes.

> [@robertklep](#):
>
> And do you mean that other sensors of the same brand/model _do_ show up in Phoscon?

The same motion sensors (Aqara) do show up in Phoscon. I only couldn’t add one (of the many) to Homey… Until today.

Today I tried to add the motion sensor again, and it shows up. Don’t know why. Maybe some cache was emptied overnight. Now everything works. Only the illumination sensor does not show up in Phoscon (but works in Homey)

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [June 6, 2020, 7:41am UTC](https://community.homey.app/t/abandoned-deconz/29390/92 "2020-06-06T07:41:27Z")

</div>

Right, thats not the device I was talking about. I dont own any of these Mija sensors.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [June 6, 2020, 7:48am UTC](https://community.homey.app/t/abandoned-deconz/29390/93 "2020-06-06T07:48:24Z")

</div>

Yes, motion sensors do show up, just that specific illumination sensor doesn’t.

---

<div class="post-metadata">

**Author:** ![jnwllm](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jnwllm/32/12909_2.png) [@jnwllm](https://community.homey.app/u/jnwllm)\
**Post date:** [June 8, 2020, 7:16am UTC](https://community.homey.app/t/abandoned-deconz/29390/94 "2020-06-08T07:16:09Z")

</div>

Hi there, I’ve started using the deCONZ solution for my Zigbee devices as well (RPi3B with home assistant SD card with deCONZ add-on installed) and control them using my Homey, making use of this app. However I struggle to get my **Aqara motion sensors** working properly. I’m using 2 different types; the ones with and without the lux detection.

I always used the [Timer app](https://homey.app/nl-nl/app/com.synplyworks.thenmore/Timer/) with Homey to control my toilet and closet lights; IF motion was detected (AND lux = \<50) THEN turn on the light for 180 sec. I use 180 seconds as I haven’t hacked the hardware. The different sensor types use 90/120 sec for the status to return from ‘motion detected’ to ‘no motion detected’, so that leaves enough time to detect new movement in the remaining 90/60 seconds.

**The problem is** that even though the motion is nicely detected and turns off, **the timer is not being re-activated if new motion is detected** in the remaining time the light is on.

Any idea what goes wrong / is different from connecting the sensors and lights directly to Homey VS via deCONZ? Should I be configuring different flows, or is something else wrong?

---

<div class="post-metadata">

**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\
**Post date:** [June 8, 2020, 8:20am UTC](https://community.homey.app/t/abandoned-deconz/29390/95 "2020-06-08T08:20:47Z")

</div>

Funny enough I got this feeling too. Haven’t started looking into it yet but the light doesn’t stay on even though there is repeated motion. Will check tonight

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [June 8, 2020, 8:35am UTC](https://community.homey.app/t/abandoned-deconz/29390/96 "2020-06-08T08:35:18Z")

</div>

> [@jnwllm](#):
>
> **The problem is** that even though the motion is nicely detected and turns off, **the timer is not being re-activated if new motion is detected** in the remaining time the light is on.

Make sure the turned-on light doesn’t hit the sensor, otherwise the lux value may be higher than 50. You could perhaps solve it with an _“AND lux \<= 50 OR the light is already on”_ condition.

---

<div class="post-metadata">

**Author:** ![jnwllm](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jnwllm/32/12909_2.png) [@jnwllm](https://community.homey.app/u/jnwllm)\
**Post date:** [June 8, 2020, 8:53am UTC](https://community.homey.app/t/abandoned-deconz/29390/97 "2020-06-08T08:53:42Z")

</div>

> [@robertklep](#):
>
> Make sure the turned-on light doesn’t hit the sensor, otherwise the lux value may be higher than 50. You could perhaps solve it with an _“AND lux \<= 50 OR the light is already on”_ condition.

The flow for my closes light has the ‘Mi sensor’ without lux detection and faces the same issue, so it’s not that. However it makes sense to add the ‘light is already on’ condition to the flow where I do use the lux-condition.

But that still leaves me with the situation being left in the dark (literally) when the timer runs out, detects my motion but doesn’t reset the timer. Any other ideas?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [June 8, 2020, 9:45am UTC](https://community.homey.app/t/abandoned-deconz/29390/98 "2020-06-08T09:45:52Z")

</div>

If the motion gets detected, and hence the flow is triggered again (which should be easy to test), my guess would be an issue with the timer. Perhaps it can’t be retriggered?

---

<div class="post-metadata">

**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\
**Post date:** [June 8, 2020, 10:06am UTC](https://community.homey.app/t/abandoned-deconz/29390/99 "2020-06-08T10:06:45Z")

</div>

Yes… there I go… I think i’ve figured why it doesn’t work for me. What i’m doing is starting a timer and based on the timer im turning off the light after 3 minutes, but only if the LUX is below 29. Start or restart of the timer doesn’t trigger, because the LUX is above 29 when the light is on. I’m going to think on this…

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [June 8, 2020, 10:27am UTC](https://community.homey.app/t/abandoned-deconz/29390/100 "2020-06-08T10:27:20Z")

</div>

> [@Martijn\_Hoogenbosch](#):
>
> I’m going to think on this…

Look up a few posts for a possible solution 😜

---

<div class="post-metadata">

**Author:** ![jnwllm](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jnwllm/32/12909_2.png) [@jnwllm](https://community.homey.app/u/jnwllm)\
**Post date:** [June 8, 2020, 10:41am UTC](https://community.homey.app/t/abandoned-deconz/29390/101 "2020-06-08T10:41:35Z")

</div>

Apparantly there were more people having issues…and after ‘updating’ the deCONZ add-on that downgrades to an older firmware solved the issue for me; my timer is working properly now and resetting when detecting new movement.

 ![Screenshot 2020-06-08 at 12.38.58](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/e/eebc3aed1bc21a851aa1cb772bda4569fee51b70.png)

[Previous page](https://community.homey.app/t/abandoned-deconz/29390.md?page=4)

[Next page](https://community.homey.app/t/abandoned-deconz/29390.md?page=6)