Page tree
Skip to end of metadata
Go to start of metadata
 When does the IoT Platform detect that my thing is disconnected?
  1. When a directly connected thing disconnects (TR50 stop), a packet is sent indicating the disconnect and the connection loss is immediately known.
  2. When a directly connected thing disconnects because of a network event, a FIN or RST packet is received and the connection loss is immediately known.
  3. When a directly connected thing disconnects because it is powered off, no packets are sent, and the connection loss will be determined based on the Time To Live (TTL) of the underlying communication session. For MQTT connections, this is twice the heartbeat interval, thus a 60 second heartbeat interval would show disconnected after 120 seconds. For HTTP sessions, the expiration can vary from several hours up to one day.
  4. For bound things, the state is updated based on the directly connected thing it is bound to, thus when the directly connected parent thing disconnects, the bound thing will immediately reflect the changes.
    For more information, see Things.
 I see the message "appId mis-match, possible device hi-jacking." what does it mean?
  1. When a device authenticates with an application token, an appId is specified during authentication.  This value is stored along with the thing, and subsequent connections must re-use this appId.
  2.  When authenticating via HTTP(S) the HTTP the appId is specified during authentication.
  3. When authenticating via MQTT, the appId is mapped to the MQTT Client_ID field.
  4. If a client connects using a particular thing key, and the appId changes, the authentication will fail, and you will see the message "appId mis-match, possible device hi-jacking." in the event logs for the thing.
  5. This error can mean that a malicious user is attempting to "hi-jack" or duplicate the device without permission.  If this is not the case, you can reset the appId in the Portal by clicking the unlock button on the thing's details page. Unlocking the appId will allow an application to reconnect and set the new appId.
    For more information, see Things View, Overview tab.
  6.   If you have 2 applications attempting to connect with the same thing key, then one will be allowed to connect and the other will receive a similar "appId mis-match" error.
 My deviceWISE Gateway shows in the Management Portal, but the "Gateway" tab is missing, how do I fix it?
  1. This issue occurs when you delete the Thing associated with a deviceWISE Gateway.  The gateway will disconnect and will reconnect, but will not re-register itself as a gateway until it is restarted.
  2. To force a gateway that is connected, but missing the gateway tab to re-register, you can do the following:
    1. Log into the Management Portal.
    2. Navigate to the API Tester in the Developer section (requires rights as an organization administrator).
    3. Execute the following command:


    4. Navigate to your Thing, and see if the Gateway tab has re-appeared.
 How to open CSV to Excel?

 CSV (comma separated values) is a common format used in the Management Portal to download a list of rows or records. The following section explains how to open a CSV file in excel:

  1. Open a new Excel workbook.

  2. On the Data tab, in the Data Tools group, click From Text.


  3. Select the CSV file you want to open.
  4. Click Import.
    Text Import Wizard - Step 1 of 3 appears.


  5. Select Delimited.


  6. Click Next.
    Text Import Wizard - Step 2 of 3
    appears.

  7. Select Comma


  8. Click Next.
    Text Import Wizard - Step 3 of 3 appears.

  9. Select the columns with numbers and change the Column data format from General to Text


  10. Click Finish.



  • No labels