Milesight Software & Firmware Release Note

 

MilesightVPN, Milesight DeviceHub, Toolbox, and more

Version 1.38

Bug Fixed:

  1. Time lost problem caused when USB cable is plugged in after powerred off, then if powerred on again, time on screen would be wrong.

Version 1.37

What’s Better:

  1. Command to reboot device: 7E0205007E.
  2. Command to disable(FF2D00) and enable(FF2D01) screen.

Bug Fixed:

  1. Illumination value might overflow when sensor is exposed under strong light and display as 65535 or 0.

Version 1.35

What’s Better:

  1. AM100-470/868/915 display is updated to AM104-470M/868M/915M now, AM102-470/868/915 display is updated to AM107-470M/868M/915M now.
  2. Logo display in idle mode is updated to Milesight one.

Version 1.33

Bugs Fixed:

  1. Program might stuck when powerred on.
  2. In the case of battery power supply, CO2 data collection might fail.

Version 1.31

What’s New:

  1. Neutral version (English).

Optimized:

  1. Internal clock mechanism.
  2. Max EIRP for CN470 devices is 19.15 now.
  3. Possible failure in collecting CO2 data.

Version 1.28

What’s New:

  1. CO2 histogram supports proportional reduction. When 3 historical values are greater than 1400, all values will be scaled down (historical maximum value/1400).
  2. Neutral version screen display.
  3. Save the frame count in ABP mode (save to RTC RAM, wouldn’t save when powered off).
  4. Save the channel mask issued by NS.

Bugs Fixed:

  1. Device might freeze when the battery is low.
  2. Failed ACK packet will be sent again.
  3. The battery level will not be reported when battery slot is vacant.
  4. When CO2, TVOC, temperature threshold triggers at the same time, the threshold report might not work.

Version 1.24

Dependency: ToolBox v6.28 and above to use new features.

What’s New:

  1. Rejoin mode to be enabled by default, and the default value is 32.
    • Rejoin mode mechanism: If the reporting interval is less than or equal to 30 min, then the device will send a LoRaMAC command (similar to a heartbeat packet) every 30 min to check the connection state. If reporting interval is greater than 30 min, then the LoRaMAC command will be sent at the set interval to check.
    • “Number of detection signals” means that device will wait to rejoin until certain amount of LoRaMAC command all fails.
  2. Entering the bootloader upgrade mode by pressing the button. Action sequence: press when device is not connected with any power supply, connect power supply like add battery or plug USB in, release when LED blinks.
  3. In OTAA mode, when ADR is enabled, Spread Factor is still configured.

Bugs Fixed:

  1. Sudden power failure when writing flash might cause the device to reset.

Version 1.23

What’s New:

  1. Manual Calibration and Restore Factory Calibration in CO2 reading via ToolBox and commands issued from NS.
    • Manual calibration (FF1A03): to put the device in an open outdoor environment for 10 minutes, and then press the button to start the calibration.
    • Restore factory calibration (FF1A00): to restore the calibration state whilst leaving the factory.
  2. Support both the new screen SSD1680 and the old screen SSD1675.

Bugs Fixed:

  1. PIR counting error and PIR interruption might cause system restarting or stuck.
  2. Upgrading from versions lower than 1.17 might cause wrong display or constant “8” on screen.
  3. When device was in shut-down state, garbled characters might display if button was clicked.
  4.  Abnormal power consumption when the TVOC/light sensor was turned off.

Version 1.19

What’s new:

  1. CO2 and TVOC area on e-ink screen displays alert icon for AM107, and alert threshold is configurable.
  2. ToolBox for Android and iOS can read and display uptime from device.
  3. Spread factor is open to set when ADR is not enabled.

Optimized:

  1. ACK confirm counter is open to set between 4 to 32 (default) in network RE-join mechanism.
  2. Frequency usage to join LoRa network for CN470 devices when the user doesn’t set certain channel mask. UC11-N1 will use channel 8~15 for the first 16 times trials, channel 80~87 for the second 16 trials, and then go through all channels 0~95.
  3. For CO2 reading less than 600, each dot in column histogram stands for 50 ppm, otherwise each dot stands for 25 ppm for more critical situation and easier visual judgement.

Removed:

  1. Lock time and continue time for threshold of temperature and humidity.

Bugs fixed:

  1. Modification in channel index might fail.
  2. Reboot caused by stack overflow.

Version 1.17

  • Device with this version automatically shuts down when the power reaches 0% and requires battery level above 30% to restart.

Added:

  1. Three new screen display modes. You can switch by pressing then releasing the reset button, or ToolBox v6.15. Different mode displays different content.

Optimized:

  1. Enable automatical calibration of CO2 reading every 180 hours. The calibration is carried out by the sensor itself and independent from manual calibration by ToolBox.

Fixed:

  1. Light sensor reading was 0 under sunlight.
  2. DevEUI might be over-written during NFC configuration.
  3. CO2 sensor reading might be wrong and rebooting didn’t help unless battery reached 0% or was changed. This bug was caused by collecting CO2 during TVOC initialization, CO2 collection should wait until TVOC initialization is completed.
  4. Restart because of interrupt PIR collection.

Version 1.14

Added:

  1. DevStatusReq mac-command specified by LoRaWAN® protocol to request battery level.
  2. Configurable LoRaWAN® version.

Optimized:

  1. Refresh e-ink screen on the hour and the half-hour.
  2. Synchronize timestamp every 5 days from Network Server.

Fixed:

  1. If the sensor was rebooted frequently it might report 0% battery.
  2. Time slowed down due to watchdog rebooting.
  3. Occasional black screen

Version 1.12

Added:

  1. AM100 Series is compatible with ASR LORA module now.

Optimized:

  1. Joining network uses DR_2 now.

Fixed:

  1. Abnormal NFC reading and writing, exceptional screen display might occur when battery voltage was low (<2V).
  2. NFC couldn’t read the correct on/off state when the program is writing flash

Version 1.11

Added:
  1. Temperature display on e-ink screen supports Fahrenheit.

Version 1.10

Initial version for AM10x.

Version 2.4.4

What’s Better:

  1. Improved UI performance.
  2. Added Lithuanian language.

Version 2.3.5

What’s Better:

  1. Support neutral version.
  2. Device Log in Device Maintenance including DO status change, node SN replacement, gateway SN replacement, node replacing gateway, which administrator, at what time, carried out what operations.
  3. Water output every time of UC51x can be set in the Rule Engine when executing Time tasks.
  4. When sharing multiple devices to another account at once, you can modify the sharing permissions in batches.
  5. The user modifies the reporting period of the device or enables or disables the channel. For configuration changes that need to be sent to the device, the interface will prompt whether the synchronization with the device is successful.

Bugs Fixed:

  1. Report display error caused by the absence of AI value.
  2. Offline recording of the LoRa device under the gateway when the gateway’s SN was replaced.

Version 2.1.5

What’s New:

  1. Domain name changes to cloud.milesight-iot.com now, redirect link and upgrade prompt will pop up in former web GUI and APP.
  2. Allow users to add any email address as contact, Cloud would send invitation email when users share anything to them.
  3. Global setting for WS86 to allow global control on “Me>Global Settings”.
  4. Allow users to share dashboards as up to 5 links with different authentication, where data synchronizes with real one, and digital output can be controlled if allowed.
  5. Pie chart as a widget to indicate device connection status per dashboard or among all end-devices.
  6. Replace faulty devices to new ones by simply changing SN. Only current user’s devices with same properties can be replaced in this way. Historical record (data and alarm) will not be erased.
  7. Supports EM500-CO, EM500-NH3, EM500-H2S, UC501, UC502, EM300-MCS, EM300-ZLD, EM300-SLD.
  8. SF info in end-devices’ properties.
  9. Filter by group or SN on “Reports” for custom generation.
  10. Keyword for certain device can be filled in to generate a new widget.

Optimized:

  1. Time range in reading certain period of historical data and events is more readable now.
  2. Action time of UC3x is based on user’s timezone now.

Version 2.07

Bugs Fixed:

  1. Alert state without the arrow notification icon.
  2. Abnormal display problem of historical data page on iPhone 8.

Version 2.06

What’s New:
  1. Support EM300-TH/TWL/TMCS and other new sensors.
  2. Devices could be grouped according to your needs.
  3. Devices filter.
  4. User inteface optimization.

Version 1.92

What’s New:

  1. Support WS86, EM500-C02, EM500-PP, EM500-LGT, EM500- SMT-MEC20/MT05.

Bugs Fixed:

  1. Failure to add device by scanning QR code.

Version 2.1.3

What’s Better:

  1. Display is updated to Milesight IoT.
  2. Support Wizard page to skip SMTP mail setting.
  3. Support SMTP settings (super administrator): modify SMTP; support SSL/STRATTLS mode. (Mail cannot be sent if SMTP is not set during installation)
  4. Support Domain domain name certificate setting (super administrator)
  5. Optimized the map component.
  6. The device side and devicehub adopt authorization code authentication logic/account authentication logic.
  7. When the hard disk information is obtained incorrectly, the default value is used.
  8. Compatible with UR75v2 device upgrade.

