Devialet Phantom II uncertified in Roon after firmware update 2.19.1 (ref#D8MQ9F)

[Aptitude8832]

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

I have a Deviatet Phantom II 98dB which has worked fined as a Roon Ready device until recently. Last week, I upgraded its firmware to the latest version (2.19.1) and it now shows the device as "uncertified" in the Roon app (Audio section of the settings). I cannot add this device back to Roon and cannot play over RAAT. Airplay2 works fine.

Describe your network setup

Not relevant here since my setup was working fine before the Devialet update.

[vadim]

Hello @Aptitude8832

Thank you for your message.

Can you please use the directions found here and send over a set of logs to our File Uploader? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!

[Aptitude8832]

Hi @vadim - log files have been uploaded. Thanks!

[vadim]

Hello @Aptitude8832

Thank you for uploading the logs.

It’s strange, but in the logs I see that your device was correctly identified as the Roon Ready device.

10/05 13:10:56 [Local 10/05 15:10:56] Trace: [raat] [Devialet Phantom 98 dB @ 192.168.1.137:41177] connecting (attempt 1)
10/05 13:10:56 [Local 10/05 15:10:56] Trace: [raat] Endpoint discovered: Sooloos.Audio.Raat.DiscoveryData
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat] Initializing RoonReady Device
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     Address:         192.168.1.173
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     Port:            41575
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     IsDev:           False
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     UniqueId:        aba56dbe-781e-4cd9-ad5c-9e20ed91bc73
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     ProtocolVersion: 3
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     Version:         3.1.2
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     RaatVersion:     1.1.43
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     Model:           Phantom Ultimate 98 dB
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     Vendor:          Devialet
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     VendorModel:     Devialet Phantom Ultimate 98 dB
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     Serial:          U24A30071LP52
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     OutputName:      
10/05 13:10:56 [Local 10/05 15:10:56] Info: [raat]     AutoName:        
10/05 13:10:56 [Local 10/05 15:10:56] Info: [devicedb] [autodetect] Match DeviceAutodetectData[Type=RoonReady Vendor=Devialet Model=Phantom Ultimate 98 dB] => Devialet Phantom Ultimate 98 dB
10/05 13:10:56 [Local 10/05 15:10:56] Trace: [raat] [Devialet Phantom Ultimate 98 dB @ 192.168.1.173:41575] connecting (attempt 1)
10/05 13:10:56 [Local 10/05 15:10:56] Trace: [devicemanager/sonos] FOUND Device IP=192.168.1.138 UDN=uuid:RINCON_C43875BE46A501400 Manufacturer=Sonos, Inc. ModelName=Sonos Arc ModelNumber=S19

Can you try clearing your endpoint cache? You can do so using the following steps:

• Create a fresh backup
• Stop Roon (or RoonServer)
• Find and open your Roon or RoonServer folder
• Navigate to /Roon/Database/Registry/Core/
• Delete all files in this directory.
• Restart Roon
• Please let us know if this helps

Note: Deleting these files will

• Log you out of Tidal/Qobuz
• Delete your endpoint names.
• Delete saved DSP configs.

If this doesn’t help, please restore the backup you made before trying these steps.

[Aptitude8832]

Thanks @vadim, this fixed the problem!