ZHA wrongly detects Fingerbot Plus

[josecarre]

The problem

Fingerbot Plus device is wrongly detected (as TS0001 by _TZ3210_j4pdtz9v), with wrong/incomplemte parameters/datapoints. Maybe the issue and fix is related to same behavior happening in zigbee2mqtt (Koenkk/zigbee2mqtt#18494). Would it be possible to fix it also in ZHA?
Device info from zigbee2mqtt: https://www.zigbee2mqtt.io/devices/TS0001_fingerbot_1.html

Thanks

What version of Home Assistant Core has the issue?

core-2023.8.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Device: https://www.zigbee2mqtt.io/devices/TS0001_fingerbot_1.html
Similar issue in zigbee2mqtt: Koenkk/zigbee2mqtt#18494

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[puddly]

This is the corresponding PR in the ZHA quirks repository: zigpy/zha-device-handlers#2506. Once it is complete, your Tuya device will be supported.

[josecarre]

This is the corresponding PR in the ZHA quirks repository: zigpy/zha-device-handlers#2506. Once it is complete, your Tuya device will be supported.

Thanks for the info @puddly , I understand that after this is merged in next ZHA release then we'd need to wait for HA to bump ZHA to whatever release is including this fix, right?

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.