Hi there! I see that your Fronius Solar.web Android app is showing 0% utilization, while the Apple app shows 100%. That's quite a difference! To help get this sorted out, can you tell me if you've tried any troubleshooting steps on the Android app so far, like clearing app cache or relinking your data? Also, is the Android device up to date with the latest version of the Fronius app?

In the meantime, here’s a step-by-step approach we can follow:

1. Clear Cache and Data on Android App
Go to your Android device's Settings > Apps > Fronius Solar.web > Storage, then clear the cache and app data. This refreshes stored information that could be causing the display issue.

2. Log Out and Log Back In
Sometimes simply logging out and back into your Fronius account on the Android app helps sync the utilization data correctly.

3. Check Connection and Permissions
Ensure the Android app has appropriate permissions (especially network and data usage). Also, verify the device has a stable internet connection.

4. Delink and Relink the Data Manager
Within the app settings, if available, try delinking and then relinking your data manager or PV system connection. This forces the app to retrieve fresh data from the server.

5. Verify Device and App Versions
Check that your Android app is updated to the latest version from the Google Play Store. Outdated versions can sometimes cause data display problems.

6. Check Inverter Visibility Settings
In some cases, the inverter visibility toggles (like an “eyeball” icon) control if utilization data is shown. Make sure it’s set to visible in the app or on the Solar.web portal.

If after these steps the Android app still shows 0 utilization, it might point to an app-specific bug or synchronization issue. In that case, reinstalling the app can help, or we may need to check the data manager connection on Fronius’s backend.

Would you like me to guide you through these steps? Also, let me know what model of Android device you’re using and the app version if possible!

This issue has come up for others as well and often clearing cache or relinking fixes it1 7.