How to network your device
When bringing your safe online, its a good practice to review the LED on the device to understand the current state and potential adjustments that need to be made. If you encounter connectivity issues, the light indicators will flash rapidly for a period of time, followed by a slow, specific number of times. To diagnose the issue, please see the steps below for troubleshooting and resolutions.
Troubleshooting & Resolutions
Light Color | Resolution |
1 Long Red Flash
2 Long Red Flashes
3 Long Red Flashes
|
These errors are typically related to localized elements from network setup. Resolution will need to be an evaluation of the network for the device or the connection itself. Some potential troubleshooting steps are:
Note: Our device can only negotiate at 10-base-T or 100-base-T.
|
4 Long Red Flashes Unable to complete device provisioning (X509) |
This typically means that the MAC address has not been entered correctly. You can find the MAC address on the Device Management page by selecting a device and choosing ‘Settings’. A possible resolution is:
All of these commands should return “true”. They can be run on Windows Powershell and can be run if there are any suspected firewall issues. Test-NetConnection – ComputerNamefirmware.app.bioconnect.com -Port 443 -InformationLevel QuietTest-NetConnection –
|
5 Long Red Flashes Unable to connect to MQTT server |
This would typically be a firewall issue that is preventing access to our cloud server. A possible resolution is:
Test-NetConnection –
|
6 Long Red Flashes Unable to log into MQTT server |
This would typically indicate a server error. If the safe has been added correctly into the Link Admin Console, and all required ports have been checked for outbound traffic, please contact MedixSafe support. |
MedixSafe Link Required Port
Below are the port requirements to ensure that your MedixSafe Link device can function properly. Please ensure that your network team is made aware prior to the installation of the device(s).
Note: Our device can only negotiate at 10-base-T or 100-base-T.
Protocol | Port | Direction | Description |
DHCP | 67/UDP 68/UDP |
Out (67) In (68) |
Devices use DHCP to obtain their IP address on the local network, and only IPv4 is supported at this time. |
DNS | 53/UDP | Out |
Domain Name Service: Used to resolve hostnames. Network dependent. Default DNS Entries are 8.8.8.8 and 8.8.8.4 |
NTP | 123/UDP | Out |
Network Time Protocol used to obtain current time of day. Required for validating server certificates and logging. Host: pool.ntp.org & time.windows.com. |
HA Device Message System | 8883/TCP | Out | TLS 1.2, MQTTS. Encrypted Connection: user enrolment, authentication, authorization, device configuration. Host: bossywolf.mq.app.bioconnect.com |
Azure DPS | 8883/TCP | Out | Used for device provisioning (TLS-Secured) Host: global.azure-devices-provisioning.net |
Azure IOT | 8883/TCP | Out | Used for Logging (TLS-Secured) Host: BioConnect-IoT-DPS.azure-devices-provisioning.net & BioConnect-IoT-EastUS.azure-devices.net |
OTA Upgrade | 443/TCP | Out | Used for downloading Over-The-Air firmware updates (TLS-Secured) - Host: firmware.app.bioconnect.com |
Activation Server | 443/TCP | Out | Used for initial device activation (initial config parameters and signing of x509 certificates) - Host: apiprod.app.bioconnect.com |

How to Network your Device
Step by Step instructions on how to Network your MedixSafe Link Device
Download