Problem with disappearing Ropiee with display

Support
1

Core Machine (Operating system/System info/Roon build number)
Ubuntu 18.04 kernel 4.15.0-128-generic
Roon version 1.7 build 710 (stable)
The coreserver shuts down for a reboot every night through cron script

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

UBNT Edgerouter Lite
UBNT Unify Switch 24
UBNT AP LR

No vlans or other specialities

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Ropieee 3.020 kernel 5.4.81-2-SPCKFSH-v7+
Raspberry Pi 2 Model B Rev 1.1 with 7" display
Hifiberry Dac+Pro XLR
Connected through wired network

Several Sonos zones
connected via a sonos bridge that also is connected to the wired netwoŕk

Description Of Issue
No problems using Roon with respect to the Sonos zones. Everything works fine.

The setup has worked fine for a year with a roon remote working on the Rpi display.
After a update the display stopped working.
Stopped working like if the display is powered on and i boot the Ropieee it newer appears in the Roon control likewise the display can’t find the zone to display.
If I boot the Ropieee without power to the display the zone appears emediately in the Roon control units

If i boot the Ropieee with power on the display, the Ropieee does not appear as a zone. If i then boot the Roon server (Ubuntu) the Ropieee appears as a zone and the display with remote is working fine.

Next time I boot the Ropieee with display (server not rebooted) the Ropieee does not appear, and the display likewise states that the zone cannot be found

I have had a longer session with @spockfish and his conclusion is that it is something in the Roon server implementation that is nor functioning as it used to - se posting 35 onwards:

3

here is a snippet from the RoonServer_log.txt:
At first I boot the Ropieee and as you can se the Ropieee apiclient (the display) is connecting to the core. But the core does not allow the Ropieee endpoint to connect so there is nothing to display.
At 18.44.00 i pull the power to the Ropieee display and instantly the core discovers the endpoint and connects to it - but now i have no display/remote.
What has changed in the Roon core since it does not allow the endpoint to be connected when the display is on?

1/06 18:40:59 Info: [stats] 1577mb Virtual, 909mb Physical, 471mb Managed, 0 Handles, 70 Threads

