SoftHub

bug fixes:

- Fixed an issue where SNMP requests with long OIDs sometimes caused spontaneous reboots.
- SNMP getNext operations on invalid OIDs sometimes wrapped around to beginning of the MIB, causing an infinite loop in some SNMP managers. Fixed.
- Improved validation of various numeric and IP-address entry fields.

enhancements:

- Removed support for deprecated SSLv3 protocol, for security reasons. Only TLS v1.2 is now supported.
- Removed support for 512-bit SSL/TLS certificates.
- Server certificates have been upgraded to 2048-bit.
- Added support for mail servers that use STARTTLS, such as Office365.
- Added support for the new A2D analog-to-digital converter, which will replace the soon-to-be-discontinued CCAT interface.
- Special characters '-', '!', and '~' are now permitted in SNMP community strings.
- New web interface, including a JSON-based web API.
- Added automatic Daylight-Saving Time (DST) adjustments.
- Added support for SNMPv3.
- Added support for IPv6.
- New, more flexible and configurable alarm system:
Alarm triggers now have individual delays for both trip and clear.
Delays and Repeats can be anywhere from 0–14400 seconds. (14400 seconds = 240 minutes, or 4 hours.)
User can define up to 8 "valid time" ranges, and set individual alarms to trip (or not trip) only within or outside of those times.
User can now define up to 32 alarm "actions", each with individually-settable delayed and repeating actions, and assign any of these actions to any alarm trigger.
(NOTE: Due to this change in the alarm-system behavior, be aware that any alarms which currently have "repeat every __ minutes" set in your current v1.x.x firmware will have their "repeat" settings reset to "0"! You will need to go back into the alarm settings after the update and manually re-enable repeats on the alarm actions after updating. Also note that all delay and repeat timers are now given in seconds, not minutes; if you previously had a 30-minute repeat, for example, be sure to reprogram it as "1800", not "30".)
Alarm triggers can be set to be either "Alarm" or "Warning" priority.
An alarm or warning can be made to "latch", requiring the user to manually log in to acknowledge and clear the event.

About Device Firmware:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device’s functionality in the event of a software update either turning up faulty or causing the unit’s overall performance to drop. However, bear in mind that applying an older firmware isn’t recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it’s best that this task be performed in a steady power