Skip to main content

[Networking] Preparing Your Network for Plugzio EV Charging Devices

A Technical Guide for Property IT Administrators

Updated over 2 weeks ago

Goal

This article outlines the recommended network preparation steps before installing Plugzio EV charging devices. Plugzio devices can connect via Wi‑Fi or Ethernet, and both connection types benefit from proper planning to ensure stable, long‑term operation.

1. Overview of Plugzio Network Requirements

Plugzio devices are low‑bandwidth IoT clients that communicate outbound to the Plugzio Cloud. They do not broadcast their own SSID, do not run DHCP, and do not accept inbound connections. They require:

  • Reliable IP assignment via DHCP

  • Stable outbound internet access

  • DNS resolution

  • HTTPS (TCP 443) outbound connectivity

Plugzio devices are certified to UL standards, meeting industry safety and electrical compliance requirements.

2. Preparing for Wi‑Fi Connected Plugzio Devices

2.1 Validate Wi‑Fi Coverage at Installation Points

EV chargers are often installed in areas with challenging RF conditions. Before installation:

  • Confirm RSSI of –65 dBm or better at each stall.

  • Ensure network is only on 2.4 GHz (No 5Ghz, or 2.4 + 5Ghz combination).

  • Check for channel congestion or interference.

  • Avoid daisy‑chained Wi‑Fi extenders or network switches.

  • Ensure APs/extenders are not overloaded with clients.

Weak Wi‑Fi is the most common cause of intermittent device connectivity.

2.2 Create a Dedicated SSID (Recommended)

A separate SSID for IoT/EV devices improves reliability and security. Recommended configuration:

  • Security: WPA2‑Personal

  • Encryption: AES/TKIP

  • Frequency: 2.4 GHz only

  • Wi‑Fi Type: 802.11 b/g/n

The network must:

  • Not use MAC filtering or MAC whitelisting

  • Not require guest login, captive portals, or TOS acceptance

  • Be discoverable (no hidden SSIDs)

  • Use simple SSID names (no spaces or special characters)

2.2.3 Plugzio Default Network

All Plugzio devices can connect to the following default network:

  • SSID: Plugzio

  • Password: WelcomePlugzio

This network is intended only for testing to verify compatibility. It should not be used as a permanent production network because the credentials are publicly available.

Once devices are online, you can assign a custom SSID and password through your Plugzio management dashboard.

Plugzio can also generate a custom secure Plugzio network for large‑scale deployments. Contact Plugzio Support for details.

2.3 VLAN Segmentation

If your network supports VLANs:

  • Assign Plugzio devices to a dedicated VLAN.

  • Reduce broadcast traffic and simplify troubleshooting.

  • Apply firewall rules specific to IoT devices.

3. Preparing for Ethernet‑Connected Plugzio Devices

Ethernet is the most stable and preferred connection method when available.

3.1 Confirm Physical Cabling

  • Use Cat5e or better cabling.

  • Ensure cable runs are properly terminated and tested.

  • Avoid unmanaged switches in outdoor or exposed environments unless rated for it.

  • Total cable length must be <300 ft (100 m) end‑to‑end.

3.2 Verify Switch Configuration

  • Enable DHCP on the target VLAN or subnet.

  • Set the switch port to access mode, not trunk mode.

  • Disable port security features that may block new MAC addresses unless intentionally configured.

3.3 Power and Surge Considerations

  • If using PoE, confirm the switch meets the required power budget.

  • For non‑PoE devices, ensure outlets are properly grounded and surge‑protected.

3.4 VLAN Segmentation for Ethernet

If segmenting:

  • Assign the switch port to the designated IoT/EV VLAN.

  • Apply the same firewall rules used for Wi‑Fi devices.

4. DHCP and IP Addressing Requirements

Plugzio devices rely on consistent DHCP behavior. Before installation:

  • Ensure the DHCP scope has at least 20% free leases.

  • Set lease times to 12–24 hours.

  • Confirm there are no rogue DHCP servers.

  • Avoid overlapping subnets or double‑NAT environments.

DHCP instability is a common cause of devices appearing “offline.”

Did this answer your question?