Audio Zone deleting... and playback reliability issues!? đŸ˜©

Intel NUC i5 Roon Core Machine

Networking Gear & Setup Details

BT Broadband and router, network switch and Ethernet to Devialet, using Devialet Air

Connected Audio Devices

I have only just Re-started using Roon again
after a couple of years with no setup, etc


Description of Issue

Hi, my internet speed seems fine, but my system reliability to actually stream music is very poor.
It seems that it either states that my Devialet is already in use, or that I may have two
or more Devialet outputs
I want to DELETE (not simply ‘disable’) all possible ambiguity in the system, but it seems there is no simple answer?! Whyever not, as surely we should be able to delete unwanted items!?

HB. This is my very first question here
please help?
Thanks in advance, Ian




1 Like

PS. It appears I may seem to have three Devialet item options with identical IP addresses ending in 249?
I wish to delete two of them; how can I do this?

The Devialet appearing several times in the Audio Settings is not an issue. If a device supports more than one option, e.g., Roon Ready, Devialet AIR, and Chromecast or whatever, it will show up in Settings > Audio for each of them. One user might prefer Devialet AIR and another Roon Ready, for instance.

You can’t delete them because then how would you later switch to another variant if you want? This is the Audio Settings configuration, it shows everything that is available from your devices. Just don’t enable the variants you don’t need and forget about it.

Any device / variant that you enable here in the Audio Settings you can then choose from the zone output button. If you enable two variants for your device, you can choose either as a zone. Should normally not hurt but clutters up the zone menu.

The actual issue you are having is most likely a network configuration issue. See for instance this thread about “Device in use” errors with Devialet:

Hi there,
Thanks for this reply and help.
I get the idea, however the Roon selection for connectivity devices doesn’t actually seem to recognise my Devialet device name properly
or consistently.
This exact system has worked properly on several occasions, but when I restart, it often fails.
Thanks again, Ian

Did you check the older thread about a similar issue that I linked? I.e. did you verify if your Devialet is also configured with a fixed IP address like in that thread?

1 Like

Hey @Ian_Gamble,

I wanted to check in on this thread to see if you were still running into issues? If so, did you test out @Suedkiez’s helpful next step in assigning a fixed IP?

I’ll be on standby for your reply. :+1:

In the other thread the Devialet had a fixed IP and seemingly was therefore not able to work properly on the network, and that led to the same error message as in this thread. The solution in the other thread was to switch it to use DHCP instead.

The cause may differ here, but apparently network problems on the Devialet can lead to the error message we are seeing here. I just wanted to rule out a static IP problem first :slight_smile:

Hi there, I am still getting intermittent issues with the connection to my Devialet using the NUC. I’m assuming it is some sort of network issue, as you suggest
but I am no expert and I am at a loss.
The Devialet should have a fixed IP address surely
and so should the Roon Core, etc?
On some occasions (relatively few) the correct Devialet name is recognised and plays flawlessly, but mostly the correct named Devialet is not recognised, another is somehow substituted
and the bloody thing will not play at all.
Sometimes I get as far as being able to select the correct device name
and it may even start playing for a few seconds, but then it stops and gives me the message that no zone is chosen!? Surely the whole thing should work more reliably and simply than this!? Why can I not delete all incorrectly named devices!?





Ian’s Devialet 1000 Pro is the ONLY device that should be recognised, so why the heavens can I not get rid of the others!?

I definitely need more help with figuring this out. Thankfully I have a CD player and turntable that always work reliably through the Devialet.

Any simplified and clear advice steps gratefully received by this network semi-Luddite. :weary::crossed_fingers:

Normally not. By default, routers hand out IP addresses by using the DHCP service. Essentially, when starting a device it sends a broadcast on the LAN, saying “hey I’m here, can I have an IP address?” and the router assigns one.

This is the safest way because every IP address must only exist once on the network, else there are collisions, i.e., some other device sends a packet to an IP address on the network and two other devices answer instead of one. Then each of these devices with colliding addresses will receive only a part of the packets and things go very wrong.

