You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2018. It is now read-only.
Hello gaetano-guerriero, today I just started using pypjlink and found out that command line utility works fine for my Vivitek projector, but when I tried using Python library, it raises assert in the protocol.py, in the parse_response function, on the "assert header == '%'" line. After spending some time I understood that the difference between command line interface and the way I used library is that CLI calls "authenticate" method on Projector instance before issuing command requested by user. But the "Python library usage" section in documentation both on GitHub and PyPi says nothing about this. So it would be great to fix the "Python library usage" documentation section and mention the "authenticate" call in it.
The text was updated successfully, but these errors were encountered:
thank's for writing this down. I can confirm the behaviour you describe with a Mitsubishi projector. Calling of .authenticate() is needed always, even if no password is set.
Hello gaetano-guerriero, today I just started using pypjlink and found out that command line utility works fine for my Vivitek projector, but when I tried using Python library, it raises assert in the protocol.py, in the parse_response function, on the "assert header == '%'" line. After spending some time I understood that the difference between command line interface and the way I used library is that CLI calls "authenticate" method on Projector instance before issuing command requested by user. But the "Python library usage" section in documentation both on GitHub and PyPi says nothing about this. So it would be great to fix the "Python library usage" documentation section and mention the "authenticate" call in it.
The text was updated successfully, but these errors were encountered: