For IT & Facilities Teams

Advanced Network Configuration

For teams deploying Guardian on managed or enterprise networks. Setting up at home? You can skip this one.

IT & facilities
View Configuration → Talk To A Person
Before you begin

Start With The Basics

The essentials before you configure. Home installs almost never need anything on this page.

Guardian needs outbound internet to reach the Guardian platform and sync data.

Most home and small-business networks work with no extra setup.

Managed networks may need firewall, proxy, or outbound-traffic approval first.

Configuration

Set Up Guardian On A Managed Network

The steps IT and facilities teams most often need. Expand each as required.

If your network uses a firewall, proxy, or web-filtering appliance, Guardian needs outbound HTTPS access to the Guardian platform before it can transmit data. If Guardian appears connected to the network but isn’t reporting, review your organization’s outbound rules first.

Need the exact allowlist? Contact HomeCleanse and we’ll provide the current approved list of domains, ports, and protocols for your IT team.
By default, Guardian obtains its network settings automatically using DHCP. Only change this if your organization requires static addressing.
  1. Open Settings, Internet, Ethernet.
  2. Choose the Ethernet port in use.
  3. Change IP Mode from DHCP to Static.
  4. Enter your IP Address, Subnet Mask, Gateway, and DNS Server.
  1. Under Settings, Internet, Ethernet, review the IP Address, Gateway, DNS, and Connection Status.
  2. If those values are populated, Guardian has successfully joined your local network.

Guardian supports BACnet/IP and BACnet MS/TP for compatible Building Management Systems. Guardian also supports MODBUS (RS-485 and IP) and MQTT. Because configurations vary widely between installations, we recommend a qualified IT or facilities professional handle the integration. Loop in your IT administrator whenever your network involves firewall rules, ACLs, MAC or IP whitelisting, DNS configuration, port whitelisting, or restrictions on outbound traffic.

For BACnet configuration references, contact HomeCleanse and we’ll point your team to the right resources.

Environments like hospitals, universities, government facilities, corporate offices, and commercial buildings may need extra steps depending on your security policies.

  1. Approve outbound traffic for Guardian.
  2. Configure any required firewall rules.
  3. Assign static network settings if required.
  4. Verify internet connectivity from the device.
Good to know

Common Questions

Quick answers to the things people ask most.

Yes. Some corporate environments require additional firewall or network configuration before Guardian can communicate successfully.

Yes. Guardian supports both DHCP and manually assigned static IP configurations through the Ethernet settings menu.

Yes. Guardian supports both BACnet/IP and BACnet MS/TP integration for compatible building management systems.

If Guardian has joined the network but isn’t transmitting, review firewall rules, outbound-traffic permissions, and internet access with your IT administrator. Outbound restrictions are the most common cause in managed environments. Contact HomeCleanse for the approved allowlist.

Keep going

Related Guides

More of your Guardian library, one tap away.

All Troubleshooting

Every Guardian fix in one place, by problem.

Open guide

Wi-Fi Troubleshooting

Everyday wireless connection help.

Open guide

Ethernet Troubleshooting

Everyday wired connection help.

Open guide
Still stuck?

We’ll Take It From Here

Deploying Guardian on a managed or enterprise network and need a hand? Call or text HomeCleanse and we’ll work with you and your IT team to get it connected.

Call or text 727-263-4177 Back to Troubleshooting