When using DHCP, the router is responsible for assigning unique addresses and this works essentially always.

When configuring fixed addresses directly on the devices, the user is responsible for giving each device a unique address and it’s easy to make errors, forget to update addresses if something changes, etc. It’s also useless work.

When one device has a fixed address while DHCP is enabled on the router, the router does not know about this and might assign the same address to another device, hence creating a collision. (In this case, most routers allow to reserve this address to avoid assigning it, but that’s often forgotten by the user).

Such collisions typically lead to intermittent errors that are difficult to track down. The router’s DHCP typically assigns IP address from a range, and most of the time things might work because the router doesn’t happen to choose an address that is already occupied by one device as a fixed IP. And once in a while it randomly chooses the occupied one and things break.

In short, everybody should be using DHCP on the router and not fixed addresses that are assigned on individual devices, unless

  • one is a network admin whose job is to manage complex networks and knows exactly why they need a fixed address on a device.
  • one knows for sure that a device has a broken DHCP service and needs a fixed address. This is very rare and in this case the address MUST be reserved on the router (i.e., excluded from the assignable addresses)

This intermittent failure mode sounds a lot like what you are experiencing. Hence my recommendation to check if the Devialet might have a fixed address configured (or possibly some other devices on your network). In the thread I linked further up, having a fixed address on the Devialet led exactly to the error message that you also experienced, “Device in use”.

If the Devialet has a fixed address configured, change it to using DHCP. (And all other devices if you did this anywhere. Alternatively be SURE that fixed addresses you assigned to devices on the network are ALL correct and reserved on the router).

If the Devialet is already configured to use DHCP, we have at least ruled out one possibility.

Hi again,

Well
 I sort of understand what you mean. Do you have any idea how I check or if necessary, change to DHCP on the Devialet?

I checked the thread you mentioned, but unless I missed something crucial, it doesn’t really give me as much information as I think I need? :crazy_face:

The solution I found is to change the Ethernet setting in the Devialet to DHCP “on” (no fixed IP).

I can take a look in the Devialet Configuration settings online, but last time I couldn’t seem to find anything


Thanks again,

Yes it doesn’t mention how to change the setting :slight_smile:

Sounds like it was really set to fixed, yes? In this case, setting DHCP to “on” is probably all you need to do. And restart it.

You could also go to the admin web page of your router. Normally it will list all devices that are on the network, with the IP for each. Check that they are all different. Probably you can also see if the IP was assigned by DHCP, which it should.

Hi again,

I have checked in the Devialet Configuration and for the Ethernet I see the following:

Add images

DHCP is ticked as ON

However
 there is a background fade as shown in the attached photo:

Fixed IP 192.168.0.77

Network mask. 255.255.255.0

Gateway 192.168.0.1

DNS

Seems like the screenshot didn’t upload correctly

Hi, it seems to be an issue at the moment. :thinking:

Sorry for late answer, I never see notifications for your replies, it seems that you are clicking the reply button for the thread, not the one for my messages. But I have set the thread to “Watching” now, so I’ll see them from now on.

The settings for DHCP are looking good. If they always were like that and rebooting didn’t help, this seems not the issue then. But probably nevertheless some other networking issue, I would guess

Thank you for all the help on this @Suedkiez!

After re-reading this thread @Ian_Gamble, I’m not sure if we’ve tested running things without your network switch involved. Are you able to hardwire your core and devialet directly to your router?

With that, I’d also like to see how things run on a fresh database (if the above proves no changes.) Steps to follow below:

  • Make a fresh backup of your current database
  • Stop RoonServer from running in ROCK’s WebUI
  • Navigate to your ROCK’s Database Location
  • Find the folder that says “RoonServer”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Restart the RoonServer in the WebUI to generate a new Roon database folder
  • On the Roon Remotes, press “Use another Core” and connect to the new database

Let me know if things run smoother before restoring from your recent backup. :+1:

1 Like

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.