You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I definitively want to report a bug within deCONZ or its REST-API
Is there already an existing issue for this?
I have searched the existing issues and there is none for the bug at hand
Describe the bug
I have a Tuya mmWave occupancy sensor (TS0601 - _TZE204_qasjif9e). It is recognized and can be configured using an existing DDF. The issue arises that after some time it also shows up as a smart plug. In fact in deCONZ it only shows up as a plug, despite the fact that the correct DDF and basic clusters are displayed.
Steps to reproduce the behavior
It happens some time (hours or days) after adding the device, and then it continues to be like that.
Expected behavior
We should see it only as a sensor device (including a motion and a light sensor).
Screenshots
Environment
Host system: Intel Generic
Running method: Home Assistent deCONZ Add-on
Firmware version: 26780700
deCONZ version: 2.25.3
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
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Does the issue really belong here?
Is there already an existing issue for this?
Describe the bug
I have a Tuya mmWave occupancy sensor (TS0601 - _TZE204_qasjif9e). It is recognized and can be configured using an existing DDF. The issue arises that after some time it also shows up as a smart plug. In fact in deCONZ it only shows up as a plug, despite the fact that the correct DDF and basic clusters are displayed.
Steps to reproduce the behavior
It happens some time (hours or days) after adding the device, and then it continues to be like that.
Expected behavior
We should see it only as a sensor device (including a motion and a light sensor).
Screenshots
Environment
deCONZ Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: