Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mmWave sensor is recognized simultaneously as a sensor and a smart plug #7778

Open
2 tasks done
retrography opened this issue May 17, 2024 · 0 comments
Open
2 tasks done

Comments

@retrography
Copy link
Contributor

retrography commented May 17, 2024

Does the issue really belong here?

  • 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

Capture1
Capture3
Capture4
Capture5

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant