Remote mayhem with two Devialet Experts

[amaynard]

Anyone else had issues with remotes when running two Devialet experts in adjacent rooms?

I've just purchased a 120 for a second system, and have been using an Expert 200 for the past few years. However, the remotes do not uniquely pair and stay paired.

I've had various mis-pairings occur - the most common being that both remotes pair with the same amp (which is incredibly frustrating as you're trying to control the amp in one room, and whoever is listening in the other room has their amp volume/input changing outside their control)

I've also had remotes pair, then lose their pairing.

What I haven't managed to achieve is each amp with its own uniquely paired remote.

There must be a workaround to this - how otherwise do dealers demo multiple amps in the same facility.

So, the plot thickens here, and lit looks like there may be a fundamental design flaw in the original Expert amps.

I reached out to Devialet for advice on the issue above, and am still in conversation with them, but this is where' we're at at the moment:

A Possible Configurator Fix

It was suggested I try setting each amp to accepting two remotes in the configurator.

All this did was ensure that both amps were controlled by both remotes -- slightly irritating when someone upstairs is changing your inputs and volume while you're trying to listen downstairs!!

Re-iterating the Problem

To help Devialet understand the nature of the problem, I sent them the attached diagram - I can't be the only person in the world who's had two Experts set up like this!

The Response

The response I got was this:

No solution for this on the non-Pro range.
The pairing can be locked on the Pro range but not on the Expert classic one.

Hope it's clear for you.

In other words, it looks like there is no way to have two fully functioning Expert/remote setups within a few meters of each other.

I'm still trying to get my head around the possibility that one of the most innovative audio companies in the world made such an embarrassingly basic design error, and hoping that there's something that's being missed here ... I haven't given up yet!