Why doesnt the Roon integration just work after a year in the field?

This has been problematic for me from day 1.

Most of the time when I come home and want to start listening to Roon, I have to reboot the remote control just to see the Roon integration. The remote sits in its cradle when not in use, so sleep or battery is not the issue.
In some cases, multiple reboots of the R2 are required just to get the Remote to “appear” like its connected to the Roon server (Innuos ZEN MK3)
Even then, the artwork will ONLY show up on the screen if I hit pause, followed by play, but that only happens after a matter of minutes, not seconds.
Removing the integration and reinstalling doesnt solve these ongoing problems.

The Roon integration version is 0.2.5 - is there a newer version perhaps?

Considering this remote has serious control issues that seem to be taking forever to fix (of course with the R3 announced we may forever be the guinea pigs), I wouldve thought that well over a year since this remote’s launch, the features it AT LEAST launched with would work reliabily and 100%.

By contrast, my Shield TV integration is flawless.

Any help, pointers etc ?
I really am at the point of tossing this in the bin.

For myself I found this:
After a time (hours, not days) the extension is deactivated in Roon. If I go to for example device “Roon DAC” and press PLAY command times out since the extension is not active in Roon. After extension is (automatically) activated within few seconds the PLAY works again.

I had several cases where for some reason the integration stops working, I then have to re-apply the integration from R2, first removeing the extension from Roon.

Annoying, yes, a lot. End of the world, no.

I really would like to see media browsing, that would be great. Itäs still on roadmap for Q3/24 which ends in two weeks so there’s hope as always.

Thanks for the reply.
Considering my problems with how I get this remote to re-engage with Roon is different to yours, AND I only want this remote to do two things and it doesnt do one of them properly, I would argue that it is, as you say, “the end of the world”.

What is the point of a Roon capable remote if I have to reboot the remote multiple times just for the lot to talk to each other and work? Kinda defeats the purpose when I can manually turn everything on, open Roon Remote on my phone and have music playing in seconds, not, maybe. 10 mins, if I use this remote.

Some things to check based on my experience:

  • Do the Roon-integration with IP
  • Do everything else with IP’s (Docks etc), minimize use of DNS and mDNS
  • R2 likes good network signal

Quite usual culprit is Wifi, how is the signal?
(And yes, 0.2.5 is the latest)