After considerable user feedback (THANKS !), we’ve added a feature to the ClearNode Smartphone app whereby the user can select WHICH Popular Host Traffic Notifications they receive. You can still turn the feature off/on completely, but now you can restrict the notifications you receive to the hosts that matter to you and ignore the rest.

From the top “Your Nodes” screen tap in the top right corner on the cog or wrench icon to enter the App Settings screen – scroll to the bottom of the screen and tap on “Choose Hosts for Traffic Notifications”. Make your selection and tap the Save icon in the top right corner.

73 … Gerry.

As part of our effort to help folks find the “action” – we’ve implemented a new ClearNode smartphone notification. We watch the reports of connections and key-ups, and aggregate them so we can detect where new traffic has started up. We then send notifications to users who have been using their nodes within the past 24 hours.

By default these notifications are enabled (if you have enabled notifications in your copy of the ClearNode smartphone app) – but you can turn them off – “Your Nodes” > “Settings” > “Accept Traffic Notifications”. This setting is global for your call sign – so turning it off will turn off the notifications for all the instances of the smartphone app you have running.

We just started up these notifications this weekend – so bear with us while we refine the algorithm that detects traffic and how it disseminates the notifications.

We only watch a subset of all the node endpoints out there – generally well known hubs like the WinSystem, Blind Hams Hubs, East Coast reflector, etc. If you are running a hub or net of your own and you’d like it to be included – let us know – send us the node # and description – we’ll include it in the process.

Conversely, if you don’t like the idea of your hub getting attention – let us know – we’ll disable notifications for that endpoint.

These notifications do not relate to your personal node – they only relate to the popular public hubs and nodes. Presently only AllStar and EchoLink are included – we’re thinking about how to include the Digital Modes, but it’s complicated.

Suggestions and experience reports are welcome !

73 … Gerry.

If you have an ASL3 based ClearNode – some Pi 4B based nodes and all Pi 5B nodes – please read the following …

ASL have just release a bunch of updates – DO NOT update yet ! You’ll know when to update because the smart phone app will start nagging you. We want a little time to do the updates on our development devices and verify that there’s no breaking changes, or changes for which we need to change configurations. Looks like there are some fixes for things that weren’t working properly in our use case – so we need to verify all that.

Check back here for announcements !

73 … Gerry.

(Apple iOS App Store release still pending …)

Recommended for all users and installations !

• New command to retrieve current kernel version from your node
• Added node shutdown to options for ClearRLS soft button
• Provide node under-volt condition notification and status in Node Details screen
• Fixed restore node configuration from server
• ASL3 update prompts now treats DVSwitch as part of overall package updates
• Fixed DTMF commands for reboot and shutdown in ASL3 distribution
• No longer polling for NWS Alert counts when SkyDescribe is disabled

73 … Gerry

If you are running ASL3 on your node – i.e. a Pi 5B based model, Pi 4B based model where you explicitly migrated to ASL, or a Pi 4B based model where you selected the ASL3 distribution option when you purchased – it is now time to update your ASL3 installation to the latest release from AllStarLink.

CRITICAL – You must update your “RedNode API Level” to 129 first !

Likely this will happen automatically when you reboot your node, or you will be offered the update in the ClearNode mobile app.

Once you have upgraded to API 129, likely you will be offered the update to ASL3 after the reboot – proceed with the update.

IMPORTANT: This update takes a LONG time ! Do not interrupt power – be patient, wait for it to complete.

When you’re done – this is how your “Versions” section should look

73 … Gerry.

All users should update as soon as they can !

Primarily this release prepares ASL3 type nodes for the upcoming update to the ASL3 code. However, there are some common changes that ALL nodes should pick up.

The update to ASL3 will be coming shortly.

73 … Gerry.

(This relates to all Pi 5B based ClearNodes, and all Pi 4B ClearNodes where you chose ASL3 at the time of purchase, or you have subsequently migrated.)

PLEASE CONTINUE TO HOLD OFF FROM UPGRADING !

Although AllStarLink.org have been working furiously (on the weekend!) to solve the issue and have released a fix. I suggest you hold off from upgrading just yet until it’s clear this fix works and that it hasn’t introduced any further issues.

Your best course of action is to wait until the ClearNode mobile app warns you that a software update is pending and offers you the upgrade.

73 … Gerry.

The ASL3 team has been tracking an issue that severely degrades the audio in ASL3 – DO NOT upgrade your ASL3 software installation until further notice. They are busy working on a fix. We will report any updates here !

The last known good version as indicated in Node Details > Versions : “Asterisk 20.10.0+asl3-3.1.0-1.deb12”. If you have already upgraded beyond this version contact Support as there is a work around.

This does NOT affect HamVoIP based ClearNodes.

73 … Gerry.

We’ve been using the down time to catch up on some overdue tasks – particularly the product documentation. We move quickly to deploy new features and to update existing ones, the unfortunate side effect is that the documentation sometimes lags behind.

It’s a good time to review SMARTPHONE SOFTWARE, ADVANCED SETUP and MANAGING WIFI.

73 … Gerry.

The last shipments before the sojourn will be made on December 26th.

We will leave the store open and accept orders – but your order will NOT BE SHIPPED UNTIL AFTER JAN 27TH. Shipments will resume in the order that payment was received.

Please be aware of this because if you submit an order in that period and then want to cancel it – we will deduct the credit card transaction fees from the refund per our normal terms.

73 … Gerry.