Understood… I’ll calm down
I just didn’t see it on your check list.
I’ve been running both side by side. If you like, I can give some more feedback or let me know when the time is right. For now, I’ve set a 1px x 1px looping video next to the clock which keeps the tablet awake. Thanks again!
Ref Tidal browsing:
The Tidal browser is tied to your internet connection speed. Web Controller just shows data from the Roon Core, so if Tidal/Qobuz browsing is slow in the official client, it will be slow in Web Controller.
The profile does show in the library page. Go to the Library page then:
Settings -> Profile
The profile does not show in the Now Playing or Queue api payload, so I can’t display it. This screenshot shows an example of what the Transport/Now Playing API has available:
Ref API key:
There is no API to pre-authorize an API key.
NOTE: the following is theoretical - I have not tested it and I cannot support it due to variations on individual systems. So your mileage may vary.
If you bind mount the config.json file to persistent storage, then you will not have to pair every time you spawn a docker/kubernetes container. When you pair Web Controller 2.x to Roon, the file (install-directory)/backend/config.json is created by node-roon-api.
So theoretically, if you add a bind mount option to the docker start up command, you could keep that file around even when new containers are created.
Something like adding this to the docker run command:
The same would be true for a Kubernetes container - but the configuration varies based on which persistent storage plugin you are using.
I have NOT tested this and cannot provide support for it. But in theory, it should work…
@Mike_Plugge thank you for this extension.
I have a question: now running version 1 and I see a lot of logging in /var/log/syslog. Is it possible already in version 1 to set the logging level to lower the amount of logging? If not, is it possible to add it in version 2?
Version 1, the easiest way to reduce the logging is to uncomment “log_level: none” at line 111 in the “app.js” file.
Version 2 uses a different style of logging and only logs the HTTP server events in a standard Apache log format, which is significantly less than the Roon events which Version 1 logs. The web server style logs are more useful system monitoring and analysis.