Bugs Fixed:

  1. GPS might deviate.
  2. Restart the server during installation, the server will get stuck and cannot start successfully.
  3. Status displayed “fail” if a discontinued product is started on Task page.
  4. Error prompt when Stop button clicked on Task list.
  5. Some typo.
  6. After the UR75v2 is successfully upgraded, there is no corresponding change in the status.
  7. The English version of the link in the reset password email shows the language of the page displayed in Chinese.
  8. Click on the device in the alarm list to enter the My Device page, showing no data.
  9. Click on the forgotten password, the redirect link reports 500.
  10. No log and address are added to the alert email.
  11. UR75 uses DeviceHub to upgrade, upgraded version number is displayed as NULL.
  12. UR75 uses DeviceHub to upgrade, the upgrade might go unsuccessful.
  13. Task list, tasks being executed by stop, non-stop time displayed by finishtime.
  14. Alarm List is missing a warning icon.
  15. If the device uses the account password to connect to DeviceHub, an error might be reported.
  16. Cannot receive alert email.
  17. The name of the txt file downloaded by the license is not modified.
  18. After the expansion is successful, you can add a user, and you can only assign a maximum of 25 device management permissions.
  19. Multiple positioning dots will be displayed after the GPS is zoomed in.
  20. No smtp is added, device is added, and the prompt for sending mail is not consistent with the standard version.
  21. Email/domain name page, click to log out, no response.
  22. SMTP test mail/alert mail DeviceHub is not modified to Milesight DeviceHub.
  23. The server domain name is set successfully, and DeviceHub cannot be accessed through the domain name.
  24. After the DeviceHub is installed successfully, the default name filled in does not meet the rules and needs to be re-modified manually.
  25. Email does not need to add logo.
  26. The prompt for successful setting of the server domain name has not been modified to Chinese.
  27. The database is not initialized normally, causing the service to be unable to connect to the data.

Version 2.0.19

  • It’s NOT recommended to parallel install MilesightVPN and DeviceHub

Added:

  1. Remote upgrade and batch configuration for UR75-EDGE.

Fixed:

  1. Devices can’t connect due to characters in device sn.

Version 2.0.17

  • It’s NOT recommended to parallel install MilesightVPN and DeviceHub

Optimized:

    1. Alarm report

Version 2.0.15

Optimized:

  1. Users need only 1 command to complete the download of the installation package and firmware
  2. Clear logs regularly each day (logs that were written 2 weeks ago)
  3. Clear database regularly (clean statistics and GPS data)
  4. UR32 supports upgrade and provision in bulk

Version 1.20

What’s Better:

  1. LoRaWAN MAC command to get device power.

Bugs Fixed:

  1. Cloud might fail to configure the threshold alarm normally, and the issue of threshold alarms causes the device to not send periodic reports.
  2. When the data is larger than 11 bytes, the transmission fails without retransmission.
  3. System power-on probability stuck.
  4. In the case of US915 SF10, the problem that the battery pack and data pack will be reported separately.

Version 1.15

Added:

  1. Save frame count in ABP mode and save in RTC RAM.
  2. Save the channel mask issued by NS in ABP mode.
  3. The first 8 LoRa transmission in ABP mode use default gateway frequencies.
  4. Random appkey preset.

Optimized:

  1. Zero battery detection by reducing the detection threshold voltage and collecting the voltage when the system is idle.
  2. Data rate is open to be configured in ADR mode.
  3. Increase the function of preset key (mainly used in LinkWan version).

Version 1.12

What’s New:

  1. Part number for 2-batteries model will be “-8000mAH”, no special indication for singel-battery ones.
  2. “M” for module after LoRa channel number, like “-868M/915M/470M”.

Version 1.11

Initial image version.

Version 2.30

What’s Better:

  1. UDL outlier calibration feature.

Bugs Fixed:

  1. System stuck problem caused by abnormal interruption.
  2. Configuration sent by the cloud might not get responce when sensor joins the network for the first time.

Version 2.28

Dependency: ToolBox v6.31

Optimized:

  1. CN470 devices’ MaxEIRP is 19dBm by default.
  2. Save the frame count in ABP mode (save to RTC RAM, wouldn’t save when powered off).

Bugs Fixed:

  1. Frame counter is cleared if device in ABP mode is reset.
  2. Device might freeze when the battery is low.
  3. Abnormal power consumption of UDL with v1.3 of hardware.

Version 2.25

Dependency:

ToolBox v6.29

ToolBox APP v1.3.5

What’s New:

  1. Change in PN and model name.
  2. Support for EM500-PP-G1/2M-868M/915M, PN is G1/2M-1002.
  3. To burn random private key in advance for all EM500 series devices.
  4. Entering the bootloader upgrade mode by pressing the button. Action sequence: press when device is not connected with any power supply, connect power supply like add battery or plug USB in, release when LED blinks.
  5. Measure Outliers Calibration for EM500-UDL.
  6. Background calibration and factory calibration options for EM500-CO2.
  7. SF is open to change no matter device is turned on or not.
  8. Rejoin mode.
  9. Changeable txpower.
  10. Snow level sensing for EM500-UDL.

Bugs Fixed:

  1. EM500-UDL might stuck.
  2. CN470 channels modification couldn’t take effect. Default frequency band: 8-15.
  3. Device reset caused by sudden power failure.
  4. Incorrect conductivity of EM500-SMTC-MEC20, incorrect reporting cycle when EM500-SMTC-MEC20 was not connected to mainboard.
  5. Incorrect reporting data from EM500-PT100.
  6. Collected data from EM500-SWL-3M/SWL-5M/SWL-18M.
  7. When device is in shutdown mode, press the button to reset but device can only be turned on.
  8. Conflict between data collection and reporting might lead to the problem of reporting data errors when threshold alarm was enabled.
  9. EM500-SMT-EC5 might re-collect when reading from dry soil is less than 1 and greater than 0.
  10. Abnormal power consumption in EM500-SMT-MEC20, EM500-PT100, and EM500-UDL when device starts until it transmits the first data packet.

Version 1.15

Added:

  1. DevStatusReq mac-command specified by LoRaWAN® protocol to request battery level.
  2. Configurable LoRaWAN® version.

Version 1.14

Fixed:
  1. When device was connected via USB cable, NFC didn’t function.
  2. Exceptional reboot.
  3. NFC couldn’t read the correct on/off state when the program is writing flash.

Version 1.12

Initial version for EM500 series

Version 1.0.20

NOTE: Do not install DeviceHub and MilesightVPN in the same system at the same time.

What’s Better:

  1. Software logo and name is changed to MilesightVPN.

Version 1.0.19

NOTE: Do not install DeviceHub and MilesightVPN in the same system at the same time.

One-click installation command: wget https://resource.milesight-iot.com/MilesightVPN/Milesightvpn_install.sh && chmod +x Milesightvpn_install.sh && ./Milesightvpn_install.sh

Fixed:

  1. Client program has connected but the status on web page shows “Disconnected”.
  2. Devices can’t connect due to characters in device sn.

Version 1.0.17

NOTE: Do not install DeviceHub and MilesightVPN in the same system at the same time.

One-click installation command: wget https://resource.milesight-iot.com/software/MilesightVPN/Milesightvpn_install.sh && chmod +x Milesightvpn_install.sh && ./Milesightvpn_install.sh

Time needed: 10 min

Compatible with:
UR32: 32.1.0.7 and above; UR35: 35.1.0.12 and above; supports working as VPN server and displays real-time connection failure notification.
UR5x: 5x.2.0.23 and above; supports working as VPN server and displays real-time connection failure notification.

Fixed:

  1. The component “forever” installation failure
  2. Problem of inconsistent version between node.js and Milesightvpn; installation package comes with embedded node.js.

Removed:

  1. Subnet conflict pop-up window notification. If there’s conflict in present subnet, mark the conflict subnet as red.

Added:

  1. Watchdog on Milesight_VPN, openvpn.

Version 1.0.16

Fixed:

  1. Clients don’t connect automatically after server reboots.

UR3x SDK Version 3.0.1

Python version: 2.7

Bugs Fixed:

  1. get_firmware_info and get_cellular_status failed to fetch data due to major upgrade in router status page.

UR3x SDK Version 2.1.8

Python version: 2.7

What’s New:

  1. This version is compatible with 3x.2.0.x firmware.

UR3x SDK Version 2.1.6

Python version: 2.7

What’s New:

  1. Bluetooth third party library: gattlib.
  2. gattlib related instance.

UR5x SDK Version 2.1.5

Python version: 2.7

Matching firmware version for this SDK: 5x.2.0.54 and above.

Optimized:

  1. Supports to customize email content when DI meets the preset condition or duration.

UR7x SDK Version 2.1.5

Python version: 2.7

Matching firmware version for this SDK: x.2.0.54 and above.

Optimized:

  1. Supports customizing email content when DI meets the preset condition or duration.

UG85/87v2 SDK Version 1.1.12

Python version: 2.7

Initial version for UG8x.

Version 7.01

The initial re-constructed version.

Version 6.36

What’s Better:

  1. Support for AM107.

Version 6.35

What’s New:

  1. Support for UC50x.
  2. Rejoin mode for LinkWAN devices.
  3. To exit current serial port and switch.
  4. Prompt to upgrade when connecting to a UC11-T1 whose firmware is lower than 2.02, or UC11-N1 whose firmware is lower than 1.43.

Bugs Fixed:

  1. Incorrect prompt of TxPower upper limit when connecting UC11xx.
  2. Incorrect unit of TxPower when connecting UC11xx.
  3. RS232 parameters shouldn’t allow edit when disabled.
  4. Editing Spreading Factor might fail when ADR is enabled.

Version 6.25

What’s New:

  1. Support for EM500-UDL-S050/EM500-UDL-S100, UC11xx hardware v3.0, UC3xxx hardware v3.0.
  2. Background calibration and factory calibration option for AM107 CO2 sensing.
  3. It’s allowed to transmit in fixed Spreading Factor with ADR disabled.
  4. Rejoin mode for UC11xx.
  5. FOTA from different servers in different regions on “Maintenance>Upgrade”.

Bugs Fixed:

  1. Description length of UC3x is now limited to 32.
  2. Irrelavant setting blocks are removed, e.g., CN470 intra-freqnency option in AS923 device.
  3. Typo in prompt.
  4. It’s saved to be SF12 but UC11xx in AS923 used SF10 to transmit signal.

Version 6.21

What’s New:

  1. Support NFC read-write configuration of EM500-SWL-L050.
  2. Simplified Chinese mode.

Optimized:

  1. Timezone calculation for UC11/UC3x “Commands”.

