Nucleus+ hardware
OS Version 1.0 (build 175) stable
Roon Server Software
Version 1.6 (build 416) stable
Roon Labs Software
Version 1.0 (build 11) stable
Control4 Software
Smart Home OS 2.10.6
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Ethernet. Pakedge Router and Gigabit switch.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
HiFiBerry
Version 1.8
RAAT SDK Version 1.1.30
DAC+ (two of them)
Digi+ (two of them)
Description Of Issue
Newly integrated Control4 with Roon (Nucleus+).
When I group the RAAT devices either in Control4 or the Roon app, the Control4 feedback breaks. I lose all metadata feed. The music plays on the devices selected but I no longer have feedback on the Control4 interface.
I can play every zone independently and it works as expected. Grouping audio devices/zones in either the Roon app or the Control4 interfaces breaks it.
Thanks for the report, I’m forwarding this information to the development team. When you ungroup the devices, does the Control4 functionality begin working again?
Thank you for the report here. Just to make sure I am understanding you clearly here - this behavior only occurs in the Control4 interface, and the Roon App interface works as expected even when the zones are grouped?
We are aware of a report of similar behavior and have a internal ticket regarding the following when zones are grouped via Control4:
Track names are not update on the bottom bar
Play/pause works but does not reflect the proper feedback status on the interface
Volume control only works for one of the zones and the volume feedback is not properly updated
Can you please confirm if you are seeing the above symptoms only or if you are seeing other behavior here as well?
Yes, this only happens in the Control4 interface. The following message appears in the LUA interface after a grouping of zones/audio devices and no further information is received until I ungroup the zone/device.:
SendToProxy (5001, SEND_EVENT)
NAME: ProgressChanged
EVTARGS: 641:04
[string “Lua Code”]:1334: attempt to index global ‘exist’ (a nil value) (ExecuteCommand)
[string “Lua Code”]:1334: attempt to index global ‘exist’ (a nil value) (ExecuteCommand)
To confirm:
Track names are not update on the bottom bar - CONFIRMED
Play/pause works but does not reflect the proper feedback status on the interface - CONFIRMED, however, the PAUSE control works which leads me to believe that Control4 is sending the command to Roon, but the feedback from Roon that the track is paused is not received by Control4 so the button never changes state and the track continues to be paused.
Volume control only works for one of the zones and the volume feedback is not properly updated - CONFIRMED. There is some strange behaviour concerning volume control and muting of zones. At any rate, this seems to be effected by the grouping of zones/devices.
The Roon app on all devices works normally.
Everything appears to work normally when there are no zones/devices grouped.
Also, it happens when the zones are grouped in the Roon app as well. Only the Control4 interface is effected, but it does not matter if the zones are grouped via the Control4 interface or the Roon app. It breaks the Control4 interface.
There is an active ticket with the dev team regarding this issue and I have added your findings to the case notes. I can’t comment on when this behavior will be addressed, but it is in the queue and pending review.
Thank you again for the report, I will be sure to reach out again to you once I have any further information regarding this issue and appreciate your patience in the meantime.
If I “Refresh Navigators” from the Control4 Composer tool when the Control4 interface is not responding with zones grouped it starts working properly. I can play tracks from either the Control4 interface or the Roon app and the Control4 seems to be getting the proper metadata and responds as expected.
The Control4 works properly when I group the zones then refresh navigators. Any changes to the grouping then breaks the Control4 interface again until I refresh the navigators again.
Thanks for the additional data point, I have added it to the investigation notes. This ticket is still in the queue and pending review, once I have any additional information to share I will be sure to let you know.
I considered the purchase of a Nucleus, largely for C4 integration. But this report is a show stopper for me. I group RAAT devices constantly. As would most people who utilize both Roon and C4.
I urge the Roon team to fix this problem as rapidly as possible. When C4 functions smoothly on a Nucleus, I will buy one.
Thank you for your interest in this issue. There is an active ticket pending review by the dev team, but I cannot comment on any specific timeline of when it will be addressed. As soon as I have any further information, I will be sure to update this thread accordingly. Thanks in advance for your patience here!
I’m still considering the purchase of a Nucleus, but will only do so when any issues related to Control4 are resolved. Including this issue related to the grouping of devices.
This thread was never updated. That would indicate that nothing has changed in the last two months, and the problem remains?
Thanks for pinging me regarding this issue. I just checked our internal ticket tracker and I see that this ticket is still pending review by the dev team. I don’t have any further information to share at this time, the devs are still planning to take a look at this behavior but I can’t comment on an exact timeline of when this will happen. As soon as I have any further information, I will be sure to update this thread accordingly, thanks!
There are no updates at this time, we still have a ticket open regarding this behavior and it is pending review by the dev team. Once the ticket has been addressed I will be sure to make an announcement in this thread. Thank you for your patience.
Yes, we are currently testing a new build of the Control4 module internally. The module is undergoing QA testing at this time and once it passes all the checks and is ready, we will make an announcement here.
I know this issue has gone on longer than anyone would like and you have our apologies for the delay, we are still actively working on the module… stay tuned!
