I am transitioning over to the AudioControl Maestro x9 Audio Video processor. It allows full IP control.
Is there a plan to add this to the compatibility list? This is a hell of an AV processor and a great addition to the out of the box integrations.
I also have a new AudioControl receiver. I would like to see the full capabilities of this product supported. You can temporarily define it as an Arcam if you connect it via serial. It has very basic functions but works.
I also defined a new custom device using Settings/Custom Devices. It works as full IP. It is not as robust as I would like. Struggled with RS232 commands that are suppose to return status such as mute, volume, current input or mode.
With Settings/Custom Devices you can send a command to the AudioControl but there is no way to parse or display any return info from the AudioControl. This is the same for all devices. Custom devices are one way only. The developers need to formally support the device in order to get feedback onto the display.
You are correct and that is why I support adding these devices by the developer. This is a great line of audio equipment that deserves attention. I have also reached out to Audio Control technical support and introduced them to Roomie Remote. I would suggest that anyone else wishing for this line to be added reaching out to Audio Control as well.
try arcam codes the work for my audio control
AVPro EDGE purchased Audio Control Home because of the quality of the products. I believe that these products need to be added by Roomie for full capabilities in lieu of work arounds. See link below:
We don’t have this receiver. We have added support for many receivers we don’t have on site. It requires an interested and dedicated user with access to the device and the technical ability to find the API and verify it on their device. Get the codeset discussed above working which appears to provide all the basic functionality, obtain the API to get volume/etc, send it us and state you’re willing to beta feedback support. Usually it’s a ~30 day process start to finish if the user is capable of installing frequent betas and verifying implementation.