Bugs Fixed:

  1. “-” couldn’t be saved in APN for UC3x.
  2. When AM10x was turned off, older version displayed “on” as status.
  3. LinkWAN version devices should not upgrade to standard version or vice versa.
  4. Wrong prompt note on “Status” after device was connected.
  5. Failure in reading saved configuration on “Command” for UC11.
  6. Some typo.
  7. Inactive setting available to change on certain models.
  8. Failure in reading saved configuration on “LoRaWAN® Settings>Channels”.

Version 6.18

What’s New:

  1. Support NFC read&write configuration of EM500-CO2/EM500-LGT/EM500-SWL (gauge pressure)/EM500-PP/EM500-SMT-MEC20.
  2. Add timeout limitation in reading attributes. The “Read Channel failed” will not pop up in this version and later.
  3. Power output time on “General>AI” is limited to 0-5000 ms.
  4. Reporting interval on “General>Basic” is limited to 60-65535 sec.

Bug Fixed:

  1. “Application Mode” interface might not display or function normally when USB disconnected from UC1152 and connected to UC3x without restart.
  2. Registers quantity could changed when register type was Coil/Discrete/Input Register(INT16)/Holding Register(16), while the RS485 master can only read 1.
  3. The height of RS232 parameter blocks might be too small to display clearly when ToolBox was running on certain models of Windows computer.
  4. Data polling interval might fail to program into UC1152.
  5. Alignment might be wrong on “General” page of UC1152.
  6. Some typos.
  7. Channel index might fail to write into LoRa devices.
  8. If any threshold on “Device Settings>Basic” was left blank for infinity, it might be read as 0.

Removed:

  1. Data polling interval input block on “General>AI” of UC11-N1 will not appear when the firmware version is higher than 2.07 (included).

Version 6.13

Added:

  1. Configurable LoRaWAN® version.

Version 6.12

Fixed:

  1. “Power On/Off” button didn’t take effect.
  2. “Status” page remained blank.

Version 6.10

Added:

  1. Supports NFC configuration

Version 5.21

Added:

  1. ADR switch on “LoRaWAN®>Basic”.

Fixed:

  1. Blank “General” after clicking “Save the Commands as a File”.
  2. Remove calibration-related options when the device is not UC11-T1.
  3. MQTT user credential tick problem

Version 5.20

Added:

  1. Channel Mask of connected gateway on Status page for UC11-T1
  2. Temperature display in Fahrenheit on Status page for UC11-T1
  3. Calibration permit for UC11-T1
  4. RS232 option on Serial page for UC11-N1
  5. Serial Baud rate 1200, 2400 for UC11-N1
  6. Counter mode in GPIO2 for UC11-N1
  7. Alterable App Port and RS232 Port
  8. Channel Mask, Counter, Uplink Count, Downlink Count Display on Status page

Fixed:

  1. Time display error on Status page for UC3xxx

Version 5.16

Added:

  1. Support English punctuations in APN

Fixed:

  1. Negtive number display problem in SNR

Version 5.12

Added:

  1. input_32, input_int32_AB, hold_int32_CD, input_float datatype for Modbus of UC11-N1/UC1152/UC3x52/UC3552
  2. Add “-DC” for DC version of UC11-N1

Optimized:

  1. Support NB node device
  2. Optimize regular report timing/poll serial ports timing/AI collection timing
  3. Work on 32-bit computer

Version 5.6

Altered:

  1. AI signal collection type was changed to: 0-10V

Version 5.2

  • ToolBox_Sensor was merged with ToolBox_IO

Added:

  1. ABP activation

Optimized:

  • Packet confirmation mechanism, to reduce unnecessary retransmissions and power consumption.
  • Details are as follows:
  • When the device sends a timed report packet (requires ACK) to the NS, if the ACK of the other party is not received, the packet is retransmitted at most three times.
  • When the device sends an attribute packet (requires ACK) to the NS, if the ACK of the other party is not received, the packet will be retransmitted.
  • When the device sends an alarm packet (requires ACK) to the NS, if the ACK of the other party is not received, the packet is retransmitted up to three times.

Fixed:

  1. Some bugs

Version 4.28

Added:

  1. Check log via USB
  2. Modbus RS485 LoRaWAN® function of UC1152
  3. “Acquire” button on interface of UC1152 to help users to acquire the newest channel data when configuring RS485 function

Optimized:

  1. Data package reporting format and decreased package size and package loss rate

Version 4.24

Optimized:

  1. Network access rate (SF=12, 11, 10)
  2. Processing mechanism when the network fails to reduce power consumption

Fixed:

  1. KR920 can’t receive data
  2. LoRa sends timeout when ChannelsNbRep is greater than 1
  3. Entering the low power probability and causing the system to restart

Version 1.4.7

What’s New:

  1. Support for EM300-NB devices.
  2. App check and update logic optimization.
  3. AM10X model switch.
  4. Support for device upgrade (due to the limitation of iOS NFC session duration, the current upgrade function is only supported by Android).
  5. Support for WS30X wireless door sensor.
  6. Support for WS50X switch panel v2.0.
  7. Optimize NFC service.
  8. Support for WS10X smart buttons and PIR.

Bugs Fixed:

  1. Fix the neutral version of the APP. When reading the AM104 information, the data collection, calibration settings, and threshold reporting are more than the content of the three sensors CO2, TVOC, and air pressure.
  2. Fix the problem of unreasonable prompts for incompatible devices.
  3. Optimize the problem of incorrect Chinese prompts when switching between screen modes.

Version 1.3.9

What’s New:

  1. Support for EM300 series and UC50x, EM500-UDL-S050/S100, EM300-SW.
  2. Calibration functions for AM102 and EM500-CO2. Reference: How to fix abnormal CO2 Values of AM102.
  3. Model name change (EM500/EM300 model name change).
  4. Rejoin mode for end-devices. Reference: coming soon.
  5. PN on status page (the old device will not display if it does not have a PN).
  6. EM500-UDL (firmware version needs to be v2.22 and above) abnormal value prevention setting. Reference: coming soon.
  7. All LoRa nodes can configure SF regardless of whether ADR is enabled.
  8. UI changes related to merging with Milesight brand (replacement of icons and startup images, and replacement of brand-related fields, icons and startup images with ToolBox).
  9. Transmit power option copywriting modification.
  10. Counting increase, configurable digital input options and filter on (disable) function.

Bugs Fixed:

  1. AM102 AlarmScreen setting is invalid in the confirmation package mode.
  2. Error prompt when reading unsupported devices.
  3. Threshold input range is not restricted in EM300 temperature and humidity calibration.
  4. Fix the problem with the alarm reporting interval limit, which makes it impossible to configure other configuration items.
  5. Abnormal value protection of PT100 does not take effect.
  6. When the equipment is AS923, cancel ADR to set the spreading factor, and remove SF11 and SF12.
  7. For the model of EM500-SMT-MEC20, the calibration, data acquisition disable and enable, and threshold setting functions cannot be set (problems caused by the new and old models).

Version 1.2.8

Added:

  1. Configurable LoRaWAN® version.

Version 1.1.10

Added:

  1. Supports temperature display in Fahrenheit.
  2. Pressure value displayed on “Status” and “Calibration Settings” calculates to nearest tenth.

Fixed:

  1. Changing temperature unit caused temperature value conversion on “Status” page, but the unit display on “Status” remains the former one.

Version 1.1.9

The initial version

UC11xx Version 2.23

NOTE:

  • This version is used on hardware V2.x only.
  • To upgrade to this version, one must reset the device and the default LoRaWAN® protocol version will be v1.0.3, otherwise one need to use Toolbox to manually change the version first.

Dependency:

ToolBox v6.26 and above

What’s New:

  1. After the upgrade and reset, all frequency bands will use SF10 to access the network by default.
  2. After the upgrade reset, the duty cycle limits of all frequency bands will use the regional default configuration.

UC11xx Version 2.22

NOTE:

  • This version is used on hardware V2.x only.
  • To upgrade to this version, one must reset the device and the default LoRaWAN® protocol version will be v1.0.3, otherwise one need to use Toolbox to manually change the version first.
  • Only with ToolBox v6.26 and above, it’s allowed to configure the LoRaWAN® protocol version.

What’s New:

  1. Request to obtain timestamp from gateway (the LoRaWAN® protocol version V1.0.3 must be enabled). After the device is powered on, the request will be sent until the synchronization is done. After the synchronization is successful, it will re-synchronize every 5 days.
  2. Drop-down box to choose transmit power.

Bugs Fixed:

  1. Uplink frame might be one more frame than the actual one.
  2. Device abnormal reset caused by flash lock.

UC11xx Version 3.06

NOTE:

  • This version is used for hardware v3.0 and above only.
  • Hardware v3.0 uses ASR LoRa module. The module frequency bands are divided as follows: 868 (EU868, RU864, IN865) and 915 (AU915, US915, AS923, KR920) frequency bands use ASR650SHT module; 470 frequency band uses ASR650SLT module.

What’s New:

  1. Pulse Counter.
  2. Random AppKey.
  3. Time zone and timestamp settings, device can synchronize local time from ToolBox, or from gateway every 5 days.
  4. When the device restarts, the state of DO remains the state before restarting (every state change of DO is written in flash for storage).
  5. 1200 as baud rate.

Optimized:

  1. Modbus section newly supports up to 16 channels.
  2. Modbus exception detection.

Bugs Fixed:

  1. Communication failure at the baud rate of 2400.
  2. System might erase LoRa parameters because of abnormal backup.
  3. System might reset its configuration becuase of abnormal power failure like unstable supply.
  4. UC1114 might fail to initialize.
  5. Data in Modbus might be lost due to length limit of LoRa queue.

UC11xx Version 2.21

What’s New:

  1. Status record of DO. After the device is powered off and restarted, the status of DO is the state before the power off (the functional device is turned on by default and there are no open configurable options).

Optimized:

  1. Critical section setting for writing flash.
  2. Save method of the uplink and downlink frame counter.

Bugs Fixed:

  1. CN470 setting channel mask could not take effect.
  2. Spread factor configuration could not take effect.
  3. System might constantly restart because network connection failed.
  4. System might constantly restart because of overly long time in processing LoRa parameters.

UC11xx Version 2.0.16

Optimized:

  1. First 3 bytes of DevEUI are fixed as “24E124”, last 5 bytes are fixed as SN without the first and the last digit.
  2. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Milesight gateways first. If it fails for 32 times (about 6 min), change to use LoRaWAN® standard specification.

UC11xx Version 2.0.15

Fixed:

  1. Time error caused by RTC cycle
  2. 8 byte limit in Modbus transparent transmittion

UC11xx Version 2.0.13

Added:

  1. Input Registers (INT32) /Input Registers (Float) /Input Register (INT 32 with upper 16 bits) /Input Register (INT 32 with lower 16 bits) /Holding Register (INT 32 with upper 16 bits) /Holding Register (INT 32 with lower 16 bits)
  2. Frequency plan is changeable in between
    1. For 868 module: EU868, IN868, RU864
    2. For 915 module: US915, AU915, KR920, AS923

Altered:

  1. Channel mask restores to default after ACK fails

Fixed:

  1. Fix frame count error related bug

UC11xx Version 2.0.7

Added:

  1. ABP method

Optimized:

  1. Allow Modbus Slave ID more than 16
  2. DO performance

Version 2.15

Optimized:

  1. Stability in querying Modbus slaves.

Bug fixed:

  1. Pulse counter increased even though connection was idle.

Version 2.11

What’s new:

  1. Obtain battery level using LoRaWAN® MAC command.

Optimized:

  1. Modbus stability with unstable external power source.
  2. Program stability with exceptional power loss when upgrading.
  3. Frequency usage to join LoRa network for CN470 devices when the user doesn’t set certain channel mask. UC11-N1 will use channel 8~15 for the first 16 times trials, channel 80~87 for the second 16 trials, and then go through all channel 0~95.

Bugs fixed:

  1. Modbus queries might fail.
  2. Deleting Modbus channel might not take effect or require user to save again.
  3. Program would restart when USB disconnected.
  4. Device might go to reboot if many Modbus channels were in use and device needed to transmit a data volume that was too large.
  5. When “Power Output Time Before Collect” was enabled, power outsourcing time might exceed and continue when user manually click “fetch”.
  6. When writing in flash, device essencial parameters might be erased if power supply was cut out. This could lead to model reading failure on ToolBox.

Version 2.07

  • Resetting is required if UC11-N1 upgrade from 1.44 and lower.
  • ToolBox v6.12 and more supports on/off switch while UC11-N1 is in shutdown mode.

Added:

  • LoRaWAN® duty cycle function.
  • USB switch function code, users can use the switch button on the ToolBox status page to switch on and off.
  • Newly added setting items to provide equipment to restore power supply status.

Optimized:

  • Modify the lora configuration from the original restart device to modify the lora configuration to only restart the lora module; when the modification mode (ABP/OTAA), frequency band is saved, the device will only be restarted when it is saved.
  • USB detection process.
  • Power consumption optimization, modification of power calculation method.
  • All collection cycles of N1 are changed to be consistent with the reporting cycle, and ToolBox removes the collection cycle configuration items.

Fixed:

  • Unable to send data because of LoRa reload under RU864 ABP mode.
  • Unable to enter low power consumption after 1 hour without access to the network.
  • Fixed the problem of abnormal ToolBox working under Windows 7.

Version 1.44

  • Resetting may be required if UC11-N1 upgrade from 1.37 and lower.
Optimized:
  1. Switch mechanism and sleep program.

Version 1.40

  • Resetting may be required after upgrade

Added:

  1. Supports restoring to the state before shutdown (configurable in Toolbox v6.8). Default mode is off for unchargeable model; default mode is on and will restore to the state before shutdown for DC model.

Optimized:

  1. Shorter device turn-off time from 6 seconds to 2 seconds when attaching a magnet to the device. If the device beeps for 2 seconds, it is powered on. If the device beeps for 6 seconds, it is powered off. Magnet can be moved away during beeping.
  2. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Milesight gateways first. If it fails for 32 times (about 6 min), use LoRaWAN® standard specification instead.

Fixed:

  1. Problem in joining network when devices are connected by USB.
  2. Battery calculation didn’t include join requests.

Version 1.36

  • Resetting may be required after upgrade

Optimized:

  1. First 3 bytes of DevEUI are fixed as “24E124”, last 5 bytes are fixed as SN without the first and the last digit.
  2. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Milesight gateways first. If it fails for 32 times (about 6 min), use LoRaWAN® standard specification instead.

Version 1.31

  • Resetting may be required after upgrade

Added:

  1. Support RS232 in Serial
  2. Support Baud rate 1200, 2400
  3. Counter mode in GPIO2 port for DC version
  4. Alterable App Port and RS232 Port
  5. Channel Mask, Counter, Uplink Count, Downlink Count Display on Status page

Optimized:

  1. When a channel didn’t read data, Cloud displays “-” rather than the latest data reported from UC11-N1.
  2. Possible error in Modbus RTU function code and CRC

Removed:

  1. Low power consumption mode for DC version

Version 1.27

  • Need reset after upgrade to this version

Added:

  1. Support to switch frequency in between
    • Alterable channels for 868: EU868/IN868/RU864
    • Alterable channels for 915: US915/AU915/KR915/AS923
  2. Data type input_int32/input_float for modbus readable data
  3. Display GPIO status in regular uplink packet

Optimized:

  1. Support bootloader upgrade
  2. Optimize power-effective working mode
  3. Optimize DO control

Fixed:

  1. Fix repeated uplink when controlling GPIO from cloud

Version 1.23

Optimized:

  1. Battery performance

Fixed:

  1. No-beep problem (need to burn this version to take effect)

Version 2.05

Added:

  1. Duty Cycle in LoRaWAN® configuration.
  2. Switching on/off (sleep mode) in ToolBox v6.12 and later; supports viewing and editing settings in sleep mode.

Optimized:

  1. Micro USB detection.
  2. Collecting interval is 20 seconds now.
  3. Power consumption.

Fixed:

  1. When device had dual power source via battery and USB, removing USB or battery might cause problems.
  2. If temperature threshold was left blank, action of reading would return 9999.

Version 1.34

Optimized:

  1. Power consumption when device transmits LoRa signal.

Version 1.30

Optimized:

  1. Success rate in joining network.
  2. Shorter device turn-off time from 6 seconds to 2 seconds when attaching a magnet to the device. If the device beeps for 2 seconds, it is powered on. If the device beeps for 6 seconds, it is powered off. Magnet can be moved away during beeping.
  3. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Milesight gateways first. If it fails for 32 times (about 6 min), use LoRaWAN® standard specification instead.

Fixed:

  1. Battery calculation didn’t include join requests.
  2. Problem in joining network when devices are connected by USB.

Version 1.27

Optimized:

  1. Turn off the 0% battery detection

Fixed:

  1. Repair possible restart at low temperature

Version 1.25

Optimized:

  1. First 3 bytes of DevEUI are fixed as “24E124”, last 5 bytes are fixed as SN without the first and the last digit.
  2. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Milesight gateways first. If it fails for 32 times (about 6 min), change to use LoRaWAN® standard specification.
  3. Uplink 1 “0% battery” packet as soon as battery voltage is detected as less than 2.4V, then uplink an additional “0% battery” packet along with regular report.

Version 1.23

  • This version is only compatible with Toolbox 5.20 and above, you must reset the device after upgraded to this version.

Added:

  1. Calibration permit
  2. Channel Mask of connected gateway on Status page
  3. Temperature display in Fahrenheit on Status page
  4. Low battery detection. Report battery level as 0 when battery voltage is lower than 2.2V.

Version 1.20

  • This version is only compatible with Toolbox 5.12 and above, you must reset the device after upgraded to this version.

Added:

  1. Frequency plan is alterable in between
    1. For 868 module: EU868, IN868, RU864
    2. For 915 module: US915, AU915, KR920, AS923

Fixed:

  1. Some minor bugs

Version 1.19

Fixed:

  1. Failing to boot after a drastic shock
  2. Probable failing to jump from bootloader to application

Version 4.04

What’s New:

  1. Modbus transparent transmission, which can only be used in Milesight IoT Cloud/MQTT modes. The topic subscribed by this function node is: uc/[sn]/ucp/+/modbus/update, and the topic published by the node is: uc/[sn]/ucp/[ucp_version]/modbus.

Optimized:

  1. Modbus increases to 16 channels, and the rule engine can set rules for 9-16 channels.

Fixed:

  1. Device might fail to connect to MQTT server when log is not turned on.

Version 4.02

What’s New:

  1. Bootloader reconstruction, adding buttons to enter interactive mode, adding two hardware judgments, allowing firmware upgrades under bootloader.
  2. Sending pin status when reporting cloud alarm.

Optimized:

  1. UC3X52 and UC3X14 UCP passwords need validation in every 30 minutes.
  2. When the lock time is modified, it is initially unlocked.
  3. Updated the modbus protocol stack and modified the baud rate clock.

Fixed:

  1. Possible flash erasure and damage that is fixed by re-allocating flash address.
  2. Device reset because of unstable power.
  3. One extra bit in serial number and hardware version in UCP protocol.
  4. UC3XXX must connect to toolbox before receiving cloud commands.
  5. Restart time takes precedence over sending information, and the lock time only starts to calculate and take effect after the command is issued once the rule is triggered.
  6. Other events under the same command cannot be triggered when the server or cloud is not connected.
  7. Increase the heap of the device and reduce the size of the system stack to solve the problem of entering the hardware error interrupt.

Version 3.11

NOTE:

  • UC3x22/UC3x14 with firmware version 2.xx CANNOT upgrade to this version
  • Upgraded UC3x52 CANNOT be downgraded to version 2.xx

Added:

  1. Configurable APN for model UC35xx

Optimized:

  1. Prolong the time to 10 min when device waits for base station.
  2. Supports up to 128-bit-long APN.
  3. Time acquiry mechanism.
  4. UC35xx default “Keep Alive Interval” is changed to 300 sec when under Aliyun mode.

Fixed:

  1. Failure to upgrade by OTA when device is under Milesight IoT Cloud mode.
  2. Wrong device name when device is under MQTT mode.

Version 3.09

NOTE:

  • UC3x22/UC3x14 with firmware version 2.xx CANNOT upgrade to this version
  • Upgraded UC3x52 CANNOT downgrade to version 2.xx

Added:

  1. Configurable APN for model UC35xx

Optimized:

  1. Keep Alive Interval set as 120 seconds for default

Fixed:

  1. Failure in configuration when failing to connect to Aliyun

Version 3.08

NOTE:

  • UC3x22/UC3x14 with firmware version 2.xx CANNOT upgrade to this version
  • Upgraded UC3x52 CANNOT downgrade to version 2.xx

Added:

  1. NB module for model UC35xx
  2. Aliyun mode for model UC35xx
  3. Support Milesight IoT Cloud China

Version 2.20

  • You must use this version or above with Toolbox 5.12 or above

Added:

  1. Add Input Register (int32)/Input Register (float)/Input Register (int32 with upper 16 bits)/Input Register (int32 with lower 16 bits)/Holding Register (int32 with upper 16 bits)/Holding Register (int32 with lower 16 bits)

Altered:

  1. Time in commands is Greenwich time, local time in status is device local time
  2. Manual reboot after Keep Alive Interval was altered in Milesight IoT Cloud mode is not necessary

Optimized:

  1. Support AWS China cloud
  2. Optimize performance in joining network

Fixed:

  1. Fix local time disappearance in status in Toolbox after device joined network
  2. Fix continual reboot after Keep Alive Interval was altered in AWS mode

Version 2.19

Fixed:

  1. Downlink problem

Version 1.08

Dependency:

  1. ToolBox_v6.33 and above.
  2. ToolBox App v1.3.9 and above.

Bugs Fixed:

  1. Low possibility to be stuck when installing batteries.

Version 1.07

Dependency:

  1. ToolBox_v6.33 and above.
  2. ToolBox App v1.3.9 and above.

Bugs Fixed:

  1. Rejoin mode couldn’t be enabled when device is working in ABP.
  2. In the counter function, when the pin is configured for pull-down, it uses rising edge counting, and when it is configured for pull-up or no pull-up or pull-down, it uses falling edge counting.

Version 1.06

Dependency:

  1. ToolBox_v6.33 and above.
  2. ToolBox App v1.3.9 and above.

What’s Better:

  1. More precise calculation of battery level.

Version 1.05

Initial version.

Version 1.12

Initial version

Hardware version: v1.1

Version 60.0.0.36

Bugs Fixed:

  1. Network Server>Multicast is not accessible with HTTPS.
  2. Node-RED is not accessible with HTTPS unless gateway is upgraded and reset.

Version 60.0.0.35

What’s Better:

  1. Support Class B.
  2. Support Noise Analyzer.
  3. Support Node-RED.
  4. Support multicast to Class B and Class C.
  5. A drop-down subject box in MQTT section for multicast delivery.
  6. New field “Class type” on Network Server>Packets.
  7. Heartbeat mechanism for connecting semtech packet forwarding. When five consecutive heartbeat packets do not receive a reply, a system restart is triggered.
  8. A single antenna installation prompt on the wizard page
  9. Compatibility of some pop-up windows.
  10. The neutral version of the Milesight IoT Cloud connection is modified to “Cloud Mode”.
  11. New DHCP hyperlink setting on Wifi page.
  12. Enable event settings by default.
  13. Optimize the prompt when WAN and WLAN IP address conflict to prevent misoperation.

Bugs Fixed:

  1. Remove the disable and enable options on the WAN page.
  2. Abnormal web page display when switching from devicehub to other pages.
  3. SIM card from China Telecommunications might fail to send text messages.
  4. GPS location cannot be displayed when connecting to basicstation.

Version 60.0.0.34

Bugs Fixed:

  1. When UG6x connects to Milesight IoT Cloud, the NS saves DevEUI in uppercase. When UG6x disconnects from Internet and then connection restores afterwards, adapter program saves lowercase DevEUI, resulting in repeated addition of nodes, causing NS to crash.

Version 60.0.0.33

  1. GPS background can be obtained, the web page is not displayed, no gps file is generated under the tmp path
  2. After importing the backup, the NS-gateway page, the local gateway will be replaced with the gateway ID of the imported backup file, the connection status is not connected, and NS cannot receive the data
  3. Fix basic station connection problem
  4. System>General, hidden storage page

Version 60.0.0.31

What’s Better:

  1. Neutral version (English). Model name is ND65/67.

Version 60.0.0.30

What’s Better:

  1. Support TTN as packet forwarder.
  2. When saving packet forwarder as localhost, the gateway ID is saved with the value of gateway EUI by default.
  3. When frequency band is changed on Packet Forwarder>Radio, related configuration remains on Packet Forwarder>General.

Bugs Fixed:

  1. RX2 downlink problem due to change of channel plan from as923-2, 923.2M to 921.4M.
  2. When downlink payload exceeds 9 bytes, Detail displays wrong payload.

Version 60.0.0.28

Bugs Fixed:

  1. When deleting this device on Cloud, delete the mapping relationship between SN and devEUI.
  2. Cloud should have enabled confirmed mode in WS86.
  3. Uplink SF didn’t present value.
  4. Gateway postpones 3 sec to send attribute in order to resolve concurrency issues.

Version 60.0.3000.28

NOTE: This version and the standard version cannot be upgraded each other, and can only be upgraded by burning or entering the undead uboot to upgrade the ext2 firmware.

What’s New:

  1. Greengrass compatibility.
  2. Python 3.7.

Version 60.0.0.25

NOTE: Upgrade from 17 and lower, please clear web cache afterwards due to massive upgrade on web GUI. Downgrade from 25 and higher, MUST enable “reset to factory defaults” on Maintenance>Backup and Restore otherwise device will be stuck in repeating reboot.

Added:

  1. Multi-gateway architecture.
  2. Support for basic station.
  3. Antenna wizard for the first login (gateway reset or upgraded from version 17 to the latest version), includes two configuration pages for antenna type and password security check.
  4. UG67 includes antenna type, SMTP, email phone settings, Change password four configuration pages
  5. Added UG65 (power-on) and UG67 (power-off/power-on) alarm function. When the mailbox and phone are configured, the device will be triggered to send emails and text messages after power off.
  6. Schematic representation of antenna type, UG65 (two built-in, built-in + external), UG67 (two built-in, built-in + external, two external).
  7. Ursalink is replaced by Milesight, default Wi-Fi name is Gateway_XXXXXX, default host name in Packet Forwarder>General is GATEWAY.
  8. 915 gateway adds AS923-2 frequency band
  9. New connection status when the gateway is connected to different NSs (note: semtech cannot confirm the connection status using UDP connection, it will be displayed as connected)

Optimized:

Bugs Fixed:

  1. Batch downlink to control WS86 might fail.
  2. JIO and Vodafone might fail to dial normally in India. Reason: APN needs to be preset in advance.
  3. Incorrect GPS data.

Version 60.0.0.17

Added:

  1. LoRaWAN regional plan on Status>Overview.

Optimezd:

  1. Model naming.

Bugs Fixed:

  1. Batch downlink to control WS86 might fail.
  2. JIO and Vodafone might fail to dial normally in India. Reason: APN needs to be preset in advance.
  3. Incorrect GPS data.

Version 60.0.0.14

Bugs Fixed:

  1. When NS received data packets from two nodes at the same time, MQTT client would not report the first data packet, but sent two second packets.
  2. If a back up file of NS with registered end-devices is imported into a new gateway, the new gateway automatically becomes failover for the registered ones now.

Version 60.0.0.13

Initial version.

Version 76.2.0.2

What’s Better:

  1. Support Unicom Yanfei 5G module.
  2. Merge UF51 and UR75v2, transplant IPv6 related feature and content.
  3. Support serial log printing.

Fixed:

  1. DMVPN connection doesn’t support domain name as hub address and indicated cannot found pskey.
  2.  Inactive firewall filtering.
  3. Dialing sequence of phone registration that involves link priority.
  4. Different network segment in VLAN prompts conflct on Network>Switch.
  5. Keep to synchronize time from local browser after upgrade.

UG85/87v2 Version 80.0.0.85

What’s Better:

  1. Upgrade packet forwarder to Loriot

Bugs Fixed:

  1. Wrong display of altitude on Status>Overview.

UG85/87v2 Version 80.0.0.83

What’s Better:

  1. Support for WS86.

Bugs Fixed:

  1. MQTT and HTTP forwarding call different decoder.
  2. UC1152’s Modbus RTU could not be recognized correctly on the gateway.
  3. WiFi configuration might fail to save.

UG85/87v2 Version 80.0.0.82

What’s New:

  1. Display module firmware version on “Status>Cellular”.

Optimized:

  1. Timeout sequence when trying to reconnect to MQTT broker: 2->4->8->16->32 sec.

Bugs Fixed:

  1. Batch downlink to control WS86 might fail.
  2. JIO and Vodafone might fail to dial normally in India. Reason: APN needs to be preset in advance.
  3. Packet forwarder configuration to ChirpStack might be erased. Resetting before upgrade is necessary to fix this problem.

UG85/87v2 Version 80.0.0.78

What’s new:

  1. Devices with freqencies CN470, US915 and AU915 come with default channel mask.

Optimized:

  1. The default tx power in NS is adjusted to maximum (CN470: 20dB; AU915: 27dB, EU868: 16dB, IN865: 27dB, KR920: 23dB, RU865: 16dB, US915: 27dB, AS923: 16dB).
  2. In Channel Mask setting the high bits of 0 will not be hidden after saving.
  3. For default spreading factors SF10, SF11, and SF12, gateway uses window 1 to downlink messages (take effect after reset).

