Ledvance SMART+ Motion Sensor disappearing

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices

BSD 3-Clause "New" or "Revised" License

1.9k stars 503 forks source link

Ledvance SMART+ Motion Sensor disappearing #4625

Closed MaMaKow closed 3 years ago

MaMaKow commented 3 years ago

Describe the question or issue you are having

I have a "Ledvance SMART+ Motion Sensor" connected to my ConBee II. The ConBee II lives on a Raspberry Pi 4 with openhabian.

The "Ledvance SMART+ Motion Sensor" tends to "disappear". Status Not reachable

Screenshots

after new pairing:

Environment

Host system: Raspberry Pi 4
Running method: Raspbian
Firmware version: 26660700
deCONZ version: 2.07.01 / 8.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? No

deCONZ Logs

/usr/bin/deCONZ -platform minimal --dbg-info=2 > debug.txt debug.txt

Additional context

There are 4 LEDVANCE Smart+ Plugs and one LEDVANCE Smart+ LED in the same network. The distance between the Motion Sensor and the next Plug (->mesh) is below 1 meter.

Mimiix commented 3 years ago

Can you provide logs on dbg-aps=2 and dbg-error=2 ?

MaMaKow commented 3 years ago

I started nohup /usr/bin/deCONZ -platform minimal --dbg-info=2 --dbg-aps=2 --dbg-error=2 > debug.txt & Right now the sensor is there. Should I let the log get bigger until the thing is gone? Or Should I just stop after it has reached about a few Megabytes? Is it OK, to have one logfile with all three options? Or is it better to have seperate files for the three options? If so, can there be three processes of /usr/bin/deCONZ at once?

Mimiix commented 3 years ago

Just have them in one log :) That's fine.

You can provide the logs already. If there's a fundamental issue, it would show regardless (interference, bad connections etc).

MaMaKow commented 3 years ago

splitme00.log

MaMaKow commented 3 years ago

splitme02.log splitme03.log splitme04.log splitme05.log splitme06.log splitme07.log splitme08.log splitme09.log splitme10.log

github-actions[bot] commented 3 years ago

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.

github-actions[bot] commented 3 years ago

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.