Selecting Devices results in Quota Exceeded Error

[wecoyote5]

Describe the bug

When selecting the Devices tab an error is created.

To Reproduce

Select Devices from the side menu. Following the instructions, here is the bug report.

Zig2MQTT report state.json.zip

Expected behavior

No response

Affected browsers

Firefox

Stacktrace

[mmstano]

I was getting this error, too. I use Chrome browser. I went to chrome://settings/content/all and deleted all site data for my HA URL. This will force you to re-login in the browser. But it successfully removed the QuotaExceeded Error and I can access windfront again.

[Nerivec]

@mmstano do you have a lot of custom HA extensions?
The browser has a limit, per domain, to its local storage space; seems some extensions might be storing way too much data in there.
It's typically 5MB, which is more than enough for its typical uses of just storing some key/values, barely reaching a few KB in most cases (WindFront alone should be something like 5-10KB).
But if something starts storing images & whatnot (instead of using more appropriate storage options), it can quickly fill up. And since HA has everything under the same domain, that adds up too.

[mmstano]

@Nerivec Well... I definitely have quite a few, lol. The error occurred on my local URL for HA. If I encounter it again, I'll be more cognizant and I'll test it against my external URL. The real strange thing to me is that WindFront log error was reporting this key "home-show-activity-key", so I went into the Chrome Developer Console to check and "home-show-activity-key" was nowhere to be found, but there was a key for "home-show-overview-key". Deleting it had no effect, which is why opted to delete the site-data to see what'll happen.

[wecoyote5]

Thanks, I'll give that a try.

[Nerivec]

home-show-activity-key is just a true or false value to show or hide the recent activity on the home page.
The key itself is irrelevant though, since this happens whenever a "store" operation would exceed the limit (also explains why you didn't see it - it wasn't able to store it).

You can probably tell quite quickly if something is filling it up, just look at the browser's dev console local storage now that you've cleared it, and see if you find any utterly long strings stored in there. If I had to guess, I'd say it's probably images in base64 or possibly whole JSON objects. Should be able to tie it to specific extensions, and report the issue there (should use indexeddb or something like that for larger stuff).

---

Note that you can do the hard refresh operation on currently opened page by holding SHIFT or CTRL or both and pressing the browser's refresh/reload button.