Bugs fixed:

  1. When NS received data packets from two nodes at the same time, MQTT client would not report the first data packet, but sent two second packets.
  2. If a back up file of NS with registered end-devices is imported into a new gateway, the new gateway automatically becomes failover for the registered ones.
  3. Idle application saved an extra copy of related data packets for another application with MQTT enabled, which caused repeated data transmission.
  4. Too many file handles during DeviceHub connection.

UG85/87v2 Version 80.0.0.75

What’s new:

  1. Support WS86.

Optimized:

  1. “lastseen” value reported by Gateway to Milesight IoT Cloud will be more realistic  with second as minimal unit.

UG85/87v2 Version 80.0.0.74

Optimized:

  1. Default frequencies for CN470 model used to be 80~87 or 80~95 and now are 8~15 (8-channel model) or 0~15 (16-channel model).
  2. Default keep-alive interval for CN470 model is 10 seconds now.

Fixed:

  1. Exit route 0.0.0.0 might be lost after failover configuration on “Network>Link Failover>WAN Failover”.
  2. Invalid SSH connection might be set up to DeviceHub when SSH was not enabled.
  3. System would be constantly rebooting after a sudden power cut when installing postgressql.
  4. MQTT client might stop publishing messages after a while.
  5. End-devices might fail to join network when keep-alive interval on “Packet Forwarder>Advanced>Intervals Setting” was 3600 seconds.
  6. Localhost as a destination on “Packet Forwarder” might fail to start when switched on from ChirpStack.
  7. chirpstack-gateway-bridge was not saved in back-up file.

Removed:

  1. Network Mode on “Packet Forwarder>Advanced>Network Setting”.

UG85/87v2 Version 80.0.0.69

Added:

  1. LinkWAN option in multi-destination (CN470 only).

Optimized:

  1. Enable NAT by default.
  2. eMMC stability.
  3. Prolong timeout for custom payload codec.

Fixed:

  1. Illegal downlink topic when gateway connected to Azure via MQTT.
  2. admin account might fail to log in via SSH.
  3. GUI of some new devices only displayed pages related to Packet Forwarder and Maintenance, other pages remained blank and the device kept rebooting.

UG85/87v2 Version 80.0.0.66

Optimized:

  1. Loriot connection.

UG85/87v2 Version 80.0.0.65

Optimized:

  1. eMMC performance

UG85/87v2 Version 80.0.0.64

Added:

  1. Add devices in batch
  2. Display MQTT connection status.
  3. Support to use “$deveui” on uplink/ack/error/notification topics. E.g. : “/Milesight/uplink/$deveui” means to publish to “/Milesight/uplink/xxxxxxxxxxxx” according to the DevEUI in packet.
  4. Support to use “$deveui” on downlink topics. E.g. : “/Milesight/uplink/$deveui” means to publish to “/Milesight/uplink/xxxxxxxxxxxx” according to the DevEUI in packet.

Optimized:

  1. LoRaWAN® uplink payload format.
  2. Pyuser user security issues.
  3. Shorten firmware upload time.

Fixed:

  1. System constantly reboots due to enabled IPSec.
  2. Cellular LED indicators switched.
  3. MQTT connection thread stuck resulting in failing to respond JnAcc.

UG85/87v2 Version 80.0.0.62

Added:

  1. Main interface set as cellular0 automatically in “Network>Link Failover>WAN Failover”.

Optimized:

  1. “Help” sidebar explanation.
  2. Default WAN static IP: 192.168.23.150, gateway: 192.168.23.1.

Fixed:

  1. Reconnect timeout extends to 6 sec when subscribing AWS MQTT service.

Removed:

  1. “LAN”, “PORT”, “VLAN Truck” tabs on “Network>Interface”.
  2. “4G First”, “3G First” options under “Network>Interface>Cellular”.

UG85/87v2 Version 80.0.3000.59.1

NOTE:

  • If you are using AU915 before upgrade, please change “Supported frequency” in “Packet Forwarder>Radios” to US915/AS923, “Save” and “Apply”, then change it back to AU915, “Save” and “Apply”.
  • Resetting to factory defaults is must when upgrading from greengrass version to normal version.

Altered:

  1. Upgrade Python 2.7 to Python 3.7 bundle and environment.

UG85/87v2 Version 80.0.0.59

NOTE:

  • If you are using AU915 before upgrade, please change “Supported frequency” in “Packet Forwarder>Radios” to US915/AS923, “Save” and “Apply”, then change it back to AU915, “Save” and “Apply”.

Added:

  1. Devices with GPS module will display GPS information on “Status>Overview”.
  2. “Basic Station” option as Packet Forwarder type.

Optimized:

  1. Cellular network problem with EG25 module.
  2. Optional Semtech server addresses. Reference
  3. Allow blank as password in MQTT user credentials

Fixed:

  1. AU915 connection problem with TTN.
  2. DeviceHub connection problem after reboot.
  3. False connection to Milesight IoT Cloud after constant switch.
  4. If Milesight, Semtech, Chirpstack are all disabled on “Packet Forwarder>General”, buttons on “Packet Forwarder>Traffic” are enabled regardless of status of embedded network server; if TTN/Loriot/Chirpstack/Base Station is enabled, buttons are disabled.

Removed:

  1. “2G First”, “2G Only” options on “Network>Interface>Cellular”.

UG85/87v2 Version 80.0.0.53

NOTE:

  • Due to massive change on web GUI, please refresh the web page after upgrade.

Added:

  1. Support multi-destination (Milesight, Semtech, TTN, Loriot, ChirpStack) for LoRa packets.
    • No other destination could be chosen when TTN, Loriot or Chirpstack is enabled.
  2. Support 16 channels under Milesight/TTN/Semtech mode.
  3. Support frequency synchronization from localhost or NS (NOT applicable to ChirpStack).
  4. Support TLS validation without certificates.
  5. Increase length limit in MQTT user credentials.

Optimized:

  1. Logical relationships warning notes at different destinations on Packet Forwarder page.
  2. Frequency-Sync stays disabled when no destination is enabled.
  3. Milesight IoT Cloud on Network Server page.
  4. When LoRa radio on Packet Forwarder>Radios>Radio Channel Setting is changed, Channel Plan Setting on Network Server page changes automatically.
  5. When Ethernet port is set as WAN, disable DHCP.

Fixed:

  1. Default route lost when using cellular.
  2. Cannot connect to Loriot server after reboot.
  3. End-devices failed to activate after reboot.
  4. Default value of IN865 channels, failure in saving IN865 channels.
  5. Failure in scanning WLAN AP.

UG85/87v2 Version 80.0.0.49

Added:

  1. Support multi-destination (Milesight, Semtech, TTN, Loriot, ChirpStack) for LoRa packets
    • No other destination could be chosen when Loriot or Chirpstack is enabled
  2. Support 16 channels under Milesight/TTN/Semtech mode
  3. Support frequency synchronization from localhost or NS (NOT applicable to ChirpStack)
  4. Support TLS validation without certificates
  5. Increase length limit in MQTT user credentials

Fixed:

  1. Default route lost when using cellular

UG85/87v2 Version 80.0.3000.43.4

Note:

  • Resetting to factory defaults is must when upgrading from greengrass version to normal version.

Altered:

  • Upgraded Python 2.7 to Python 3.7 bundle and environment.

UG85/87v2 Version 80.0.3000.43.2

Note:

  • This version works exactly the same as 43.1 but is a springboard between 43.1 to 43.4 or higher Greengrass version.
  • Resetting to factory defaults is must when upgrading from greengrass version to normal version.

UG85/87v2 Version 80.0.3000.43.1

Note:

  • Resetting to factory defaults is must when upgrading from greengrass version to normal version.

Added:

  1. Greengrass related features.
  2. Python 2.7 bundle and environment.
  3. soft links are now saved in /etc/root/home (before were saved in /mnt/mmcblk0p1).
  4. When upgrading, backup system stays the same.

Altered:

  1. GRPC port from 8000 to 9000 to avoid conflict with Greengrass.
  2. Permission on system utility from read-only to read&write.

UG85/87v2 Version 80.0.0.43

Added:

  1. Allow blank or special characters in MQTT user credential

Fixed:

  1. Downlink conflict bug
  2. Cloud connection failure due to port mismatch

UG85/87v2 Version 80.0.0.39

Added:

  1. Display “-CH16” in 16-channelled gateway’s PN code

Optimized:

  1. Timezone synchronization mechanism

UG85/87v2 Version 80.0.0.38

Optimized:

  1. Support 16-ch module
  2. Optimize nodes’ network joining judgement

Fixed:

  1. Timezone problem in Packets of Network Server
  2. System time error after reboot

UG85/87v2 Version 80.0.0.35

Added:

  1. EG25-G module

UG87v1 Version 81.1.0.117

Optimized:

  1. Allow special characters in MQTT user credentials but not blank

Fixed:

  1. Downlink conflict

UG87v1 Version 81.1.0.115

Fixed:

  1. System timezone error and time display error in NS packets after upgrade when device local timezone is not UTC+8
  2. System time error due to device reboot
  3. Probable login failure due to altered password

UG87v1 Version 81.1.0.111

Added:

  1. Modbus RTU to TCP/Modbus RTU over TCP feature

UG87v1 Version 81.1.0.108

Fixed:

  1. MQTT related bug
  2. Frame count bug for device in ABP mode

UG87v1 Version 81.1.0.106

Added:

  1. Redis backup
  2. Subscription in MQTT client to downlink

Altered:

  1. Disable Frame-counter Validation as default

Fixed:

  1. SSH/Telnet access error when using WAN
  2. Multi clients bug to MQTT

3x.2.0.36

What’s Better:

  1. Open to configure TX/RX gain of UR35’s FXS port.

Bugs Fixed:

  1. EG25/EP06 module cannot be reloaded.
  2. OpenVPN server cannot ping the client.

3x.2.0.35

What’s Better:

  1. Support UR32L (web page display).

