If you see the following warning on the station output, then your CloudConnector is not connecting to the
Honeywell Sentience cloud platform.
Figure 19. Station output warning
To help with troubleshooting this, set the cloud.connector.http and cloud.connector.sentience log levels to FINE or a lower level (such as FINER, FINEST, ALL). Also, you may need to adjust some additional log levels
such as cloud.iotmsg.
The first step in the troubleshooting process is to confirm the device status with the
Honeywell Sentience Operations team. Once it is confirmed that the device is enabled, further diagnosis can proceed.
Figure 20. System disabled by
Honeywell Forge Operations
NOTE: In the above image, the authentication steps all return an HTTP 200 (see lines 3, 7, and 11 ), indicating success. The exception
occurs only when attempting to establish the IoTHub connection (see lines 32–40).
Solution
If this is happening, your device may be blocked (that is, throttled) by
Honeywell Sentience due to sending too much traffic at some point. If that is the case, you should have received an email from the
Honeywell Sentience Operations team indicating that the device has been blocked.
- If you did receive such an email, contact your
Honeywell Support channel to request that your device's ability to connect with
Honeywell Sentience be re-enabled.
- If you did not receive such an email, then there may be a problem with the email addresses on file for this system. You may
need to work with your
Honeywell Support channel to set the proper notification configurations.
NOTE: You should adjust your backfill protection settings, as described in “nCloudDriver-CloudHistoryDeviceExt” section of this
guide, under the heading “Cloud histories and restored connectivity”. If you do not have any backfill properties in your History
Device Extension, you need to upgrade to a newer version of NCHSD software.
