AEP Firmware Changelog

1.4.16 (03/29/2018)

Bug Fixes

  • Fix for some JoinEUI values creating invalid Join Accept messages to be transmitted
  • Fix db migration from AEP 1.4.3/1.4.14 for lora database path

Known Issues

  • IN865: Rx2 frequency for downlink is not set by network server.
    • Workaround by fixing the Rx2 Frequency through the API
      • curl 127.0.0.1/api/loraNetwork -X PUT –data ‘{“lora”:{“rx2Frequency”:866550000}}’
      • curl 127.0.0.1/api/command/save_restart -X POST –data ”
    • If the channel plan is changed the Rx2 frequency setting should be unset
      • curl 127.0.0.1/api/loraNetwork -X PUT –data ‘{“lora”:{“rx2Frequency”:0}}’
      • curl 127.0.0.1/api/command/save_restart -X POST –data ”

1.4.14 (03/21/2018)

Changes

  • Increase the RSA key length in server.pem (the default self-signed certificate) to 2048 bits.
  • Upgrade to wpa_supplicant 2.6
  • Upgrade pyserial to version 3.4
  • Display LoRa Server and Packet Forwarder versions in web UI.
  • Be able to use the lora network server without a mtac-lora card installed
  • Update Node-RED to version 0.15.3
  • Add support for LDC3 radio
  • Custom Apps: Update user defined defaults to backup and restore custom apps installed in /var/config/app. Custom Apps are not uploaded with configuration to Device HQ.
  • Add libnfnetlink and libnetfilter-log to AEP 1.4.x and turn on CONFIG_NETFILTER_XT_TARGET TPROXY and NFLOG in kernel
  • lora-network-server now version 2.0.18
  • Add LoRaWAN Private mode for LoRaWAN compatible network using 0×12 syncword
  • Restart lora services if a packet forwarder has not been seen in 10 minutes
  • Class C scheduling up to 5 seconds out, instead of failing schedule call multiple times
  • Set default join delay to 5 seconds, if null was provided OTA join was not possible
  • Fix sample config file JSON error comma at end of list
  • Add app port to application MQTT topic for up and packet_sent events
  • Allow for application specific filtering such as Multicast or Multipart
    • mosquitto_sub -v -t lora/+/+/+/+
    • mosquitto_sub -v -t lora/<APP-EUI>/<DEV-EUI>/<APP-PORT>/<EVENT>
  • PUT update to LENS cloud for end-device class, name, hardware or firmware version if changed on Conduit
  • Add some time randomization for class C downlink rescheduling
  • Fix for US/AU private mode Rx2, frequency was not correct
  • Emit queue_full message if no room left, check of queue size was added before making a call to add the packet
  • Lora:
    • show join request result description in hover over
    • statistics for dropped packets has changed
    • add gateway card info to packet forwarder config section
    • do not hide Command to restart lora services based on capabilities.
  • LoRaWAN Changes
    • Removed Setup > Lora menu item
    • Added LoRaWAN menu group
    • Added LoRaWAN menu items
    • hide menu items if network server is not enabled.
    • Network Settings
    • Key Management
    • Gateways
    • Device Configuration
    • Device Sessions
    • Packets
    • Downlink Queue
    • Added restart lora services command to commands menu
    • Backup lora database before creating config download
    • Added Packet Forwarder mode configuration UI
    • Updated to Network Server to v2.0.11
    • Added multiple gateway support
    • Added LENS cloud join server support
    • Added LENS cloud statistics support
    • Command API updates to add devices, sessions and downlink packets
    • Added json output options
    • lora-query interface changed to pass commands to network server
    • MQTT event updates for applications

