"Failed to connect" error #26
Comments
|
Can you show me a screenshot of the minicom session? |
|
Sure thing: I also tested using benqprojector.py directly and got this |
|
Ok, minicom output looks exactly like it should Can you add the |
|
Sorry, getting back to the minicom output, it actually doesn't look like it should. I'm expecting to see |
|
Here's the debug output: Minicom does actually show Thanks for the quick replies! |
|
Is the warning message consistent when you run the |
|
It's now slightly different than that first run using |
|
Are you sure the baudrate is correct? You can find the baudrate in the on screen menu of your projector |
|
Yes, it's definitely correct |
|
Can you set it higher and see if that helps? Maybe there is indeed a timeout in the code that exceeds with low baud rates. I run my serial connection on 115200 baud |
|
Yeah, 115200 is what I had mine set to originally, as well. I dropped it down based on some feedback I got elsewhere when I was just testing the cable. Tested again at 115200 and at 57600 a few times and unfortunately still no dice: |
|
Could you try from a different machine? |
|
Using |
|
Unfortunately, |
|
Ok, I think the problem here is the |
|
No problem. Also happy to take a stab at it sometime next month, though my python is admittedly a bit rusty. Thanks again for taking a look. |
|
If you'r comfortable with changing some code for testing then try the following: In the |
|
Cheers, thanks for that. I was able to give this a try tonight (also discovered my macbook had an older version of python3, so I had only able to install an older version of Unfortunately, I'm definitely not strong enough with regex to be able to parse what's expected and what my projector is sending that's not expected, though I suspect it's the |
|
For testing you could change the line |
|
Sorry, that won't work. You can replace |
|
Thanks. That looks to have done it (at least in terms of Running the Powering off the projector works fine I'm also noticing that the modelname response is different when the projector is off vs on 😵💫 - not really sure why BenQ makes things so difficult! At any rate, I have been able to get the projector to turn on using a simple command line argument with |
|
Yes, some projectors behave differently when they're on than when they're off and plenty of other quirks which vary between models. BenQ doesn't seem to be very consistent in following their own interface definition. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to connect my BenQ W700 projector via this integration and keep getting a "Failed to connect" error.
In the logs all I see is
Failed to get projector command prompt, is your projector properly connected?(Looks like this is the source of the errorSource: custom_components/benqprojector/config_flow.py:157)I have tested using minicom and I'm able to communicate with the projector (on, off, modelname), I've made sure the baud rate is the same on the projector as I'm entering here, and I've tested with the projector both on and off already.
The one thing that sticks out to me is that it's timing out very quickly - almost immediately after clicking "Submit" when adding the projector, I get the above error.
Let me know if there's any other info I can provide to help troubleshoot this and thanks in advance for any help!
The text was updated successfully, but these errors were encountered: