This brings the Apple iOS app up to date and implements NVMQ node<>app command messaging, which will automatically be set as the default. This is a minor release for Android, cleans up a couple of bugs and dials back the developer instrumentation.

API 96 clears up a couple of bugs and also now updates the wpa_supplicant WiFi control configuration file with the appropriate country code.

Season’s Greetings … Gerry.

This releases focuses on our migration away from AWS Messaging Services. By default, after you install the update for your Android device, your mobile app will start using “NVMQ” in favor of “AWS MQTT” for App to Node messaging.

This update requires that your nodes be at API Version 95 and RedNode Code Revision 1245 or better.

Also in the release is support for “Private Nodes” – an automated way of configuring your nodes that are on the same network so they connect to each other without complicated configuration in “rpt.conf”. You can find the option on the “Your Nodes” screen’s context menu.

We released the Android version first because the issues between Android and AWS MQTT were primarily what drove the migration – thus Android was the priority.

Apple iOS users – hang in there – we’ll get caught up hopefully next week.

73 … Gerry.

(Wait what happened to API 94 ? Three guesses …)

This is the beginning of our move to a new messaging structure. Historically we have used AWS’s IoT MQTT messaging service to propagate information between your ClearNodes and your Apple iOS and Android mobile applications. There seems to have been changes at AWS that have degraded service for our system.

We have implemented our messaging server using a system that is Open Source and very mature. Initially we will be running the two systems in parallel so we can validate the solution – with an eye to making a complete switch at some point in the near future. This should guarantee us that teething problems won’t affect the current production environment.

There will be updates for the ClearNode mobile apps coming later in the month – but for now we need to prove out the back end infrastructure. Until the mobile app release, you shouldn’t see any difference in your nodes or the mobile app.

73 … Gerry.

Just received a healthy supply of the Raspberry Pi 4B !

This should keep us in production for a while. No word on Pi Zero 2W unfortunately. The Raspberry Pi Foundation say they are working as hard as they can to bring supplies forward, but it’s still unclear when the supply chain will get back to normal.

One day at a time …

73 … Gerry.

This video is a few of weeks old – it just barely addresses the interrupted supply of the Raspberry Pi boards. But it’s also interesting in that it tracks the evolution of the Foundations mission and customer base. Spoiler alert – they didn’t predict the interest they were going to get from us “mature consumers”.

(PS … by no means endorsing “Micro Center”.)

73 … Gerry.

We are working on some changes to the server infrastructure behind the “Fleet Last Heard” live feed of active nodes. So there will be interruptions to this service today, and occasionally for the rest of the week.

Apologies for the inconvenience, but it’s all in service of more a more robust infrastructure going forward …

73 … Gerry.

Some of you got API 93 over the weekend as a part of a test of new infrastructure which we are working on. You can ignore this version, it will not be made current, likely the next version will be API 94. There is no functional difference from 92 from the end user’s perspective. If for any reason you want to go back to API 92, just perform a regular RedNode update and you will be stepped back to API 92.

73 … Gerry.