Stable release 3.107 (2021/05/08)

8525f17895b88840

This is after working well, turning DAC off, turning it back on after an hour. High temperature, not showing up in Roon.

Checked again that rebooting NUC doesn’t do anything.

I want to add my 2 cents that after this last update that I must restart the RoPieee pie each morning as it is not recognized when I turn on my integrated app. For months I turn off the Pie by touching the power sign on the screen and then shut down my amp. When I start my amp and start Roon the bridge would show. Now I start my amp and nothing shows in Roon. Restarting core didn’t help. I have only had success when rebooting the RoPieee. Thanks!

HI @spockfish I’m having problems with a brand new rpi4, no hat - never been connected to roon. I cannot get it to show up as an endpoint. I’ve reimaged a few times, rebooted, tried wireless, and ethernet as we well as XL, and small Ropieee and the 3.109 beta with the same result

A few of my other devices updated with no issues.
My new device will show the airplay endpoint but not the roon endpoint.

Log: 3439ecfd044ba7e6

Weird stuff. Your logs seem totally fine. Furthermore the last release was fairly ‘boring’, so nothing remotely related to USB/power mgt/kernel stuff has happened.

One more thing: can you test this if this is also the behaviour when running on cable in stead of wifi?

Thanks

Hi,

No HAT connected and no USB DAC connected (that is powered on). Hence it does not show up in Roon.

Thanks

Same with cable plugged in. Do I need to deactivate WiFi in the Pi though? 57e9e4c7919d278f

yes please do.

Harry @spockfish, an interesting thing happened to one of my displays last night: the clock “froze”, but otherwise the pi seemed okay in the morning. Rebooting fixed it, but in case the logs have anything of interest to you:

faea145555f1b177

Thanks as always. No response necessary, as this is FYI only.

Nathan

Same on the cable. 92c3d42468f30c9c.

Happy to skip this release, try the new kernel, in case nothing obvious jumps out to you.

I’ve also experienced my RPi4 not being recognised (USB) - rebooting the It does the trick.

EDIT: lost again this morning requiring another reboot. In fact merely switching off my DAC is enough to require another reboot.

1 Like

I wasn’t clear - yes it was plugged in to a DAC but I didn’t troubleshoot that connection. It was a bad USB cable, replaced and back in business. Thank you for your help!!

I’m having this issue too. I power off the SMSL Sanskrit DAC at the end of the day and leave the RPi4 running. Next morning it doesn’t appear in Roon. A reboot of the Roon core didn’t fix it but a reboot of the Pi did. Length of time between power off and power on doesn’t seem to matter - Ropieee doesn’t appear in the audio zone list.

Hmmm this is annoying. Nothing fancy has changed in the area of USB and furthermore I’ve not run into this issue myself.

I’ll check the versions of RoonBridge.

Harry,

If it’s of any assistance, here’s how things look on Roon’s end when I power cycle the DAC (on 3.107).

It seems – to my untrained eye – that RnetJsonClient times out when trying to enumerate devices, and goes into a endless retry loop.

05/13 15:01:17 Info: [stats] 1406mb Virtual, 697mb Physical, 241mb Managed, 0 Handles, 62 Threads
05/13 15:01:27 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection.
05/13 15:01:27 Warn: [rnet/RnetJsonClient] error writing to connection
05/13 15:01:27 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] lost client connection. Retrying
05/13 15:01:27 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] connecting (attempt 1)
05/13 15:01:27 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] connected
05/13 15:01:27 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
05/13 15:01:31 Trace: [roonapi] [apiclient 127.0.0.1:51862] CONTINUE Changed {"controls_changed":[{"control_key":"10","display_name":"Living room - Listen to Roon","supports_standby":true,"status":"selected"}]}
05/13 15:01:32 Info: [stats] 1406mb Virtual, 697mb Physical, 241mb Managed, 0 Handles, 61 Threads
05/13 15:01:37 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection.
05/13 15:01:37 Warn: [rnet/RnetJsonClient] error writing to connection
05/13 15:01:37 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] lost client connection. Retrying
05/13 15:01:37 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] connecting (attempt 1)
05/13 15:01:37 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] connected
05/13 15:01:37 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
05/13 15:01:40 Trace: [broker/accounts] [heartbeat] now=13/05/2021 12:01:40 nextauthrefresh=13/05/2021 12:36:41 nextmachineallocate=13/05/2021 12:21:40
05/13 15:01:47 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection.
05/13 15:01:47 Warn: [rnet/RnetJsonClient] error writing to connection
05/13 15:01:47 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] lost client connection. Retrying
05/13 15:01:47 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] connecting (attempt 1)
05/13 15:01:47 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] connected
05/13 15:01:47 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
05/13 15:01:47 Info: [stats] 1406mb Virtual, 698mb Physical, 242mb Managed, 0 Handles, 60 Threads
05/13 15:01:56 Trace: [dbperf] flush 0 bytes, 0 ops in 29 ms (cumulative 3163720 bytes, 1327 ops in 9581 ms)
05/13 15:01:57 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection.
05/13 15:01:57 Warn: [rnet/RnetJsonClient] error writing to connection
05/13 15:01:57 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] lost client connection. Retrying
05/13 15:01:57 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] connecting (attempt 1)
05/13 15:01:57 Trace: [raatserver] [RaatServer ropieee @ 10.0.1.158:34809] connected
05/13 15:01:57 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
05/13 15:02:02 Info: [stats] 1406mb Virtual, 698mb Physical, 257mb Managed, 0 Handles, 59 Threads
05/13 15:02:07 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection.
...

Hi Harry,

My Pi 3 updated with 3.107, the USB maybe appear for second in Roon then disappeared, reboot Roon core and Pi didn’t help, can you take a look of the log?

00000000b70f1639

Yes this is RoonBridge. Hmmmm… weird. We need to ask @support to have a look what’s going on.

So @pva is this wireless or wired?

Hi @spockfish I have two logs for you if they will help.

This is log from when I started my DAC and nothing came up: 3bdfab623f064716

This log is post reboot when it is working: 8572ee5b26bbd76a

Mine is wireless.

Where’s the identifier?

The difference in the RoonBridge logs are there. Can’t just think of what has caused this…