Lots of nodes on DeCONZ GUI + I can't add sensors #3465
Comments
ghost
added
the
|
Those devices are the ones paired to your gateway before. Therefore, they are now orphaned. You can still see them. If you re-pair them, they will disappear. |
|
Hello mimions, I never had 85-100 devices ! If I count I have 6 on Conbee and 7-10 on IKEA Tradfri. Is it possible to remove all orphans devices because there a all paired except 1 Aqara Door sensor. I delete them on GUI but still pop everywhere on the screen. Update : when I’m trying to pair the sensor, the docker crash and stopped.
|
|
How have you reseted the gateway ? Removed the db file ? |
|
Hello Smanar, This is my configuration (I don't know if it's sensible data ^^)
|
|
I deleted the zll.db file. |
|
Am I the only one noticing the suspicious mac addresses? No clue what could be causing this, but there’s something very weird going on. @manup, any idea? |
|
This looks indeed very suspicious, like only mac address prefixes are there. Note while deleting zll.db file deCONZ must not be running. Can you please post the log while the sensor is paired, to hopefully see which points are reached. |
|
What, malicious MAC adresses ? It scares me quite a bit. Yes, I’ll will recreate a new docker container of DeCONZ without any configuration and post logs. Thank you for your support. |
|
This is the log file after a a new container without paring devices : https://privatebin.net/?598d9159d1997cb5#FRKhAjQtosrePe3GSrYHXwTunvkJFiTUbY975NN58qGB When I'm pairing an Aqara temperature sensor : https://privatebin.net/?93a35c655371e705#EeyYJP1n8mbw9xS3HvGMfFP6oz7LzbzdMk7wPVcCmtr6 |
|
I don't see the bug on your last 2 logs, still have the problem ? |
|
The the moment, I have only one device paired, this is my deCONZ GUI, is it an excepted mesh ? (I think the unit off / on is old Ikea plug, i'll try to power off).
I'll try to add all my devices. |
|
I tried to pairing a new device, after I clicked on "Add new sensor", deCONZ GUI was spammed with tons of new nodes (61 right now). I didn't pushed a single button on my aqara devices |
|
By curiosity, I tried to test on my windows 10 computer (familial computer). I lunched deCONZ app, opened Phoscon web App and started to add an sensor. Same issue, lots of nodes (+50) were discovered and deCONZ app closed itself after few seconds. Can it be a firmware problem or a defective unit after some months ? |
|
IDK, it s realy strange, you have a kind of "flood fake announce" with device using fake MAC adress.
If the problem is from a device, it s probably a router, try to turn off your powered device. |
|
I unplugged all my bulbs, battery from devices, unplugged my IKEA gateway. I just let my routeur from my ISP to connect to the local address to control Phoscon App. I tried to add an Aqara sensor, nothing happens. I tried to add an IKEA bulb, 30 nodes appeared on deCONZ Gui : It's demoralizing, I don't know what to do anymore. UPDATE : I disconnected my routeur. Put the conbee 2 on my laptop, installed deconz, launched the GUI, add sensor and I was spammed by nodes. How on earth it is possible ? |
|
deCONZ does get device announcements, so that explains the nodes. The issue is not in deCONZ, but in the Zigbee network, in the ConBee, or in the device you’re adding. My money would be on the latter. |
|
Hello @ebaauw, I downgraded the firmware to the 26650700 version but the problem is still present. I think I’ll bought a second Conbee stick for test. |
|
My guess is that a single Zigbee device has gone crazy. It is sending bogus device announcements. These cause the ConBee to see bogus devices. As soon as you open the network in search of new devices, deCONZ creates the nodes for these bogus devices. You want to confirm that it is indeed a single device gone crazy, and then discard that device. Once created, the bogus nodes will be persisted in the deCONZ database and, worse, the bogus devices will still be in the ConBee’s neighbour table. Meaning the bogus nodes will re-appear automagically after you delete them. You need to stop deCONZ, and delete the database. I would hope that removing and re-inserting the ConBee will clear its neighbour table, but I’m not sure. If the nodes re-appear after starting deCONZ, we’ll know it doesn’t. Starting from a clean installation, using the 2nd ConBee, add the devices one by one. Power on the device, and search for new devices. The node should appear. Reset the device if needed. If it looks normal, wait a couple of minutes (for the database to be updated), shutdown deCONZ, and make a backup copy of the database. If not, power down the device, shutdown deCONZ, remove and re-insert the ConBee, and restore the database from the last working backup copy. Then proceed adding the other devices. Hopefully you’ll end up with a normal network with all your devices, except the one gone crazy. |
|
Hello @ebaauw, So, I unplugged the conbee stick, created a new docker, put the conbee stick and launched the container. This is the what I see on deCONZ GUI, it's a good start !
After, I clicked on "Add new sensor", but not powered any device ! After 2min30, he found a device :
I checked on the net the code for the manufacturer : 0x117c. It can be the remote of IKEA Tradfri. I forgot to remove battery. Okay, now I add devices one by one ! Fingers crossed !! |
|
Quick update, I added most of my Aqara devices. I have a problem with 2 on 3 Aqara Window / Door Sensor. The first one added without problem, but others two are found on deCONZ GUI but not found on Phoscon App :
The light blinks in Blue one time then in Green when I push the button on the Sensor.
I tried to keep pushing the button every 2 seconds without success on Phoscon App. |
Better to make short press (every 1/2 s), after the blink |
|
Okay, I succeeded for the 2nd but I'm still trying for the 3rd! My poor fingers :D No node error. Next step, Add all my IKEA devices to find the crazy device ! Thanks everyone for your support, I appreciate a lot. |
I restored / unplug/plug stick after each test. |
|
What was the last device you added before adding the Trådfri bulb? What if you power down that device? |
|
I added an Aqara Window / Door Sensor (very hard to detect, I tried like 30 times). I removed battery, started a new pairing discover :
Tested 2 times with same behaviour (restoration, unplug/plug between new pairing). I don't tested to add light yet. |
|
This is beyond me. As far as I know there’s only one API call to search for new devices, and searching for IKEA vs Other in Phoscon shouldn’t make a difference. |
|
Oh okay, that's really, really weird. If you ever want me to do further testing, let me know (Use a different docker container, etc). |
|
OK you have one old firmware in your CornBee !!!! Mapu was saying it was fixes in the last version so trying updating the firmware in it. |
|
Yes, I forgot to update the stick after the replacement. I'll try this before killing all nodes :D |
|
Good but DONT KILL Your Rpi !! ;-)) |
|
Well well, |
|
The second try was the good one. Wait, the firmware wasn't the last. Need to retry :D EDIT : okay good
|
If I understand correctly:
OR just open the pairing, check log and remove battery / unplug will the scanning is opening to find when ghosts nodes stops spamming ? Sorry to insist but i don't want to mess around and do the procedure properly. |
|
Also, what is this error, is it related to ghosts nodes ? |
|
Such errors can happen here and there https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Zigbee-Error-Codes-in-the-Log Can you maybe share a longer log (like 15 mins) and share it as a file here? |
|
Sure, I just check debug INFO and ZPD , 20 mins of logs , I hope it's enough : logs.txt |
|
Hm, that is utterly quiet. Could you raise to
Also, it would probably be helpful to try to reproduce the conditions as before where all that ghost stuff was dripping in. I presume you wanted to include some further devices? Anyway, if you could search for new devices after 5 mins after taking the logs, that hopefully brings further insights. You have quite some of those messages in the 1/3 of the log, which seems a bit odd: |
|
I can't copy past from VNC (thousands of line, probably to much lines), is it possible to change settings in the docker to enable INFO_L2 / Error / Error_L2 ? I found theses variables environment in the doc, is it related with info and error ? (for ZLC / APS / OTAU) |
|
Yes, those are the deconz debug switches (some of them). Set info to 2 and if there's also DEBUG_ERROR, set it to 2 as well. ZDP to 1 |
|
No DEBUG_ERROR variable, unfortunately. This is the logs after open pairing a new light, I hope it's enough : logs.txt |
|
@manup I have looking thru the last loog and cant finding any router that is reporting the accepted IEEE ghosts as neighbours that is pointing in the direction that there is coming from the CornBee itself and not from the real device that is the network. @Zazou89 For the moment its no useful "killing" devices then some is not easy taking out the batteries, Xiaomi whether sensor is little tricky and i think some more 2. |
|
One more interesting thing is is the spectrum of the bad IEEEs. 2 examples from the last log and one matrix: 110 % is not radio interference that is making it so must being some bad behaving program / firmware. The big Q is which device or CornBee ? |
|
@MattWestb Yeah, noticed the same as well. From my perspective, it's something working with variable And this only happens when the network is open. When it's closed, silence again. |
|
My feeling is that is not coming form the devices in the network. Also the user have getting the CornBee II replaces so its not very likely one more bad hardware. I have only one RspBee I so i think its useless for testing this scenario. The user have also resteing the setting before and the last install is in one new docker install so it should not being any strange setting that is being made. I think in the end the CornBee firmware is not liking some IEEE or combinations of them and is bugging out :-(( Killing all devices and start bringing them online one by one can working but its much work with some Xiaomi sensors that must being demounted and trickey getting the battery out. |
|
I do not understand everything but I read your messages carefully! For the Hue bulb : Hue E12 White Ambiance Candle ( 1.29.0_r21169) |
|
Wait and see what SwoopX and manup is saying / finding. If you like / can killing all your devices (making them unpowered / battery out) and bringing them back one by one and see then deCONZ is start getting the "ghost attacks" then having deCONZ in pairing mode. if start "ghosting" kill the device and go to the next one. You can making one "light version" only killing the devices that is easy to kill and testing rebooting deCONZ and opening for joining and looking in the log for our ghost friends is showing up or not. |
|
@manup How is iit going ?? Should the user making one more exchange of the CornBee II or looking for some other solution for getting his system working to christmas ?? By the way santa is coming to Dresden with more Zigbee work this christmas 3/12 Home Smart Home |
Okay, il try that and post some logs if it’s relevant |
|
If you can its great but its not so easy to "kill" all your devices like the Aqara weather is tricky and can being damaged the using to much force. Its also possible going offline with the coordinator and changing pan-id, epan-id and network key so all "old" devices cant coming back in your network but im not sure if its working ok so the "old" devices 110% cant rejoining without you have resetting them one by one. Start bringing the router device back first so you getting the mesh working before adding the end device that is far away and take time for testing open for joining and looking if the ghosts coming back so you not must going back and doing all from scratch. |
|
Hey @Zazou89 I hope its going well with your system and that you have getting it up and running !!! Then some representa from the company is start deleting / locking and blocking other user to helping and they (the company) is not doing it i cant continuing helping you in this case and must moving on like many other have don and is doing. All the best for you !!! MW |
|
Hey @MattWestb ! To be honest, I stopped to search solution. I’m bit bored. It’s working mostly of the time. It’s good for me. If tomorrow nothing works anymore I’ll put all devices in a box. I wish you a merry Christmas |
|
@Zazou89 Please ignore @MattWestb. Read along in the issue he mentioned. I'll ask Manuel to look into this issue tomorrow. |
|
Thanks @Zazou89 ! Then you have time and being little bored after the christmas you can looking for some good working cordianter for your devices (do not buying the cheap CC-253X ones !!!) and trying out some system that is working for you and your devices (it gets france ones 2). I hope you is getting more nice hard packages for the christmas and can enjoying it for 110% !! And I wish you a merry Christmas 2 !!! |
Thank you @Mimiix ! |
|
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again. |
Describe the bug
Hello,
I use DeCONZ / Homebridge on docker with Conbee II. I switched from Raspberry 2B.
Earlier today I had a problem to add Aqara Motion sensor and Door sensor. I resetted the gateway. I added without problem 2 devices.
Now I want to add a third sensor (Aqara door senser). On Phoscon, I had the sensor but it doens't found.
Moreover, When I check deCONZ GUI, I have a TON of nodes (84 right now, and it's grow every 5-10 seconds), I don't understand why I have a lot of nodes (I've only 5-6 sensors, and 4-5 lights on IKEA Tradfri).
Expected behavior
Except to add the sensor and not viewing 84 nodes in DeCONZ GUI.
Screenshots
Environment
Version : 2.05.86 / 15/10/2020
Firmware : 26660700
deCONZ Logs
Some spamming logs :
Thank you
The text was updated successfully, but these errors were encountered: