[Matt Barney]

@aufdenkampe – I’ve confirmed that indeed, all stations are now reporting data as expected.

[Matt Barney]

Thanks @aufdenkampe, that sounds like a great plan. I like the idea of the forwarding log too.

We’ll watch for a change in stations’ status once the proxy is in place.

[Matt Barney]

Interesting – we have 1 site with the new LTEbee, and it also weathered the cutover successfully.

@aufdenkampe, As of now, we’re not seeing any of our Digi stations that are able to upload to the new server as a result of the temporary shutdown of your old server, assuming that that indeed took place yesterday.

Matt

[Matt Barney]

We have 1 site that resumed uploading data at 12/8/2021 14:45 ET. We’re assuming that the volunteer restarted it.

5 additional sites are uploading after we restarted them, and 19 sites have not reported since the cutover to the new server.

[Matt Barney]

We tried the Hologram SIM pause idea on one station, but it had no effect, which isn’t too surprising.

@aufdenkampe, please keep us informed about the timing of the temporary shutdown of the old server. Thanks for your efforts.

Matt

[Matt Barney]

Thanks @heather, and @aufdenkampe, that does makes sense, with the symptoms we’re seeing. Good to know that the data are not being lost in the interim.

Shutting down the old server temporarily sounds like a good idea; all of our devices are on a 15-minute sampling period, so 20+ minutes should cause at least one failed message from the device, and the relative cost of losing one or two data points would be well worth it.

Power cycling all of our devices would be pretty painful; some stations (e.g. with wipered sensors) are hours from their caretakers’ locations.

Wow, it would be nice to be able to remotely initiate a cache flush (or even a reset) on the LTE modems! But, as I read Digi’s documentation, I think that would have to be initiated by an AT command from the host (Mayfly). (Right??) I don’t *think* there’s a way to address this from the Hologram dashboard, but if anyone knows, please share. Hmm… I wonder what clicking Hologram’s “Pause” button for each SIM would do…?

Matt

[Matt Barney]

oof… what a day to release onto AWS! 🙂 https://techcrunch.com/2021/12/07/amazon-web-services-went-down-and-took-a-bunch-of-the-internet-with-it/

Nonetheless, happy to hear of this milestone for MMW!

-Matt

[Matt Barney]

FWIW, I asked SIMCom about their Verizon certification, and this is their reply:

We are in the process of getting the certification.  All testing has been completed and we are just needing to schedule and official drive test with Verizon.  After this we expect to have certification shortly after.  I am estimating we will have it completed late December or January.

Matt

[Matt Barney]

Ok, that’s very interesting. It sounds like the LTEBee with a Hologram SIM has been using what it sees as the ‘best’ carrier for a given connection. The Digi modems would never do that for us in areas where Verizon was the only viable option, so we had to get Verizon-branded SIMs for those cases.

[Matt Barney]

Hmm, so maybe no one has tried Verizon with the new modem yet. SIMCom claims that chip supports Verizon, but (suspiciously?) they don’t have a Verizon Certification document available for download, as they do for other carriers. And they list all their supposedly supported carriers under a heading labeled “Certifications(plan)”, which makes me wonder if it’s not been certified by Verizon yet.

We have 4 stations in the field running via Verizon on the Digi modem, so I hope this gets resolved soon. It’s nice to have options for multiple carriers when you operate stations across the country.

[Author]

Posts