mPower Firmware Changelog

Upgrading to 5.0.x
Note: Backup your configuration before performing this upgrade. If the firmware
upgrade fails, or it does not show the login page again, wait an additional 10
minutes. Power off and on the device and web in to check the version. If the
version does not show the latest, then the upgrade was not successful. Try to
perform the firmware upgrade again by repeating all the steps.Signing Options:
MultiTech is offering an unsigned (“standard”) and a signed version of the AEP 5 firmware. From the factory and for upgrades from 1.x to 5.x, the “Firmware Validation” setting in AEP 5.0.0 and newer defaults to “Signed Firmware Validation” enabled (checked). If you have AEP 5.x and newer and this option is enabled, then choose the Signed firmware. If disabled (not checked), then you may choose the unsigned (“standard”) or the signed version.Upgrade Process:

  • To upgrade using the Web UI to the latest AEP 5.0.x, you must be running at
    least 1.6.4 firmware.
  • If older than 1.6.4, you must be running at least 1.4.4 to upgrade to 1.6.4.
  • With older firmware, it is necessary to be at 1.4.4 before upgrading to
    version 1.6.4 or 1.7.4.

5.3.5 (10/19/2021)

5.3.4

Known Issues

  • Packet forwarder can stop transmitting after several days, work-around using CRON job to killall -9 lora_pkt_fwd – mPower 5.3.5 has this fixed

5.3.3 (3/29/2021)

5.2.1 (6/10/2020)

Known Issues

  • Repeated valid join requests can cause the lora-network-server.db to fill the /var/config partition
  • Packet forwarder can stop transmitting after several days when LBT is enabled

5.1.6 (3/08/2020)

Bug Fixes

  • Web-UI clears local storage on signin to fix browser issues after upgrading

Known Issues

  • LoRaWAN FOTA should use non-default Rx2 datarate, US/AU DR10 and other plans DR2 or above. The session may expire and the end-device will return to Class A mode before the firmware has finished broadcasting over multicast.

5.1.5 (3/08/2020)

Bug Fixes

  • Fix logrotate issues when configured in packet forwarder mode

Known Issues

  • LoRaWAN FOTA should use non-default Rx2 datarate, US/AU DR10 and other plans DR2 or above. The session may expire and the end-device will return to Class A mode before the firmware has finished broadcasting over multicast.

5.1.2 (12/06/2019)

Changes

Known Issues

  • Packet forwarder logs not being rotated
    • FIX: Update lora-logging IPK to 1.0-r3
  • LoRaWAN FOTA should use non-default Rx2 datarate, US/AU DR10 and other plans DR2 or above. The session may expire and the end-device will return to Class A mode before the firmware has finished broadcasting over multicast.

5.0.1(09/04/2019)

Changes since 5.0.0

  • Add support for the L4E1 and L4N1 models

Bug Fixes since 5.0.0

  • Allow access to SD card, access was lost in 5.0.0.
  • Fix for LoRa Network Settings defaulted on upgrade from version <=1.7.4
  • Fix two race conditions in LoRa Network Server, one blocked MQTT output, the other would cause a crash on uplink
  • Disable node-red logging to /var/log/app/node-red.log, log was not rotating correctly causing RAM to be filled

Known Differences since 5.0.0

  • No Known Differences.

Known Behavior in 5.0.1

  • User must be at version 1.6.4 (or newer) before upgrading to 5.0.1.
  • Although not recommended, downgrading to a version before 5.0.0 will require a
    hard reset back to factory default settings.
  • A Hard Reset (or Factory Default) will force 5.0.1 firmware into Commissioning
    Mode to create a new Administrative Username and Password.
  • On LVW2, certain newer Verizon SIM’s do not support SMS. Contact Verizon.
  • On LVW2, received SMS’s greater than 140 characters may be truncated to 140.
  • Command AT+WS46 reverts to default after a power cycle which may affect a user
    that sets a non-default value.
  • SMS Command API ignores 6 character password limit, does not fail if SMS is
    longer than 160 characters, has issues depending on location of spaces and can
    not view/delete inbox/outbox.
  • Notifications API can delete existing alerts, add new alerts, modify with
    non-existing group, add two groups with same name and generate email with
    bad characters.
  • DHCP API can set invalid Gateway.
  • With SMS Commands, the Whitelisted numbers may need to be updated to include a +,
    a 1, or full phone number. Send a test SMS to the device to confirm.
  • Version 1 API call (/api/v1/whoami) does not respond.
  • Connecting OpenVPN Tunnels, user is unable to open WebUI of remote device.
  • If using Remote Management and you perform a manual check in to Device HQ, your
    device may show two check in’s based on your Check In Interval.
  • The lora-network-server should be updated to from v2.2.30 to v2.2.41 to address a possible deadlock issue

5.0.0 (07/03/2019)

Changes since 1.7.4

  • Migration of Web UI to vueJS. Look and Layout has changed.
  • Added RADIUS support.
  • DHCP Lease Time displays expiration date and time.
  • Firewall display/layout aligns more with Linux layout.
  • Implement X.509 Certificate support.
  • Eliminate Default Username and Password. User prompted to set up a Username and secure Password upon Factory Default/Hard Reset, Commissioning Mode.
  • The Logout option has changed to Door Exit icon.
  • The browser tab name references page name.
  • Changed LogIn screen to sign-in.
  • Page links have removed the .html extension.
  • Add IPSec certificate based authentication support.
  • Updated supported ciphers in multiple features (SSH, HTTPS, etc…).
  • Implement Trusted IP feature.
  • Implement Self-Diagnostics beta feature to check Resource Overuse and Security Violations.
  • Incorporated Signed Firmware support.
  • SNMPv3 advanced security settings enhancements and support for multiple trap destinations. Extended SNMP read parameters.
  • Usage Policy implementation in the Web UI.
  • Display Notifications sent via Email, SMS, or SNMP.
  • RADIUS Message Authenticator Attribute was added to all PAP requests.
  • Implement tunnel features.
  • Implementation of more Network Interface capabilities under Setup > Network Interfaces.
  • Updated Global DNS Configuration under Setup > Global DNS.
  • Added Bootloader password configuration to the Initial Setup Wizard.
  • LoRa Network Server updated to v2.2.27.
  • LoRa Packet Forwarder: Added duplicate packet filter, fix for GPS lock and time synchronization and increased radio lead time for better downlink success.
  • Updated Help Content.

Bug Fixes since 1.7.4

  • Add Statistics page for OpenVPN tunnel.
  • Populated leading 0’s in SMS #cellular Command, Uptime now reads 00:00:00 not 0:0:0.
  • Fixed “Invalid Date” issue when viewing Remote Management with Firefox 47.
  • Fixed SMS Command #cellular eliminating Uptime leading 0’s.
  • Fixed device position on GPS page map to not depend on NMEA configuration settings.
  • Fixed Generate Certificate so that the City value is not lost and set to empty when generating a new Web server certificate.
  • SMS Commands should work again for International numbers.

Known Differences from 1.7.4

  • A hard reset/factory default of the 5.0.0 will force Commissioning mode.
  • Security modifications may require “sudo” usage if using SSH or debug console.
  • Security modifications require a “sudo su” to log into root and adding the following “–unix-socket /var/run/api/http.sock” to existing curl commands.
  • Although not recommended, downgrading from 5.0.0 to a previous version will require a hard reset back to default settings. Very important to not downgrade when remote to the device or when using DeviceHQ (Remote Management) because access will be lost.
  • On WiFi models, the Dashboard WiFi MAC address now matches the WiFi hardware instead of matching the Ethernet MAC Address. This was improper reporting on the Dashboard only, the WiFi hardware was correct.
  • Because of additional GPS options, GPS may take longer to acquire satellites.
  • IP Defense options, DoS Prevention, Ping Limit and Brute Force Prevention are Enabled by default.
  • Under Adminstration > Access Configuration, SSH via LAN is disabled by default.
  • For security, Telnet Radio Access and Telnet have been removed.
  • The Clear History buttons have moved from Administration > Debug Options to the Ethernet, WiFi and Cellular tabs under Status & Logs > Statistics.
  • GPS NMEA options default with GGA, GSA, GSV and RMC enabled and GLL and VTG are disabled.
  • The code version has been removed from the log in screen, it is replaced with the new mPower Edge branding.
  • Dashboard banner and Firmware version includes “-AEP”, i.e. 5.0.0-AEP.

Known Behavior in 5.0.0

  • User must be at version 1.6.4 (or newer) before upgrading to 5.0.0.
  • Although not recommended, downgrading to a version before 5.0.0 will require a hard reset back to factory default settings.
  • A Hard Reset (or Factory Default) will force 5.0.0 firmware into Commissioning Mode to create a new Administrative Username and Password.
  • On LVW2, certain newer Verizon SIM’s do not support SMS. Contact Verizon.
  • On LVW2, received SMS’s greater than 140 characters may be truncated to 140.
  • Command AT+WS46 reverts to default after a power cycle which may affect a user that sets a non-default value.
  • SMS Command API ignores 6 character password limit, does not fail if SMS is longer than 160 characters, has issues depending on location of spaces and can not view view/delete inbox/outbox.
  • Nofications API can delete existing alerts, add new alerts, modify with non-existing group, add two groups with same name and generate email with bad characters.
  • DHCP API can set invalid Gateway.
  • With SMS Commands, the Whitelisted numbers may need to be updated to include a +, a 1, or full phone number. Send a test SMS to the device to confirm.
  • Version 1 API call (/api/v1/whoami) does not respond.
  • Connecting OpenVPN Tunnels, user is unable to open WebUI of remote device.
  • Firmware upgrade may revert LoRa Network settings to default. Network Mode set to Private LoRAWAN may change to Public LoRaWAN. Rx2 Datarate to 8 for 915 cards and 0 for 868 cards. Rx1 Delay to 1. Join Delay to 1 for Private MTS or 5 for Public LoRaWAN. Additional Channels setting for KR920 and AS923 to 922.9 or 922.6, respectively. MaxEIRP and DwellTime Up/Down for AS923 to 0. WorkAround is to modify /var/config/db.json “__v”: 1 setting in “loraNetwork” collection to “__v”: 18 before the upgrade to avoid reverting. Otherwise modify the above settings after the upgrade.
  • If using Remote Management and you perform a manual check in to Device HQ, your device may show two check in’s based on your Check In Interval.

1.7.4 (05/14/2019)

Bug Fixes

  • In MTCDT AEP 1.7.3, it was identified that when the Ethernet cable was unplugged and plugged back in, the IP address would revert to the factory default setting (192.168.2.1) instead of the customer-defined IP address. This issue has been corrected.
  • In MTCDT AEP 1.7.3, gpsctl occasionally fails to initialize the GPS module, so GPS information is not consistently sent. This has been corrected by downgrading gspd to an earlier and more reliable version (3.16) while continuing to use 3.18.1 libraries.

1.7.3 (04/18/2019)

Changes

  • Changes were made to reduce noise during bootstrap, bootloader (u-boot), and kernel device tree on pins connected to the usb hub and GNNS module.

1.7.2 (03/15/2019)

Changes

  • The LoRa Network Server has been updated to version 2.2.18.
  • The LoRa v2.1 AES key is set by network server for accessing fine-timestamps for geolocation

Bug Fixes

  • Fix: LoRaWAN Network Server – Send correct Channel Mask in first downlink for AU/US

1.7.0 (02/27/2019)

Changes

  • The LoRa Network Server has been updated to version 2.2.6.
  • The GPS functionality has been re-architected for better performance and consistency.
  • Configurations downloaded from the device now no longer contain the AppManager.json file. That behavior was found to be problematic, causing App versions to possibly be incorrect.
  • A radio reboot feature has been added to reboot the radio when ppp has been unable to connect after all backoff timers have been exercised or ping/tcp connect has failed for ~2 hrs.
  • Custom Apps install was enhanced: back up the current app if one exists, and restore it if the new app install fails.
  • Support for the MTAC-XDOT card has been added.
  • LoRa: Dual Card Support has been added.
  • LoRa: RU864 (864- 870 MHz)
  • LoRa: Class B support
  • LoRa: Class C Multicast

Bug Fixes

  • The ICCID on the Radio Status Page has been added back in.
  • Radio switching between AT&T and Verizon on the MTCAP models with the LNA3 radio has been fixed.
  • A number of help links in the Web UI have been fixed including SMS Configuration.
  • Custom Apps: Fixed a race condition between restoring Custom Applications and reboot in User-Defined-Defaults restore.
  • SMS issues with international numbers have been fixed.
  • LoRa Packet forwarder logs are disabled, the forwarder logging did not work well with logrotate

Known Issues

  • LoRaWAN Network Server – US/AU channel plan sends ADR MAC command in first downlink after join that disables all channels. Devices that do not reject it will be silenced. mDot/xDot 3.1.0 with ADR disabled accepts the channel mask and is affected. (Update is pending to repair)

1.6.4 (11/29/2018)

Bug Fixes

  • Fix remote management but related to GPS interval that prevents configuration of remote management on devices with no GPS capability

1.6.2 (08/29/2018)

Changes

  • Built with Yocto 2.2 (Morty) and mLinux 4.0
  • Radio FOTA for H5 and LTE radios
  • Enable/Disable call home feature
  • Monit added for custom application monitoring
  • Back-up custom applications with user-defined-defaults
  • Python support for MODBUS and SSL
  • LDC3 Radio support
  • Netfilter NFLOG, TRPROXY, XT_MATCH_IPRANGE and XT_MATCH_TIME in kernel
  • Added libnetnfnetlink and libnetfilter-log to the mPower Conduit® image to support applications
  • Increased RSA cert length to 2048-bits
  • SMS Commands
  • Firewall – user chanins processed first
  • DeviceHQ config upload controls
  • OpenVPN Upgrade to v2.4.2
  • Certificate upload support
  • Bootloader login support
  • LoRa Network Server v2.1.5
  • Support for LoRaWAN Multicast
  • Support for LoRaWAN FUOTA
  • Combined LoRaWAN > Devices Configuration and Device Sessions
  • Added LoRaWAN menu items
    • Devices
    • Device Groups
    • Profiles
    • Operations

Bug Fixes

  • WAN fail-over dnsmasq now updates resolv.conf correctly
  • LoRa Network Server downlink queue allows delete through UI, lora-query and MQTT
  • Node-RED logs are not rotated
  • Packet forwarder manual mode maintained on upgrade from 1.4.3

Known Issues

  • GPS error when trying to enable Remote Management on non-GPS units. Workaround using API: https://192.168.2.1/api/remoteManagement?method=PUT&data={"accountKey":"<ACCOUNT-KEY>","enabled":true}

1.4.17 (07/16/2018)

Bug Fixes

  • Fix for watchdog when restarted by update from DeviceHQ – it should not monitor api, ppp, or lora
  • Fix for WAN manager to setup DNS resolve paths when interface changes are detected
  • Firewall – Apply custom user rules first

Known Issues

  • Packet forwarder manual mode is not maintained on upgrade from 1.4.3
  • 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.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 0x12 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 mPower 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 mPower 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 0x14 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.4 (09/29/2017, released for Conduit IP67 only)

Changes

  • LoRa Network Server updated to 1.0.41
  • Updates to radio-query and radio-cmd for support of new radios
  • Upgrade from mLinux 3.3.6 to mLinux 3.3.12, including MTCDTIP support (mLinux Changelog)

Bug Fixes

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 mPower 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 mPower 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!