#PBnJ
1 messages · Page 1 of 1 (latest)
Hi 👋 I haven't heard of additional complaints about this yet, do you have more details that you can share?
When did this start happening, when were you last able to process an update, are all readers impacted or only some, what version are they currently on and what version are they updating to?
We have at least three different locations in the last 12hrs reporting this.
IDs of the impacted readers would also be beneficial.
Hm, those look like three distinct error codes, interesting.
Yes. Not a common thread and these guys say that they tried with different WiFi networks too.
Let me dig around and get the reader IDs.
Thank you, I'm also looking to see if this was flagged on our end.
@silver snow this is what I got:
tmr_FDYcOAn65dVmQA
tmr_FLuvZQ1iStSHKG
tmr_FLu3vwUycLTLHl
- First noticed around 4pm CST - 7/24/23
- Unsure of last processed update as the readers are on ‘auto update’
So far we believe this effects readers that attempt to update - so the number would start small and grow over time.
Thank you, taking a look to see if anything jumps out at me.
Hello 👋
Taking over, we're still waiting on hearing back from our terminal team
In the meantime, have the merchants try rebooting the readers to see if that fixes the update?
I beleive they did but let me confirm and get back.
Looks like tmr_FDYcOAn65dVmQA reader is bricked and would warrant a replacement. Please work with our support team to get it replaced.
The other two readers aren't showing any signs of being bricked