Grafana and rendering issues

Overview

Most display problems with SolarAssistant are caused by cached files on the device you are viewing from, not by a fault on your SolarAssistant device. Your browser stores a copy of the dashboard files to load pages faster, and after a software update it can keep serving the old copies. Clearing the cache resolves the majority of these reports.

Symptoms

You are most likely affected if you see any of the following:

  • Charts or Grafana panels stay blank, or never finish loading.
  • The page layout looks broken, unstyled, or overlaps itself.
  • You still see the previous version of a page after updating SolarAssistant.
  • The dashboard works correctly on one device or browser but not on another.

Step 1 - Reload the page

Start with a forced reload, which tells the browser to fetch the files again instead of using its stored copies. Press Ctrl + F5 on Windows, or Cmd + Shift + R on a Mac. On a phone or tablet, close the tab completely and open the dashboard again.

Step 2 - Confirm it is a caching issue

Open the dashboard in a private or incognito window. These windows do not use your stored files, so if the dashboard displays correctly there, the problem is your cache and clearing it will resolve it.

Step 3 - Clear your browser cache

Each browser handles this differently. Follow the guide for the browser you are using. You only need to clear cached images and files; you do not need to clear your saved passwords.

If your browser is not listed, look for Clear browsing data or Clear cache in its settings. Browsers built on Chromium, such as Brave and Vivaldi, follow the same steps as Google Chrome.

Step 4 - Restart the browser

Close the browser completely and open it again, then load the dashboard. Some browsers keep files in memory until they are restarted, so the cache is not fully cleared until you do this.

Still having trouble?

If the dashboard still does not display correctly after clearing the cache, try a different browser or another device to narrow down where the problem is. If the issue persists, please report the issue and include which browser and device you are using, along with a screenshot of what you are seeing.