Bug Fixes

  • lora-in node fix to reconnect if disconnected from MQTT broker
  • Disabled logging on LoRa Packet Forwarder in forwarder only mode to prevent filling up /var/log
  • Node-RED LoRa node fixes [IN002602] lora-out node UI cannot be overridden.
  • Node-RED mCard and lora node fixes handling lora nodes and new rev of LoRa network server
  • Support Portal Case #5084641: Device GPS position data not displaying
  • dnsmasq: Starting too early causes it to point to stale empty resolv.conf file
  • SNTP: SNTP server settings don’t transfer after device firmware upgrade
  • WAN priority defaults after upgrade
  • Logging: Setting Debug Options syslog level to INFO doesn’t allow INFO
  • Make firmware upgrade error message stay displayed on AEP web UI
  • Support #5085601: Lora networking disables if device config from template is used for device config upgrading
  • lora packet forwarder does not run after clicking submit button
  • ntp_sync: update to call ntpdate with both the -u and -b options
  • Radio Firmware upgrade using AEP web UI fails
  • Turn off Server Cert Validation in URLopener call for Node-RED app download
  • network configuration: Cannot configure the eth0 interface with very restrictive subnet mask
  • PPP up and down Verizon (ppp-check process was trying to use ppp0 before it was up – race condition)
  • Help link broken for OpenVPN

Known Issues

  • Some JoinEUI values sent in the OTA Join Request can cause an invalid Join Accept response, this is fixed in lora-network-server v2.0.19 which is available for download
    • 12-00-00-01-00-00-00-00 is an example value
    • If the last half of 4th byte is greater than zero and the first byte is less than 0×14 an invalid Join Accept may be created
    • If the last half of 4th byte is zero there is no issue with the remaining bytes of any value like this example
    • 12-FF-FF-F0-FF-FF-FF-FF
  • Lora end-devices will not be saved over reboot for some configurations. See LoRaWAN > Network Settings > Database > Database Path set to /var/config/lora/lora-network-server.conf or click Reset To Default and reconfigure.

1.4.3 (06/09/2017)

Changes

  • Update OpenSSL to be in sync with the mLinux version of OpenSSL for backwards compatibility of applications.
  • Update LoRa Network Server to version 1.0.31.  The latest version is available on multitech.net.

Bug Fixes

  • Fixed SNTP feature upgrade to preserve non-default configurations.  This bug was introduced in AEP-1.4.1.
  • Fixed eglibc memory leak with gethostbyname

Known Issues

  • When upgrading to AEP 1.4.3 from a firmware level older than AEP 1.3.2 it is necessary to upgrade to AEP 1.3.3 first and then to AEP 1.4.3 in order to retain the LoRa configuration settings. If it does not matter whether the LoRa configuration settings are retained or not, then it is possible to upgrade from any firmware older than AEP 1.3.2 to AEP 1.4.3.
  • Node-Red lora-in node may become disconnected from the broker and not connect again. Edit /opt/node-red/nodes/core/lora/lora.js and move the following code.
    client.subscribe(mqttTopic);

    To the inside of the ‘connect’ handler function.

        }).on('connect', function() {      
          node.log("Connected to MQTT for LoRa in node.");
          setStatus(node, "connected");                                  
          client.subscribe(mqttTopic);                                           
        })

1.4.1 (04/20/2017)

Changes

  • WiFi AP and Client support
  • Bluetooth IP and BLE support
  • Custom Application installation in flash (SD Card no longer required)
  • GNSS support (GPS NMEA support)
  • WAN failover
  • Ethernet Card support
  • LoRa support for US915, AU915, and EU915 channel plans
  • LoRa network server upgraded to version 1.0.26

