Open Norm2023 opened 6 months ago
I suspect this is related to Browserless timeout (maybe Hardware is not great and it goes in timeout?). How to increase the timeout in browserless hassio addons? Can you make it configurable?
browserless.io:limiter Job has hit timeout after 30,003ms of activity. +30s
Hi, please try adding TIMEOUT: 60000
in the config.yaml it will pass it as env variable. I'll push a new version of the addon with this as default
Did you mean config.json? I am using local addons as I had to change the PLAYWRIGHT_DRIVER_URL env variable due to websocket error. Now websocket is OK but it goes in timeout after 30sec. Adding TIMEOUT to config.json or config.yaml does not change anything. I was expecting to change something in browserless addon rather than changedetection.
Hi it seems things are getting better now (I updated to Browserless to 2.12.0-2 with 60sec timeout). Thansk for that!! What if I wanted to increase more the timeout? Can you make it configurable in next releases? Also I don't know why but I am not able to find the config.json for browserless hassio addon, while the one for changedetection I can (do you know the path?)
Hi, indeed browserless chrome dorsn't expose it's config; something i can solve in the future
Added for changedetection too
Description
I am encountering this error "Target page, context or browser has been closed" for any website in the watchlist.
Strange thing is that if I use Browser Steps and Visual filter selector I actually see the webpage being fetched.
My setup:
Pi4 8GBHome Assistant 2024.1.5
changedetection addon 0.45.14
Browserless Chrome addon: 2.2.0-5
Reproduction steps
Addon Logs
Architecture
aarch64
OS
HAos