I guess they would be RAAT. They are both USB devices connected directly to the RoonServer. They are labeled Hint6 and Mastersound. That’s the issue. They show up as an available group on my Windows desktop Roon Remote and on my ios Roon Remote but not in Community Remote. I created the group on my mobile client, if that makes any difference.
Based on the log file I’d expect a MasterSound zone in the zone list. HINT6 is marked as an output, but that output is not included in any of the available zones. If MasterSound is not in the (scrollable) zone list, does this change if you ungroup?
Maybe you can share some screenshots showing difference between Roon Remote and Community Remote. There seems to be something special with these devices.
Bonehead move on my part. The group is working. It wasn’t showing up because the HINT6 amp was powered down. When I turned it on, the group showed up and worked as expected. Sorry about that!! Keep up the good work. I really enjoy using this remote.
1 Like
This will be included in the next release:
1 Like
Just installed and works. Very nicely done! Much, much appreciated.
Installed on a Thinkpad T460s running Linux Mint 21.3 Cinnamon
1 Like
Community Remote version 0.0.5 is now available
This release brings Access Control to Community Remote. First point of control is profile selection, this can remain selectable or given a fixed assignment from a Roon Remote. Access Control will be further extended in future releases.
I described the idea behind access control in a separate post:
To update to version 0.0.5 on Linux you issue the flatpak update command in the terminal or use the software install tool of your distro. For Android or Windows the apk file or installer has to be downloaded from the release page.
Note: Access has to be granted after installation or update. 1) Open the Community Remote Settings in a Roon Remote (Settings → Extensions). 2) Save the default setting to restore previous operation or assign a dedicated profile.
2 Likes
Hi Jan this is a great idea and I downloaded and installed the Android App on my Pixel phone to test.
For some reason it doesn’t find my Roon server, same as your text based client, but there I can add a server flag and it just works.
Any Roon app on my network immediately finds the server so not sure why your clients don’t see it.
Happy to help if you want to try some debugging work.
Hi Michael,
If you click the button in the lower right corner (with the link icon) you can set the IP address and port number of your Roon server. This uses the same connection method as you use with Roon TUI.
The app is not phone ready yet, it is high on my list to change this.
Hi Jan thanks for that information, I was mistakenly clicking on Settings and expecting it to offer me something there
I have put my details in here but it doesn’t connect either (assuming the port number is correct).
I will give it a go on my Pixel Tablet at some point as well if that’s useful.
You might try by killing the app and starting it again. On Windows I saw the need for a restart when supplying IP manually. You can verify the port setting in the Roon Remote in Settings → Displays.
I now also tried on my Pixel 4a (Android 13), it could discover my Roon server.
1 Like
Thanks Jan I will try Windows and Android again. I am using port 9330 as I thought.
Discovery never worked on my setup with TUI but does with Roon and it might just be my setup.
I will feed back to you
Edit: Actually when I threw the app away and restarted it I got the option to enable the extension in Roon.
Useful information to have here 
Jan
On the tablet it instantly managed to find the Roon server and I just had to enable the extension.
It’s already looking pretty good on the tablet
1 Like
Good. Anyway a good idea to stick to a tablet in its current form.
But meanwhile the move to phone compatibility has started:
The dynamic layout also enables a split screen on Android tablets, a feature not supported by the Roon Remote:
4 Likes
Community Remote version 0.0.6 is now available
This release brings an adaptive screen layout, so now Community Remote can also be used in small windows and on Android phones. Queue, Zone, Volume and Now Playing all have a dedicated screen that can be reached via the controls at the bottom of the home screen.
5 Likes
Hi Jan starting to take shape nicely
One issue I found in portrait mode on the phone is that you cannot expand or contract the menu. Not sure if you have seen this on your phone. It works perfectly in Landscape mode
Hi Michael,
This is intentional. With the navigation rail expanded there remains too little room to have e.g. a proper track listing (on my Pixel 4a only 5 characters remain). For this reason I thought it would be acceptable to disable the expand and category hiding features on small layout. If you think differently let me know, there might be a better solution to this problem.
1 Like
Actually that makes total sense Jan and improves the layout.
I was unsure if you had noticed it was all.
1 Like
Community Remote trending on Flathub
Today Community Remote is on the Flathub homepage when viewing the Trending category. I assume this is because of the update wave resulting from the recent release, but not really sure.
It is nice to see that there are already over 500 Linux installs since the first release, about two months ago. I hope by also giving attention to Android and Windows that the project can further grow and become a useful tool for a bigger part of the Roon Community.
Keep the feedback coming, and enjoy your day!
6 Likes
@Jan_Koudijs Just installed this from the tar on Fedora 40. Started up without any issues! I’ve been using roon-tui and that too is amazing. Thank you for your work! I am cloning the repo and will try my hand contributing by fixing some issues.
Now if only they would have Roon Bridge without forced exclusive mode on Linux…
1 Like
Just installed it onto Linux MInt. Same here. Immediately starts without any problems. Nicely done, Jan!