# Switching fleet leads to connectivity issues (encryption issue)

**URL:** <https://community.particle.io/t/switching-fleet-leads-to-connectivity-issues-encryption-issue/70910>\
**Category:** Cellular\
**Tags:** msom\
**Created:** [January 9, 2026, 8:37pm UTC](https://community.particle.io/t/switching-fleet-leads-to-connectivity-issues-encryption-issue/70910 "2026-01-09T20:37:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![edison\_vs\_tesla](https://avatars.discourse-cdn.com/v4/letter/e/e95f7d/32.png) [@edison\_vs\_tesla](https://community.particle.io/u/edison_vs_tesla)\
**Post date:** [January 9, 2026, 8:37pm UTC](https://community.particle.io/t/switching-fleet-leads-to-connectivity-issues-encryption-issue/70910/1 "2026-01-09T20:37:39Z")

</div>

Hey,

I've been trying to move some MSOM devices over to a new fleet. I was able to move the device over and it shows as online for a brief time, but goes offline again. Re-configuring the device with [setup.particle.io](http://setup.particle.io) also works and it will come online for a few hours with tinker. However, once I try to flash my own firmware, it will not connect to cellular or come online. Stuck in green flashing mode. I can’t even get the device onto the original fleet.

I have been playing around with the particle CLI to see if I can refresh the encryption keys, but I haven’t been able to make that work.

On a slightly related note, I have a couple of other MSOMs sitting around with a deactivated SIM. I was trying to re-purpose those. Getting the flashing green LED there too. Even after a new run through [setup.particle.io](http://setup.particle.io).

Any advice would be appreciated!

Thank you!

---

<div class="post-metadata">

**Author:** ![rickkas7](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/rickkas7/32/8681_2.png) [@rickkas7](https://community.particle.io/u/rickkas7)\
**Post date:** [January 9, 2026, 11:41pm UTC](https://community.particle.io/t/switching-fleet-leads-to-connectivity-issues-encryption-issue/70910/2 "2026-01-09T23:41:14Z")

</div>

You should add this line to your firmware:

```auto
SerialLogHander logHandler(LOG_LEVEL_TRACE);

```

and get a debugging log from the USB serial connection from boot during blinking green, for several minutes, and ideally 10+ minutes, to see what actually is failing. You can also use the [Web device doctor](https://docs.particle.io/tools/doctor/).

It's almost certainly not encryption keys because those are only used after you're in blinking cyan.

---

<div class="post-metadata">

**Author:** ![edison\_vs\_tesla](https://avatars.discourse-cdn.com/v4/letter/e/e95f7d/32.png) [@edison\_vs\_tesla](https://community.particle.io/u/edison_vs_tesla)\
**Post date:** [January 13, 2026, 4:37am UTC](https://community.particle.io/t/switching-fleet-leads-to-connectivity-issues-encryption-issue/70910/3 "2026-01-13T04:37:52Z")

</div>

> [@rickkas7](#):
>
> `LOG_LEVEL_TRACE`

Thank you. It ended up being a bug in my firmware. Reverting to a boilerplate implementation worked.
