hass-pfsense icon indicating copy to clipboard operation
hass-pfsense copied to clipboard

firmware_update_info Timeout Error

Open craibo opened this issue 2 years ago • 10 comments

After updating to the recent release, the following error is appearing in the logs constantly

This error originated from a custom integration.

Logger: custom_components.pfsense.pypfsense
Source: custom_components/pfsense/pypfsense/__init__.py:110
Integration: pfSense (documentation, issues)
First occurred: 11:37:47 (2 occurrences)
Last logged: 13:38:30

Unexpected get_firmware_update_info error err=TimeoutError('The read operation timed out'), type(err)=<class 'TimeoutError'>

I have also noted that since the recent update, the device updates have become unstable resulting in undefined values resulting in incorrectly triggered automation alerts.

craibo avatar Feb 13 '23 03:02 craibo

Have the same error since update, running latest update v0.6.0 Home Assistant 2023.4.2 pfSense 2.6.0-RELEASE (amd64) built on Mon Jan 31

PerJarlemark avatar Apr 11 '23 17:04 PerJarlemark

Just another one, with v0.6.1 (latest), FYI …

pfSense: Firmware: 2.6.0-RELEASE

HA:

Home Assistant 2023.5.2
Supervisor 2023.04.1
Operating System 10.1
Frontend 20230503.3 - latest

HA error:

This error originated from a custom integration.

Logger: custom_components.pfsense.pypfsense
Source: custom_components/pfsense/pypfsense/__init__.py:110
Integration: pfSense (documentation, issues)
First occurred: May 6, 2023 at 12:47:16 (23 occurrences)
Last logged: 10:02:35

Unexpected get_firmware_update_info error err=TimeoutError('The read operation timed out'), type(err)=<class 'TimeoutError'>

sokai avatar May 08 '23 10:05 sokai

When you click on the firmware update process in the pfsense ui does it timeout? It could be any number of things making that slow :(

travisghansen avatar May 08 '23 13:05 travisghansen

Hey @travisghansen

In the pfSense ui, I have no issues with checking for updates or experiencing any timeout issues. This error is still occurring constantly on HA for me

craibo avatar May 08 '23 13:05 craibo

How often is constantly? Under normal circumstances the data is cached in pfSense and should return immediately…which to properly test the pfsense ui you really need to kill the hass integration and wait for a couple hours.

travisghansen avatar May 08 '23 13:05 travisghansen

I have the same issue. I just restarted Home Assistant because of a different issue and immediately got this error. I've been getting it for a while now, but never got around to do anything with it. And just to make it clear, I get this error without doing anything regarding this integration or anything in pfSense. This error is just there in the logging.

If there is anything I can do to test, please let me know

bscheutjens avatar Jun 01 '23 14:06 bscheutjens

Hello,

Same problem for me.

Do you have a solution ?

Thank you

prohand avatar Aug 03 '23 08:08 prohand

frequently see this error after HA boot

fama-lama avatar Dec 15 '23 06:12 fama-lama

I get this too. A manual check in pfsense takes about 5 secs to complete. Is there a hard coded value for this check in the integration which could be exposed that allows us to make the timeout longer?

dmshimself avatar Apr 04 '24 20:04 dmshimself