Skip to content

SiteMonitor Release Notes and Firmware Images for Version 20230325

Hardware Support

This version of the firmware is only for the SiteMonitor Base 3 (and expansion modules). It is the last standalone firmware released before migration to the combined firmware platform.

Due to a critical reliability bug which was discovered in early 2023, earlier versions of firmware are not recommended to be run on the Base3. As a result, we have removed all earlier firmware images.

Bug fixes for previous versions are maintained in the documentation below for historical purposes.

All Base3s which are not yet upgraded to the combined firmware should be running this version due to various critical reliability bugs resolved in the last standalone firmware version.

Upgrade Procedure for this version

  1. Download the firmware file. You'll want the 'regular' firmware file from below, not the recovery image.
  2. Upload and select the firmware file. Log into the web interface of the device. Using the interface found on the 'System' Tab, upload the firmware file you downloaded in the previous step. Once it has been uploaded and processed, select to to run on the next boot by clicking on the appropriate icon.
  3. Reboot the device. Click on the 'Reboot this Device' button (or a similarly named button if it is different in the firmware you are using). The device should restart with the new firmware. Note that this step should not disrupt devices attached to injection boards or expansion modules, except that in some cases Sync may be interrupted on Revision A control boards (where Canopy/Cambium sync is in use).
  4. Hard-refresh the web interface. Often, caching in a particular web browser will keep the web interface software from a previous version around which will cause all sorts of weird behavior. Often holding control while clicking refresh will cause this to occur. Sometimes, you'll need to exit the browser and restart. Or clear all cache for the website you're visiting. Or some other procedure. This typically isn't as difficult as we're making it sound, but some browsers simply seem to want to hold onto an old version of the web interface.
  5. Log back in and upgrade expansion modules if needed. On the connected devices tab, you should find all of your expansion modules. Some may be in a state which indicates that they should be upgraded. Click on the upgrade firmware icon to cause the firmware to be upgraded in that module. We recommend you do these one at a time. The upgrade itself will take around 2 minutes during which time the radios or other devices attached to the device will be affected.
  6. Verify proper operation. At this point the upgrade process should be completed. However, you'll want to verify that all settings are correct and the device is working as expected.

Firmware Files

The following are the files for this version.

SITEMONITOR-20230325.pfp - "regular" Base3 firmware image. This is the image you'll need almost always.

SITEMONITOR-RECOVERY-20230325.zip - Base3 Recovery Firmware Image. This file is only useful to do a firmware recovery as described in the factory reset documentation.

Bugs fixed in this and previous versions

Bugs fixed in Version 20230325

  • A bug which caused the web interface to misbehave when certain types of expansion modules were attached has been fixed. As a proactive measure we have audited and standardized sections of similar code across the codebase.

Bugs fixed in Version 20230210

  • A certain (very small) percentage of Base 3's would randomly reset for no apparent reason. This has been resolved by adjusting memory timings to revised recommendations from our CPU manufacturer based on their discovery that a certain percentage of the CPU's needed a more lax timing configuration than expected. Note that some non-upgraded Base 3's will get into a boot loop due to this issue. If this applies to your device then going through the recovery procedure below using this firmware version will likely recover your device.
  • Fixed a bug where entering a value between 0 and 1 in the web interface without the leading zero would be ignored. For example, setting a cycle value to 0.5 would work but setting it to .5 would not.
  • A bug where the unit would respond to OIDs with extra digits at the end of the OID instead of responding with "no such instance". If updating to this code results in broken SNMP polling, check to verify that the SNMP OID you are polling doesn't have extra oid digits at the end. The most common example of this would be the addition of one or more .0's at the end of the OID.
  • The library we use to develop the web interface has been updated to the latest version. This should improve compatibility across supported (modern) browsers.

Bugs fixed in Version 20220222

  • A bug where the SNMP stack would incorrectly encode the Request ID for certain ranges of IDs was fixed. As most SNMP tools discard Request IDs which don't match the Request ID they sent, this would cause the Base 3 to appear nonresponsive for any packet containing a Request ID from the affected ranges. Because many SNMP management tools assign request IDs sequentially this may appear as the Base 3 being unresponsive to SNMP for a period of time, and then automatically recovering.
  • Logging of the IP address of the SNMP requester when an invalid packet is received was added

Bugs fixed in Version 20220115

  • Adds support for PowerInjector+Sync, SiteMonitor PDU, and SiteMonitor Single Gigabit PoE modules versions J1 and K1, which started shipping in December of 2021. These modules use a different current sensor which was changed due to problems obtaining the original sensor.
  • An issue where an unsupported module being attached to the base unit would not appear in the list of connected devices was fixed.

Bugs fixed in Version 20201001

  • Support for additional expansion modules was added

Bugs fixed in Version 20200608

  • A critical error where not all of the configuration was restored after a power cycle was fixed