#Akshay
little ice
brittle turtle
Hi đź‘‹ I'm not familiar with the ability to add a simulator device from the dashboard, can you elaborate on what you're referring to?
compact sorrel
I went to the dashboard , created a location inside that i created a simulated terminal device
In the front end i am trying to connect to that simulated device by giving location id
brittle turtle
Ah, alright, I see what you're talking about. Do you have multiple devices registered with that location?
brittle turtle
Gotcha, which integration path are you following? (Server-driven, javascript, mobile)
compact sorrel
Javascript
brittle turtle
Gotcha, the creation of a simulated reader in the dashboard seems to be specific to testing our server-driven approach, so I don't think it is what you will want to use here. Instead, when calling discoverReaders you'll want to set simulated to true. You can see a sample of this here:
https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=js&reader-type=simulated
compact sorrel
So that is useless for javascript implementation?
brittle turtle
I believe so, I don't think the created simulate reader plays a role in the js test flow.
compact sorrel
If i dont have a physical device.. will i be able to replicate all the failure scenarios with the simulated device?
And another question , if i use the server driven implementation Will tht “device should be on same network error” be gone
brittle turtle
As mentioned in that page, the simulated reader accespts both testCardNumber and testPaymentMethod parameters that allow you to control how the simulated reader will behave. You can also find a list of our test cards here:
https://stripe.com/docs/testing
compact sorrel
Wt about the answer to my second question?
brittle turtle
Yes, on the same network only applies to Javascript integrations where the POS and reader directly communicate with each other.
brittle turtle
Happy to help!