Bugs Fixed:

  1. Watchdog might restart when the serial port sends data too fast.
  2. Short network interruption during cellular IP renewal.
  3. User name/password is not set when dialing in the GM510 module.
  4. Python interface get_do_output_info is called incorrectly when the DO mode is not custom.
  5. After the serial port DTU failed to connect to the Server, the Socket handle was not closed, and the connection could not be successful after the Server was restored.
  6. Devicefound memory leak problem.
  7. Watchdog restart that was caused by IPSec transferring large files.
  8. Importing a backup file containing devicehub, the web page cannot be accessed, and DeviceHub cannot be successfully connected.

3x.2.0.32

What’s Better:

  1. Support Fibocom NL668 module.
  2. CLI command “show system information” adopts local time.
  3. CLI command to configure the PPP dial interface mask, the default PPP dial subnet mask is set to 32.
  4. Status display on DDNS configuration page.
  5. Dialing program for Fibocom module.
  6. CLI “ping” command increases the number of PING packets parameter (1-86400), by default it only pings 3 packets.

Bugs Fixed:

  1. Log size of cellular, WiFi log, hostapd.log and firewall exceeds 2 MB and more rather than saves in .old file.
  2. ICMP detection might not perform immediately when the link is available again.
  3. OpenVPN time displays wrong.
  4. Link-in-use identifier of the link backup should be reset when the link becomes invalid.
  5. Emergency reboot might not take effect.
  6. Number saved in the database might be truncated when the phone number exceeds 16 digits.
  7. DHCP Server address pool configuration might fail to save.
  8. Revert interval in link failover cannot be 604800.
  9. Routes added by link backup should not be deleted.
  10. PC or other devices in LAN cannot update IP address after DHCP address pool is changed.
  11. Occasional sys.log crash when router connects to MilesightVPN Server.
  12. IE11 cannot log in to the device management page.
  13. VRRP will be closed by default when restarting.
  14. After the UR35 restarts, the device connected to the LAN port should not get the WAN port assigned IP.
  15. Custom firewall rules might be erased after restarting restarting.

3x.2.0.28

Bugs Fixed:

  1. Local network cannot access the router when the IPSec local subnet overlaps the remote subnet.
  2. Truncated cellular log.

3x.2.0.27

What’s New:

  1. When a [xxx]-custom.conf file exists in the IPSec/OpenVPN configuration file directory, replace default configuration file with [xxx]-custom.conf.
  2. upgrade program for QFlash module from Quectel.
  3. Network restart timeout limit is extended from 150 sec to 300 sec, and the module restarts when QIACT did not return.
  4. Default rightid configuration for IPSec.
  5. GPS information query and configuration node for SNMP MIB library.
  6. Support for EC200S, L610-CN, and SLM320 modules.

Bugs Fixed:

  1. When on-demand dialing mode is enabled, cellular link couldn’t become inactive after being idle.
  2. Modbus Master might double the address in the request.

3x.2.0.22

