Raatclient should write the zone name in the logfile

Feedback Feature Suggestions
1

The following log lines in RoonServer_log.txt which were written by [raatclient] include the hardware type but don’t include the zone name. On my Roon system each zone has a distinct name, do most people not do this? It would be helpful for debugging network issues if the raatclient would include the zone name in the logfile line.

Example log:

RoonServer_log.20.txt:06/01 18:26:07 Warn: [amplifier + gym + garage + office] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
RoonServer_log.20.txt:06/01 18:26:07 Trace: [amplifier + gym + garage + office] [zoneplayer/raat] too many dropouts. stopping stream
RoonServer_log.20.txt:06/01 18:26:07 Trace: [snd_rpi_hifiberry_dac] [raatclient] GOT [95] {"status":"Dropout","samples":22050}
RoonServer_log.20.txt:06/01 18:26:07 Trace: [snd_rpi_hifiberry_digi] [raatclient] GOT [151] {"samples":22051,"status":"Dropout"}
RoonServer_log.20.txt:06/01 18:26:07 Trace: [snd_rpi_hifiberry_digi] [raatclient] GOT [5296] {"status":"Dropout","samples":22050}
RoonServer_log.20.txt:06/01 18:26:08 Trace: [snd_rpi_hifiberry_amp] [raatclient] GOT [5166] {"status":"Dropout","samples":22050}
RoonServer_log.20.txt:06/01 18:26:08 Trace: [snd_rpi_hifiberry_digi] [raatclient] GOT [151] {"samples":22050,"status":"Dropout"}
RoonServer_log.20.txt:06/01 18:26:08 Warn: [amplifier + gym + garage + office] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
RoonServer_log.20.txt:06/01 18:26:08 Trace: [amplifier + gym + garage + office] [zoneplayer/raat] too many dropouts. stopping stream

I only have one hifiberry_dac but I have multiple hifiberry_digi and multiple hifiberry_amp, and it’s not obvious from the log line which one was dropped. This specific logfile shows all of the zones dropping out at the same time, which is probably due to rebooting an ethernet switch or the wifi extender system or something. However, when only one of the zones drops out it would be helpful to know which one and not just the device hardware type.

The following raatclient logs are harmless and aren’t needed for troubleshooting, but they also don’t include the zone name for which the volume was being changed:

06/05 16:40:48 Trace: [snd_rpi_hifiberry_amp] [raatclient] SENT [25]{"request":"update_volume","value":57}
06/05 16:40:48 Trace: [snd_rpi_hifiberry_amp] [raatclient] GOT [25] {"status":"Success"}
06/05 16:40:48 Trace: [snd_rpi_hifiberry_amp] [raatclient] GOT [5] {"controls":{"volume":{"value":57,"step":1.0,"max":100.0,"min":0.0,"info":{"config":{"type":"alsa","device":"hw:CARD=sndrpihifiberry,DEV=0"}},"mute":false,"type":"number"}},"action":"Changed","status":"Success"}
06/05 16:40:48 Trace: [snd_rpi_hifiberry_amp] [raatclient] GOT [5] {"controls":{"volume":{"value":57,"step":1.0,"max":100.0,"min":0.0,"info":{"config":{"type":"alsa","device":"hw:CARD=sndrpihifiberry,DEV=0"}},"mute":false,"type":"number"}},"action":"Changed","status":"Success"}

I was changing the volume of only one hifiberry_amp device, which has a distinct zone name.

Thanks a lot,
James

2

It does. For example:

05/29 11:26:57 Trace: [snd_allo_digione] [raatclient] GOT [2292] {"status":"Ready"}
05/29 11:26:57 Trace: [Allo DigiONE] [zoneplayer/raat] Endpoint snd_allo_digione State Changed: Buffering => Ready
05/29 11:26:57 Trace: [Allo DigiONE] [zoneplayer/raat] wait for ready in 44ms
05/29 11:26:57 Trace: [Allo DigiONE] [zoneplayer/raat] Adjusting playback start offset from 50ms to 59ms
05/29 11:26:57 Trace: [Allo DigiONE] [zoneplayer/raat] Doing 'ASAP' Start since we are just playing to one device
05/29 11:26:57 Trace: [snd_allo_digione] [raatclient] SENT [2293]{"request":"start","min_offset":59818594,"stream_sample":0}
05/29 11:26:57 Trace: [Allo DigiONE] [zoneplayer/raat] Endpoint snd_allo_digione State Changed: Ready => Playing
05/29 11:26:57 Trace: [snd_allo_digione] [raatclient] GOT [2292] {"status":"Playing"}
05/29 11:26:57 Trace: [snd_allo_digione] [raatclient] GOT [2293] {"status":"Success","time":378800246762516}

The Trace in your example is preceded by the zone name. However, in this instance it is a grouped zone: [amplifier + gym + garage + office]. Therefore, the first step in diagnosis would be to ungroup since the client appears to only know the hardware name.

You should refine the feature suggestion to state that [raatclient] also displays the custom zone name.