Companion closed down when input was enabled

[Mikeeo]

I have experienced exactly this issue. (you should be able to find historic posts on this subject in the “Slave inputs” thread, and elsewhere) I have sent a number of queries to Devialet, and even spoke to Thierry in person. I received a number of suggestions from Devialet, none of which worked, and then ultimately received a correspondence from Devialet advising that there is indeed a bug in the dual mono configurator that they were working on to fix. My last query to Devialet on the subject remains "open".

It might actually be interesting to send a query to Devialet and see if they revert directly by admitting that they have an issue with the Configutator, or maybe we each get two or three delaying responses first before an admission that Devialet are not perfect.

I am assured that they are working on a solution. However, I first raised this issue about three months ago and still no solution, I would have thought that this would be a relatively easy fix?

To be honest, I had more or less forgotten about this one! Although, I do have a nice CD player sat on my rack, but not actually connected to anything, while I wait for Devialet to sort this one out!

Dear Confucius,

Well good to hear that I am not alone! I really would like that analogue input to work, as I run the analogue 2CH music out signal from the Oppo player which I found better than the digital one as suggested by kind spirits here on the forum.
How on earth can such a simple change like enabling the ethernet input on the master create this bug??? Even more strange, companion sees the input but then closes down the unit.

Tired/Mike