Issues provisioning eSIM following latest instructions

Tachyon
1

Hi all, got my beta Tachyon a week or two ago and have had many problems getting the Tachyon to connect to my wifi at home - blew through the 100MB free cellular limit just by messing around on the machine and forgot it was limited :sweat_smile:. I've got it at a hackerspace on wifi now so I can keep messing around.

anyways, I'm really interested in the cellular capabilities of the device but not super interested in paying Particle $300 up front for a block of cell data, and have been exploring the tachyon docs on installing my own eSIM profile. I followed the instructions in the docs (looks like they've recently changed?) and I'm running into this issue:

the docs say to use this command:

particle-tachyon-ril-ctl esim download '<rsp_url>' <iccid>

While I've figured out that rsp_url probably actually means the provisioning string given to me by my carrier (and my tries seem to confirm that as listed below?), but I have no clue what I should be putting for the ICCID value. In the previous version of the docs I believe there was a placeholder value to use if I didn't know what value to use? It might even be the 12341 profile listed below?

rild when starting shows these values:

Jun 12 19:04:05 agnes particle-tachyon-rild[3346]: [89000123456789012341, disabled] #perhaps this is the placeholder i should be using?
Jun 12 19:04:05 agnes particle-tachyon-rild[3346]: [xxxxxxxxxxx1245267, disabled]
Jun 12 19:04:05 agnes particle-tachyon-rild[3346]: [xxxxxxxxxx919000202, enabled]

the 267 profile (iccid?) is the Particle line. The other profiles were on the device already.

for the command:

particle-tachyon-ril-ctl esim download 'LPA:1$url.from.my.provider.com$AFAKEMATCHINGIDTHATISNOTREAL' 8969696969696969690

and

particle-tachyon-ril-ctl esim download 'LPA:1$url.from.my.provider.com$AFAKEMATCHINGIDTHATISNOTREAL' 89000123456789012341

I get the same output in the logs, pasted here:

Jun 12 19:31:43 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:41.653 PDT 2025: Processing: LPA DOWNLOAD
Jun 12 19:31:43 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:41.653 PDT 2025: LPA STATUS command received
Jun 12 19:31:43 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:41.653 PDT 2025: rsp_url: LPA:1$redacted.com$redacted, iccid: 89000123456789012341
Jun 12 19:31:43 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:42.989 PDT 2025: lpa: [INFO] Connection established with redacted on port 443
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.334 PDT 2025: lpa: [INFO] TLS Handshake completed successfully
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.720 PDT 2025: lpa: SM-DP+ address: redacted
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.720 PDT 2025: lpa: Matching ID: redacted
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.720 PDT 2025: lpa: [INFO] Downloading profile
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.720 PDT 2025: lpa: [INFO] SM-DP+ address: "redacted"
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.720 PDT 2025: lpa: [INFO] Matching ID:    "redacted"
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.720 PDT 2025: lpa: [INFO] Initiate authentication
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.720 PDT 2025: lpa: [tp] Sending ISDR request
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.721 PDT 2025: lpa: [tp] Sending ISDR request
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.721 PDT 2025: lpa: [INFO] ES9+.InitiateAuthentication succeeded
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.721 PDT 2025: lpa: [INFO] Mutual authentication
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:43.721 PDT 2025: lpa: [tp] Sending ISDR request
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:47.896 PDT 2025: lpa: [INFO] ES9+.AuthenticateClient succeeded
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:47.896 PDT 2025: lpa: [INFO] Getting bound profile package
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:47.896 PDT 2025: lpa: [tp] Sending ISDR request
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.734 PDT 2025: lpa: 67", Response: +CSIM: 4,"9000"
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.735 PDT 2025: lpa: [INFO] ES9+.GetBoundProfilePackage succeeded
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.735 PDT 2025: lpa: [INFO] Loading bound profile package
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.735 PDT 2025: lpa: [ERROR] Load BPP failed (es10b): -50336515
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.735 PDT 2025: Error: lpa output: [ERROR] Load BPP failed (es10b): -50336515
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.735 PDT 2025: lpa: [ERROR] Profile download failed: ES10 preconditions not fulfiled, argument error (code -0x03001303)
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.735 PDT 2025: Error: lpa output: [ERROR] Profile download failed: ES10 preconditions not fulfiled, argument error (code -0x03001303)
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.735 PDT 2025: lpa: [INFO] Operation took 250 ms
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.740 PDT 2025: Error: lpa exited with error code: 253
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.740 PDT 2025: LPA STATUS command received
Jun 12 19:32:01 agnes particle-tachyon-rild[9246]: Thu Jun 12 19:31:52.740 PDT 2025: lpa download final result: failed, unknown

