MultiTech mDot¶

The MultiConnect® mDot™ offers significantly longer range and improved radio performance compared to traditional wireless solutions—resulting in greater transmission range and reduced capital expense. By leveraging LoRa™ technology, mDot simplifies local connectivity for Internet of Things (IoT) applications for the North American and European markets. By eliminating common deployment complexities, remote device connectivity is now simple and easy to deploy. With support for multiple interfaces, just about any thing can now be connected with MultiTech’s mDot technology.

AT Commands¶

• RESET - Reset the mDot CPU
• ATSEND <string> - Send the provided string data to the radio
• ATSENDI <interval> <string> - Send the provided string data to the radio on the specified interval
• ATRECV - Show the last 10 received packets

M2X Commands¶

The Conduit Gateways provide a link to the AT&T's M2X cloud through the following commands.

• Set feed-id - attach a m2x blueprint feed-id to the mDot-id to send stream data to
  • Both feed-id and m2x-key must be set, otherwise data will be sent to default m2x account
  • ATSEND feed-id:[new feed-id]
  • ex. ATSEND feed-id:fd7ddad4853749f2b4a86d5b70a6af0d
• Set m2x-key - attach a m2x blueprint m2x-key to the mDotid to send stream data to
  • Both feed-id and m2x-key must be set, otherwise data will be sent to default m2x account
  • ATSEND m2x-key:[new m2x-key]
  • ex. ATSEND m2x-key:39ddc135fa09721edd9aa8f141b2a9c0
• Set mDot alias
  • ATSEND alias:[new alias]
  • ex. ATSEND alias:first_floor_temp
• Subscribe to trigger stream
  • ATSEND subscribe:[stream name]
  • ex. ATSEND subscribe:temp-trigger
• Unsubscribe from a trigger stream
  • ATSEND unsubscribe:[stream-name]
  • ex. ATSEND unsubscribe:temp-trigger
• Update stream
  • Send data to a specified stream on M2X, mDot-id or alias will be prepended to stream name
  • Sending numerical values will create the M2X stream in the cloud on the fly.
  • If you want to post non-numerical data the stream must first be created in the cloud, however triggers can only be used with numerical data.
  • ATSEND [stream-name]:[stream-data]
  • ex. ATSEND temp:72

M2X Triggers¶

The MultiTech Conduit Gateway's can also send messages back down to the mDots. M2X triggers can be used to alert mDot's that a stream value has reached a certain threshold.

See AT&T M2X documentation about setting up triggers.

Configure the trigger to use the following callback url: http://54.174.33.191:3000/ This will forward the trigger message down to mDots that have subscribed to the trigger stream.

The following JSON object is an example M2X trigger post:

{
    "stream":"e2-test_trigger",
    "condition":"<",
    "threshold":1.0,
    "value":0.9,
    "timestamp":"2014-12-08T15:54:41.187Z",
    "device_id":"fd7ddad4853749f2b4a86d5b70a6af0d",
    "trigger":"TEST2"
}

The stream property will be used to as the stream-name to publish the message to.

To override the trigger stream-name use the callback url: http://54.174.33.191:3000/[trigger-stream-name] Be sure to provide a unique stream-name to avoid name collisions with other teams. Perhaps add your team name or some random value to the stream-name.