mDot in Auto OTA can't switch to new network

[Agathe Lee]

I tried to switch a previously used mDot to a different network. I started by sending at&f, then I was going to follow up with AT commands relevant to the new network settings. Since the mDot had been previously used in Auto OTA join mode, it kept attempting to join its previously known network and did not respond to the AT commands. I was able to change its settings by powering the Conduit it used to know and letting it join its previous network. But this concerns me, because in the event that the previously known network is permanently unavailable (that is broken or stolen) do we have mDot that can’t respond to commands to join a new one. How do you work around this?
Thanks!

[Bryan Tran]

Hi Agathe,

Try shift key and +++ and see if it helps.

Thank you,

BT

[Agathe Lee]

It helps sometimes. I found that it helped best when sent shortly after a hardware reset.

[Author]

Posts