<div dir="auto">Makes sense. I guess I could always automate with a boot script.</div><div dir="auto">Thanks again.</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 18, 2021 at 8:19 AM Aleksander Morgado <<a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Hey,<br>
<br>
On Tue, May 18, 2021 at 12:47 PM Christopher Penney <<a href="mailto:mrpher@gmail.com" target="_blank">mrpher@gmail.com</a>> wrote:<br>
><br>
> Wow, it worked! Thank you VERY VERY much. Turns out the problem was exactly that; the default profile was incompatible with IoTDataWorks default APN.<br>
> You really saved the day (week, months really) thanks again.<br>
><br>
<br>
Glad it worked!<br>
<br>
> I'll let the Balena team know about the default versions and the fix in case others run into the same problem.<br>
><br>
> Meantime, one more favor to ask - is there a programmatic way to clear that default profile at boot rather than have to do it manually on each new device we provision?<br>
><br>
<br>
No, there is no such thing right now. ModemManager won't do any<br>
"automatic" configuration of this kind, if there are profile changes<br>
to be done, they should be requested by the user.<br>
<br>
-- <br>
Aleksander<br>
<a href="https://aleksander.es" rel="noreferrer" target="_blank">https://aleksander.es</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Sent from my phone pardon the typos</div>