[RELEASED] Python plugin to control Onkyo receivers

[JimmyH1969]

I know, but that's a domotic thingy. The max is 100%, but for a selector switch there should be no limit i think.

[dwmw2]

https://github.com/domoticz/domoticz/issues/2110

[biggles]

You can move the inputs up and down when you modify the selectorswitch. Moving the desired input up at a level below 100 should do the trick.

Hi Jimmy,

I found something else that is weird and i am unable to find a solution.
If i edit the ONKY Selector switch and i delete the value at the Selector Actions / Action (let say there is a value of 05) then i am unable to put in a new value as it is expecting to start with script of http and i am unable to put in any action value like a number.

Is there a workaround for this ?

Regards,

Biggles.

[Varazir]

Any update on this script ?

[dwmw2]

The 4.9700 stable release was made a week or two ago, containing built-in support for Onkyo amps.

[Varazir]

The 4.9700 stable release was made a week or two ago, containing built-in support for Onkyo amps.

yes I know, it was in the beta for some time and it works fine but I hate that I can't force connect.
It's hard set to 30 sec.

[dwmw2]

yes I know, it was in the beta for some time and it works fine but I hate that I can't force connect.
It's hard set to 30 sec.

Hm, that's the first time I've spotted that complaint. Why's it a problem? You can connect to the amp even if it's "off"... do you use a hard power switch with it?

It probably isn't hard to fix; I think it sends a multicast when it starts up (and periodically thereafter). But I didn't see this "complaint" until after the stable release happened so it'll be a while before it gets fixed in the next stable release...

Patches welcome

[Varazir]

yes I know, it was in the beta for some time and it works fine but I hate that I can't force connect.
It's hard set to 30 sec.

Hm, that's the first time I've spotted that complaint. Why's it a problem? You can connect to the amp even if it's "off"... do you use a hard power switch with it?

It probably isn't hard to fix; I think it sends a multicast when it starts up (and periodically thereafter). But I didn't see this "complaint" until after the stable release happened so it'll be a while before it gets fixed in the next stable release...

Patches welcome

I turn off and on the power to my amp using my greewave switch. So the build in tries to connect every 30 sec.
So when I turn it on I have to wait up to 30 sec until I can turn it on. I wish I could use a script to force connect when the amp responds to ping.
Turn it on and unmute.

[ronald1977]

Hi i have now update Domoticz to 4.9700 and I can see more of my Onkyo 609.
But I wish to switch with selector or button from radio broadcast, but I see in the log that he sees it, but there is nothing created in the hardware list.

Must I make a script or is there a way around?

[jake]

Hi i have now update Domoticz to 4.9700 and I can see more of my Onkyo 609.
...

I assume you use the built in version for the Onkyo? That is not the same (topic) as this Python version.

[silver323]

Does somebody know why i get the following in my log:
2018-11-05 12:07:15.562 (Onkyo) Pushing 'onHeartbeatCallback' on to queue
2018-11-05 12:07:15.608 (Onkyo) Processing 'onHeartbeatCallback' message
2018-11-05 12:07:15.608 (Onkyo) Calling message handler 'onHeartbeat'.
2018-11-05 12:07:15.608 (Onkyo) onHeartbeat called
2018-11-05 12:07:15.609 (Onkyo) Checking if discovery data has been received
2018-11-05 12:07:15.709 (Onkyo) Sending UDP discovery packet
2018-11-05 12:07:15.710 (Onkyo) UDP Discovery packet send succesfully

Its repeats over and over. Can't get any devices..
My Onkyo is online.

[jake]

@jorgh, is there still a benefit for using this plugin versus the built in hardware within domoticz?
I use the NR535 receive.

[silver323]

Does somebody know why i get the following in my log:
2018-11-05 12:07:15.562 (Onkyo) Pushing 'onHeartbeatCallback' on to queue
2018-11-05 12:07:15.608 (Onkyo) Processing 'onHeartbeatCallback' message
2018-11-05 12:07:15.608 (Onkyo) Calling message handler 'onHeartbeat'.
2018-11-05 12:07:15.608 (Onkyo) onHeartbeat called
2018-11-05 12:07:15.609 (Onkyo) Checking if discovery data has been received
2018-11-05 12:07:15.709 (Onkyo) Sending UDP discovery packet
2018-11-05 12:07:15.710 (Onkyo) UDP Discovery packet send succesfully

Its repeats over and over. Can't get any devices..
My Onkyo is online.

Nobody?

[jake]

Is your Onkyo device supported by the plugin?

[silver323]

Is your Onkyo device supported by the plugin?

Is there a way to check if my device is compatible with this script?
I didn't see any list which are supported

[jake]

Is your Onkyo device supported by the plugin?

Is there a way to check if my device is compatible with this script?
I didn't see any list which are supported

I believe that all models after 2012? are supported. Back in this thread I read about accepting XML or not, defining how well the plugin works.

[silver323]

Is your Onkyo device supported by the plugin?

Is there a way to check if my device is compatible with this script?
I didn't see any list which are supported

I believe that all models after 2012? are supported. Back in this thread I read about accepting XML or not, defining how well the plugin works.

I've got the TXNR609
For now i use the "Onkyo AV Receiver (LAN)" as default implemented in the domoticz.
Then I get the normal switches with on/off and volume but that's not working correct.
Most of the time the switch stays at Off. Doesn't see when it's on.
When the onkyo is really off Iget a lot of logs.
2019-02-21 07:08:45.824 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:09:18.944 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:09:52.064 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:10:25.184 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:10:58.304 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:11:31.424 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:12:04.544 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:12:37.664 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:13:07.666 Error: OnkyoAVTCP: Can not connect to: IP

Does somebody know that?

[mvveelen]

Is there a way to check if my device is compatible with this script?
I didn't see any list which are supported

I believe that all models after 2012? are supported. Back in this thread I read about accepting XML or not, defining how well the plugin works.

I've got the TXNR609
For now i use the "Onkyo AV Receiver (LAN)" as default implemented in the domoticz.
Then I get the normal switches with on/off and volume but that's not working correct.
Most of the time the switch stays at Off. Doesn't see when it's on.
When the onkyo is really off Iget a lot of logs.
2019-02-21 07:08:45.824 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:09:18.944 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:09:52.064 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:10:25.184 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:10:58.304 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:11:31.424 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:12:04.544 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:12:37.664 Error: OnkyoAVTCP: Can not connect to: IP
2019-02-21 07:13:07.666 Error: OnkyoAVTCP: Can not connect to: IP

Does somebody know that?

Same here.

I used to have a package installed on Buster, but now I moved to Bookworm, I can't install it and use the built-in Onkyo support. The volume switch works, the on-off switch doesn't recognise the right status. And I received several messages about the IP as mentioned above and that's just "ugly". If the IP isn't available, the status of the Power switch should be changed to "Off" and no error message should be in the log, right?