- 4G LTE-M1
- WiFi 2.4GHz, IEEE 802.11 b / g / n (static channels 1 to 11)
Minimum signal strength per charging station: –75 dBm
- Powerline (PLC) – HomePlug Green PHY®, 10 Mbit/s
DHCP server with a sufficient number of IP addresses – one for every device connected
The anticipated data traffic for every Zaptec Pro is around 3 MB a day.
All traffic and communication between the charging stations and the cloud solution is encrypted. All the following network services are required to allow Zaptec Pro to work together with Zaptec Portal. All the ports stated are outgoing ports, and you have to open them in active firewalls. Zaptec Pro links to the necessary services without opening incoming ports, even if they are located behind a NAT.
TCP port 8883: zapcloud.azure-devices.net
A connection to Azure IoT Hub, which uses MQTT over TLS, acts as a primary communication channel between Zaptec Pro and Zaptec Portal. The condition of the charger is transmitted to Zaptec Portal, and it receives control commands such as start/ stop charging. Communication is encrypted using TLS v1.2, and the server certificate is verified by Zaptec Pro. When it is connected, the server verifies the charger by means of a unique password that is generated during production. More information on Azure IoT Hub can be found here: https://docs.microsoft.com/en-us/azure/iot-hub/about-iot-hub
TCP port 443 (multiple domains)
Zaptec Pro connects to Zaptec Portal by means of HTTPS in order to download firmware updates. This communication is encrypted. Zaptec Pro verifies the server certificate before the update is download, and the firmware update itself is verified cryptographically before being installed.
The following domains are used during firmware updates:
UDP port 68
DHCP is used on the local network to assign an IP address to Zaptec Pro and give the IP address to the DNS server.
UDP port 53
Zaptec Pro uses DNS look up the IP addresses of the domains used to communicate Zaptec Portal.
If the DHCP server does not specify a DNS server, or if it does not respond promptly, Zaptec Pro uses the DNS server (or DNS servers) specified by the DHCP server, in addition to Google (184.108.40.206) and Cloudflare (220.127.116.11) DNS servers.
UDP-port 123: no.pool.ntp.org
If the Zaptec Pro real-time clock is wrong, the charging station cannot authenticate itself with Zaptec Portal. Zaptec Pro has to be connected to an NTP server so that the internal clock can be updated. This communication takes place via UDP port 123.
The NTP server used by Zaptec Pro is no.pool.ntp.org.
The hostname used for NTP is static. It cannot be changed by the user at present.