# Roon Extension: Roon Web Controller v1.2.0

**URL:** <https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412>\
**Category:** Roon API\
**Created:** [July 16, 2017, 3:12pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412 "2017-07-16T15:12:51Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [September 12, 2017, 9:02pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/62 "2017-09-12T21:02:32Z")

</div>

Very odd - Chrome is my main browser…

Try refreshing the page with CTRL-R

Failing that, clear you cookies and try again. This page uses a cookie to store state information. At the moment, that cookie expires after 7 days. That will likely change to something much longer in the future.

---

<div class="post-metadata">

**Author:** ![volpone](https://community.roonlabs.com/letter_avatar/volpone/32/5_5575768a8748004e209b776fc1b2916d.png) [@volpone](https://community.roonlabs.com/u/volpone)\
**Post date:** [September 13, 2017, 6:22am UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/63 "2017-09-13T06:22:34Z")

</div>

OK Mike, seems an issue with the cookie. What is the cookie name, for convenience i would prefer not to clear all my cookies.

Edit:  
OK, i did it. Cookie name is the node host server name (IP). I clear the cookie and “now playing” is back.

---

<div class="post-metadata">

**Author:** ![seagull](https://community.roonlabs.com/user_avatar/community.roonlabs.com/seagull/32/48296_2.png) [@seagull](https://community.roonlabs.com/u/seagull)\
**Post date:** [September 15, 2017, 9:38pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/64 "2017-09-15T21:38:01Z")

</div>

Roon Web Controller is broken on my system.  
In Settings/Extensions the Roon Extension Manager PAIR button shows up periodically, then disappears again.  
If I click on PAIR and then on SETTINGS I cannot select any extensions.

 ![](https://roon-community-uploads.s3.amazonaws.com/original/3X/3/b/3bbde99e7bcde1523fc6ab704e4153b5905ba06e.jpg)

I’ve seen that Node.js has been updated to v8.5.0. Could that be the issue? Or is LTS v6.11.3 used?

Anyone experiencing the same issue?

---

<div class="post-metadata">

**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\
**Post date:** [September 16, 2017, 10:02am UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/65 "2017-09-16T10:02:31Z")

</div>

Looks like the extension repository hasn’t been loaded. Is there an error reported in the Extensions overview?

Can you provide me the log file of the Extension Manager? It is located here:

```
%appdata%\RoonExtensions\roon-extension-manager.log

```

> [@seagull](#):
>
> In Settings/Extensions the Roon Extension Manager PAIR button shows up periodically

Are there multiple cores running in your system?

> [@seagull](#):
>
> I’ve seen that Node.js has been updated to v8.5.0. Could that be the issue? Or is LTS v6.11.3 used?

The Windows installer installs an LTS version, 6.11.1 to be precise. This should be fine.

---

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [September 16, 2017, 5:35pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/66 "2017-09-16T17:35:36Z")

</div>

@volpone - to clear just the cookies for the Web Controller in Chrome:

1. go to the Web Controller page with Chrome
2. open the Developer Tools (see [https://developer.chrome.com/devtools](https://developer.chrome.com/devtools) to show you how, I hit F12 on Linux, and I think that works on Windows, just not sure on Mac OS)
3. click the “Application” tab
4. expand “Cookies”
5. right-click on the URL for your copy of Web Controller, and click “Clear”

That will clear the cookie just for Web Controller but leave the rest of your cookies alone.

ERM - just noticed that you updated your post and you are good now. Glad that it worked for you! But I will leave these instructions just in case someone else needs them.

---

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [September 16, 2017, 5:37pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/67 "2017-09-16T17:37:27Z")

</div>

@Jan_Koudijs - seems to be a lot of issues if there are multiple Roon Cores on the network…

Any thoughts on what is going on with that?

---

<div class="post-metadata">

**Author:** ![seagull](https://community.roonlabs.com/user_avatar/community.roonlabs.com/seagull/32/48296_2.png) [@seagull](https://community.roonlabs.com/u/seagull)\
**Post date:** [September 16, 2017, 9:28pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/68 "2017-09-16T21:28:26Z")

</div>

There is only one core, running an an HP MicroServer Gen 6 running Windows 10 Pro 64bit.  
RoonExtensions are installed on the same server.  
Here is the [logfile](https://www.dropbox.com/s/mtqgcexh1y4g39z/roon-extension-manager.log?dl=0).

---

<div class="post-metadata">

**Author:** ![volpone](https://community.roonlabs.com/letter_avatar/volpone/32/5_5575768a8748004e209b776fc1b2916d.png) [@volpone](https://community.roonlabs.com/u/volpone)\
**Post date:** [September 28, 2017, 9:02am UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/69 "2017-09-28T09:02:20Z")

</div>

@Mike_Plugge,  
It’s OK and easy to solve it by clearing, but the cookie issue is quite recurrent on my setup.  
However, thank you for your work.

---

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [September 29, 2017, 7:55pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/70 "2017-09-29T19:55:17Z")

</div>

Not sure why you are seeing cookie issues…

Though one thing you can do is extend the age of the cookie.

In the file (INSTALL DIR)/public/js/nowplaying.js, lines 481-483 sets the expiration time for the cookie.

The line currently looks like this:  
`Cookies.set(name, value, { expires: 7 });`

The “7” is the number of days that the cookie remains valid. If you change that to 365, you will get a year. The next minor release will likely include that change.

---

<div class="post-metadata">

**Author:** ![Christoph\_Bach](https://community.roonlabs.com/letter_avatar/christoph_bach/32/5_5575768a8748004e209b776fc1b2916d.png) [@Christoph\_Bach](https://community.roonlabs.com/u/Christoph_Bach)\
**Post date:** [October 13, 2017, 9:48pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/71 "2017-10-13T21:48:27Z")

</div>

Hi Mike! I have the same problem with no more state changes after a transfer zone by api command.  
Are there any news about this bug?  
Kind regards, Chris

---

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [October 13, 2017, 10:01pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/72 "2017-10-13T22:01:15Z")

</div>

It is a known bug. The fix should be included in the next stable release of the Roon server. But there is no ETA on the release date.

---

<div class="post-metadata">

**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\
**Post date:** [October 18, 2017, 5:09pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/73 "2017-10-18T17:09:58Z")

</div>

Hi @Mike_Plugge, @ben,

I just updated to build 269 and I can confirm that the transfer issue is now fixed!

---

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [October 18, 2017, 6:09pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/74 "2017-10-18T18:09:54Z")

</div>

Great news!

I haven’t had a chance to update yet so I will check it again tonight.

Thanks Jan

---

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [October 19, 2017, 1:38am UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/75 "2017-10-19T01:38:18Z")

</div>

Yup - looks good here, too!

Thanks @ben and thanks @Jan_Koudijs for reporting it in the first place.

---

<div class="post-metadata">

**Author:** ![anon73739233](https://community.roonlabs.com/letter_avatar/anon73739233/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon73739233](https://community.roonlabs.com/u/anon73739233)\
**Post date:** [November 20, 2017, 9:05pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/76 "2017-11-20T21:05:48Z")

</div>

Last night my Pi based endpoint stopped working so I imaged a card with DietPi, installed X server and Chromium and the extension. It runs fantastically well on the 7” Pi touchscreen (using the side by side view in my case). It’s absolutrly brilliant. Thanks @Mike_Plugge

---

<div class="post-metadata">

**Author:** ![anon44636269](https://community.roonlabs.com/letter_avatar/anon44636269/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon44636269](https://community.roonlabs.com/u/anon44636269)\
**Post date:** [November 26, 2017, 6:12pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/77 "2017-11-26T18:12:34Z")

</div>

Just using this in Chromium on dietpi for a now playting screen and control, The cover view does not seen to work properly on the pi as the background art is not defcocused like it is when using web browser on a full PC. Is there anything I can do to fix this or is it a limitation of Chromium on the Pi?

Installing a different version of Chromium sorted this. thanks @anon73739233 for all your help setting this up.

---

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [November 27, 2017, 1:16am UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/78 "2017-11-27T01:16:20Z")

</div>

Looks like I was beat to the punch. Glad it is sorted. But I am curious, which version of Chromium was causing problems?

The defocused look is created using the CSS filter feature - specifically the opacity and blur features. That feature is fully supported in Chromium/Chrome version 53 and newer.

[https://caniuse.com/#feat=css-filters](https://caniuse.com/#feat=css-filters)

---

<div class="post-metadata">

**Author:** ![anon73739233](https://community.roonlabs.com/letter_avatar/anon73739233/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon73739233](https://community.roonlabs.com/u/anon73739233)\
**Post date:** [November 27, 2017, 1:47am UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/79 "2017-11-27T01:47:32Z")

</div>

DietPi installs v52.0.2743.116 if you install from their menus.

---

<div class="post-metadata">

**Author:** ![Mike\_Plugge](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mike_plugge/32/48414_2.png) [@Mike\_Plugge](https://community.roonlabs.com/u/Mike_Plugge)\
**Post date:** [November 27, 2017, 1:55am UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/80 "2017-11-27T01:55:53Z")

</div>

Oy! That is over a year and a half old! CSS Grid is out of the question, too, then. Definitely explains the problem though…

I guess I am spoiled with my Arch Linux ARM distro. It always has the latest packages, but it is a bit more involved to get up and running and to maintain it…  
[https://archlinuxarm.org/platforms/armv7/broadcom/raspberry-pi-2](https://archlinuxarm.org/platforms/armv7/broadcom/raspberry-pi-2)

---

<div class="post-metadata">

**Author:** ![florib](https://community.roonlabs.com/user_avatar/community.roonlabs.com/florib/32/104803_2.png) [@florib](https://community.roonlabs.com/u/florib)\
**Post date:** [December 3, 2017, 1:04pm UTC](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412/81 "2017-12-03T13:04:43Z")

</div>

Hi,  
I had the same problem as described by @Simon_Arnold3, but can’t update my webbrowser due to dependency problems (using osmc).

So I added a line to the site.css file of your extension in the #coverBackground section using -webkit- prefix:

`-webkit-filter: opacity(.2) blur(1px);`

Played a bit around with the values to fit my needs. It has not the same effect as your code line but is working for me so far.

[Previous page](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412.md?page=3)

[Next page](https://community.roonlabs.com/t/roon-extension-roon-web-controller-v1-2-0/28412.md?page=5)
