Good morning everyone and happy Monday!
I’m feeling much better after a solid weekend of rest. Thanks for all the well wishes, they sincerely helped.
Alright, sleeves rolled up and let’s tackle how to get you guys new switches effectively.
–
I will be sending out a form within the next couple of days that will help us verify those affected and get you on the list for replacements. I need to put together instructions to help people get the IEEE numbers (which shouldn’t be too hard).
–
To answer some of the questions I saw above (feel free to re-ask if I missed them, I’m still sort of sick so I may have missed them).
IEEE numbers affected?
Right now I only know of 94:34:xx and 38:5B:xx but I have a note out to the manufacturer for confirmation as they didn’t mention specifics in their report.
What was the root cause?
In my opinion, I’m not sure how the R1 and R4 was missed during QC, but I think the biggest factor as to why this was missed was the 0.5m testing range. No clue why that was an appropriate testing threshold as I have 10yr old Bluetooth devices that can connect at that range, but they sure can’t mesh properly.
Not trying to rehash any bashing as I know they’ve learned their lesson, but moving forward we’ve moved the testing to 5m for all devices and then spot checks at 100m.
Can these be safely used still?
Yes, the defect has no impact on the safety of the device.
Are all switches in these ranges defective?
We recommend that if you are experiencing any issues to reach out for a replacement. However, if you are not experiencing any issues, it’s up to you. We will honor it regardless.
–
Thanks again everyone for your understanding, I was fully expecting to walk into a pitchfork situation this morning, but was pleasantly surprised 