Integrating Solis Data Loggers into Secure Networks: Communication Protocols, Server Configurations

The Solis Data Logger serves as a critical component in monitoring and remotely managing inverters by relaying data to SolisCloud. For high-security networks, like those managed by third-party entities (e.g., some municipal sites like school, government buildings), understanding and configuring network requirements is essential for enabling secure communication between the data logger and cloud servers. 

Below is a comprehensive guide to the communication protocol, server specifications, and configuration recommendations for integrating the Solis Data Logger into such networks.

1. Communication Protocol and Server Addressing

Protocol: The Solis Data Logger uses MQTT (Message Queuing Telemetry Transport) for efficient data transmission. This protocol is often used in IoT applications due to its lightweight design and secure data handling.

Server Domain and Ports:

• Primary Server: a55AEauzdn1.iot-as-mqtt.eu-central-1.aliyuncs.com on port 443/1883 for data upload/download commands.

• Firmware Server: oss.soliscloud.com on port 443 for firmware downloads.

• Recommendation: For added security, it’s recommended to whitelist all domains containing *.aliyuncs.com and *.soliscloud.com.

2. Security Recommendations for Secure Networks

• No Incoming Connections: Solis data loggers only initiate outgoing connections, making them suitable for networks that do not allow incoming traffic.

• Specific Server Whitelisting: If wildcard domains are not supported, add specific domains (like aliyuncs.com and soliscloud.com) to the whitelist manually.

3. Two-Way Communication and Port Requirements

• Port Usage: The primary communication operates through port 443 for secure HTTP connections (HTTPS) and 1883 for MQTT.

• Two-Way Communication for Modbus Commands: For installations that require real-time monitoring and parameter adjustments via MODBUS, bidirectional communication is necessary. This enables remote configuration changes and ensures seamless operation within restricted environments.

4. Configuration for Device Compatibility

• Firmware Updates: For firmware updates, the device connects to the dedicated server oss.soliscloud.com on port 443.

• Testing Addresses with Network Firewalls: It is advised to test all IP addresses associated with the data logger in the network’s firewall configuration to avoid disruptions in data flow.

5. Common Customer Concerns and Resolutions

• Data Transmission and Firewall Compliance: Customer inquiries often revolve around ensuring compatibility between Solis Data Loggers and their secure network infrastructure. Clarifying the device's exclusive use of outgoing communication and designated secure servers helps resolve these concerns.

• Network Approval: For approval processes with cybersecurity teams, providing detailed protocol information (MQTT, HTTPS) and port configurations ensures compliance and helps facilitate integration.

Conclusion

Integrating the Solis Data Logger into secure, highly regulated networks requires attention to specific server and protocol details. By following the configuration guidelines above, clients can achieve a secure, efficient setup for their data loggers, ensuring continuous data monitoring and reliable performance. For further assistance, please contact Solis Support at 866-438-8408.