Control (on-premise) - Release Notes

Release Notes
1

Thanks for all of your feedback helping improve the Alta products!

If you don’t see an upgrade after its release, please follow the steps HERE. You can perform the steps via SSH, or if you’re not comfortable with that, there is also a backup and restore option available.

1.0h Release Notes

Released on 08/16/2024

  • Improve web responsiveness on sites with hundreds or more Alta devices
  • Add Minimum Connection Strength option to SSIDs

1.0g Release Notes

Released on 07/25/2024

  • Add “location” support to uniquely identify Alta devices via their LED (Network tab)
  • Add ability to restrict specific channels from being selected for auto-channel selection (Settings->Site)
  • Resolve issues with restoring from backup that has VLAN settings
  • Resolve some issues with Google Translate

1.0f Release Notes

Released on 07/19/2024

  • Add User Groups Support
  • Add support for port-forwarding and reverse proxy configurations
  • Add support for hotspot on APs connected to local controllers
  • Add support for disconnect notifications
  • Resolve issues with controller restore functionality (backups from all prior Control versions can be restored)
  • Add option to disallow creation of new accounts
  • Fix Switch 10 Mbps link color
  • Add Adult Content filter option
  • Make controller discoverable via mDNS
  • Auto-update Let’s Encrypt Certs
  • Auto-update dynamic DNS when LAN IP changes

1.0e Release Notes

Released on 05/08/2024

  • Improve DynDNS reliability
  • Improve refreshing of devices that have been factory reset
  • Fix searching by Device MAC and IP; fix Network Device IP search; add search by make

Alta Control upgrade notes

Did you see a new release out, but it’s not showing when you check for an update? Please see the different steps below to assist working around this issue.

SSH Steps

If you do not see any updates after checking multiple times, you will need to perform the following steps:

  1. Create your own ssh key using a shell, if you don’t already have one. This is easiest in macOS or Linux, but can be done with “wsl” for Windows, as well
  2. Add your public ssh key as an administrator ssh key to the controller
  3. ssh to the device as the root user, and run the “dpkg --configure -a” command
    Then you will be able to successfully check for an update.

Backup and restore steps

If you are not familiar with ssh, and you don’t have any devices set up, or you are OK deleting and setting up your devices again (their configurations will be preserved if you restore from a backup), you can:

  1. Make sure you have a backup!
  2. Delete all of your devices, if you haven’t already
  3. Factory reset the Control device to 1.0d
  4. Upgrade directly to 1.0f.
  5. Restore your backup
  6. Click Set up by all devices
2 Likes