01/06 18:41:14 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:41:29 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:41:44 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:41:59 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:42:07 Info: [roonapi] [apiclient 192.168.1.107:52722] connected (websocket)
01/06 18:42:07 Trace: [roonapi] [apiclient 192.168.1.107:52722] GOT com.roonlabs.registry:1/info
01/06 18:42:07 Trace: [roonapi] [apiclient 192.168.1.107:52722] COMPLETE Success {“core_id”:“ee9f416d-0e48-454d-95bc-062df3fd3596”,“display_name”:“roon-server”,“display_version”:“1.7 (build 710) stable”}
01/06 18:42:07 Trace: [roonapi] [apiclient 192.168.1.107:52722] GOT com.roonlabs.registry:1/register {“extension_id”:“org.ropieee.remote”,“display_name”:“RoPieee Remote Control V2 [ropieee]”,“display_version”:“3.020”,“publisher”:“Spockfish”,“email”:"htenberge+ropieee@gmail.com","required_servic$
01/06 18:42:07 Trace: [roonapi/registry] [org.ropieee.remote, RoPieee Remote Control V2 [ropieee] v3.020 by Spockfish htenberge+ropieee@gmail.com] is awaiting authorization
01/06 18:42:14 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:42:29 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:42:44 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:42:59 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:43:14 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:43:29 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:43:44 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:44:00 Info: [stats] 1577mb Virtual, 909mb Physical, 472mb Managed, 0 Handles, 70 Threads
01/06 18:44:07 Trace: [raat] RAATServer discovered: RaatServer ropieee @ 192.168.1.107:40407
01/06 18:44:07 Info: [raatserver] GOT SERVER f846b474-0f1a-e13c-cd1b-2156504553c6::1ac8f1e0-9018-4bdc-ba41-646e7c8a22b2 @ 192.168.1.107:40407 ropieee PROTOVER=1 RAATVER=1.1.38
01/06 18:44:07 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
01/06 18:44:07 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.107:40407] connecting (attempt 1)
01/06 18:44:07 Trace: [push] retrying connection in 11893ms
01/06 18:44:07 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.107:40407] connected
01/06 18:44:07 Trace: [rnet/RnetJsonClient] SENT {“request”:“enumerate_devices”,“subscription_id”:“0”}
01/06 18:44:07 Trace: [rnet/RnetJsonClient] GOT NONFINAL {“status”: “Success”, “devices”: [{“device_id”: “hw:CARD=sndrpihifiberry,DEV=0”, “type”: “alsa”, “config”: {“unique_id”: “50fb6250-1f8a-c2e7-3644-0a9ea862e54f”, “volume”: {“type”: “software”, “exclusive_mode”: null}, “output”: {“name”: "s$
01/06 18:44:07 Trace: [devicedb] [autodetect] No Match for DeviceAutodetectData[Type=Local Model=snd_rpi_hifiberry_dacplus]
01/06 18:44:07 Info: [raatserver] GOT DEVICE 1ac8f1e0-9018-4bdc-ba41-646e7c8a22b2::hw:CARD=sndrpihifiberry,DEV=0 Type=alsa Name=snd_rpi_hifiberry_dacplus
01/06 18:44:07 Trace: [rnet/RnetJsonClient] SENT {“request”:“enable_device”,“device_id”:“hw:CARD=sndrpihifiberry,DEV=0”,“subscription_id”:“1”}
01/06 18:44:07 Trace: [rnet/RnetJsonClient] GOT NONFINAL {“device”: {“discovery_data”: {“vendor”: “N/A”, “tcp_port”: 37665, “unique_id”: “50fb6250-1f8a-c2e7-3644-0a9ea862e54f”, “model”: “N/A”, “version”: “N/A”, “raat_version”: “1.1.38”, “protocol_version”: “3”}, “device_id”: "hw:CARD=sndrpihifi$
01/06 18:44:07 Info: [raatserver] [snd_rpi_hifiberry_dacplus] connecting (attempt 1)
01/06 18:44:07 Trace: [rnet/RnetJsonClient] GOT NONFINAL {“status”: “Success”}
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] Initializing RAAT session
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] Loading script raat.dat:base.lua as module base [1088 chars]
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] Loading script raat.dat:dkjson.lua as module dkjson [22416 chars]
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] Loading script raat.dat:protocol.lua as module protocol [2045 chars]
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] Loading script raat.dat:roon_tcp.lua [43475 chars]
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] RAAT Session initialized in 119ms
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] SENT [2]{“request”:“info”}
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] SENT [3]{“request”:“set_client_type”,“client_type”:“Roon”}
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] GOT [2] {“transport”:{“is_supported”:false,“info”:[]},“flags”:{“has_write_chmap”:true},“status”:“Success”,“info”:{“unique_id”:“50fb6250-1f8a-c2e7-3644-0a9ea862e54f”},“volume”:{“is_supported”:true,“info”:{“supports_dsd”:false,"config$
01/06 18:44:07 Trace: [raatserver] [snd_rpi_hifiberry_dacplus] connected
01/06 18:44:07 Info: [transport] creating endpoint for raat device 50fb6250-1f8a-c2e7-3644-0a9ea862e54f
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] SENT [4]{“request”:“subscribe_transport”}
01/06 18:44:07 Debug: AudioDeviceMunge.GetManufacturer(AudioDeviceType.Local, “”, “snd_rpi_hifiberry_dacplus”, “”, “”) => “HiFiBerry”;
01/06 18:44:07 Debug: AudioDeviceMunge.GetModel(AudioDeviceType.Local, “”, “snd_rpi_hifiberry_dacplus”, “”, “”) => (null);
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] GOT [3] {“status”:“Success”}
01/06 18:44:07 Debug: AudioDeviceMunge.GetManufacturer(AudioDeviceType.Local, “”, “snd_rpi_hifiberry_dacplus”, “snd_rpi_hifiberry_dacplus”, “”) => “HiFiBerry”;
01/06 18:44:07 Debug: AudioDeviceMunge.GetModel(AudioDeviceType.Local, “”, “snd_rpi_hifiberry_dacplus”, “snd_rpi_hifiberry_dacplus”, “”) => (null);
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] SENT [5]{“request”:“subscribe_controls”,“controller_id”:“ee9f416d-0e48-454d-95bc-062df3fd3596”}
01/06 18:44:07 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] GOT [5] {“action”:“Changed”,“status”:“Success”,“controls”:{“volume”:{“mute”:false,“value”:0,“min”:-80.0,“info”:{“supports_dsd”:false,“config”:{“type”:“software”},“requires_external_persistence”:true},“type”:“db”,“step”:1.0,“max”:0.0$
01/06 18:44:07 Trace: [dspengine] loaded DSP config {“version”:3,“items”:[{“type”:“bs2b”,“enabled”:false},{“type”:“parametric_equalizer”,“enabled”:false},{“type”:“audeze_presets”,“enabled”:false},{“type”:“speaker_setup”,“enabled”:false}],“headroom_adjustment”:{“type”:“headroom_adjustment”,"enab$
01/06 18:44:07 Trace: [transport/audeze] picking preset lowlatency
01/06 18:44:07 Trace: [transport/audeze] picked null preset!
01/06 18:44:07 Trace: [zone stuen] Loading
01/06 18:44:07 Trace: [zone stuen] Suspend
01/06 18:44:07 Info: [zone stuen] Canceling Pending Sleep
01/06 18:44:07 Trace: [stuen] [zoneplayer/raat] Endpoint snd_rpi_hifiberry_dacplus Initial State: Idle
01/06 18:44:07 Info: [transport] created zone stuen
01/06 18:44:07 Info: [transport] with endpoint snd_rpi_hifiberry_dacplus (23:1:50fb6250-1f8a-c2e7-3644-0a9ea862e54f) [IsAvailable=True]
01/06 18:44:07 Trace: [stuen] [Inactive] [STOPPED @ 0:00]

4

Hello @Jens_Kjellerup, could you please use the directions found here and send us over a set of logs using a shared Dropbox link.

5

Hi Nuwriy.
The RoonServer_log logfiles JensK.zip can be accessed here:


The RAATServer_log logfiles can be accessed here

The links are active until 14.01.2021

The the most recent part of the logfile RoonServer_log.txt is when i start the Ropiee with power to the display and the Ropiee zone does not appear. After a few minutes take the powert from the display and the Ropiee zone appears amidiately after.

6

Hello @Jens_Kjellerup, and thanks for uploading those files. I have received them and since sent this information over to our QA team for their input. I’ll return shortly with their feedback!

8

@nuwriy
The problem is solved - so so.
Apparently Ropieee down not work with both a display and a zone when it’s on a Rpi 2b.
I put on a Rpi3 instead and now everything works as expected with the HifiBerryu Dac+ Pro and a Rpi display/remote

9

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.