I have played around with the IR scrutinizer tool a little bit. Do the following Pronto codes work at all:
Stop/ Eject for the Disk Player: 0000 0073 0000 0009 0020 0020 0040 0040 0040 0040 0040 0020 0020 0040 0020 0020 0040 0040 0020 0020 0040 0CC8
Volume Up for DAC: 0000 0073 0000 000A 0020 0020 0040 0020 0020 0040 0020 0020 0040 0040 0040 0040 0040 0020 0020 0020 0020 0020 0020 0CC8
heimspielvier, I apologise but I have been very busy and I also ran into multiple problems with the integrations I installed on the remote. After all the effort to set up integrations, to define activities, to select entities, to define sequences, to customise screens, remote buttons etc, when I finally sat down to start an activity I got error after error. Oppo timing out. Vrroom not switching inputs. And so on. Frankly, I have wasted a lot of time to make this work and so far it really feels like wasted time.
So this time I am taking a different approach. I created a bogus activity and starting to run each command that I need in isolation. Oppo on / off. ATV on / off. Vroom on / off. And so on. Once I confirm that this command works for all my integrations, I will add vrroom. Oppo on / vrroom on. And the corresponding Oppo off / vrroom off sequence. Once I confirm that this works I will try Oppo on / vrroom on / switch vrroom input. Once I confirm this works I will try Oppo on / vrroom on / Lyngdorf on / switch vrroom HDMI input / switch Lyngdorf HDMI input. You get the idea. One step at the time so I can identify exactly what works and what doesn’t (while useful, the logs can be overwhelming). Once I hit a road block - vrroom not switching HDMI inputs for instance, I contact the developer and we work on a fix. This is what I have been slowly doing so far - working my way through problems and bugs to get to the point where triggering a specific activity will correctly start and switch the IP controlled devices. I am not done yet (the developer is for instance looking at the vrroom code to see if he can streamline the HDMI switching in a sequence) but getting there.
On a different note I have been in touch with the developers on Github and they are working on improving IR compatibility - you can read about their progress here . There are new beta firmwares for both remote and docks which are supposed to address some of the issues.
But all this takes a lot of time and effort. So for those of you who want a turnkey solution, UC is not it. Please consider a used Harmony or, if you have deep pockets, a C4 server. UC is for geeks, tinkerers and people with a lot of patience, some IT knowledge and time on their hands.
Heimspielvier, many thanks for the above codes, once I am done troubleshooting integrations, we will be back in business with IR. I have also installed the beta firmwares suggested by developers for improved compatibility and we shall see. I will continue to update this thread as I am making progress.