What
To ensure stable communication, Nobi lights need access to specific internet ports. These firewall settings make sure the light can send and receive essential data.
Why
Nobi lights rely entirely on their network connection to detect falls, trigger alerts, and receive software updates. If the required ports are blocked, communication with the cloud, time synchronization, or even audio calls may fail.
Requirements
For uninterrupted performance, these firewall ports must be open:
# Cloud connection
-
*.nobi.cloudandnobi.cloud: port 443 (TCP) -
*.nobi.cloud: port 5671 (TCP)
# NTP (time sync)
-
time1.google.com,time2.google.com,time3.google.com,time4.google.com: port 123 (UDP)
# Debugging
-
*.nobi.cloud: port 2222 (TCP)
# SIP signalling
-
nobi.sip.us1.twilio.com: port 5060 (TCP + UDP) -
nobi.sip.us1.twilio.com: port 5061 (TCP)
# SIP media
-
168.86.128.0/18: port range 10,000–60,000 (UDP)
# Software updates
-
hosted.mender.io: port 443 (TCP) -
s3.amazonaws.com: port 443 (TCP) -
c271964d41749feb10da762816c952ee.r2.cloudflarestorage.com: port 443 (TCP)
For the firewall ports the following should be added:
sentry.io port 443
*.sentry.io port 443
DHCP needs to be active on the Wifi network. Nobi lights always gets their IP address via DHCP. If required, fixed IP addresses can be given via DHCP reservation.
Without these settings, Nobi may not function as expected—alerts could be delayed, updates might fail, or the light may lose cloud connection.
Troubleshooting
-
Make sure no login or proxy stands in the way of a direct internet connection
-
Run a firewall check if your light doesn’t seem to connect or update correctly
-
Want to learn more about WiFi setup? → Check our WiFi requirements article
Solid connectivity = reliable care. Keep the network clear, and Nobi will do the rest.