#franz - terminal wisepos e
light sedge
Hello! Just starting a thread for you -- I'll review and respond as soon as I can 🙂
Is the device actually shut down, or is the display just turned off?
gleaming carbon
i pressed the "power off" button.
it's completely off.
the state has updated, and now it shows as "offline" but it took a very long time to update it.
I stopped checking after a few minutes, so I'm not sure how long it took
light sedge
I think that's expected, it takes some time for the system to assume the reader has disconnect after not receiving an update, you can track this by handling conenction errors when you try to connect to a reader
gleaming carbon
hmmm is there an amount of time which should be expected?
also the onUnexpectedReaderDisconnect function gets triggered, even though the discoverReadrers result doesn't get updated.
light sedge
Which platform are you on?
the discover reader result might be cached unless you use the cancellable on ios, for example
If you make a subsequent discoverReaders call to refresh the list, you must first cancel the previous call with the Cancelable returned by discoverReaders.
light sedge
gotcha
I think you'd just want to handle the failed connection then as described here:
https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=js&reader-type=smart#connect-reader
Your UI can display the reader labels in the discover reader results so the staff member can verify they are selecting and connecting to the right reader with them which is powered on
gleaming carbon
yes, i'm already doing that.
I will not use the online/offline status label, and that should probably be ok - as you said somebody can inspect the device.
i just think it's misleading that the status shows it's online when it's not, and that it takes > 5min to update the status. In my view, this is seems like a bug. Not a blocking one, for my work, but still.
light sedge
I'm checking with folks on our side but my understanding is that this works by recognizing the reader has not "checked in" recently, but generally i'd say you should assuming the online status is valid but handle the error case