Insights Timeout after 10000ms

Questions & Help
1

All Insights graphs on my Homey Pro (2026) “Timeout after 10000ms”.
Rebooting the Homey Pro will fix it for a short while before breaking again.
I think that it has always behaved this way (for the couple of weeks that I have had it).

2

Can’t relate. Pro 2026 & SHS as H.A. add-on show any insight graph I choose.

Do you use any network tool, like AdGuard, PiHole?

3

Yes.
I have Ubiquiti’s Unifi CyberSecure Ad Block on for the Homey’s network.
Removing that immediately fixes the problem.
Thanks!

I am curious, however.
What “ad” sites (says my blocker) does Homey Insights require access to draw a graph?

1 Like
4

Ah, nice to hear!
Yeah the “what would I need to allow…” stuff can be discovered.

What you can do:
on the insights page, open the browser console, and open tab “Resources” and “Sources”.
Here you can see the used resources;
From what I can see, you’ll need to allow fonts.googleapis.com as it’s part of the stylesheet.

639
6391200×1753 179 KB

For Android Firefox, I use “Mobile DevTools” extension, which makes an excellent console.

(I use AdGuard myself, and sometimes stuff doesn’t work (like Google Home automations for example), AND at the same time it doesn’t show anything new being blocked.
Probably it needs a few Ggl trackers I dislike to be enabled)

5

I would use the Network tab for this, it allows you to see exactly which network requests failed

6

I see nothing related in my Chrome browser’s Network log.
I was hoping that I would as that would point a point a finger at a blackholed domain.

I do see a lot of this in the console.

useFetchEntries.js:74 LSe: Timeout after 10000ms
at zSe.timeout (Util.js:93:26)
at ug.__request (Manager.js:277:27)
at ug.value (Manager.js:203:38)
at ug.getLogEntries (ManagerInsights.js:14:17)
at useFetchEntries.js:25:29
at Array.map ()
at useFetchEntries.js:21:8
at f (useFetchEntries.js:43:34)
at useFetchEntries.js:79:7
at useFetchEntries.js:80:5
at w0e (react-dom.production.min.js:262:359)
at e.unstable_runWithPriority (scheduler.production.min.js:18:343)
at mg (react-dom.production.min.js:122:325)
at xh (react-dom.production.min.js:261:308)
at O3 (react-dom.production.min.js:292:141)
at uye (react-dom.production.min.js:73:323)
at HTMLBodyElement.n (helpers.js:97:17)

ToastManager.jsx:135 LSe: Timeout after 10000ms
at zSe.timeout (Util.js:93:26)
at ug.__request (Manager.js:277:27)
at ug.value (Manager.js:203:38)
at ug.getLogEntries (ManagerInsights.js:14:17)
at useFetchEntries.js:25:29
at Array.map ()
at useFetchEntries.js:21:8
at f (useFetchEntries.js:43:34)
at useFetchEntries.js:79:7
at useFetchEntries.js:80:5
at w0e (react-dom.production.min.js:262:359)
at e.unstable_runWithPriority (scheduler.production.min.js:18:343)
at mg (react-dom.production.min.js:122:325)
at xh (react-dom.production.min.js:261:308)
at O3 (react-dom.production.min.js:292:141)
at uye (react-dom.production.min.js:73:323)
at HTMLBodyElement.n (helpers.js:97:17)

that does not seem to get me any closer to the blackholed domain