Are that the round ones or the square Aqara ones? I have about 8 Aqara sensors. I use them mostly in my vivariums. All except 1 running for over a year.
Hi to all,
I need help to remove deconz from my docker installation of hassio.
I’ve followed the official guide and installed the marthoc/deconz image, but now I wish to remove it and use the native integration for many rasons (one is the fake serial number of the gateway, 0000000000 that cause a log error).
How can I do?
I need all the passages because I’m a total noob in raspberry & raspbian.
I have noticed with the latest deconz version (6.6.0) and with the latest firmware (0x26680700) that deconz just silently stops. This has happened 3 times the last 4 days. A restart solves it.
03:09:47:538 remove dead link for (2FAB, 5F5B)
03:09:48:612 remove dead link for (5F5B, F478)
03:10:00:462 remove dead link for (D5D9, 5F5B)
03:10:02:612 remove dead link for (5F5B, AC03)
03:10:03:712 remove dead link for (5F5B, 5C21)
03:10:15:537 remove dead link for (B626, 5F5B)
03:10:19:863 remove dead link for (8DA3, 5F5B)
03:10:31:712 remove dead link for (188E, 5F5B)
03:10:40:312 remove dead link for (5F5B, 5EFB)
03:10:42:463 remove dead link for (5F5B, EC4C)
03:10:50:013 remove dead link for (5F5B, 8E6D)
[02:32:49] INFO: Running the OSRAM LEdvance OTA updater...
[02:32:49] INFO: Can't fetch data from osram!
03:11:02:938 remove dead link for (44F3, 5F5B)
03:11:04:013 remove dead link for (5F5B, 5FB6)
03:11:10:463 remove dead link for (5F5B, 9197)
03:11:18:013 remove dead link for (D832, 5F5B)
03:11:21:237 remove dead link for (BCF, 5F5B)
03:11:26:778 dev /dev/ttyAMA0
03:11:33:088 remove dead link for (1293, 5F5B)
03:11:34:162 remove dead link for (5F5B, 7A53)
03:11:47:088 remove dead link for (D57D, 5F5B)
03:11:48:162 remove dead link for (8FF1, 5F5B)
03:12:57:548 Announced to internet http://dresden-light.appspot.com/discover
03:12:57:550 discovery server date: Tue, 15 Dec 2020 02:12:57 GMT
03:12:57:551 local time seems to be ok
03:15:26:779 dev /dev/ttyAMA0
03:19:26:781 dev /dev/ttyAMA0
03:22:57:502 Announced to internet http://dresden-light.appspot.com/discover
03:22:57:504 discovery server date: Tue, 15 Dec 2020 02:22:57 GMT
03:22:57:505 local time seems to be ok
03:23:26:783 dev /dev/ttyAMA0
03:27:26:781 dev /dev/ttyAMA0
03:31:26:778 dev /dev/ttyAMA0
03:32:57:544 Announced to internet http://dresden-light.appspot.com/discover
03:32:57:546 discovery server date: Tue, 15 Dec 2020 02:32:57 GMT
03:32:57:547 local time seems to be ok
03:35:26:777 dev /dev/ttyAMA0
03:39:26:777 dev /dev/ttyAMA0
03:42:57:519 Announced to internet http://dresden-light.appspot.com/discover
03:42:57:521 discovery server date: Tue, 15 Dec 2020 02:42:57 GMT
03:42:57:522 local time seems to be ok
03:43:26:778 dev /dev/ttyAMA0
03:47:26:777 dev /dev/ttyAMA0
03:51:26:778 dev /dev/ttyAMA0
03:52:57:545 Announced to internet http://dresden-light.appspot.com/discover
03:52:57:547 discovery server date: Tue, 15 Dec 2020 02:52:57 GMT
03:52:57:548 local time seems to be ok
03:55:26:776 dev /dev/ttyAMA0
03:59:26:778 dev /dev/ttyAMA0
04:02:57:502 Announced to internet http://dresden-light.appspot.com/discover
04:02:57:503 discovery server date: Tue, 15 Dec 2020 03:02:57 GMT
04:02:57:504 local time seems to be ok
04:03:26:783 dev /dev/ttyAMA0
04:07:26:785 dev /dev/ttyAMA0
04:11:26:776 dev /dev/ttyAMA0
04:12:57:547 Announced to internet http://dresden-light.appspot.com/discover
04:12:57:549 discovery server date: Tue, 15 Dec 2020 03:12:57 GMT
04:12:57:550 local time seems to be ok
04:15:26:764 dev /dev/ttyAMA0
04:19:26:778 dev /dev/ttyAMA0
04:22:57:488 Announced to internet http://dresden-light.appspot.com/discover
04:22:57:490 discovery server date: Tue, 15 Dec 2020 03:22:57 GMT
04:22:57:491 local time seems to be ok
04:23:26:785 dev /dev/ttyAMA0
04:27:26:778 dev /dev/ttyAMA0
04:31:26:767 dev /dev/ttyAMA0
04:32:57:558 Announced to internet http://dresden-light.appspot.com/discover
04:32:57:560 discovery server date: Tue, 15 Dec 2020 03:32:57 GMT
04:32:57:561 local time seems to be ok
04:35:26:771 dev /dev/ttyAMA0
04:39:26:778 dev /dev/ttyAMA0
04:42:57:558 Announced to internet http://dresden-light.appspot.com/discover
04:42:57:559 discovery server date: Tue, 15 Dec 2020 03:42:57 GMT
04:42:57:561 local time seems to be ok
04:43:26:772 dev /dev/ttyAMA0
04:47:26:764 dev /dev/ttyAMA0
04:51:26:774 dev /dev/ttyAMA0
04:52:57:498 Announced to internet http://dresden-light.appspot.com/discover
04:52:57:500 discovery server date: Tue, 15 Dec 2020 03:52:57 GMT
04:52:57:501 local time seems to be ok
04:55:26:769 dev /dev/ttyAMA0
04:59:26:777 dev /dev/ttyAMA0
05:02:57:484 Announced to internet http://dresden-light.appspot.com/discover
05:02:57:485 discovery server date: Tue, 15 Dec 2020 04:02:57 GMT
05:02:57:486 local time seems to be ok
05:03:26:779 dev /dev/ttyAMA0
05:07:26:777 dev /dev/ttyAMA0
05:11:26:785 dev /dev/ttyAMA0
05:12:57:625 Announced to internet http://dresden-light.appspot.com/discover
05:12:57:626 discovery server date: Tue, 15 Dec 2020 04:12:57 GMT
05:12:57:627 local time seems to be ok
05:15:26:778 dev /dev/ttyAMA0
05:19:26:766 dev /dev/ttyAMA0
05:22:57:525 Announced to internet http://dresden-light.appspot.com/discover
05:22:57:526 discovery server date: Tue, 15 Dec 2020 04:22:57 GMT
05:22:57:527 local time seems to be ok
05:23:26:779 dev /dev/ttyAMA0
05:27:26:778 dev /dev/ttyAMA0
05:31:26:765 dev /dev/ttyAMA0
Does someone know how I find the number to enter in the group binding edit box?
Hi Stigvi : had many many issues with deCONZY 6.6.0, had to go back to 6.4.1 AND i had also to downgrade firmware to 26650700.
If i move to 26660700, nothing works anymore.
Note that Sylvania/Osram/Ledvance released a lot of products over the last few years under those brand names that look very similar but have important differences… reminds me a bit of the recent TP-Link HS110 mess where they have a bunch of plugs in the field that are all called HS110 but can have very different hardware inside the case.
Earlier this year, I got in on some of the super-cheap sales on Sylvania Zigbee lights (A19, BR-30, strips, etc.) I didn’t know much about them then, but they were a good price, so I jumped.
What I’ve learned since then (both through reading of others’ experience and through my own experience) is that some of the earlier bulbs/strips (usually under brand OSRAM) have an older Zigbee chip in them and are not very reliable as routers. In the US, they have an FCC ID of “DZO-IQHOME”, and this is printed on the packaging and on the device itself.
Other devices (usually branded Sylvania in my experience) have Zigbee modules with an FCC ID of “DZO-LEDV-AETHER” and have an OTA firmware of 0x00102428 available. With that version of the firmware, I have been fairly sucessful with setting up a reliable network. I have about 90 devices on a ConBeeII stick running ZHA, and the only mains-powered devices are the Sylvania bulbs/strips. My network is about half routers and half endpoint devices.
I’ve read that some of the Sylvania/Osram/Ledvance products have smallish buffers and can drop packets on very busy networks. I have yet to determine if my network is affected by that issue. Based on my current experience, if my network grows large enough to hit that issue (if indeed the LEDV-AETHER products have it), my plan is to split my Zigbee network in two with one ConBee running ZHA directly on the HA box and another ConBee running deCONZ on a PC. I have a proof-of-concept running with that now - deCONZ running a half-dozen bulbs on a different channel while the HA box runs ZHA with the other 90 devices. Seems ok so far.
Hey,
My phoscon shows that I have version 2.08.00 / 08/12/2020 (I run marthoc/docker-deconz). But when I check the changelog it says the latest version is v2.7.1 Are these just two different version numbering or am I missing something?
I am pulling with the tag latest right now.
2.8.0 is the current beta version.
That’s conforms with the “latest” tag, which uses the “latest release of deCONZ, stable or beta”.
I’m using Rpi3b+ with Deconz Raspbee and Homeassistant until this morning. I’ve been struggling with the latest update and SSD. This morning deconz was not connected to HA anymore and the last days I’ve seen the Phoscon gateway disconnecting every now and then for a couple of seconds and then reconnecting.
Deconz is on 2.07.01.
Today I’ve started the Rbi3b+ with Rasberian to flash the Raspbee with the latest FW and try to connect everything. I loaded a backup after flashing and had to reconnect bulbs and sensors.
On the rasperian raspbee is stable.
So I changed the SD cards to start HA. Here I deleted the deconz integration and tried to reconnect it. Now the login page in Phoscon comes but after entering “Network was not found” is shown. In the deconz software the raspbee is disconnected and will not connect.
Has this anything with autentication of raspbee to do? When running raspbee under HA I’m not able to stay connected long enough to get to “Autenicate”.
I have a Rpi4 with ConBee II and apparently when HA auto-updated the Deconz addon from 6.6.0 to 6.6.1 Deconz broke. On Phoscon it prompted that couldn’t find network and on Deconz it was prompting to update firmware of the stick (was already running latest). Clicking the update firmware button did nothing. Had a look at Deconz discord and some people have had the same issue. Current workaround was to downgrade to older firmware version for the stick: 26660700.
please allow me what must seem to be terribly basic to you all:
just managed to install a new Conbee II stick via Supervisor Add-on, and after a couple of restarts, (no discovery was notified) could install the integration which found the stick alright, and an already setup Ikea motion sensor (did that before adding the ingetration).
I get a couple of entities, one of which is the Tradfri sensor:
there seems to be no battery sensor made for this entity, and, maybe even more surprisingly, the sensors state remains on for over a minute, long after a motion has been detected.
Main reason for me installing this was the superior response time compared to the Hue and Ikea Hubs, but this is far from usage of course.
Second to that, the attribute dark remains false, even in a completely darkened room…
As there is an attribute on which is set to true as you can see, I wonder if we can turn-off these sensors too? Or would this have to do with the knob on the back of the sensor setting the moon and sun (light sensitivity)?
All in all, not a very grandiose first impression. It must be user error, so please, if you can help me here, teaching me some of the basics, it would be much appreciated.
I recomanend you to take a look in phoscon. Probably there you can adjust the times. But I don’t have your sensor but I could set up there one Phillips I had.
Motion stays on for over a minute: This can’t be changed at all unfortunately, to preserve battery life (as I read somewhere). Aqara motion sensors have the same problem. The ones from Hue are on for only 15 seconds though (they use 2x AAA batteries instead of 1x CR2032).
Battery level doesn’t get reported: I also had that problem with a few Tradfri devices (motion sensor, on/off switch and the 5 button remote)! It may take a few days/weeks for them to pop-up… restarting the addon (a few times) might! help. But they should show up eventually.
WTH dark/on: I assume, the dark attribute does refer to the moon/sun button on the back of the sensor, as there is no illuminance sensor - but I didn’t test that extensively to be honest, so I can’t tell you how much of a difference it really makes. I think the on attribute is simply stating that the sensor is powered, but I could be wrong.
Motion stays on for over a minute: This can’t be changed at all unfortunately, to preserve battery life (as I read somewhere). Aqara motion sensors have the same problem. The ones from Hue are on for only 15 seconds though (they use 2x AAA batteries instead of 1x CR2032).
I am not sure but I think you can adjust this? I think I used deconz.configure feature in HA Developer Tools. It’s while ago I did this and memory (mine) starts to in bad shape 
I suggest to try this.
As you see below mine clears in about 12-13 seconds. This also works with Aqara - they clear in around 10 seconds.
And EDIT: Forgot to say Merry Christmas to Everyone!
1 Like
thanks! confirming all of my suspicions 
btw, I indeed finally saw a battery sensor appear, and, while I used brand new quality batteries, it showed 21 % after a couple of hours and now is on 16%, within half a day…
seems to be very much related to this: https://github.com/home-assistant/core/issues/43969
that’s another issue though.
Still, the much anticipated responsiveness of the Deconz is a bit of a disappointment, at least as far as the ikea sensors go.
Will test a Hue sensor next, which would be more of a difference going from the polling it uses now, to pushing changes using the Deconz.
While that is true, they are “blind” afterwards - and won’t change to detected for the same period they would normally be on. Or am I mistaken?
There is a hardware hack that i am using and it works like a charm see the topic Aqara Motion Sensor Hack for 5 sec
I used electric paint for this instead of soldering easy to do, and it still works very good.
1 Like
You are right - “they are blind afterwards” - but for instance with Aqara sensors they were ready to detect again in less than a minute. Without the adjustment that time was something more than 2 minutes - if I remember right . But when needed that hardware hack (above) is also possible to cut the time to minimal.