-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[onkyo] Command LISTEN_MODE_QUERY (LMDQSTN) causes sound interruption Onkyo TX8050 #1534
Comments
I think currently there is no workaround. Alternatively, we could make the polling frequency a configuration option, so in your case you can set it to very slow/disable |
addressing openhab#1534 Formatting fixes readme to better display in http://docs.openhab.org/addons/bindings/onkyo/readme.html
It doesn't look like @dvolochnik is active on GitHub anymore. The polling is now defaulted to 0 in current versions and looking at the code this problem should only appear for a brief moment when openHab connects to the device. As noted by @marcelrv the protocol does send unsolicited updates when values change so polling is probably there for those receivers that have unstable EISCP/networking implementations. @cweitkamp can you get someone to close this issue please? |
@Cossey Yes, I can. Thanks for cleaning up the Onkyo issues. |
… if needed (openhab#1534) Signed-off-by: Christoph Weitkamp <[email protected]>
Typo in the "Properties Tab" section. represneted should be represented.
I've tested onkyo binding with my TX8050 receiver and as soon as Onkyo Thing was online, the receiver started to have short sounds interruptions approximately every second. Further investigation showed, that the interruptions happened every time right after the binding send status query to the receiver.
After few experiments, it was clear, that problem is caused by
sendCommand(EiscpCommandRef.LISTEN_MODE_QUERY)
command in the checkStatus() function.
So easy and dirty solution was to comment out problematic row as following:
`private void checkStatus() {
After that the problem was gone.
Most likely, it is a model specific problem which exists only for TX8050 receiver, but, anyway, is there any workaround, or, probably, somebody can create one?
The text was updated successfully, but these errors were encountered: