At 20:46 (CET Daylight saving time) yesterday, my Lyngdorf 3400 / Nucleus ran into communication trouble again after a few days of wonderful, trouble-free operation.
Nucleus reports that it cannot set 3400 to the ROON Ready input. However, the 3400 was already set to ROON Ready input, because Nucleus had done that, since I had been playing via Nucleus for a while. This took place when I wanted to listen to another piece of music (the current had ended).
I did what you suggested and switched to the SONOS zone to play the piece of music that did not work on 3400 to see if contact could be established. It could. On the next occasion of communication problems (a few minutes later) I switched to SONOS, who had been playing all the time, but I saw that Nucleus briefly reported trouble finding the SONOS zone and then continued playing the music as it was supposed to. I cannot say whether there was a brief drop-out during the time the warning was displayed, I was in another room.
Rebooting 3400 is normally the cure here, so it was yesterday. But, on one occasion, the 3400 recovered by itself (assuming 3400 is the suspect here). The initial volume setting on 3400 was -23dB. Upon recovering, ROON Remote reported a volume setting of -50dB(!). This is strange given the fact that the default start-up volume setting is -40dB, as set by me.
The volume, however, was acoustically still -23dB until I started to adjust the volume of the 3400 by means of the ROON Remote. Then it suddenly dropped to -50dB acoustically, thereby complying with the shown setting and I was able to set it back to -23dB by using the ROON Remote. This has happened a few times before.
One more thing here. Lyngdorf has an app that lets you control volume, input source, voicing etc. It even provides access to the web interface of the 3400, which is a convenient tool for setting up the fairly complex system.
If I open the app to use it to control input source and volume, then put my phone on the coffee table to listen to my choice, and then log into my phone again to adjust something, it will in most cases tell that it is unable to find 3400. It asks me to confirm which device I am looking for and presents me with alternatives. The alternatives boil down to 1, which is my 3400. The identity seems to be its MAC address, but I am not 100% sure and the Lyngdorf documentation is among the worst on the market, so it is difficult to find out.
On a few occassions I may find the 3400, but in almost all cases there is nothing else to do than to close the app and restart it. This app failure does not affect the streaming, which goes on completely undisturbed, be it from Sonos (which was previously connected to the 3400), the built-in internet radio of 3400 or a NAS-disk I used to have connected.
If I enter the web interface from the Lyngdorf app, it opens in a browser, which stays open at all times (it appears to have no relation to the app). Even if I do something else with my phone or tablet, the web interface seems not to be prone to this communication problem. If I open the Lyngdorf app I will in most cases run into the communication problem again, while the browser with the setup still works perfectly fine.
I have, through the setup of the 3400, granted permission for streaming services to control source input setting, volume and to have the 3400 being switched on from stand-by.
Should I disable these permissions? Will ROON Remote object if it can’t find the state of the 3400 input source and volume, when communication between the two goes via ethernet and not USB?
IMHO, it should work nicely without these permissions granted. After all, they have learned to know each other by the time I established the zones. Could this step make them stop having these disagreements?
I will try this tonight.