-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration crashes after beamer being powered off / unreachable for a longer time #24
Comments
Hi @DaKue77, thank you for your kind words regarding my integration. I don't own a networked projector myself, so am dependent on community feedback like yours if things don't work. So with powered off you mean taking the power off the projector right? Not powering off as in putting in stand-by. |
Hi @rrooggiieerr , yes, this is really a very useful integration and I am happy to help out with any feedback I can provide. :) Indeed, I mean taking off the power from the projector. I have a wireless power plug in front of the beamer that I am remotely switching off. When putting the projector simply into stand-by I did not encounter any issues so far, but I can test it during the upcoming nights by leaving the beamer in stand-by without taking off the power - just to make sure. EDIT: One other point - so far the issue was on 2024.12, today I updated to 2025.1.1, so I will also test behaviors on this version now. |
Your issue looks very much like #23, did you upgrade to HA Core 2025.1? And did the integration still work on HA Core 2024.12? |
Reloading asks for restarting HA and yes, after restarting HA it works again.
Agree, but since the issue #23 was referring to an issue introduced with 2025.1. Since I observed my issue with 2024.12, I did choose to create a separate issue. You can of course merge these issues. As written above, today I updated to 2025.1 (45 mins ago) so I will now re-check for the behavior. |
I wasn't expecting you were asked to restart HA, than it's quite severe. Does it ask this when the projector is off power, or also on power but stand-by? |
Good idea - I'll try and see whether this would allow a reload without a HA restart. |
Hi @rrooggiieerr , I am back again with another test result. This night I completely turned off power again and after approx. 1h this error occurred again, this time on HA version 2025.1.1:
I also tried to reload the device via the automation - this is the result:
A second device device entry was created by the automation and both are not available: In addition I am not able to reload the device via the GUI anymore: After restarting HA, the newly created device is available again, but the initial one not. So I have to relink it now to all the existing rooms and scripts and I wonder how to remove the first one. |
Thanks! I'm working on hardening the underlaying library to be able to handle these errors, how comfortable are you with testing my Python code from the command line? |
I'm also trying to understand why you get the error after about an hour. Does your DHCP lease time happen to be one hour? |
I feel comfortable to test from the command line, happy to help. DHCP was also the first thing that came up to my mind, so I already changed the projector's network configuration to static. I do not expect any issues related to networking. I do have other devices being switched off together with the projector, that are on the same network even with DHCP, still they re being recognized again by their integrations, once up again. (an AVR, a BD Player and a Android TV Player). |
I made changes to the underlaying python library, could you give these a try? Please modify the requirements of the
And restart your HA afterwards |
I am on vacation until next Monday and will test it as soon as I am back!
rrooggiieerr ***@***.***> schrieb am So., 12. Jan. 2025,
19:46:
… I made changes to the underlaying python library, could you give these a
try?
Please modify the requirements of the
custom_components/benqprojector/manifest.json to link to ***@***.***
+https://github.com/rrooggiieerr/benqprojector.py.git like so:
{
"domain": "benqprojector",
"name": "BenQ Projector",
"codeowners": [
***@***.***"
],
"config_flow": true,
"documentation": "https://github.com/rrooggiieerr/homeassistant-benqprojector",
"integration_type": "device",
"iot_class": "local_polling",
"issue_tracker": "https://github.com/rrooggiieerr/homeassistant-benqprojector/issues",
"loggers": [
"benqprojector"
],
"requirements": [
***@***.***+https://github.com/rrooggiieerr/benqprojector.py.git"
],
"version": "0.1.2"
}
And restart your HA afterwards
—
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BH37MJ6X7VNPHV3XD2HU6T32KK2BXAVCNFSM6AAAAABUXPA34OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVHA3DQMJSHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey @rrooggiieerr , I did as requested, unforatunately still the same error after exactly 2h:
This seems to happen after the runner retried for approx 2h and afterwards the runner also stops:
|
I was expecting something else. Did you restart HA after making the changes? No typo's? In case of a typo HA will write an error in the log file and keep using the previous version of the library. |
I did a copy & paste and this is how the changes look like:
I did restart HA and there were no typo related errors. Also, when the error occurs and I simply restart HA with projector still externally powered off and without reloading the devices there is following error in the HA log:
What I can also see is warning log entries related to blocked messages:
and
In addition I observed that if I restart first, I can then afterwards just reload the devices without forcing me to restart once more. So in summary: BTW: There is regularly a second device created with same name but without room assigned. I still try to figure out, why this happens just once with a second device, but I never saw a third one... will further observate. |
Looking at the logging I can see my modifications are not used and an older version of the library is still used. Can you send the Blocked items usually happen when the projector is starting up or shutting down. They are warnings not errors. Generally not something to be worried about. |
that's strange... please find the log file attached. The script errors in the log are also related to the benq integration, since the projector device is regularly being recreated after reboot ... I always need to amend the scripts afterwards. Though this might only happen, if the initial device is mapped to a room. Still trying to nail it. I'll also restart the whole container and see whether it will pick up your changes. |
I got news: After rebooting the container yesterday, the error didn't occur this night. So things worked as expected. I will give it a few more tries and report back afterwards. |
@DaKue77 I'm looking forward to the results of your tests, I hope all problems are resolved. In the meantime, could I ask you to share the MAC address of your projector? I'm trying to figure out if there is a specific MAC range that BenQ uses on the integrated network interfeces so I can implement auto configuration |
Hi,
I love this integration and how it eases my interaction with my Benq Beamer (w4000i/ht4550i).
One annoying thing is that the integration does seem to crash after the Beamer is powered off and not reachable via Network anymore.
Situation:
I have my Benq W4000i/HT4550i connected to the network. It has an integrated LAN port. It is being discovered by the Benq integration and can be controlled properly. I have configured a fixed IP address, but did also try DHCP before.
During night I power off my hole theater including the Beamer via an external power switch.
Expected behavior:
As for all other devices and integrations I use, I expect the Benq integration to automatically discover the Beamer once it is network reachable again.
Actual Behavior:
In opposite to all the other devices, the Beamer does not get available again (Status: Not available). The Benq integration seems to have crashed an can only be reactivated by completely restarting Home Assistant.
Error log:
Warning Message:
Error message:
The text was updated successfully, but these errors were encountered: