#nic-Terminal
desert cargo
Hi @bitter quartz when you call discoversReader(), the Stripe SDK discover and reader the online readers within the same network. If you want to list all registered readers regardless of the network, you can call the list readers API (https://stripe.com/docs/api/terminal/readers/list?lang=curl#list_terminal_reader)
bitter quartz
The SDK returns all readers regardless of the network from my testing?
I don't want to return all the readers, just particularily the ones on the same network as the client using the sdk
desert cargo
OK. are you passing a location when calling discoverReaders() ?
bitter quartz
I'm not passing location, only simulated = false
desert cargo
You can pass a location to the discoverReaders() function so that it will return the readers that are registered to that location.
bitter quartz
I'm not concerned about the location. A single location could have multiple networks that the readers could connect to. So unfortuantely this option doesn't help as it wouldnt make sense to create a new location for each network
desert cargo
You said that discoverReaders returns all readers regardless of network. Can you send me the list of reader IDs that you get from discoverReaders?
bitter quartz
Here is just the Reader ID that is discovered tmr_Er8VKA8fYOLxya
desert cargo
OK, is this reader in the same network as your Terminal app?
bitter quartz
no
desert cargo
What reader do you have in your network?
bitter quartz
None
desert cargo
Was this reader in your network previously?
bitter quartz
yes
desert cargo
The status of tmr_Er8VKA8fYOLxya is online, so it's currently connected to a network but it's different from the network from your Terminal app? What's the relationship between these two networks? are they connected?
Also what kind of error do you get when trying to connect to this reader? can you send me the request ID of the connection token creation API?
bitter quartz
- Yes, it's a different network
- No relationship between these two networks. One is literally a hotspot via my mobile and the other is my home wifi.
- Once the sdk attempts to connect to the reader that is on a different network, the sdk will return
{
"error": {
"message": "Could not communicate with the Reader. Please make sure your reader is online and on the same network as your device. See https://support.stripe.com/questions/terminal-connectivity-issues for more details.",
"code": "reader_error"
}
}
- Here is the Request ID of the Connection Token creation req_G3YobqlrEHlrci
desert cargo
Sorry I haven't got a time to reproduce this problem with the setup that you described. Can I suggest you to create a location for the readers that are in the same network of the Terminal app, so that when you call discoverReaders(location) you can get the list of readers that you can connect to.
bitter quartz
Thats a shame. Unfortunately , that approach won't be practical for my process. I'll hve to find another way. Thankyou for your time, is there someone else who would have time to reproduce the set-up?
desert cargo
I'm really sorry for that, the discord channel is quite busy today.
Can I suggest you to write to Stripe support https://support.stripe.com/contact and tell them you've chatted with the engineer in Discord, and they will forward your ticket to us and we'll continue to support you via email.