Firewall Ports and Adresses

through which ports does clemap load management communicate? the edge device connects to adress/service ip range port description direction required/optional communication encrypted dns udp/tcp 53 dns domain name system translate human friendly domain names into ip addresses outbound required no mqtt cloud clemap com 35 157 95 169 tcp 8883 tcp 3032 standard comunication with clemap main mqtt broker communication enchrypted, mqtt over ssl outbound required yes bitbucket org 104 192 136 0/21 185 166 140 0/22 18 205 93 0/25 18 234 32 128/25 13 52 5 0/25 tcp 22 firmware updates are downloaded from this address communication encrypted via ssh outbound required yes ntp org udp 123 ntp network time protocol time server used to synchronize the time on clemap devices ntp is essential for ensuring accurate and consistent timekeeping across a network, as it enables clemap devices to maintain a common time reference outbound required no https //s2 cloud clemap com/ 18 184 141 52 tcp 3024 tcp 3080 remote access to devices with ssh outbound optional yes https //b2 cloud clemap com 18 184 141 52 tcp 8883 comunication with clemap monitoring mqtt broker communication enchrypted, mqtt over ssl outbound required yes local local ip of child clm tcp 7000 used for communication between cascading parent and child devices local optional yes/depends on configuration https //api zaptec com tcp 443 control of zaptec charging stations via zaptec cloud (for clemap load management) outbound optional yes https //api easee com tcp 443 control of easee charging stations via easee cloud (for clemap load management) outbound optional yes https //api smart me com tcp 443 control of pico smart me charging stations via smart me cloud (for clemap load management) outbound optional yes