Compare the extension manager version in the very first post’s screenshot.
Yours seems to be different and outdated, which is likely the cause why.
Good catch! Any advice on how to update my version?
Hi everyone, v0.0.4 is out!
This new version contains:
- Support for zone transfer (available in the volume drawer)
- Support for zone grouping (available in the volume drawer)
- Various enhancements for a better mobile and small screen experience
- A better keyboard navigation (or remote for those on TV screen)
- A more verbose options for logging (if you set log level on DEBUG or lower, every http request will be logged)
This version is already available via roon-extension-manager, have fun and enjoy!
I’m gonna take a break for the one or two coming weeks, because I’ve other stuff to deal with, outside of this project.
So, if no major or blocking bug is found in the coming days, don’t expect that much news before spring or maybe April.
Wish you all the very best!
6 Likes
The new version is released.
As announced, it includes more verbose logging, to help to understand what’s going wrong in your case (or others that could face issues with their installation).
During the update, you can switch to debug log level, you then will have way more logs available in the extension logs.
Also, after the update, there should be a log available in your browser console describing the reason the app failed to start.
My guess is that, in your browser console, there will be a message saying, error during startup... can't browse content... (or maybe can’t load depending on the API call that is failing in your roon core).
I also expect that the extension logs show an error during the call to browse or load API with the error message returned by your roon core.
If you make correlation with what’s in your core logs, there should be matching timestamps and the error you’ve shared at the beginning of this conversation.
If all that is confirmed by your tests, I would conclude, that, for an unknown reason (maybe an incompatibility between roon 1.8 and the latest releases of roon API 
), you roon core does not want to play ball with the API… and I won’t investigate why.
1 Like
great work, I went to update it and it was already on 0.4 so that was good news 
1 Like
The version was released yesterday in the evening, I wanted to let it run on my side (after test version built locally) before announcement, just to avoid bad surprises on the user side.
If you can check with the version displayed in the settings that your client instances have been also updated (that should be automatic, but who knows ).
I that’s the case, you can enjoy the new features 
1 Like
Hi @Omar_Chaudhry,
Upgrading to Extension Manager 1.x requires a clean installation:
Display in small smartphone screen is now OK with this version. Thanks!
2 Likes
Thanks for the feedback.
There could be more tuning, for instance on the font-size and information density, but that will come in a second time.
Just wanted to say I’ve switched from roon-web-controller to roon-web-stack and not going back. Love the improved UX experience. Really looking forward to seeing where this project goes from here. Thank you @nihil !
2 Likes
Nice work!
I have it running in Container Manager on my Synology NAS using the provided docker. Configured with it’s own dedicated ip using MacVLAN in docker.
I can finally control Roon using my work laptop 
Added it to a workspace on my browser where it’s running in a iframe so that it’s always readily accessible.
1 Like
Thank you! The new logs unfortunately don’t add anything new to the previous version. I conclude that this plugin doesn’t work with Roon 1.8 and I don’t intend to troubleshoot it further as well.
I’ll continue to use Roon Web Controller 1.2 which works perfectly with Roon 1.8
Updated working fine. I did notice that for some reason when I powered on my M11 it showed up I switched to control it’s zone but it didn’t show what was last playing and controls where greyed out. After playing direct from the m11 it could be controlled and now playing showed up. Not massive but an oddity.
Is it possible to have access to the play queue not to edit or anything but to see what’s in the queue? Or is that in the API?
I wonder why you stay on 1.8 now the connectivity problem is solved?
Hi everyone, v0.0.5 is out.
The main change is the use of web-worker for communication with the app instance in the browser.
This was needed to ensure a more consistent and reliable state management, especially when the app was run in an appliance mode (for instance in kiosk mode, always on).
Also, to help for the cases where things would go wrong in these cases, a reload app button has been added in the settings dialog.
The only other change is a fix for the misaligned control icons in compact mode when displayed on an medium screen (like the 7’’ touch raspberry pi one).
Enjoy and have fun, my hiatus really starts for the two coming weeks.
3 Likes
Glad you liked the update, you should enjoy the version released tonight!
Regarding the play queue, you must mean on mobile, as it’s available on tablet and desktop.
It’s coming, but a little rework is needed to display the queue in a dialog (the only realistic UI/UX on mobile).
This rework is also needed to open more layout flexibility, so it will be the first thing I’ll look after my pause.
1 Like
Have you restarted the extension with debug as a log level?
What do the http logs look like in the extension.log?
Yes on mobile. Sounds interesting as to what’s coming. Great work and thanks.
Which connectivity problem is solved?
I’m guessing this refers to no longer requiring a permanent internet connection for Roon to work