Like @Steven_Keller, I am moving away from Particle after years of working with their products. I have been developing with the XBee3 Cellular LTE-M/NB-IoT modem and the Xbee3 ecosystem as a whole. I am able to easily and consistently get the Xbee3 cellular modem to connect to AT&T and T-Mobile using a Hologram SIM and the following relevant Digi XCTU settings:
- AN: hologram
- CP: 0 (auto detect)
- N3#: 2 (LTE-M Only)
An issue I am running into is not getting connected, but actually having a usable connection. The behavior is such that the modem is returning a True for the cellular.isconnected() method which signifies the modem is connected to a cellular network and has a valid IP address. I am also able to open a socket, and the modem sends the data without catching an error, but it will stop coming through on the cloud side (Ubidots) after a while.
I have a transmission counter set for each send, and it will be chugging along at the set 10min interval and then the transmission count will jump because the cloud side did not receive the data, but the modem thought it was sent so it counted it.
As a test, I purchased a AT&T IOT SIM and put it in the exact same device with the same setup only changing the APN to match the required from AT&T and after 24 hours of testing it has not missed one transmission, where the other identical setup (with Hologram SIM) stopped getting data to the cloud after about an hour from starting the test. At the time the Hologram SIM was showing AT&T Hologram as the network operator.
I could me missing a vital setting or best practice, so I wanted to put it out there to see if anyone had similar experience or suggestions/advice.