Closed marithpl closed 3 years ago
Those devices seem not to be paired correctly. Could it be that there's a version difference between the migration?
Either way, re-pairing should fix it.
It's what I did. Versions was the same. But is very annoying some sensor I have behind wash machine etc. I use Deconz for 1 month and I had to re-pair devices about 3-4 times.
I don't know why sometimes end devices connect to Conbee which is on 2nd floor but they won't connect to device which is 1-2 meter away.
Now I turned off Xiaomi Gas Sensor because I suppose it makes a lot of problems in mesh network.
I don't know why sometimes end devices connect to Conbee which is on 2nd floor but they won't connect to device which is 1-2 meter away.
No clue either, but that is what they do. Xiaomi devices tend to not switch parents. Would be interesting to see some logs.
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.
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 question or issue you are having
I've made a migration of docker. I copy settings of images and copy files of Deconz. It's seems to work, but in Deconz UI I have some unrecognized devices like 0x2B53 etc. Is it possible to force update devices names? As I see in Phoscone I'm can only see devices with name in Deconz.
Screenshots
Environment
Host system: NAS Synology Running method: Marthoc Docker container Firmware version: 26660700 deCONZ version: 2.09.00 / 23.12.2020 Device: ConBee II Do you use an USB extension cable: yes Is there any other USB or serial devices connected to the host system? If so: -----
deCONZ Logs
Additional context