Serach Icon

    Xovis — network & firewall requirements

    This article documents the official Xovis firewall and network requirements for sensors running Firmware 5.x (current) and Firmware 3.x/4.x (legacy). Source: Xovis Knowledge Base.

    Firmware 5.x — Required outbound connections (sensor → internet)

    All connections are outbound only from the sensor. No inbound ports need to be opened.

    Port

    Protocol

    Destination

    Purpose

    443 TCP

    HTTPS

    *.xovis.cloud / *.xovis.com

    HUB Device Control — whitelist with wildcards (Xovis Cloud IPs are dynamic)

    443 TCP

    HTTPS

    remotesupport.xovis.com (185.187.120.162)

    Xovis remote support

    443 TCP

    HTTPS

    iot.xovis.com (185.187.120.166)

    Update service & licensing — mandatory

    443 TCP

    HTTPS

    pip.xovis.com (185.187.120.6)

    Product Improvement Program (optional)

    123 UDP

    NTP

    Time server

    Time synchronisation — sensors can also act as NTP server

    Firmware 5.x — Optional local network connections

    5365 UDP

    Client → Sensor

    Sensor discovery scan within same network

    443 TCP (HTTPS)

    Client → Sensor

    WebUI, REST API, Sensor Explorer — recommended

    80 TCP (HTTP)

    Client → Sensor

    WebUI, REST API (not recommended — unencrypted)

    Any TCP

    Parent → Child sensor

    Multisensor parent-child connection (HTTPS)

    Firmware 3.x / 4.x — Required connections (legacy sensors)

    Firmware 3.x/4.x sensor-support.xovis.com endpoint reaches end of support 31 July 2026. Update sensors to FW5 before this date.

    443 TCP

    sensor-support.xovis.com (185.187.121.9)

    Sensor support — EOS Jul 31, 2026

    443 TCP

    IBEX server

    Remote management

    443 TCP

    licserver.xovis.com/sensor/plugin/issue (185.187.120.6)

    License server — mandatory for recurring licences

    123 UDP

    Time server

    NTP — note: local Microsoft timeserver does NOT work

    Data usage reference

    Bandwidth (ideal)

    > 200 KB/s (4 fps in live view)

    Bandwidth (minimum)

    100 KB/s (limited live view fps)

    Data transmission (no WebUI)

    < 20 KB/s

    HUB heartbeat

    ~3.54 MB/month per sensor (every 2 min, 168 bytes)

    NTP sync

    0.2–4 MB/month

    IoT/licensing/update check

    ~15 MB/month (once per day)

    Live data push (1 min interval)

    ~19 MB/month per sensor

    Power consumption

    PC2SE

    max. 7.5W

    ~6.57 CHF/year (at 0.10 CHF/kWh)

    PC2RE

    max. 8W

    ~7.01 CHF/year

    PC3SE

    max. 7.5W

    ~6.57 CHF/year

    PF

    max. 15.4W

    ~13.49 CHF/year

    For the Vemcount-specific firewall requirements (data push to Vemcount servers), see the Vemcount firewall guidelines. Both the Xovis requirements above AND the Vemcount requirements must be met for full functionality.

    clock

    7PM

    GMT+2

    clock

    7PM

    GMT+2

    clock

    7PM

    GMT+2

    Company-with-Circle-BG

    Who We Are

    Aliquam Dui Diam, Tincidunt Eget Nulla Eget, Dictum Feugiat Felis. Cras Mattis Eget Tellus Quis Fringilla. Morbi Molestie Enim

    Aliquam dui diam tincidunt eget nulla eget dictum feugiat felis.

    Sed dictum ligula luctus intum Vivamus.

    Lorem ipsum dolor

    Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.

    Lorem ipsum dolor

    Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.

    Lorem ipsum dolor

    Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.

    Lorem ipsum dolor

    Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.

    Lorem ipsum dolor

    Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.

    Lorem ipsum dolor

    Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.

    Become Our Supplier Or Partner

    Mauris tempor libero massa, at vulputate velit aliquet eget. Fusce et tortor ex. Nullam venenatis, quam vel blandit molestie.

    Banner