david-walker_unexpected

[median rain]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1222922350215958578

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[vocal hornet]

Looks like a faulty device to me

Have you reached out to the support team for this?

[quiet glade]

We had that thought as well, but it's happening on 8 devices across two batch numbers

[vocal hornet]

Ok let me double check with a colleague then

[quiet glade]

And yes, we have reached out to support

[vocal hornet]

Are these all new devices

[quiet glade]

Thank you!

All new devices except for a two month old devkit we use for testing

[vocal hornet]

Interesting ok

We're looking into this

We think it may be some bad batches of devices, but too early to tell. Will keep you updated

[quiet glade]

The affected batch numbers we're aware of are STR70Z1-11-044 and STR70Z1-11-003

Thanks again

[vocal hornet]

No problem. Do you have the serial numbers of all the affected devices?

[quiet glade]

The two I know are STR70Z1C316003122 and STR70Z1C316002161, and the devkit is SDR70Z1C335000050

[vocal hornet]

Thanks

Ok so this is going to require investigation from the team

They're aware of your support ticket as well