The station does not know it is registered

Once the Device Registration widget on the station hyperlinks you to the remote Device Registration web service, the registration process occurs on the remote site, not in the station. The station knows nothing about the subsequent steps in that process.

So, when you register the device's Host Id with the Asset Manager, and device’s System Id with the Niagara Cloud Honeywell Sentience Driver Identity Provider, the station is unaware of this.

The only process occurring in the station is the RPK Authentication, and that occurs only once the Honeywell Sentience registration process completes. Once that is true, the RPK Authentication process can succeed. The station will obtain the correct Registration status from Honeywell Sentience, and establish connection to the IoTHub.

Proxy server preventing connection

If you are able to register the station with Honeywell Sentience and Niagara Cloud, but the station cannot connect (the connector's Connection State never gets to "Connected"), then there may be a problem with the local IT network's proxy settings, or with the firewall settings imposed upon the station.

If network settings prevent the station from connecting properly, the station will remain in the Unregistered state, even if it is registered. If you have gotten the successful registration notification (shown ) your device's System Id is successfully registered with Honeywell Sentience and Niagara Cloud. If the device's Cloud Connector is still showing Unregistered, it is most likely because it cannot reach the authentication endpoint.

Figure 26.   Successfully registered message

If the station output shows messages similar to the following, then your station may be behind a named (explicit) proxy server. This configuration is not supported prior to Niagara 4.9.

Figure 27.   Station output for station behind named proxy server

Solution

Review with your IT administrator the section "Setting up device internet access" in the “Getting Started” section of this guide, specifically regarding firewall access and unauthenticated transparent proxy access. This is a common problem with network setup, especially in a heavily restricted corporate or educational network. Ensure that the requirements in this section are met by the IT network configuration. Note that the transparent proxy requirement was added only in very recent versions of the documentation, so it may not be present in the documentation delivered with the software. For the most up-to-date version of the documentation, visit https://docs.niagara-community.com/.

If your network is using a proxy server, you may be able to find success by including the following lines into your system.propertes file, usually found in /opt/niagara on JACE controllers. Use the File Transfer Client to retrieve the file from the JACE to your Workbench and add the lines in a text editor, then copy the modified system.propertes file back to the JACE using the File Transfer Client. You should also apply the same changes to the system.properties file on your Workbench, if it is also subject to the same proxy server, as the Workbench will be used in registering the device.

Figure 28.   Proxy settings

If your local network is using a named proxy server, you will need to work with your network administrator to obtain transparent proxy server access.

AMQPS Blocked

If you're using AMQPS as your Transport setting, you've registered your CloudConnector, and you're seeing the connector status stuck in "Pending Connect", it may be because AMQPS is blocked on your network.

Figure 29.   CloudConnector properties for AMQPS blocked

This can be confirmed by looking at the station output (as a connection problem, having the cloud.connector, cloud.connector.http, and cloud.connector.sentience logs set to ALL will help here.)

Figure 30.   Station output for AMQPS blocked

Solution

If this is the case, your network is blocking AMQPS traffic. For a rapid solution, you can switch to AMQPS over WebSocket by changing the setting in the Cloud Connector > Connector Impl > Message Client > Transport. If you really want to use AMQPS, you can try working with your IT administration to modify the network settings to allow this protocol.

For most of the Honeywellnetworks, AMQPS is blocked by default. So, any device on the Honeywell corporate network (or our various internal test networks) will need to use AMQPS over WebSocket.