Open Cornmeister opened 2 months ago
Hey, thanks for reaching out!
Navigation timeout of 60000 ms exceeded
sounds like the Browser was not able to settle rendering of the page after one minute. The timeout looks quite reasonable for the hardware specs, but maybe you can check what's on your dashboard and maybe try rendering some lovelace page first, which maybe has one default entity on it? Just to be sure that the URL etc works and can then try to narrow it down on maybe some part of the content.
Unfortunately this doesn't seem to be a very straight forward advise, but it's the best I can tell from just the logs. The browser isn't very "talkative" when it comes to finding the reasons why navigation failed after 60s.
Strange, a simple lovelace dashboard with one card renders fine. After switching back to the original dashboard, it still runs :D
no clue why, it works for now, will reopen issue if it returns.
thanks
:( It rendered once, but now it will only render simple lovelace dashboards with one card, larger dashboards result in timeouts.
did some testing, without an Apex Chart card, it runs fine. takes too much time/resources I guess.
Technically the only option we have is to just enforce rendering, even after the timeout error was raised. It may result in broken screenshots but even this might be more helpful than an exception in the logs...
I'll think about this and let you know once I'll give this a try.
Thanks for the hint with the Apex Chart card! It's something I can try to use for reproducing the issue and fiddling around with timeout handling.
@Cornmeister @sibbl maybe it has to do with hardware graphic acceleration in the virtualized environment? maybe headless Chrome tries to access that, but fails to get enough of it from Proxmox... Did you allocate any GPU to your VM?
However much you put on that dashboard, your CPU config should be able to handle that...
Hi,
I'm not able to use your tool, It starts, and after trying (and failing) to connect, it shuts down itself, Sometimes it is able to render an image, but fails most of the time.
It happens with both the HA addon and the standalone docker, running on a proxmox VMs with 16GB ram and 4 CPU cores assigned on a gen10 i7 host
any suggestions ?