IoT Developer Kit Home Overview Accompanying Apps Data Sheet What's in the Box How to See Signs of Life Connecting to the T-Mobile LTE-M Network Interacting with the Kit at CLI via tmo_shell API Sample Requests Development Environment Setup macOS for Zephyr Development Windows OS for Zephyr Development Linux OS for Zephyr Development iOS for Mobile App Development Description of tmo_shell Source Files Upgrading the RS9116W Firmware Adding Certificates of Authority Ambient Light Sensor Sample Send a JSON Payload to AWS Add a Tone Troubleshooting FAQ Release Notes Errata Notice What is IoT?

Errata Notice

Home / Portfolio / Content / Technical Writing / IoT Developer Kit Home / Errata Notice

Overview

This documents current issues / limitations / restrictions for the T-Mobile DevEdge IoT Developer Kit. In addition, it may refer to features that will be offered sometime in the future.

Prerequisites

What are the ultimate goals of this document?

To give the reader an understanding of the restrictions, limitations, and issues as currently applicable to the T-Mobile DevEdge IoT Developer Kit.

Known Limitations / Issues

  • Currently, dragging and dropping files onto your DevEdge IoT Developer Kit does not work on a Windows 10 or Windows 11 machine. This is a known issue.
  • The T-Mobile CAT-M network currently does not support the PSM/eDRX features. As a result, the Developer Kits will not have the automatic Modem wake up capability, which consumes less power. The mitigation is to use Gecko alarms to periodically wake up the Modem manually, which would consume more power. T-Mobile is actively working to resolve this.
  • Currently, the Modem is awake, instead of asleep, by default.
  • The modem CLI and debug ports will not work on the Developer Kit, as they are disconnected.
  • Currently, there is no way to delete, or list, certificates once downloaded to the modem.
  • Currently, for the cell modem, DNS is not working while roaming is enabled.
  • SAMPLE versions of modem firmware cannot be updated to GOLDEN versions of firmware nor vice-versa.
  • Currently, the rate plan being used for the SIM cards that are in the DevEdge IoT Developer Kits do not support SMS messaging.

  • Currently, the Wi-Fi driver fails to restore to an "On" state after being turned "Off" via the Low Power Mode command; the workaround is to manually do a full board reboot (i.e. kernel reboot cold).

  • Currently certs are not overwritten for Wi-Fi; this is an issue with the RS9116W Wi-Fi Firmware (FW).
  • Currently, the location fixes outdoors for the GNSS driver are taking an extended period of time for some developer kits, and location fixes indoors are not supported.
  • GNSS FW updates should not be necessary and are not supported.
  • DevEdge Boards with RS9116 v2.6 firmware can be updated to the latest supported RS9116 v2.7 firmware, following the steps mentioned here. The WiseConnect 2.7 Release Notes page can be used as reference.
  • Running the command "sensor get trng@4001d000" in tmo_shell to retrieve sensor data may result in the console hanging indefinitely.
  • Running the command "sensor get <device name>" in tmo_shell to retrieve sensor data may result in the console outputting a USAGE FAULTerror message for some devices. This is being investigated. In the meantime, the workaround is to physically reboot the board.
  • The tmo_shell commands sendb and recvb are limited to 5KB.
  • Mobile app features have been tested and work fine in iOS. They are yet to be fully tested on Android.