Initial thoughts & frustrations

[DaveN]

I've had my AVA for about a month. Some good, some bad.

My dealer and I are still working on the fact that my Altitude 32 will not turn off via power off command in most flows yet a button on a separate Altitude flow with the same command works.

Wifi connectivity is randomly lost despite a strong wifi signal.

IR commands will at times fail me. My VPL-VW5000ES will require multiple flow initiation to turn on.This never happens with the Sony remote.

The lack of two way communication leads to frustration when things don't work and you have to go to the equipment room to check if a device has responded.

The remote does have a nice display, the control pad works well and programming is easy. The remote feels great and I'm hopeful that we will get the bugs worked out.

 

[audio-videophile]

I've had my AVA for about a month. Some good, some bad.

My dealer and I are still working on the fact that my Altitude 32 will not turn off via power off command in most flows yet a button on a separate Altitude flow with the same command works.

Wifi connectivity is randomly lost despite a strong wifi signal.

IR commands will at times fail me. My VPL-VW5000ES will require multiple flow initiation to turn on.This never happens with the Sony remote.

The lack of two way communication leads to frustration when things don't work and you have to go to the equipment room to check if a device has responded.

The remote does have a nice display, the control pad works well and programming is easy. The remote feels great and I'm hopeful that we will get the bugs worked out.

I'm neither an expert nor a dealer, just a fellow user, but here are five ideas to try with your AVA Cinema-Remote issue:

1. Make sure that you have DHCP reservations for all of your equipment that you are controlling via IP.
2. Restart the remote and try your problematic flow again.
3. In your flows, add a second 'power off' step below the existing one and then test the flow. I've done this, and I've also duplicated the 'power on' steps when they don't seem to work consistently.
4. Duplicate the problematic flow, rename it, delete the old problematic flow, and then try the newly named flow.
5. Create a new flow that contains the same steps as the old flow, but with a new name, and then delete the problematic flow. Next, try the new flow.

I sometimes feel like I have to treat the remote like a PC and reboot it or recreate a "corrupt" file that doesn't seem to work properly.

Also, I've connected both a Bluetooth keyboard and mouse to my remote and it makes editing flows etc., much more pleasant since I don't have the Nano Brain. The keys on the remote's keyboard are very small.

Good luck!

 

[DaveN]

I'm neither an expert nor a dealer, just a fellow user, but here are five ideas to try with your AVA Cinema-Remote issue:

1. Make sure that you have DHCP reservations for all of your equipment that you are controlling via IP.
2. Restart the remote and try your problematic flow again.
3. In your flows, add a second 'power off' step below the existing one and then test the flow. I've done this, and I've also duplicated the 'power on' steps when they don't seem to work consistently.
4. Duplicate the problematic flow, rename it, delete the old problematic flow, and then try the newly named flow.
5. Create a new flow that contains the same steps as the old flow, but with a new name, and then delete the problematic flow. Next, try the new flow.

I sometimes feel like I have to treat the remote like a PC and reboot it or recreate a "corrupt" file that doesn't seem to work properly.

Also, I've connected both a Bluetooth keyboard and mouse to my remote and it makes editing flows etc., much more pleasant since I don't have the Nano Brain. The keys on the remote's keyboard are very small.

Good luck!

I've tried a few of these suggestions. The double power off didn't help. Have not tried the duplicate/rename.

How do you do a restart of the remote? I haven't had any luck pressing the lower right button and holding it.

 

[audio-videophile]

To restart the AVA Cinema-Remote: There's a button on the top of the right side of the remote that is flush with the case of the remote. Hold that for a second, and you'll get a pop-up. Select "Restart" from there.

 

[DaveN]

Does anyone have insight as to whether AVA will be updating firmware to allow both IR from remote when using a brain?

 

[HCS]

This feature is currently in the works but no eta.

 

[DaveN]

So far implementing control of my theater with AVA has been less than ideal. When I try to have my K and AppleTV flows turn off my Trinnov Altitude nothing happens. When I use the same command under a separate flow for the Trinnov device only, it work every time.

Is anyone here successfully using AVA to power off your Altitude 32? How are you doing this and what should I change? I find it incredible that the same command in different flows to the same device doesn't work the same way in all.

 

[thrillcat]

So far implementing control of my theater with AVA has been less than ideal. When I try to have my K and AppleTV flows turn off my Trinnov Altitude nothing happens. When I use the same command under a separate flow for the Trinnov device only, it work every time.

Is anyone here successfully using AVA to power off your Altitude 32? How are you doing this and what should I change? I find it incredible that the same command in different flows to the same device doesn't work the same way in all.

Add a second "power off" command in the shut down flow. I had to do that with my projector which was only shutting down half the time, and it works perfectly now.