anyways, let me know what I might be missing!

2

Hey Ellie!

Welcome to the forum and to Tachyon!! :tada:

I’m so glad you’re exploring Tachyon, but sorry to hear it won’t connect to your Wi-Fi at home. First, just to check - did you follow the instructions here for connecting your device to Wi-Fi?

:backhand_index_pointing_right: Setup instructions & plan details

The setup process should reliably connect to wifi, BUT it does require quite a bit of data when it first boots up. I'll make sure this is documented now.

This guide should help onboard your device and get it connected:

:backhand_index_pointing_right: Wi-Fi instructions

If not, that page also includes guidance for manually configuring Wi-Fi if needed.

And about that 100MB cellular limit - I wanted to check that this means that your phone’s hotspot was used to tether and then it ran out? Just so you know (good news for you, not so much for us yet! :sweat_smile:), the Tachyon beta data plan currently includes gigabytes of data for testing - it’s not unlimited, but there’s a generous allowance right now for the first few weeks while customers test things out. We’ll lock this down to ~2GB free per month soon (and allow you to 'top up' each month if you run out), but for now your device should have plenty of cellular data available.

On the $300 block of cell data, that is actually for our microcontroller products, not for Tachyon. The data plan we offer for Tachyon is much more reasonable and is published here:

Finally, regarding your eSIM command, you’re doing the right thing! The command you used looks correct. We doneed to improve our documentation a bit to more clearly explain what the rsp_url and iccid parameters should be - I’ve just updated the eSIM docs here to expand this section a little more:

:backhand_index_pointing_right: Updated eSIM instructions

Note that we need to remove the iccid param in the download - we'll update the daemon shortly and loop back.

I’ll also come back in a bit to take a closer look at your log output and see if I can help diagnose why the download might be failing.

Thanks again for sharing this and for trying things out so deeply - we really appreciate it! :raising_hands:

Thanks

Nick.

3

Welcome to the forum and to Tachyon!! :tada:

thanks!

The setup process should reliably connect to wifi, BUT it does require quite a bit of data when it first boots up. I'll make sure this is documented now.

I think my issue is the documented issue with wpa3 - although going in and using nmtui to set it to wpa2 didn't work for my home network for whatever reason. It's now at my hackerspace in the server rack and successfully connected there.

And about that 100MB cellular limit - I wanted to check that this means that your phone’s hotspot was used to tether and then it ran out?

No. I received emails and notifications in the particle console that my 100MB limit had been reached. I haven't seen any mention of any limit higher than that.

image
image1326×712 62.5 KB

Thanks for providing that sheet! Glad to see more info.

I’ve just updated the eSIM docs here to expand this section a little more:

Thank you!

Note that we need to remove the iccid param in the download - we'll update the daemon shortly and loop back.

right on, thanks. to get the new version would I just apt update particle-linux? Or would I need to reflash?

Again, thanks for your response - heartened to receive a quality response so quickly. excited to see what silly things I can build :slight_smile:

4

Ah! Thanks and sorry - looks like a bug in our dashboard. Surprised nobody spotted that before, but we'll get it fixed asap!

Will loop back in the AM on the log.

Thanks

Nick.

1 Like
5

Hey Nick - just wanted to check in and see if there had been any progress? Saw a particle-linux update in apt but seems like the esim subcommand is still requiring an ICCID.

No rush, I'm currently blocked on my esim provider's upstream SM-DP+ server serving a self-signed cert as it is anyways.

bonus selfsigned cert callout 
root@agnes:/# date
Wed Jun 18 18:28:41 PDT 2025
root@agnes:/# curl -vvv https://thales2.prod.ondemandconnectivity.com -k
>> snip
* Server certificate:
*  subject: C=US; L=Virginia; O=Thales SA; OU=DIS; CN=*.prod.ondemandconnectivity.com
*  start date: Apr  9 00:00:00 2025 GMT
*  expire date: May  8 23:59:59 2026 GMT
*  issuer: O=GSM Association; CN=GSM Association - RSP2 Root CI1
*  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.

>> snip