Roonbridge disappears

Hi,
my roonbridge constantly disappears … i have no clue why… its running on arm7 pc, here is what i found in the log (tail -f )

roonbridge_log.txt

6/23 09:11:12 Trace: [rnet/RnetJsonServer] [client 10.0.1.48:51160] disconnected
06/23 09:28:54 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:37498] GOT {"request":"updates_subscribe"}
06/23 09:28:54 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:37498] SENT NONFINAL {"status":"Success","updates":{"is_supported":true,"status":"U
pToDate","progress":null,"current_version":{"machine_value":100700571,"branch":"stable","display_value":"1.7 (build 571) stable"},"available_vers
ion":null,"update_mode":"AutoCompatible"}}
06/23 09:52:32 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:37498] disconnected
06/23 10:35:41 Debug: ScanInBackground timer callback. serial: xxx, userid: , product: RoonBridge, branding: , d
esired_branch: stable, version: 1.7 (build 571) stable
06/23 10:35:41 Debug: [base/updater] Checking for updates: https://updates.roonlabs.com/update/?v=2&serial=xxx
serid=&platform=linuxarmv7hf&product=RoonBridge&branding=&curbranch=stable&version=100700571&branch=stable
06/23 10:35:41 Debug: [appupdater] Update not needed
06/23 11:35:53 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:40742] GOT {"request":"updates_subscribe"}
06/23 11:35:53 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:40742] SENT NONFINAL {"status":"Success","updates":{"is_supported":true,"status":"U
pToDate","progress":null,"current_version":{"machine_value":100700571,"branch":"stable","display_value":"1.7 (build 571) stable"},"available_version":null,"update_mode":"AutoCompatible"}}
06/23 11:52:03 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:40742] keepalive timeout. Closing connection
06/23 12:31:20 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:41748] GOT {"request":"updates_subscribe"}
06/23 12:31:20 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:41748] SENT NONFINAL {"status":"Success","updates":{"is_supported":true,"status":"UpToDate","progress":null,"current_version":{"machine_value":100700571,"branch":"stable","display_value":"1.7 (build 571) stable"},"available_version":null,"update_mode":"AutoCompatible"}}
06/23 12:37:43 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:41748] disconnected
06/23 17:01:52 Trace: [push] short read from connector (1)
06/23 17:01:52 Trace: [push] retrying connection in 82127ms
06/23 17:03:19 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
06/23 17:03:19 Trace: [push] request to manager resulted in unsuccessful response: {"status":"NotAvailable"}
06/23 17:03:19 Trace: [push] retrying connection in 40479ms
06/23 17:04:10 Warn: Error in web request https://push.roonlabs.com/push/1/connect: NetworkError (Aborted.)
06/23 17:04:10 Trace: [push] request to manager failed
06/23 17:04:10 Trace: [push] retrying connection in 265877ms
06/23 17:08:36 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
06/23 17:08:36 Trace: [push] request to manager resulted in unsuccessful response: {"status":"NotAvailable"}
06/23 17:08:36 Trace: [push] retrying connection in 318382ms
06/23 17:13:55 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
06/23 17:13:55 Trace: [push] request to manager resulted in unsuccessful response: {"status":"NotAvailable"}
06/23 17:13:55 Trace: [push] retrying connection in 332424ms
06/23 17:19:28 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
06/23 17:19:28 Trace: [push] connecting to 34.74.171.1:9200
06/23 17:19:28 Trace: [push] connected
06/24 10:35:41 Debug: ScanInBackground timer callback. serial: xxx, userid: , product: RoonBridge, branding: , desired_branch: stable, version: 1.7 (build 571) stable
06/24 10:35:41 Debug: [base/updater] Checking for updates: https://updates.roonlabs.com/update/?v=2&serial=Xxxxx&userid=&platform=linuxarmv7hf&product=RoonBridge&branding=&curbranch=stable&version=100700571&branch=stable
06/24 10:35:42 Debug: [appupdater] Update not needed
06/24 21:30:50 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:33312] GOT {"request":"updates_subscribe"}
06/24 21:30:50 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:33312] SENT NONFINAL {"status":"Success","updates":{"is_supported":true,"status":"UpToDate","progress":null,"current_version":{"machine_value":100700571,"branch":"stable","display_value":"1.7 (build 571) stable"},"available_version":null,"update_mode":"AutoCompatible"}}
06/24 21:44:28 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:33312] disconnected
06/24 21:48:57 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:33848] GOT {"request":"updates_subscribe"}
06/24 21:48:57 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:33848] SENT NONFINAL {"status":"Success","updates":{"is_supported":true,"status":"UpToDate","progress":null,"current_version":{"machine_value":100700571,"branch":"stable","display_value":"1.7 (build 571) stable"},"available_version":null,"update_mode":"AutoCompatible"}}
06/24 21:54:32 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:33848] disconnected


