Stable release 3.015 (2020/12/12)

First - Thank you @spockfish for Ropieee - its a fantastic little Rpi distro.

I had a problem with my SD card so I installed Ropieee on a new 8Gb card.
I had it setup and played on it last evening but today when I turn it on it doesn’t show up in Roon - and then again it show 30 minutes after it has been turned on. All my other zones appear in Roon.

While waiting on Roon to discover the Ropieee i can connect to the webserver on the Ropieee - but i doesn’t appear in the Roon client.
Earlier versions appeared after only 1 minute or two.

Is there a configuration parameter (Ropieee ping or Roon discover) I can set that gets Roon to discover the Ropieee faster?

I am using the nonXL Ropieee version on my Rpi 2 with Hifiberry Dac+XLR version with a Rpi display. It is connected via wired network. My roon server is on a Ubuntu 18.04.

Hi,

There is no parameter for discovery, as Roon takes care of that completely autonomously.
There is an important thing to realize: Roon discovery is not only a network thingie: if there is no audio output the device will not show up.

Can you send me feedback? The option can be found on the ‘advanced’ tab of RoPieee’s webpage. Ideally in the situation where the unit is not visible in Roon.

Thanks

Sorry misunderstod your message.
Feedback send

Uhhh no. Sorry. You need to hit the ‘Send Feedback’ button and give me the unique id that will be shown.

Hi Harry.
I think it’s a Roon server problem. I just turned my Sonos zones of and after 15 minutter the Roon server (seen through the Roon client) haven’t discovered it yet. I can try to play on the Sonos zone but I get the message that Roon cannot control the zone.
I will make a post about the server is very slow (30 minutes) to discover changes in the device infrastructure.

Well I was wrong. I tried to turn everything off and restart the Roon server process on my Ubuntu server.
The Sonos zones gets displayed 1 - 2minutes after they been turned on.
The Ropieee is not displayed now 10 minutes after it has been turned on.
So there is something wrong with the way the Ropieee is recognized by the Roon server.

The Roon server log show this messages that i can connect to the Ropieee (192.168.1.107):

12/15 09:40:11 Trace: [roonapi] [apiclient 192.168.1.107:49558] CONTINUE Changed {“zones_added”:[{“zone_id”:“16017dbc8a4ddfc21ccaaad10ad205243146”,“display_name”:“IN2023”,“outputs”:[{“output_id”:“17017dbc8a4ddfc21ccaaad10ad205243146”,“zone_id”:“16017dbc8a4ddfc21ccaaad10ad205243146”,“can_group_with_output_ids”:[“17017dbc8a4ddfc21ccaaad10ad205243146”],“display_name”:“IN2023”,“source_controls”:[{“control_key”:“1”,“display_name”:“Default Output”,“supports_standby”:false,“status”:“selected”}]}],“state”:“stopped”,“is_next_allowed”:false,“is_previous_allowed”:true,“is_pause_allowed”:false,“is_play_allowed”:false,“is_seek_allowed”:false,“queue_items_remaining”:0,“queue_time_remaining”:0,“settings”:
{“loop”:“disabled”,“shuffle”:false,“auto_radio”:true}}]}

and

12/15 09:53:44 Trace: [roonapi] [apiclient 192.168.1.107:49558] CONTINUE Changed {“message”:“Running (15)”,“is_error”:false}
12/15 09:53:47 Trace: [roonapi] [apiclient 192.168.1.107:49558] GOT com.roonlabs.transport:2/get_zones
12/15 09:53:47 Trace: [roonapi] [apiclient 192.168.1.107:49558] COMPLETE Success {“zones”:[{“zone_id”:“160178cfa19ab3203e415f5710259cbd7a55”,“display_name”:“Hanne Maries”,“outputs”:[{“output_id”:"17$
12/15 09:53:47 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
12/15 09:53:47 Trace: [push] connecting to 35.196.178.149:9200
12/15 09:53:47 Trace: [push] connected
12/15 09:53:57 Info: [stats] 1802mb Virtual, 958mb Physical, 436mb Managed, 0 Handles, 62 Threads
12/15 09:54:12 Info: [stats] 1805mb Virtual, 961mb Physical, 441mb Managed, 0 Handles, 62 Threads
12/15 09:54:27 Info: [stats] 1806mb Virtual, 962mb Physical, 442mb Managed, 0 Handles, 62 Threads
12/15 09:54:42 Info: [stats] 1810mb Virtual, 966mb Physical, 447mb Managed, 0 Handles, 63 Threads
12/15 09:54:44 Trace: [roonapi] [apiclient 192.168.1.107:49558] CONTINUE Changed {“message”:“Running (16)”,“is_error”:false}
12/15 09:54:57 Info: [stats] 1810mb Virtual, 966mb Physical, 447mb Managed, 0 Handles, 60 Threads

Hi Harry.
This is the ID: c52619f9c29732d2

RoonBridge reports keep-alive time-outs (with the server).
So this might be an infra issue.

Strange. They are on the same network - connected to the same switch. Up until a month ago everything worked fine and the network hasn’t changed - only the versions of RoonServer and Ropieee.
I must check if there is a cabling error

Have you changed the ssh login credentials?

root/ropieee

@Andreas_Philipp1 Thanks
@spockfish I have examined cabling and connections. I have discovered that if i start the Ropieee without the RPI 7" screen everything is working normally. The endpoint is ready within 1 minute after boot.

If the screen is powered on and connected the error appears.

The screen and the Rpi have separate power supplies

Apologizes, I’ve been tied up with EOY stuff at work, so haven’t had time to reply.

NO lights, and the display does not wake up, either. Not even the lights on the Ethernet port (I have the unit connected via Ethernet, FWIW). Pull the USB plug from the DAC for just long enough to clear the port and put it back in (so less than a second) and it starts to boot. Ethernet port lights up, screen comes on and gives the multicoloured square, etc.

I am using the official 3A power support for the RPi4, and the DAC is self-powered so shouldn’t be consuming any power from the RPi4. So I think power issue is unlikely. It runs fine once it starts booting.

And again, this did not happen with the previous 2.x releases, which were an older kernel, correct?

Yep. I’ve tested this myself, and I can’t reproduce this, but obviously I’ve got another DAC.

But if it does not boot it would also not be related to the kernel. That’s the weird part.
So… did you flash the USB controller firmware by any chance?

Yes, USB contoller firmware flashed via RoPieee after installing the 3.x update and having it hang on startup to see if that would improve it. It made no difference.

I still can’t logically reason why this should be related to the new kernel:

  • with the DAC plugged in it doesn’t boot at all (otherwise you would have seen something on the screen).

So it must be something related to the firmware on the Pi or something.

Can you send me feedback of the unit running without the DAC and then plug it in? And then send me feedback?

Cold boot with DAC disconnected: b339f3a275215f60
After plugging in the DAC USB cable: d80565152d729766

Thanks.

In the mean time: can you update the unit on the beta channel?
That has the latest bootloader and firmware for the Pi. Just to be sure.

Updated the USB firmware on my RPI4 (not XL) to 000138a1. The RPI4 is typically running a few degrees (55/55.5) warmer than before (53). I use an Allo hat, getting similar results USB audio on or off. Is this normal without a fan. Idle or playing doesn’t seem to affect the temperature much. 48da1850391676bf

14 posts were split to a new topic: Roonbridge connection problems