Bas Scheutjens

I'm not sure if what I'm seeing is the same issue, but it seems to be. If it isn't, I'll apologize right now ;) Anyway, what I'm seeing is that...

I already have an update on monitoring pfSense. It wasn't too much work, I created a small application that loads the login page (using the same URL as filled in...

> What do the similar logs show during the outages? Do specific operations take longer? Do they just all fail? Etc I wanted to make the joke "I'll let you...

It just happened, not sure why that 2 hour changed, but ok. This is my full logging of when it happened. I'm not sure if that iaohttp is part of...

> Probably the only way to figure out what exactly is triggering the issue is to find someone comfortable enough with coding that can start hacking the integration and selectively...

> Basically when checking the latest firmware data pfSense itself caches the data for 2 hours, so that's likely the cause. And that might explain the shift of the two...

After updating to 0.5.1 and restarting HA I get the following errors: ``` This error originated from a custom integration. Logger: homeassistant.loader Source: custom_components/pfsense/update.py:107 Integration: pfSense (documentation, issues) First occurred:...

I'm running the latest versions: > Home Assistant Core 2022.6.7 > Home Assistant Supervisor 2022.06.2 > Home Assistant OS 8.2

Ow, by the way. I was using 0.4.1 before updating to 0.5.1, so this could be a 0.5.0 issue. And despite the errors, the integration does seem to work

The issue is partly solved. I can see in the logging what you tried to do, but it didn't solve the problem. The logging: ``` 2022-07-06 19:16:02 DEBUG (SyncWorker_6) [custom_components.pfsense]...