RAAT Session failed to initialize with latest RoPieee version and older. USB SMSL DAC or AMP

Audio Gear Talk RoPieee
1

trying to enable my SMSL DAC device connected via USB via Raspberry Pi running RoPieee. but it gets stuck is enabling state forever.

tried with pi3 and pi5 and continues to run into the same error where the server just says

03/21 12:52:50 Trace: \[Broker:Transport\] \[SMSL USB AUDIO\] \[raatclient\] Initializing RAAT session
03/21 12:52:50 Trace: \[Broker:Transport\] \[SMSL USB AUDIO\] \[raatclient\] Loading script raat.dat:base.lua as module base \[1088 chars\]
03/21 12:52:50 Warn: \[Broker:Transport\] \[SMSL USB AUDIO\] \[raatclient\] raat.dat:base.lua failed: Result\[Status=InvalidCodeSignature\]
03/21 12:52:50 Warn: \[Broker:Transport\] \[SMSL USB AUDIO\] \[raatclient\] RAAT Session failed to initialize
03/21 12:52:50 Trace: \[Broker:Transport\] \[raatserver\] \[SMSL USB AUDIO\] client connection failed. Retrying in 1125ms
03/21 12:52:52 Info: \[Broker:Transport\] \[raatserver\] \[SMSL USB AUDIO\] connecting (attempt 4)
03/21 12:52:52 Trace: \[Broker:Transport\] \[SMSL USB AUDIO\] \[raatclient\] Initializing RAAT session
03/21 12:52:52 Trace: \[Broker:Transport\] \[SMSL USB AUDIO\] \[raatclient\] Loading script raat.dat:base.lua as module base \[1088 chars\]
03/21 12:52:52 Warn: \[Broker:Transport\] \[SMSL USB AUDIO\] \[raatclient\] raat.dat:base.lua failed: Result\[Status=InvalidCodeSignature\]
03/21 12:52:52 Warn: \[Broker:Transport\] \[SMSL USB AUDIO\] \[raatclient\] RAAT Session failed to initialize

but from my phone or tablet roon client, the roon USB SMSL device from ropieee is constantly stuck in “enabling” state.

image
image598×247 9.95 KB

I tried older versions of RoPieee and it also had the same issue. I remember using RoPieee fine last year with the same equipment but having issues this week.

2

Are you running the latest Roon Bridge with an earlier version of Roon Server? (This type of thing enabling issue can happen if the bridge is newer than the server).

3

thank you James.

the server is earlier than the bridge. I don’t want to update the roon server if possible. I can downgrade the bridge no problem. but any trick I can use to nail down the correct build version of the bridge (ropieee)?

image
image604×175 12.7 KB

image
image596×160 10.6 KB

4

Why? You’re running Roon 2.0, so why mot ise build 1641? How do you plan to downgrade Roon Bridge on Ropieee? The older binary is no longer available, and a fresh install of Ropieee downloads the latest version.

5

I see thank you for the help here. anychance I can track down older versions of ropieee that might have the older bridge binary?

6

RoPieee doesn’t include the bridge binary. It only downloads the latest bridge.

7

I see that’s a big information for me. so even older ropieee versions will have the same issue unless I update the server.

8

Correct. .

9

@trap_haus What is the motivation not to upgrade your Roon Core to the latest version? The latest version has, according to me, only advantages over older versions. I am curious to understand.