storagefaults.comstoragefaults.com

SolarEdge•Unknown

Analysis by Marcus & Team

SolarEdge - Backup Configuration Not Saved - Troubleshooting

Troubleshoot SolarEdge 'Backup Configuration Not Saved' error. Focus on network settings, cloud sync, and firmware updates to restore system backup functionality.

Frequently Asked Questions

•How do I check the internet connection status of my SolarEdge Gateway?

The internet connection status is typically displayed in the SolarEdge monitoring app under the 'Communication' or 'Network' settings. You may also be able to view this information through the SolarEdge web portal.

•What are the recommended firewall settings for SolarEdge Gateway communication?

Ensure that outbound traffic to SolarEdge cloud servers is allowed on ports 80 and 443. Consult the SolarEdge documentation for a complete list of required ports and IP addresses.

•How often should I update the firmware on my SolarEdge Gateway?

It is recommended to update the firmware whenever a new version is released by SolarEdge. Firmware updates often include bug fixes, performance improvements, and security enhancements.

Related questions

Loading related questions...

Marcus leads the technical research department at Storage Faults. Together with a team of systems analysts, he specializes in translating complex solar storage error codes into actionable diagnostic steps for the US market.

← Back to list

Technical Overview:

The SolarEdge Gateway relies on consistent data synchronization between the local device, connected energy storage components, and the SolarEdge cloud. Configuration data, including inverter settings, battery parameters (charge limits, discharge rates, SOC), and grid profiles, are stored locally and backed up to the cloud. Loss of network connectivity or firmware issues can interrupt this backup process, leading to the 'Backup Configuration Not Saved' error. The system communicates via Modbus TCP/IP or similar protocols, and relies on API endpoints to sync data.

Technical Recommendation:

Check the SolarEdge Gateway's event log in the monitoring portal for specific error messages related to configuration backup failures. This log may provide more detailed information about the root cause of the issue and guide further troubleshooting steps. Filter the log by severity (error, warning) and time period.

Important Warnings:

Ensure the DC disconnect switch is in the OFF position prior to performing any network or configuration changes. Incorrect configuration can affect the system's safety and performance. Always use strong passwords and enable two-factor authentication for the SolarEdge monitoring portal and app to prevent unauthorized access to system settings. Regularly review user access permissions.

Recommended Action:

1

Verify the SolarEdge Gateway's internet connection status in the monitoring app or web portal. Check the Wi-Fi signal strength or ethernet connection.
2

Restart the SolarEdge Gateway using the remote restart function in the monitoring app. Allow sufficient time for the system to reboot and attempt to back up the configuration.
3

Check the SolarEdge monitoring portal for any alerts related to network connectivity or cloud service outages.
4

Update the SolarEdge Gateway firmware to the latest version via the monitoring app or web portal. Ensure a stable internet connection during the update process.
5

Review the Gateway's network configuration settings in the monitoring app to ensure proper DNS settings and firewall exceptions for SolarEdge cloud servers.
6

Perform a factory reset of the SolarEdge Gateway via the app (if available) as a last resort, noting that this will erase all existing configurations. After the reset, reconfigure the system and verify successful backup.
7

Contact SolarEdge support if the issue persists after following the above steps. Provide detailed information about the system configuration and troubleshooting steps taken.

Common Causes:

Intermittent or unstable Wi-Fi or ethernet connection to the SolarEdge Gateway.
Firewall settings blocking outbound communication from the Gateway to the SolarEdge cloud servers.
Outdated firmware on the SolarEdge Gateway preventing successful configuration backup.
Corrupted configuration file on the Gateway due to unexpected power interruption or software glitch.
Insufficient storage space allocated for configuration backups on the Gateway.
Cloud service outage affecting the SolarEdge server's ability to receive configuration data.

What to Look For:

The SolarEdge monitoring portal displays an error message indicating that the system's backup configuration was not saved. This may lead to loss of system settings upon device reset or failure.

Preventative Care:

Schedule regular firmware updates for the SolarEdge Gateway through the monitoring app or web portal
Routinely check the Gateway's network connection status and ensure a stable internet connection
Review cloud sync status periodically in the app settings
Backup the Gateway configuration manually (if option available) before major system changes