Hi all, I would like to let you know that I have started work on an Onkyo AVR custom integration., now in version 0.0.1 It is in early development phase and please do read the README before you start playing with it. As it is early development breaking changes are to be expected so don’t just switch to it if your current setup has a high WAF for example.
7 Likes
Nice. Thanks for this. Should work with my Pioneer Elite AVR, as it is supported by the Python library you’re using. Once it gets a bit further along, I’m happy to test and provide patches for any issues I encounter where possible 
Great! Any feedback is appreciated!
Maybe you also find this discord interesting:
Hi all, version 0.5.0 is now available.
MediaWidget:
-
show DAB station name
-
show artist, title, album and album art when using NET (which is also used for Spotify for example, see the updated readme)
Cheers, Ed
Hi all, version 0.5.3 is now available which has no problem anymore with reboots of the remote.
Also made a small change that allows for a slightly lower ‘overshoot threshold’ because the commands are send a bit faster to the AVR when long-pressing volume (while only short-press is assigned on the remote, see updated README).
Cheers,
Ed
Hello
I’am interested with your integration, tried to upload the uc-intg-onkyo-avr-0.5.3.tar into my remote but system refuses it and say “Invalid archive, missing data in archive or included metadata cannot be read.”
Am I getting the wrong file?
Could find any on the release section, so tried to pick a TAR file somewhere.
Could you please help?
Thanks
Guillaume
It must be .tar.gz try another browser for download.
Ralf
1 Like
Hi Guillaume, its best to first download the tar.gz to you laptop/pc from here:
Click the 3 dots and select download.
And then upload to your remote as described in the readme.
The error you describe sounds like the file was empty or something so maybe download failed.
Kind regards,
Ed
I think he used a browser which expands the .gz part. I had this with chrome on Windows 11 and heard similar from Apple.
Ralf
Aha! Yes that could be it.
I tried to download again the integration from Edge instead of Chrome and it worked! Thanks a lot for your help, wouldn’t have found it wihtout help from you.
I will test the integration and let you know the results.
Thanks again
You are not the first. I couldn’t believe it when I had this problem.
Rslf
Teamwork makes the dream work!
Hi, the integration just exposes the AVR as mediaplayer.
With that you can control anything of the AVR, for example as part of an integration as described in the readme.
You can also just add the selected AVR to a page on the remote then some buttons are already mapped.
Ed
Hi all, released 0.5.4 which has a lot of changes under the hood. Also started to get the github project itself in better shape although that is still work in progress.
Hello,
I have successfully downloaded and install the integration (5.03 version).
However, while setting it up, it discover only media player, not any remote for instance.
My Model is RZ3100 from 2016.
Can it be that it has some limitations?
Thanks
Regards
Guillaume
I answered your question already. Why remove your question and then port it again?
OK, I see.
Indeed, I tried for it and it I have been able to map commands.
Sorry about this I’m just getting started with the remote 3 and I must confess it is much more difficult to set up compare to the harmony.
And sorry to have reposted the question, of course discart it.
Another question: when there is a new version of the integration, can we update the existing one (how?) or we should remove it and install the new one?
Ok no worries. You can update by deleting the integration, twice so it is not showing anymore in the integration screen. Then upload the new version.
Your mappings in the activities will keep on working as long as the selected receiver has the same name as it already had. So if in old version the AVR entity was ‘TX-RZ50 192.168.2.103’ the when adding it as entity in the new version that name should be the same. Using autodiscovery that would be the case.
Version 0.5.4 could mess up its own config, my bad…
Now fixed in 0.5.5