Also note, whenever I'm shutting the system down completely instead of switching from one flow to another, I have the programmable side button set so that a long press shuts everything down, and I'm using that every time I shut it down for the night.

 

[DaveN]

Add a second "power off" command in the shut down flow. I had to do that with my projector which was only shutting down half the time, and it works perfectly now.

Also note, whenever I'm shutting the system down completely instead of switching from one flow to another, I have the programmable side button set so that a long press shuts everything down, and I'm using that every time I shut it down for the night.

I’ve tried adding redundant commands without success. Both app launch and power off.

The side button long press accidentally turned off parts of my system when I didn’t mean to press it so I disabled the button.

 

[audio-videophile]

So far implementing control of my theater with AVA has been less than ideal. When I try to have my K and AppleTV flows turn off my Trinnov Altitude nothing happens. When I use the same command under a separate flow for the Trinnov device only, it work every time.

Is anyone here successfully using AVA to power off your Altitude 32? How are you doing this and what should I change? I find it incredible that the same command in different flows to the same device doesn't work the same way in all.

My AVA Cinema-Remote successfully turns on and off my Trinnov Altitude 16. Please reread my post in this thread written on 11/15/2025 for ideas of what to try to get it to work. There are 5 steps to try.

 

[DaveN]

My AVA Cinema-Remote successfully turns on and off my Trinnov Altitude 16. Please reread my post in this thread written on 11/15/2025 for ideas of what to try to get it to work. There are 5 steps to try.

I had tried 1-4 previously without improvement. I was tired of trying so many changes before using the remote only that I gave up before #5. Tried number 5 and it did the trick! Thanks for the suggestion.

I've bought a brain and will probably wait to do the other device using my laptop.

New question. When I added the Lutron App launch to turn the theater lights off it automatically disabled the Kaleidescape slides setting on the flow. When I go out of the Lutron app I can no longer control the Kaleidescape. Is there a way around this or must I launch the app from it's dedicated flow?

 

[DaveN]

How many folks are controlling a Lumagen processor via IR with their AVA remote? I am suffering through the Lumagen not recognizing the AVA commands. The blue light on the Lumagen flashes indicating a command was received but the input will not change. This occurs with a brain and separately with another AVA remote not connected to the brain. Other Lumagen commands appear to be accepted.

 

[thrillcat]

How many folks are controlling a Lumagen processor via IR with their AVA remote? I am suffering through the Lumagen not recognizing the AVA commands. The blue light on the Lumagen flashes indicating a command was received but the input will not change. This occurs with a brain and separately with another AVA remote not connected to the brain. Other Lumagen commands appear to be accepted.

I'm not having any issues other than needing to turn around to aim the remote at the Lumagen. No brain in the system.

 

[HCS]

How many folks are controlling a Lumagen processor via IR with their AVA remote? I am suffering through the Lumagen not recognizing the AVA commands. The blue light on the Lumagen flashes indicating a command was received but the input will not change. This occurs with a brain and separately with another AVA remote not connected to the brain. Other Lumagen commands appear to be accepted.

I have the same issue. All Lumagen commands work fine except for powering on and off which is hit and miss. I may have to go down the CYP IP to serial option.

 

[DaveN]

If you are contemplating an AVA remote and have a Lumagen, factor in having to purchase the CYP IP RS-232 box. Even with a brain, the AVA is unable to control the Lumagen via IR reliably.

 

[thrillcat]

If you are contemplating an AVA remote and have a Lumagen, factor in having to purchase the CYP IP RS-232 box. Even with a brain, the AVA is unable to control the Lumagen via IR reliably.

I have no issues with IR and the Lumagen, but will still likely buy the translator. Jim has been in touch with AVA to coordinate development of an official driver for the Lumagen, too.

 

[DaveN]

I have no issues with IR and the Lumagen, but will still likely buy the translator. Jim has been in touch with AVA to coordinate development of an official driver for the Lumagen, too.

What type of driver? IP?

 

[thrillcat]

What type of driver? IP?

Lumagen has no IP address. It will still require the serial to IP controller, but should include 2-way comms similar to the UC integration that’s been built.

 

[JohnA]

I have no issues with IR and the Lumagen, but will still likely buy the translator. Jim has been in touch with AVA to coordinate development of an official driver for the Lumagen, too.

Glad they are working together with the possibility of a Lumagen RS232 template. I hope they improve the IR driver as well as that is what most users will be using.

 

[DaveN]

My system includes 2 AVA remotes and 1 brain. My original remote is local only while the second is connected to the brain. Both have lost connection to my AppleTV.

I have been unsuccessful in reconnecting AppleTV to either brain system or other local remote. AVA sees the device when I rediscover it. I then try to reconnect. The pairing code shows up on my screen, I enter it, and AVA says it can’t find the device. Suggestions?

Thanks,

Dave