Roon Core Machine
Roon Rock build 1148, 1167 and 1169 running on an Intel NUC8I5BEK
Networking Gear & Setup Details
Roon Rock is connected with LAN cable. Android remote are working on WiFI (Orbit)
Connected Audio Devices
NA
Number of Tracks in Library
22000 tracks
Description of Issue
Since build 1148 I have all kind of connection problem from android remotes to Roon Rock. Running latest OS en Roon version with UEFI. I have this message on one Android device at this moment, while it is working on another. But this is completely random. If I try it a few times it will connect, but it won’t randomly when I try to start the app on the same device. Connect with “help” and IP address doesn’t work either. So completely lost with no android remotes working!
Using Roon Remote from Wiindows 11 is working fine at the same moment.
Just updated ROCK and all apps to 1167/69 and problem is still present unfortunately.
By the way I also had the issue with Roon Server Software not running, but solved this with removing the database on the NUC and restored everything from last night backup. I just noticed the workaround with removing the bits file, but solved it myself already. Restoring from backup also solved the issue for me.
This is now going on all android remotes. Only Windows remote is still working as it should. Why am I getting a red dot and can’t I connect from Android Remote app?
RoonARC is working as it should.
In logfile RoonServer_log.txt on NUC I can find below error message of the Android Remotes.
11/30 23:08:43 Trace: [raat] RAATServer discovered: RaatServer Pixel 7 @ 192.168.0.21:9200
11/30 23:08:43 Info: [raatserver] GOT SERVER 4f07a31c-7d3d-3694-b2e0-744170de1583::4f07a31c7d3d3694b2e0744170de1583 @ 192.168.0.21:9200 Pixel 7 PROTOVER=1 RAATVER=1.1.39
11/30 23:08:43 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.21:9200] connecting (attempt 1)
11/30 23:08:43 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.21:9200] connected
11/30 23:08:43 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
11/30 23:08:43 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"device_id": "default", "is_system_output": true, "type": "android", "name": "Default Output", "auto_name": "Pixel 7", "auto_enable": true}]}
11/30 23:08:43 Trace: [devicedb] [autodetect] No Match for DeviceAutodetectData[Type=Local Model=Default Output]
11/30 23:08:43 Info: [raatserver] GOT DEVICE 4f07a31c7d3d3694b2e0744170de1583::default Type=android Name=Default Output
11/30 23:08:45 Trace: [remoting/brokerserver] [initconn 192.168.0.21:48904=>192.168.0.6:9332] Connected
11/30 23:08:45 Warn: [remoting/brokerserver] [initconn 192.168.0.21:48904=>192.168.0.6:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: f17c95ab-a8bc-4abe-96f9-fbd2fd133441
at Sooloos.Broker.Distributed.InitConnectionV2.Go()
11/30 23:08:46 Trace: [remoting/brokerserver] [initconn 192.168.0.21:48906=>192.168.0.6:9332] Connected
11/30 23:08:46 Warn: [remoting/brokerserver] [initconn 192.168.0.21:48906=>192.168.0.6:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: f17c95ab-a8bc-4abe-96f9-fbd2fd133441
at Sooloos.Broker.Distributed.InitConnectionV2.Go()
11/30 23:08:47 Trace: [remoting/brokerserver] [initconn 192.168.0.21:48908=>192.168.0.6:9332] Connected
11/30 23:08:47 Warn: [remoting/brokerserver] [initconn 192.168.0.21:48908=>192.168.0.6:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: f17c95ab-a8bc-4abe-96f9-fbd2fd133441
at Sooloos.Broker.Distributed.InitConnectionV2.Go()
11/30 23:08:49 Trace: [remoting/brokerserver] [initconn 192.168.0.21:48910=>192.168.0.6:9332] Connected
11/30 23:08:49 Warn: [remoting/brokerserver] [initconn 192.168.0.21:48910=>192.168.0.6:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: f17c95ab-a8bc-4abe-96f9-fbd2fd133441
at Sooloos.Broker.Distributed.InitConnectionV2.Go()
I can see the Pixel 7 in the device overview but in a strange way and it is not connecting.