Bug Fixes

  • The app-manager utility now sets the environment variables correctly for the “Start reload” command after a config file install from Device HQ.
  • The size of the fields for the rx_bytes and tx_bytes sent to Device HQ for Cellular stats has been increased and should support far larger values.
  • A bug preventing disabling of the LoRa Network Server after it was enabled has been fixed.
  • The Multi-Serial Node in Node-RED has been fixed so that RS-485 Half Duplex works and no longer continuously displays “disconnected”.
  • The level of OpenSSL has been upgraded to 1.0.2k to address multiple CVE’s.
  • An issue has been fixed where the DHCP client would not renew the lease on an Ethernet interface when cable was unplugged for a time and then plugged back in.
  • The DHCP server gateway address now gets updated when the IP on the Conduit interface is changed.
  • A bug when resetting to User Defined Defaults not working with non-default IP address has been fixed.
  • Installing a custom application from Device HQ, deleting it on Device HQ, adding the app back on Device HQ, and then re-installing the app to the Conduit no longer shows two of the same application in the app-manager DB.
  • A bug in the Inbound Forwarding Rule menu’s Input Filter Rule not showing the External IP address has been fixed.
  • A bug has been fixed involving AEP set for 868, LoRa setting Rx 1 DR Offset drop down menu adds values after changes are submitted.
  • A bug has been fixed involving LNS not sending LoRa downlinks with CRC disabled.
  • A bug has been fixed involving AS923, join on Rx2 NS uses DR0.

Known Issues

  • When upgrading to AEP 1.4.1 from a firmware level older than AEP 1.3.2 it is necessary to upgrade to AEP 1.3.3 first and then to AEP 1.4.1 in order to retain the LoRa configuration settings. If it does not matter whether the LoRa configuration settings are retained or not, then it is possible to upgrade from any firmware older than AEP 1.3.2 to AEP 1.4.1.
  • There is limited support fro running Wi-Fi Access Point and Client Mode concurrently at 2.4GHz. When concurrent mode is configured, the channel is not configurable because the channel is restricted to be the same as the channel the Wi-Fi client mode gets. To perform a Wi-Fi scan for access points when Wi-Fi client is connected, all “Saved Wi-Fi Networks” must be disabled.
  • It is not recommended to use Wi-Fi 5GHz in concurrent mode with Access Point and Client modes both enabled.
  • The version of mLinux stated on the AEP Conduit firmware 1.4.1 is 3.3.5. The mLinux version contains every commit for mLinux 3.3.6 except the commit that updates the revision and got tagged. So, in essence it is the same as mLinux 3.3.6.

1.3.3 (11/17/2016)

Changes

Bug Fixes

  • Leave Node-RED enabled on upgrade

1.3.2  (9/15/2016)

Changes

  • Custom Application Support
  • Configuration File Management for Custom Applications
  • Partial Configuration Download
  • LoRa network server upgraded to version 1.0.13
  • LoRa Web UI changes adding ADR support
  • Updated and new help content

Bug Fixes

  • Fix: Add support for decoding GSM PDU encoding characters
  • Do not set or allow setting LVW2 APN -> provider automatically sets APN
  • ppp doesn’t connect after the SIM card is ejected and inserted again
  • LEU1: Ping feature not working, increase ping data size due to provider/SIM limitation on minimum ICMP data size
  • Diversity gets disabled on LTE models – Initial Setup Wizard was defaulting diversity to false for LTE models
  • lora: query MTAC-LORA card frequency band on set defaults.
  • lora_pkt_fwd logging is disabled, process can be run manually to debug issues

Known Issues

  • Node-RED will be disabled after upgrading to 1.3.2, but you can re-enable it in the UI or through DeviceHQ (this will be fixed in the next release)
  • With 868 MTAC_LORA card installed, LoRa Network Server configuration must be set to EU868 channel plan after update.

1.2.2  (6/8/2016)

Changes

  • Upload LoRa stats to DeviceHQ
  • Upload system logs to DeviceHQ
  • Upload Node-RED application status to DeviceHQ
  • Make Node-RED settings.js modifiable. You can now modify this file without it being overwritten each time node-red restarts.
  • Add LoRa support for ADR (Adaptive Data Rate)
  • Improve Node-RED serial card performance by 10x
  • Added support for LTE radios
  • Improve LoRa config UI
  • Upgrade help content framework and theme
  • Upgrade lora network server to 1.0.8

