Connector is not registered

If your station output appears as shown:

The HTTP 404 "Not Found" response in the station output shows that the Honeywell Sentience Identity Provider does not have a record of this system.

And, if your CloudConnector properties appear as shown here:

Of course, this indicates that the CloudConnector is not registered.

Solution

Register the device with Niagara Cloud and Honeywell Sentience by opening the Device Registration view of the CloudConnector. Click Register Device, and follow the on-screen prompts as described in the “Install and configure” section of this guide, under the heading “Registering the device”.

 

Connector keys are lost

This applies to all non-QNX stations, and to JACE-8000 hosts running Niagara 4.4. Controllers running Niagara 4.6 or later should use hardware encryption, unless the CloudConnector was originally registered under Niagara 4.4 or earlier.

If your station output appears as shown here:

And, your CloudConnector properties appear as shown here:

This indicates that the station is registered with Honeywell Sentience, but it cannot authenticate. Most likely your station does not have the required public/private key pair necessary to authenticate to Honeywell Sentience. You can confirm this by checking the Certificate Manager for a key with an alias matching the station name (note the alias will be all lowercase, with hyphens replacing any underscores in the station name). If you do not see the alias for your station, then your station cannot register because it does not have the necessary key pair.

Solution

If you have saved the keys using the steps described in the  ”Upgrading a Host” section, you can try importing the key back into your User Key Store in the Certificate Manager. If the file contains the correct keys, the CloudConnector should be able to reconnect successfully.

Otherwise, you will need to deregister your system with Honeywell Sentience and re-register it. This currently requires you to contact your Support channel, and request that they de-registering your system.

 

Connector does not attempt connection

If you have registered your CloudConnector and received the following successfully registered notification, but your CloudConnector does not attempt to connect at all (i.e., there is no "Connecting to Sentience" message in the station output, when you have cloud.connector.sentience log set to ALL).

This problem may be more likely to occur if the System Type field had to be manually entered because the CloudConnector was added from the cloudSentienceConnector palette instead of from one of the branded palettes.

Solution

Try disabling the CloudConnector, and then re-enabling it.