elad-bar / ha-hpprinter

HP Printer Integration
88 stars 23 forks source link

Error after upgrade - Failed to get /ePrint/ePrintConfigDyn.xml #123

Closed StefanoGiu closed 2 weeks ago

StefanoGiu commented 3 weeks ago

2024-05-06 17:46:41.050 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /DevMgmt/ProductConfigDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/DevMgmt/ProductConfigDyn.xml, Line: 327 2024-05-06 17:46:44.033 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /DevMgmt/ConsumableConfigDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/DevMgmt/ConsumableConfigDyn.xml, Line: 327 2024-05-06 17:46:47.041 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /DevMgmt/ProductUsageDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/DevMgmt/ProductUsageDyn.xml, Line: 327 2024-05-06 17:46:50.048 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /IoMgmt/Adapters, Error: Connection timeout to host http://XX.XX.XX.XX:80/IoMgmt/Adapters, Line: 327 2024-05-06 17:46:53.055 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /ePrint/ePrintConfigDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/ePrint/ePrintConfigDyn.xml, Line: 327 2024-05-06 17:46:56.063 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /DevMgmt/NetAppsSecureDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/DevMgmt/NetAppsSecureDyn.xml, Line: 327 2024-05-06 17:46:59.073 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /DevMgmt/ProductConfigDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/DevMgmt/ProductConfigDyn.xml, Line: 327 2024-05-06 17:47:02.081 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /DevMgmt/ConsumableConfigDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/DevMgmt/ConsumableConfigDyn.xml, Line: 327 2024-05-06 17:47:05.089 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /DevMgmt/ProductUsageDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/DevMgmt/ProductUsageDyn.xml, Line: 327 2024-05-06 17:47:08.147 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /IoMgmt/Adapters, Error: Connection timeout to host http://XX.XX.XX.XX:80/IoMgmt/Adapters, Line: 327 2024-05-06 17:47:11.157 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /ePrint/ePrintConfigDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/ePrint/ePrintConfigDyn.xml, Line: 327 2024-05-06 17:47:14.188 ERROR (MainThread) [custom_components.hpprinter.managers.rest_api] Failed to get /DevMgmt/NetAppsSecureDyn.xml, Error: Connection timeout to host http://XX.XX.XX.XX:80/DevMgmt/NetAppsSecureDyn.xml, Line: 327

elad-bar commented 3 weeks ago

More context please Did it work before? What version are you using (HA / Integration)? What is the device model? Does it support EWS?

Thanks

StefanoGiu commented 3 weeks ago

It was working before I upgraded to the latest version. I have HA 2024.4.0 and HP integration v2.0.0b5 installed via HACS. My printer is HP Smart Tank 640. Before I had no error in the logs... now logs are flooded by this error.

elad-bar commented 3 weeks ago

I think that you printer is not accesible with that url and might use https and port 443 and http 80, Can you pls check it?

StefanoGiu commented 3 weeks ago

How can I check? I was using the same configuration and the same printer before the upgrade of your custom component....

elad-bar commented 3 weeks ago

From the log above: http://XX.XX.XX.XX:80/DevMgmt/ProductConfigDyn.xml

Thanks

elad-bar commented 3 weeks ago

The best option is to remove integration and re-add, If you would like to investigate why it is not working I will need that information if it is related to url or just something different

StefanoGiu commented 3 weeks ago

This link is working properly on port 80: http://XX.XX.XX.XX/DevMgmt/ProductConfigDyn.xml

I don't want the log to be flooded when the printer is off (turned off), like it was before the upgrade.

elad-bar commented 3 weeks ago

i will release new version during the weekend with fully working diagnostic component so you will be able to export the data from the integration and it will be easier to understand the issue over there

StefanoGiu commented 3 weeks ago

Is it possible that this error is fired when the printer is turned off?

elad-bar commented 3 weeks ago

if the printer is off and the integration will try to call it, most likely you will get this error (for now).

i have changed the process so at the first load of the integration, one of the endpoints of data must return Ok (200) result with data, if afterward it all of them will return 404, it will log it as DEBUG message, will reset the counters but you will not see an issue, i will release new version soon with that fix

elad-bar commented 3 weeks ago

released v2.0.0b6 with a fix for the issue, can you please check and report back?

thanks

StefanoGiu commented 3 weeks ago

Thanks. Would you mind to remove the error also at the startup of HA if the printer is off ?

elad-bar commented 3 weeks ago

Thanks for the update If the printer is off, it means there is an issue, like with any other integration if the service it calls is down, in that case it will show the error

StefanoGiu commented 3 weeks ago

No the printer is off because I switch it off and there is no problem...

elad-bar commented 3 weeks ago

For the integration that is not aware of it, it is an issue... it tried to update and failed, none of the endpoints were accessible, it is an issue, If you have bluetooth device and remove it without disabling the component, how will HA react to it?

I can suggest that either you can disable the integration or add filter in logs, since the integration doesn't know what is the reason, it cannot avoid it

elad-bar commented 2 weeks ago

closing as original reported item solved and additional need is nto going to be addressed as mentioned above