What’s new:

  1. CLI command to manually activate DO (ROUTER(config)# activate do).

Bugs fixed:

  1. Router disabled SSH service, DeviceHub still prompted that SSH was available.
  2. Absent OpenVPN log in vpn.log file.
  3. Abnormal function caused by too many handles of devicehub.

3x.2.0.20

What’s new:

  1. Cellular module’s firmware on “Status>Cellular”.

Optimized:

  1. The maximum number of Wi-Fi clients is limited to 15, and the default number is 10.

Bugs fixed:

  1. When QoS download was stopped, upload might not stop.
  2. Wrong OpenVPN configuration might cause crash log and abnormal OpenVPN related process.
  3. Kernel dump problem when multiple Wi-Fi clients are connected
  4. When the OpenVPN authentication method was username + certificate, configuration file did not save with TLS authentication checked.

3x.1.0.63

Bugs fixed:

  1. SNMP MIB file loading failure.
  2. Failure in obtaining SNMP WAN port’s Gateway.
  3. DTU TCP-Server/UDP-Server mode (the select interval 10ms is incorrectly set to 10 nanoseconds) might cause CPU occupation up to 100%.
  4. Abnormal selection of the quagga caused by the vty handle not being closed normally.

Removed:

  1. Cellular Connection Setting configuration items in the SNMP MIB (because these configuration items are related to each other, and SNMP write operations can only be configured one by one).

3x.2.0.18

What’s new:

  1. Cellular speed and uptime interfaces in MIB.
  2. OpenVPN is upgraded from 2.4.0 to 2.4.9.

Bugs fixed:

  1. Reload counter was not reset after dialing succeeded, which led to a direct restart instead of reload in the next exception.
  2. If system recorded signal like “ICMP FAILED” while dialing, reload counter might not be reset and caused exception in next dialing action.
  3. Default route of cellular missed.
  4. Cellular network was normal but the signal lights were all off.
  5. CSQ99 event is prevented from triggerring the cellular module to redial now.
  6. Security issues.
  7. Expert options were not written into configuration.
  8. DI false alarm.
  9. After the OpenVPN Client was successfully connected, the status page displayed “Disconnect”.
  10. Network might not automatically recover when the AT command read and wrote abnormally under high temperature conditions.
  11. High CPU usage in DTU process caused in tcp_server and udp_server modes, the timeout setting of select was incorrectly set to 10 nanoseconds (expected to be 10 milliseconds).
  12. Hardware reset button might fail.
  13. Out-dated interfaces left in MIB.

3x.2.0.10

Added:

  1. “Network>Firewall>Port Mapping” allows 64 rules now.

Fixed:

  1. Major change in ubus interfaces led to possible failure in reading product and firmware information on “Status>Overview”

3x.2.0.8

Optimized:

  1. Quicker dialing under weak signal or other occasions that switching SIM cards is needed.

Fixed:

  1. cellular0 might obtain void address.

3x.2.0.6

Added:
  1. “Link in use” block on “Status>Overview”.
  2. Cellular signal strength bars on “Status>Cellular”, no bars for 0 asu.
  3. Cellular usage monthly statistics on “Status>Cellular”.
  4. “Satellites in Use”, “Satellites in View” data display on “Status>GPS”.
  5. AT commands debugger on “Maintenance>Debugger>Cellular Debugger”. NOTE: If debugger result is cleared, it can’t be downloaded as log file.
  6. Create firewall by typing in firewall rules on “Maintenance>Debugger>Firewall Debugger”, and to modify or delete a firewall rule is not supported.
  7. Daily, weekly, monthly reboot cycle to achieve more flexible reboot schedule.
Modified:
  1. Link failover is moved from “Network>Link Failover>WAN Failover” to “Network >Interface>Link Failover” and integrated with the switch to enable or disable each interface.
  2. Order of “Network” settings on left navigation panel are “Network>Interface, DHCP, Firewall, QoS, VPN, IP Passthrough, Routing, VRRP, DDNS” now.
  3. Order of “System” settings on left navigation panel are “System>General Settings, Phone & SMS, User Management, SNMP, AAA, Device Management, Events” now.
Optimized:
  1. NTP server and client are separated.
  2. Add “Choose All” checkbox for each column on “System>Events>Events Setting”.
Fixed:
  1. PPPoE password encryption.
  2. NAT is enabled by default and cannot be disabled.

3x.1.0.61

Fixed:

  1. UR32 WAN NAT does not take effect after being disabled
  2. After the WAN port nat is enabled or disabled, the ping operation cannot take effect immediately
  3. EG25 occasionally can’t register the Internet

Optimized:

  1. Encrypt pppoe related password under admin account
  2. pyuser user security issues
  3. Shorten firmware upload time
  4. Python SDK installation prompts version mismatch problem

3x.1.0.58

Added:

  1. References counter in SLA/Track. Rules can’t be deleted when referred to.

Optimized:

  1. Reload automatically when recording qxdmlog.
  2. Request timeout time to connect to DeviceHub is extended to 10 sec.
  3. Multiple IP addresses of same subnet are allowed in bridge IP configuration
  4. Length limitation of DDNS password: 1-256.
  5. CPU 100% occupied by DeviceHub remote access.
  6. Reboot VPN clients when default route switches.

Fixed:

  1. Only 1 serial port could be read while 2 ports are using DTU-Modbus.
  2. Default port missing in static routing configuration while WAN is using PPPoE.
  3. Failed to download log file with http.
  4. False connection to DeviceHub when the device is not removed from previous account.
  5. Fail to delete phone group when it’s referred by a deleted event.
  6. Cancel email notifications or SMSs after reference is diabled

3x.1.0.48

Fixed:

  1. Default route missing
  2. The middle indicator of UR32 SIM signal LED keeps staticly on
  3. Telstra private network connection failure
  4. IPsec client cannot be pinged by server subnet
  5. Cellular connection failure problem because of SMS center redialing
  6. RS232 serial port error in first usage

Altered:

  1. Remove “4G first”, “3G first”, “2G first” options in cellular configuration page

3x.1.0.42

Fixed:

  1. Default route missing problem

3x.1.0.38&39

Added:

  1. DI edge trigger

Fixed:

  1. Even parity bug in RS232

3x.1.0.35

Fixed:

  1. TCP connection bug under FTP mode
  2. Static route missing after track recovery

Optimized:

  1. Distribute different track ID for each static route

Version 3.0.41

Fixed:

  1. Pyuser user security issues
  2. Shorten firmware upload time

Optimized:

  1. Add PN into Model, which displays on “Status>Overview”

Version 3.0.40

Fixed:

  1. Error caused by urtool -b when programming commands

Version 3.0.39

Added:

  1. References counter in SLA/Track. Rules can’t be deleted when referred to.

Optimized:

  1. Firmware upgrade can only be used within its own product series.
  2. Remove “This SDK does not match the current firmware version, please upgrade the Python SDK” after imported successfully.
  3. Remove “I/O error” after Python app with name containing special characters or numbers is imported.
  4. Remove unnecessary blank space on RS232 configuration.
  5. Stablize AppManager status.
  6. Request timeout time to connect to DeviceHub is extended to 10 sec.
  7. Multiple IP addresses of same subnet are allowed in bridge IP configuration
  8. Length limitation of DDNS password: 1-256.
  9. CPU 100% occupied by DeviceHub remote access.
  10. Reboot VPN clients when default route switches.

Fixed:

  1. Only 1 serial port could be read while 2 ports are using serial ports as RS485.
  2. Default port missing in static routing configuration while WAN is using PPPoE.
  3. When use PPPoE to access Internet with default netmask, default route was displayed as inactive and 2 bridge IP were displayed.
  4. When using PPPoE to access Internet, default interface displayed as “wan” without “pppoe” option.
  5. Failed to download log file with http.
  6. False connection to DeviceHub when the device is not removed from previous account.
  7. Fail to delete phone group when it’s referred by a deleted event.
  8. Cancel email notifications or SMSs after reference is diabled
  9. “3G-Only”, “4G-Only” cannot be taken into effect with LongSung module.
  10. When using L2TP routing, the connection cannot automatically restore after disconnect to Internet.
  11. Fail to connect to DeviceHub after hardware reboot.
  12. Possibility on failing to dial up with EC25-G.
  13. Error occurred when connecting to Azure with Python.

Version 3.0.36

Added:

  1. System reboot CLI (ROUTER# reload).
  2. NAT for IPsec server.

Fixed:

  1. Failed to upgrade.
  2. Memory leak problem caused by CLI (ROUTER(config-serial_1)#no serial debug).
  3. Register failure with Telstra.
  4. HTTPS/TELNET/SSH default ports.

Altered:

  1. Removed “4G-first”, “3G-first”, “2G-first” options on cellular page.

Version 3.0.32

Fixed:

  1. Default route missing problem

Version 3.0.31

Fixed:

  1. Some bugs

Version 3.0.28

Fixed:

  1. RS232 RTU mode Modbus even parity problem

Version 3.0.27

Fixed:

  1. Bug to redial after rebooting and SIM being inserted

Version 3.0.26

Fixed:

  1. TCP connection in FTP port mode

Version 2.0.81

Added:

  1. NAT for IPsec server.
  2. System reboot CLI (ROUTER# reload).

Fixed:

  1. Default route missing problem.
  2. Memory leak problem caused by CLI (ROUTER(config-serial_1)#no serial debug).
  3. OpenVPN client failed to generate configuration file.
  4. Register failure with Telstra.
  5. https/telnet/ssh default ports.

Altered:

  1. Removed “4G-first”, “3G-first”, “2G-first” options on cellular page.

Version 2.0.68

Added:

  1. SDK installation in SSK.

Fixed:

  1. Multi-IP bug in WAN status when choose PPPoE mode for WAN

Version 1.0.30

What’s Better:

  1. Cellular interface supports IPv6, IPv4/IPv6 full stack.
  2. WAN interface supports DHCPv6 client, PPPoEv6, DS-Lite. (WAN doesn’t support to individually obtain IPv6 or IPv4 address; PPPoEv6 supports to obtain both address at the same time.
  3. DHCPv6 Server feature to support stateful DHCPv6.
  4. Ping detection supports IPv6 address detection.
  5. Remove abundant interface (miireg, ifb1, ifb0, bond0).
  6. ath1 is now WLAN-5G, ath0 is now WLAN-2.4G.
  7.  Network mask is displayed as xxxx/xx for both IPv6 and IPv4.
  8. IPSec supports Expert Options; when there is a configuration conflict, the expert option prevails.
  9. Texts to IP address in help bar are updated.
  10. “Network Mask” is now “Network Mask/Prefix Length” on Status>Routing.
  11. “Network Mask” is now “Network Mask/Prefix Length” on Network>Routing>Static Routing.
  12. Display for network mask of IPv6 is now “Prefix Length”.

Bugs Fixed:

  1. Process stuck caused by invalid DeviceHub server address.
  2. Possible failure to upgrade from DeviceHub.
  3. Wrong display of connection status on web GUI of router when connected to DeviceHub.
  4. Corresponding process stays when router is deleted from DeviceHub.
  5. Possible failure to upgrade certain files after upgrade is done.
  6. OpenVPN server might fail to ping client.
  7. Modbus Master might double the address to query.
  8. Error caused by calling get_do_output_info when DO mode is not custom.
  9. Handles might not close when DTU mode failed to connect to TCP server.
  10. Wrong display of status when upgrading router from DeviceHub.
  11. Blinks of Ethernet port LED when no data flows over.
  12. Maximum resending times of SMS is now fixed to 2.
  13. Failure to pip install without root access.
  14. Failure to IP passthrough to PC when cellular interface changes IP address.
  15. SSL or StartTLS questions failed to save on System>AAA>LDAP.
  16. Missing CPU and SN in updating data to DeviceHub.
  17. Network mask to 28 failed to save.

Version 1.0.29

What’s New:

  1. Mandatory set ath1 MAC to wifi1 MAC.
  2. Change the default mask of the PPP dial interface to 32, and add CLI commands to modify the mask.
  3. Network>Interface>Cellular>Network Type adds 5G-NSA, 5G-SA as options.
  4. WiFi AC mode allows configuration bandwidth (20MHz/40MHz/80MHz).
  5. In WiFi AP mode, when WPA encryption is enabled, “group key update interval” option is available, the default value is 3600 sec.
  6. Add reboot printing to system.log.
  7. The neutral version product code was changed to NA75.
  8. WLAN2 status information to the status page.
  9. System information page Model field function codes are arranged in alphabetical order.

Bugs Fixed:

  1. 5G network registration might fail in SA mode.
  2. L2TP cannot be connected after enabling and disabling L2TP for multiple times.
  3. Web GUI displays abnormally when registering on the 5G SA network.
  4. DHCP Server address pool might fail to be changed.
  5. Number saved in the database and the number on the web GUI are truncated when the phone number exceeds 16 digits.
  6. Originally registered host cannot get the IP after the DHCP address pool is changed.
  7. Link failover’s recovery interval cannot be set to 604800, its upper limit.
  8. OSPF/RIP cannot configure L2TP and PPTP interfaces.
  9. Connected client cannot be displayed when WEP encryption is enabled in WiFi AP mode.
  10. Python content is cleared after upgrade.
  11. SINR parameter error in NR-SA network mode.
  12. System.log updates no more after router connects to Milesight VPN.
  13. Status still shows connected after the WiFi client is closed.
  14. Unable to ping under CLI, prompting to root.
  15. Abnormal display of cellular status LAC in 4G/5G network mode.
  16. Missing configuration items on the web GUI when WiFi is switched from client mode to AP mode.
  17. Wrong display of upstream and downstream bandwidth in SA network mode.
  18. ICMP route automatically added by the link backup might be deleted in the static route.

Version 1.0.21

Optimized:

  1. Upgrade method: backup>reset>upgrade>read backup file, in case the modified files are not overwritten.
  2. Enable CPU load balance by default (CLI command: ROUTER(config)# [no] cpu load balance) to increase the cellular downlink rate.

Bugs Fixed:

  1. Cellular downlink rate was limited to 150Mbps.
  2. SSH service was disabled on the router, DeviceHub still prompted that SSH was available.
  3. Absent OpenVPN log in vpn.log file.
  4. Kernel crash because GPS and Quagga concurrent access to /dev/ttyUSB.
  5. cloudclient crash because abnormal file writing under abnormal power failure.
  6. Password reset when upgrading without reset.

Removed:

  1. QoS page.

Version 1.0.19

What’s new:

  1. 5G modules like Huawei MH500, Gemalto, etc.
  2. Display module firmware version on “Status>Cellular”.

Optimized:

  1. Maximum VLAN ID is limited at 127.
  2. vlan 1 is used by Bridge0.
  3. vlan 2 is reserved for WAN port.
  4. 11 as vlan ID is restricted and not allowed to use.
  5. Priority order of available DDNS service providers.

Bugs fixed:

  1. SNMP problem with faulty MIB file.
  2. WAN access might fail.
  3. VLAN configuration might fail.
  4. QoS might fail.
  5. DHCP Server might fail to allocate subnets when VLAN was enabled.
  6. Quectel RM500 module could not dial up when the network mode is “5G-only”.
  7. RM500 SIM card switching might fail.
  8. When “Status>Cellular” was refreshed, there might be multiple lines of “data usage statistics”.
  9. More than one udhcpc processes.
  10. DDNS program inadyn might fail.
  11. Button “Save” might not respond when the DDNS setting was saved for the second time.
  12. InACL and OutACL in the interface list become empty when the firewall deletes an ACL that was not referenced.

Removed:

  1. Service providers that no longer operate or do not provide DDNS on “Network>DDNS”.
  2. DMVPN log “config change, mtu=1500”.

Version 1.0.15

Bugs fixed:

  1. DTU TCP-Server/UDP-Server mode (the select interval 10ms is incorrectly set to 10 nanoseconds) might cause CPU occupation up to 100%.
  2. Some information in MIB interface could not be obtained.
  3. Quagga restart problem due to zebra segmentation error.
  4. Hardware reset button might fail.

Version 1.07

What’s Better:

  1. Optimize battery voltage sampling.
  2. Modify the switch logic, start immediately after power-on, and execute the collection task.
  3. Added the power-on indicator light will stay on for 3s.
  4. Modify the original shutdown interface, now, skipping the original shutdown interface to send a command will write the shutdown state, but will not restart the device.
  5. Modify the start node of the acquisition cycle timer.
  6. Modify the reload operation of not connected to the network to avoid the problem of unable to connect to the network caused by repeated triggers.
  7. The network re-entry mode is modified to send the link check command to the next data packet more than 30 minutes, and the longest interval is the period packet.
  8. Modify the reset button function, remove the switch machine, add restart.
  9. Added OEM pre-configuration function.
  10. Modify the processing when an ECCD check error occurs in the NMI interrupt.

Bugs Fixed:

  1. Fix the problem that the default value of the debounce configuration is wrong.
  2. Fix the problem that the reset process is interrupted and the device parameters are wrong.

Version 1.06

Initial version.