Any update on this issue, it’s never been addressed and still doesn’t work. It’s a problem with your driver, not with control4. Every other favorite in control4 works just fine.
I’m a C4 dealer and a Roon dealer and the support level provided, especially given the price of the nucleus is really below expectations. You need a channel dedicated to dealers with proper timely support so we can help our customers. The dealer documentation provided for the driver is very poor at best. Who can I speak to about these issues?
Vincent this seems to be a problem with the Roon driver and its been an issue from day one. I think it needs a complete revision but that seems to be very low down the priority for Roon. What I would say however is purchasing the Nucleus has been one of the best things I’ve done. Super reliable and quick, so I just put up with having to press one extra button on My C4
I have a HT integrated with a stereo Pre, separate amps for L, R, and C. There’s also an AVR. All of this powers up with the C4 button. The DAC stays powered up 24x7.
What happens if you press the Red C4 button and wait for your entire system to power up? Does choosing Roon from the main page work after everything is powered up work? Or do you still have to go to Listen?
If C4 recognizes the room as powered on and recognizes Roon as the source, the shortcut should get you to the Roon menu as normal. However, I haven’t tested that exact scenario before; this is just a guess.
Come to think of it, if you turn on Roon using the red C4 button, you won’t need the shortcut anymore. You can just push the Roon button from the “now playing” field on the home page of the relevant room.
Our C4 started out in the early days to simplify use of our HT/ Stereo HiFi in our living room. Pretty much everyone is in the habit of powering up the system with the C4 button. That came from the delays associated with tube heating in the Pre and Amps. Once the C4 home page shows up, sources are selected from that screen.
We don’t normally pickup the remote and choose a source from either Watch or Listen. Based on what you’ve described, we should be good to go with moving from Rock to a Nucleus Plus and C4 driver’s
This issue was reported here on this thread on 12/2020. Surely those of us that purchased Nucleus and Nucleus Plus should get a little attention. I specifically purchased a Nucleus Plus for the C4 integration.
I spent four hours today at home with a Control4 technician. He himself was on the phone with Control4 for two of the four hours trying to make the integration work as expected. We learned a few things:
The Roon supplied Control4 Driver is not Control4 Certified.
The driver is locked so Control4 can’t open it up and see what’s going on.
Any Roon icon favorited to the Home screen will not function at all.
It seems that Team Roon, particularly @danny failed to mention that the driver isn’t Certified and Control4 can’t help when there’s an issue.
It doesn’t seem that there’s any passion for this with @brian@enno or @danny. It’s a shame really since we are directed to get a Nucleus if we want this integration.
Does anyone reading this have issues with the driver?
I hope this helps anyone else with these Control4 drivers. I had to spend $500 on a technician to learn that @danny promoted something to me that doesn’t work.
Also of note, it’s been thirty days since my last posting, and there’s been no reply from Roon management.
@Vincent_Kennedy : Yes, I continue to have unresolved problems with the driver, and I believe others do too. Of note, however, I no longer experience the problem with the favorited home screen Roon Icon. I am not sure how it got resolved, although my suspicion is that an update to the T4 touch screen solved it.
The (major) problems I continue to have are: (1) Roon consistently crashes my C4 touch screens when scrolling through long lists in Qobuz; (2) playing a zone from the Roon app does not get reflected in C4; (3) grouping and ungrouping zones in the Roon app does not cause them to become grouped or ungrouped in C4. I reported all these – along with about 5-6 other secondary issues – back in August 2020, but there has been no progress on resolving any of them, and I have heard no news since @noris acknowledged receipt of my issues list back then.
Ouch. That’s a remarkably long list and a shameful resonse from support.
I have often wondered what the 1 - 3 year Roon roadmap looks like. But it’s clear to me that these issues aren’t top of mind. They have enticed us to purchase a product and it doesn’t work as advertised, there’s no communication, and no support.
Well, I am on the fence about two major purchases, so this is disappointing to hear about this lack of love. Considering purchasing the Whirl Wind instead of the Nucleus Plus, and buying into the Control4 ecosystem. If it’s not perfect for audio integration with Roon, family is not going to use it.
Our family uses the Roon app instead of C4 to control Roon. In itself, I don’t view that as a problem, because the Roon app is more fun to use than the C4 interface.
However, the real problem is that the Roon Control4 driver does a fair to poor job of reflecting Roon app actions in C4 – e.g., C4 should reflect that Roon is playing, and the meta-data should be there too. In contrast, the Sonos driver for C4 is terrific at reflecting Sonos app actions in C4; the contrast between the polish of the Roon and Sonos C4 drivers is painfully stark.
I have programmed around some of the most egregious problems with the Roon driver – e.g., my programming switches the source to Roon when it detects Sonos playing an “unknown” track, which almost always implies that Roon is playing. However, there is no way for the C4 user to program around the various zone grouping issues that I mentioned above through programming. That has to be fixed in the driver.
I wanted to let you all know that there is a lot of work happening behind the scenes on the Home Automation side of Roon. Nothing specific I can share just yet, but stay tuned…
I am a Control4 Dealer from Austria. I have the same problem as discussed here before. As soon as the ROON icon is a “favourite” on the home screen on T3, it doesn’t work any more. It doesn’t start to play. If I go to “Listen” first and then to ROON it works without any problems. I talked to the Control4 team yesterday for two hours, and they also believe that the ROON driver is the problem. I hope to have a solution for this problem soon.
We have a few exciting changes to announce, one of which is that we have open-sourced our Control4 module! Please feel free to make any changes needed to the module regarding this issue and submit a pull request at our GitHub, linked below:
Hi All - good to see continued discussion on the C4 integration and the announcing open-sourcing the Control4 module hopefully will be a very positive thing. I still have months before I have an operational C4 integration with a Nucleus yet-to-be purchased at a house being renovated.
Meanwhile, I continue to enjoy using Nuimo Control and rooExtend to control Roon music volume from my recliner rather than always grabbing my phone when I have music playing loudly when somebody else comes in the room. Unfortunately, that line-of-sight from the Nuimo Control to my music server will go away with the renovation and an equipment rack install … wait-a-sec, it’s not communicating to the music server with line-of-sight, it is line-of-sight to the raspberry Pi.
Whew… was worried about that. I started looking into devices supporting Matter home automation, looking at all other volume controls that don’t have subscriptions like Josh.ai has, and was really eyeballing the Flic Twist as a volume control once it really comes out.
Maybe I will pick up another Nuimo Control and see about controlling volume from another room now!
And maybe many of the past and present oddities about Control4 integration will be resolved by the time I get my system installed.