raatserver_log.txt

06/23 02:43:16 Trace: [raat_wrap] starting RAAT device
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] [10.0.1.44:59088] accepted connection
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [session] [10.0.1.44:59088] created: 0xb380deb0 (0xb38068d8)
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] new script with name=raat.dat:base.lua module=base
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [session] [10.0.1.44:59088] pre-loading lua module base
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] [10.0.1.44:59088] SENT[LL] [1] {"status": "Success"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] new script with name=raat.dat:dkjson.lua module=dkjson
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] new script with name=raat.dat:protocol.lua module=protocol
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [session] [10.0.1.44:59088] pre-loading lua module dkjson
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [session] [10.0.1.44:59088] pre-loading lua module protocol
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] [10.0.1.44:59088] SENT[LL] [2] {"status": "Success"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] [10.0.1.44:59088] SENT[LL] [3] {"status": "Success"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] new script with name=raat.dat:roon_tcp.lua module=(null)
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [session] [10.0.1.44:59088] executing lua script
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  [roon] clock socket listening on udp 0.0.0.0
:42718
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  [roon] audio socket listening on tcp 0.0.0.0
:43912
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  [roon] output info {"config": {"type": "alsa
", "device": "hw:CARD=WT04,DEV=0", "dsd_mode": "none", "force_max_volume": false, "name": "REIYIN Bluetooth Audio WT04"}, "alsa_device": {
"
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  [roon] volume info {"config": {"type": "alsa
", "device": "hw:CARD=WT04,DEV=0", "exclusive_mode": null}}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] [10.0.1.44:59088] SENT[LL] [4] {"status": "Success"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  GOT [2] {"request":"info"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  SENT [2] {"platform":{"uname":{"release":"3.
4.113-bananian","machine":"armv7l","sysname":"Linux","version":"#8 SMP PREEMPT Sat Nov 26 00:48:28 UTC 2016","nodename":"bananapi"},"os":"
l
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  GOT [3] {"request":"set_client_type","client
_type":"Roon"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  SENT [3] {"status":"Success"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  GOT [4] {"request":"subscribe_transport"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  GOT [5] {"request":"subscribe_controls","controller_id":"15619a4e-d715-4b42-83a9-702140b911e5"}
06/23 02:43:16 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb382ae94] [10.0.1.44:59088]  SENT [5] {"status":"Success","controls":{"volume":{"min":0.0,"type":"number","step":1.0,"max":100.0,"info":{"config":{"type":"alsa","device":"hw:CARD=WT04,DEV=0"}},"mute":false,"value
06/23 03:03:17 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 03:03:17 Trace: [raatmanager] stopping device REIYIN Bluetooth Audio WT04
06/23 03:03:17 Trace: [raat_wrap] calling force_teardown on output
06/23 03:03:17 Trace: [raat_wrap] stopping RAAT device
06/23 03:03:17 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [device] stopping server
06/23 03:03:17 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] [10.0.1.44:59088] destroying client
06/23 03:03:17 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [session] [10.0.1.44:59088] destroying session
06/23 03:03:17 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [device] run exited successfully
06/23 03:03:18 Trace: [raat_wrap] deleting device
06/23 03:03:18 Trace: [RAAT::REIYIN Bluetooth Audio WT04] deleting device
06/23 03:03:18 Trace: [RAAT::REIYIN Bluetooth Audio WT04] closing multicast
06/23 03:03:18 Trace: [RAAT::REIYIN Bluetooth Audio WT04] deleting server
06/23 03:03:18 Trace: [raat_wrap] deleting volume
06/23 03:03:18 Trace: [raat_wrap] deleting output
06/23 03:03:18 Trace: [raat_wrap] deleting transport
06/23 03:03:18 Trace: [raat_wrap] deleting log
06/23 03:03:18 Trace: [raat_wrap] freeing
06/23 03:03:18 Trace: [jsonserver] [10.0.1.44:45658] SENT [1] [nonfinal] {"status": "DeviceChanged", "device": {"device_id": "hw:CARD=WT04,DEV=0", "type": "alsa", "name": "REIYIN Bluetooth Audio WT04", "config": {"unique_id": "d0af64ab-3b63-f5e7-8397-8d1a24b01877", "volume": {
06/23 03:03:18 Trace: [jsonserver] [10.0.1.44:45658] SENT [2] {"status": "Removed"}
06/23 03:03:18 Trace: [jsonserver] [10.0.1.44:45658] SENT [1] [nonfinal] {"status": "DeviceRemoved", "device": {"device_id": "hw:CARD=WT04,DEV=0", "type": "alsa", "name": "REIYIN Bluetooth Audio WT04", "config": {"unique_id": "d0af64ab-3b63-f5e7-8397-8d1a24b01877", "volume": {
06/23 03:03:20 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 03:03:20 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 03:03:20 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 03:23:21 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 03:23:23 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 03:23:23 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 03:23:23 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 03:43:24 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 03:43:26 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 03:43:26 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 03:43:26 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 03:53:26 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 03:53:28 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 03:53:28 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 03:53:28 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 04:13:29 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 04:13:31 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 04:13:31 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 04:13:31 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 04:33:32 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 04:33:34 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 04:33:34 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 04:33:34 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 04:43:34 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 04:43:36 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 04:43:36 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 04:43:36 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 05:03:37 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 05:03:39 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 05:03:39 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 05:03:39 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 05:23:40 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 05:23:42 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 05:23:42 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04
06/23 05:23:42 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
06/23 05:43:43 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
06/23 05:43:45 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
06/23 05:43:45 Trace: [raatmanager/linux]       vendor=                               name=REIYIN Bluetooth Audio WT04


dmesg:
[386183.587348] usb 4-1: USB disconnect, device number 116
[386183.613564] ehci_irq: port change detect
[386184.045525] ehci_irq: port change detect
[386184.105592] The port change to OHCI now!
[386184.408476] usb 4-1: new full-speed USB device number 117 using sw-ohci
[386184.622331] usb 4-1: New USB device found, idVendor=0a12, idProduct=1004
[386184.642868] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[386184.661880] usb 4-1: Product: REIYIN Bluetooth Audio WT04
[386184.678516] usb 4-1: SerialNumber: ABCDEF0123456789
[386184.835048] input: REIYIN Bluetooth Audio WT04 as /devices/platform/sw-ohci.2/usb4/4-1/4-1:1.3/input/input621
[386184.870390] generic-usb 0003:0A12:1004.04D7: input,hiddev0,hidraw0: USB HID v1.11 Device [REIYIN Bluetooth Audio WT04] on usb-sw-ohci-1/input3
[386184.922077] generic-usb 0003:0A12:1004.04D8: hiddev0,hidraw1: USB HID v1.11 Device [REIYIN Bluetooth Audio WT04] on usb-sw-ohci-1/input4
[386785.254272] usb 4-1: USB disconnect, device number 117
[386785.280521] ehci_irq: port change detect
[386785.711087] ehci_irq: port change detect
[386785.771011] The port change to OHCI now!
[386786.073929] usb 4-1: new full-speed USB device number 118 using sw-ohci
[386786.287332] usb 4-1: New USB device found, idVendor=0a12, idProduct=1004
[386786.307493] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[386786.326280] usb 4-1: Product: REIYIN Bluetooth Audio WT04
[386786.342776] usb 4-1: SerialNumber: ABCDEF0123456789
[386786.494707] input: REIYIN Bluetooth Audio WT04 as /devices/platform/sw-ohci.2/usb4/4-1/4-1:1.3/input/input622
[386786.528872] generic-usb 0003:0A12:1004.04D9: input,hiddev0,hidraw0: USB HID v1.11 Device [REIYIN Bluetooth Audio WT04] on usb-sw-ohci-1/input3
[386786.572320] generic-usb 0003:0A12:1004.04DA: hiddev0,hidraw1: USB HID v1.11 Device [REIYIN Bluetooth Audio WT04] on usb-sw-ohci-1/input4

any idea here? thanks

Post in the support area and fill in the template it will give you.

Well first, what is the device that is actually running Roonbridge. Do you have REIYIN Bluetooth Audio WT04 plugged into the device and have you tried removing it and seeing if the issue resolves itself?

hi,
its running on http://wiki.banana-pi.org/Banana_Pi_BPI-M1%2B, bananian OS, yeah its REIYIN WT04 and i tried to remove and plug again… doesnt help. only reboot works ;-(

any update please?

As Ged said, it’s best to post requests for support in the Support category of the forum - that’s where Roon’s Support Team lives…

is it possible to move that thread there? thanks

I’ve done that - but you should now give full details of your setup: what is your Core, your Remotes, and your network. This will aid in diagnosis by the Support team. Thank you.

core latest release, remote - one described, network not important its not network issue.

Please see attached logs…

How do you then know it’s not a network issue?
Just fill in the details.

because its straight forward from the logs i provided there is no network connection with that issue.

Warn: Error in web request

Hi @John_Smith,

Looking at the log trace you provided, it’s definitely possible that this is stemming from a network-related issue. Can you provide some additional details about your setup? What is your networking setup? How are your devices connected? Are any other networked devices connected in the same way as this RoonBridge device?

@dylan i do not believe its network issue, device is reachable on local network 100% time. Device is connected to the main router via wifi card as all my devices.

Today it got disappear again… device was still on/ reached by network … so i executed the following commands and the endpoint shows up in roon devices again…

root@bananapi ~ # /etc/init.d/roonbridge status
[ ok ] RoonBridge is running.
root@bananapi ~ # /etc/init.d/roonbridge stop
[ ok ] Stopping RoonBridge:.
root@bananapi ~ # /etc/init.d/roonbridge start
[…] Starting RoonBridge:Daemon is running as PID 10988
. ok
root@bananapi ~ # ps uax | grep -i roon
root 1180 0.0 2.6 77212 26268 ? Sl Jun25 0:06 RoonBridge --debug --gc=sgen --server RoonBridge.exe
root 1508 0.1 6.6 118156 66080 ? Sl Jun25 12:28 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe
root 1514 0.0 0.0 1684 292 ? S Jun25 0:00 /opt/RoonBridge/Bridge/processreaper 1508
root 11019 0.0 0.0 3668 840 pts/0 S+ 13:01 0:00 grep --color=auto -i roon
root@bananapi ~ # kill -9 1180
root@bananapi ~ # kill -9 1508
kill: kill 1508 failed: no such process
1 root@bananapi ~ # ps uax | grep -i roon :frowning:
root 11027 0.0 0.0 3664 800 pts/0 S+ 13:02 0:00 grep --color=auto -i roon
root@bananapi ~ # /etc/init.d/roonbridge start
[…] Starting RoonBridge:Daemon is running as PID 11035
. ok
root@bananapi ~ # ps uax | grep -i roon
root 11035 0.0 0.0 1428 460 pts/0 S 13:02 0:00 /bin/sh /opt/RoonBridge/start.sh
root 11039 73.7 2.6 78904 26184 pts/0 Sl 13:02 0:05 RoonBridge --debug --gc=sgen --server RoonBridge.exe
root 11068 116 1.6 66192 16052 pts/0 Rl 13:02 0:05 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe
root 11074 0.0 0.0 1684 292 pts/0 S 13:02 0:00 /opt/RoonBridge/Bridge/processreaper 11068
root 11088 0.0 0.0 3664 800 pts/0 S+ 13:02 0:00 grep --color=auto -i roon

Hi @John_Smith,

It looks like you’re getting some network errors when trying to communicate with our servers as well.

Have you tried connecting the bridge via Ethernet as a test?
Do you have any firewalls which you can temporarily try disabling?

@noris, as it temporarily lost connection why its not reconnecting? Wrong app design?

No firewalls at all… i havent tried ethernet but can try it later on.

connected via ethernet it looks like it works… then i assume its bug in roon … as once connection drops for a short moment its not able to - reconnect properly, question is wh?

Is the WiFi communication on the same Bus for this device as Bluetooth? Maybe the Bus is being running out of power but on Ethernet it does not face this issue.

Have you tried bypassing the REIYIN Bluetooth adapter and try playing to the 3.5 output on the Banana Pi directly (via WiFi)?

well i connected external wifi card to it via ethernet, i was not using internal wifi.

also the external wifi card had its own power adaptor.

Have you tried using the internal WiFi at all? Maybe there is an issue with the external WiFi card.