Bas Scheutjens

> Yeah, do you have a fancy new update entity? It replaces the binary sensor previously used and integrates with hass so you can trigger firmware updates right from the...

> Can you send more lines preceding the fetch that failed? These are the four before the one that failed and the one that failed. I noticed that the line...

> Go to `v0.5.3` and it should be backgrounding the firmware data calls. I just installed this version and restarted HA. The startup errors are gone and I now have...

As promised an update. Unfortunately the problem persists. This is the logging: ``` 2022-07-07 09:17:47 DEBUG (SyncWorker_0) [custom_components.pfsense] execution time: PfSenseData._get_system_info 0.178 2022-07-07 09:17:47 DEBUG (SyncWorker_0) [custom_components.pfsense] execution time: PfSenseData._get_host_firmware_version...

> Ok the back grounding is working. That’s another call that’s taking too long. Can you bump the timeout for the xmlrpc client in code to see if it helps?...

> The telemetry call is the bulk of data behind the integration. If you’re comfortable hacking some more in that file I’d ask to start stepping through the individual pieces...

I've no experience with php either, so I'll stick to editing the script. Because it seems like the timing is only that long during that 2 hour mark it will...

So, this update is way sooner as expected. To start with the conclusion: I don't think the telemetry call has an issue. When I was waiting for your reply on...

> Indeed it appears though that the api _generally_ locks up when that has been invoked on the system (and pfSense needs to **really** refresh the data). I'm unclear why...

> Patches released in `v0.5.4`... I installed this version. The logging seems ok, but I have to wait an hour and a half for the next "2 hour mark".