Troubleshooting

This topic explains the solutions to problems with the system, devices and configuration settings.

HUB

Symptom

Possible cause

Solution

When adding a device, the device is rejected or will not join.

The device may not be supported by the system.

Only use devices listed in List of Wiser Devices.

The device is not able to connect with the Hub. After pressing 3 times, the device LED blinks amber for 30 s.

Pairing mode has changed.

Press the Reset button on the device 3 times then hold for 20 s, until the LED blinks red. The device should reboot into the correct mode.

The hub is not communicating or receiving updates.

IPv4 is not enabled in the network settings.

Make sure that IPv4 is enabled in your local area network and Internet settings on your Internet provider’s router. Systems configured as IPv6-only will impact the hub’s ability to communicate and receive software updates.

The system cannot connect to the internet via the Wi-Fi® network router.

The router port settings may not be properly set for the system to access the internet.

Check that the following router ports are open:

Host	Protocol	Port	Description
hub.foundries.io	TCP	443	Docker container registry
hub-auth.foundries.io	TCP	443	Docker registry authentication service
storage.googleapis.com	TCP	443	OSTree and Docker redirects
api.foundries.io	TCP	443	If using lmp-device-register
app.foundries.io	TCP	443	If using lmp-device-register
cnm-ih-na.azure-devices.net	AMQP	5671	Hub to cloud connection
ota-lite.foundries.io	TCP	8443	Device gateway
ostree.foundries.io	TCP	8443	OSTree server for updates

If you face any issues in commissioning the device, refer to the troubleshooting section of the specific device user guide.

Refer to List of Wiser Devices for the links to Device user guide for each devices.