OTA from z2m_remote_index not filtering manufacturer name correctly resulting in bricked devices about zigpy HOT 4 CLOSED

@Hedda in fact the risk mentioned there is when you use the ota directory without metadata, which precisely z2m index attempts to mitigate. And I've used the z2m index.

Yes, I know there is no 0 risk due to the shitty Tuya ecosystem in particular and how vendors handle updates and access to them.

I'm not blaming anyone here, I was willing to test, and knew the risk and that's why I've updated 1 device at a time and tested the result.

But in any case there is bug in the logic of the z2m index metadata loading in zigpy and I'm reporting it, without that bug the firmware would not be detected as valid for that device. Your comment doesn't provide any value, if there is a bug can't I report it? I'm willing to test and risk precisely for reporting bugs.

from zigpy.

I don't like mention someone directly, but I think is important to fix this bug ASAP to prevent more bricked devices so... pinging @puddly and @dmulcahey as the author and approver of the #1340 PR that introduced the bug.

from zigpy.

FYI, believe the risk of bricking Tuya devices was mentioned in #1340

from zigpy.

FYI, believe the risk of bricking Tuya devices was mentioned in #1340

And also in home-assistant/core#111159

from zigpy.