Bug Fixes

  • Fix IE11 save & restart
  • Fix LTE radio RSSI isn’t updated after removing antenna
  • Fix only update system time in initial setup wizard if user is changing it
  • Fix sms send truncation on C2 radio SMS messages
  • Fix C2 receive SMS being truncated.
  • Fix for sms: characters like @ $ not working on CDMA & LVW2 multi-part sms
  • Fix Issue where “broken” tar files for apps were still “installing” the app though it could not run and was effectively broken.
  • Fix for updating time in the initial setup wizard -> only updates time when user has changed it in the wizard.
  • Fixed a bug in the jsparser that should resolve the DHCP lease expiration time issue.
  • Add npm utility back in, got removed because openEmbedded moved npm utility to a different package than nodejs.
  • Fingerprint assets (js/css) to fix caching issues
  • Fix restart page to redirect to login.html instead of dashboard.html
  • Remove password from lighttpd & api logging
  • Fix don’t validate DHCP form if not enabled
  • Fix app upload input fields too narrow
  • Fix LTE PPP doesn’t work when SIM requires PIN
  • Fix lora address range can’t be lowercase
  • Fix redirect to login page after factory default goes to wrong IP
  • Fix firewall rule description hover help not working
  • Fix initial setup wizard: change to LAN lost when backing through wizard
  • Fix sms characters = + and ` (but ` doesn’t work with all carrier combinations)
  • Fix Remote Management – device not consistently checking into DHQ at scheduled interval
  • Fix LoRa stats and nodes to DeviceHQ: reset appears to cause API to not return anything for node list on the Conduit.
  • Fix when Node-RED restarted, serial streamer instances not getting killed
  • Fix cases where firmware upgrade would fail
  • Fix LoRa logging: lora-pkt-fwd-1.log not getting rolled and keeps on growing.

Known Issues

  • lora-pkt-fwd-1.log still not being rotated. Will consume all RAM if unchecked.

1.1.2  (1/27/2016)

Changes

  • Add LoRa Packet Forwarder Mode
  • Upgrade Nodejs to 0.10.40
  • Upgrade Node-RED to 0.11.1
  • Make LoRa logging level configurable through the UI.
  • Update Node-RED SMS node to use only HTTP instead of HTTPS to conserve memory.
  • Change Node-RED log to always be /var/log/app/node-red.log
  • Improve Time Configuration UI
  • Improve Initial Setup Wizard
  • Feature: On Install Apps page, change “options” to “actions” and use better icon.
  • Add support for no-radio and LTE models.
  • Add Node-RED LoRa out support for requesting ACKs and setting the LoRaWAN FPort
  • Add Node-RED M2X node.
  • Improve stability & UI of multi-serial card nodes in Node-RED. Remove option for DTR/DSR flow control and 5 and 6 data bit options.
  • Add popup prompt if configuring lora network server without enabling it
  • Update LoRa Network Server to 0.0.9-2
  • Update LoRa packet forwarder to 1.4.1-r9

Bug Fixes

  • Fix Node-RED gpio node error message
  • Fix Node-RED sms UTF8 support.
  • Fix can’t browse to Node-RED via WAN port.
  • Fix sms to correctly handle characters like @ $ etc.
  • Fix firewall – lost access to box after enabling NAT Loopback on Prerouting Rule
  • Make default LoRa log level to be 30 instead of 100
  • Fix “SIM card is locked. Requires SIM Pin” message after enabling Dial-on-Demand
  • Fix can’t save default lora configuration
  • Fix Save & Restart not red after adding fixed DHCP address
  • Fix can’t add DHCP fixed address when using non-default subnet
  • Fix can’t configure DHCP infinite lease time
  • Fix can’t login to web interface with password containing ‘&’

Known Issues

  • npm is no longer in this version (unintended), but will be added back in the next release.
  • DHCP Server does not respond to requests if lease time is set to 11-13-47 or higher. Will be fixed in next release

1.0.33  (9/2/2015)

  • First official release!