-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Some commands do not provide reading #7
Comments
It's actually a bit difficult to detect if a command is supported if the status can not be requested. In that case the real command should be tested which changes the state of the projector. If it makes sense what I'm saying For instance when I'm detecting the supported input sources I first request the current source, then try all know source types and at the end set the source type back to the original source. This way I'm leaving the projector in it's original state after the detection has been finished. If I'm not able to request the current state of a feature I'm also not able to return to this state after the detection has been finished. |
For showing and navigating the menu, the whole idea of using a library is to not having to use the menu. So I'm thinking about not supporting those commands all together. Do you see a use case for using and navigating the menu with the library? |
What I'm also noticing is that your projector returns |
Ich see a use case: Having a remote control on the mobile phone. I could make an remote control card inside home assistant and fully control the projector. But it's a lot of work and i would prioritize this low. If the internal commands (beside navigating in the menu) work, I would be very happy already. |
Also, one more thing: |
I created a function to send raw commands. This way the mentioned commands but also future commands which are not (yet) supported by the library can still be send. The HA integration will have a service to send raw commands to the projector so that's also covered. Do you think this is a workable solution? I also improved the |
I saw it already. :-)
I think so. If everything works in general I'll check it out. Thank You! |
Hi @pkoevesdi , I'm guessing the items mentioned in this issue are now resolved/covered so I can close the issue? Please reopen if you think that's not the case. Thanks! |
Just a short comment: I can imagine, it's fixed, You took some commands into an ignore list, can be a good workaround. I haven't checked yet, if this list is complete or too harsh for my projector. I have only few time, last weekend I spend my very few hours it with putting together your last commit and what I did that week before. |
Ok, thanks for the heads up. Looking forward to your improvements |
Some commands don't provide reading, they can only be written.
Example:
\r*menu=?#\r
on Benq W1100 doesn't work, but\r*menu=on#\r
and\r*menu=off#\r
do very well.For them, the function
examine
doesn't work correctly, it reports false negative:The text was updated successfully, but these errors were encountered: