#farrukh-terminal-location
pale sage
Hi 👋 connecting and disconnecting from the reader each time may be excessive if your POS is staying active between transactions, but otherwise that sounds right I believe.
Retrieve the Payment Intent after creating it may be redundant, but may not be depending on the surrounding context.
pure jewel
Do i need to discover the reader with every transaction?
there could be 1 or more POS systems installed that may be using this 1 reader
pale sage
You'll probably want to discover each time you need to connect to a reader, doing that for each payment sounds like it may be excessive, but I'm not familiar with your landscape so it may make sense in your context. Is this working as you're expecting in your testing?
pure jewel
it works most of the time but some clients are complaining that the reader does not show up when discovered, what could be the cause?
Clients do have stable internet connection
pale sage
It's hard to say without more details, what troubleshooting have you gone through with those clients so far?
pure jewel
I have logs of the POS that indicate that the client internet was stable and all of the above mentioned steps successfully executed, the only difference is that the "discover reader" is not returning any reader so the process exits at the 3rd point.
Troubleshooting
I have had a live session with the client
Checked their internet connection (it was stable)
Restarted the reader
Restarted my POS
these steps worked for one client but failed for others
pale sage
What type of readers are you using?
pure jewel
BBPOS WISEPOS_E
pure jewel
we do have DNS configured at the client's location, they are currently using only 1 network with 1 router.
Is there any chance that these configurations are being changed randomly?
pale sage
That's not something I'd have insight into, I wouldn't expect their local network setting to change randomly but I guess they could.
pure jewel
would a reader be discoverable if it is already connected a system?
pale sage
I'm fairly certain it is
pure jewel
what are the possibilities for these readers not being discovered?
this has been reported by multiple clients so my first thought was that I am doing something wrong.
pale sage
The reader isn't connected to the network
It isn't connected to the same network as the POS
The DNS being used by the network doesn't support local DNS resolution.
An incorrect location is being used.
pure jewel
can you please elaborate "An incorrect location is being used."
quartz streamBOT
pale sage
When you discover readers, you can provide a location field to only discover readers registered with that specific location. If you provide a location with no registered readers, I would not expect to see any readers returned.
Usually what you're describing is caused by local DNS resolution limitations though. What DNS server are your impacted clients using?
copper minnow
farrukh-terminal-location
pure jewel
192.168.5.58
heady ember
Hello! I'm taking over and catching up...
Generally we recommend a 1:1 relationship between a Terminal reader and each POS device. Using a single POS device with multiple readers, or a single reader with multiple POS devices typically causes several issues.
Specifically, the discover process is designed to be run infrequently. You discover a reader, connect to it, then process many transactions. That usually happens once or twice a day if everything is working well.