Dashboard devices list

[CharleyVarrick 283]

I must be missing something obvious, but when I go to Dashboard/Devices, I see 4 valid entries, one of which is Firefox device, but this one is duplicated for 48 pages long.

Its like its not recognized from one day to the next.

 

Is this a normal expected behaviour, and is there any way I can shorten the list without right clicking/delete individually 700+ identical entries?

 

[Luke 42080]

That's not normal. Sounds like browsing data must be getting cleared, or running in incognito mode. You can just delete them.

[CharleyVarrick 283]

That's not normal. Sounds like browsing data must be getting cleared, or running in incognito mode. You can just delete them.

One by one? There's 700 or so of them.

Edited December 26, 2018 by jlr19

[Luke 42080]

As of right now they can only be deleted one at a time unfortunately.

[CharleyVarrick 283]

OK then,

thanks and happy holidays

[CharleyVarrick 283]

so far so good, the devices list has been cut down to the last 3 actual devices, Fingers crossed.

Edited January 12, 2019 by jlr19

[CharleyVarrick 283]

I may have found out the cause of the endless duplicate devices list.

After many hours of deleting one by one until I got an empty list, a couple of weeks passed without any spawning.


Then a moment ago, I just caught one. Moments before it happened, I needed to sign-on to LastPass (a password mgr add-on I use with Firefox).


The password mgr login seems to set off Emby into not recognizing the browser anymore. This is when a dupe device is created in the list.


Pretty soon, I'll be back in Emby web but without LastPass signed-in and again, this will trick Emby in seeing it as a new browser in town.


Left unchecked for a year or two, that's how it got to over 700 and growing.

[Happy2Play 9781]

I may have found out the cause of the endless duplicate devices list.

 

After many hours of deleting one by one until I got an empty list, a couple of weeks passed without any spawning.

 

 

Then a moment ago, I just caught one. Moments before it happened, I needed to sign-on to LastPass (a password mgr add-on I use with Firefox).

 

 

The password mgr login seems to set off Emby into not recognizing the browser anymore. This is when a dupe device is created in the list.

 

 

Pretty soon, I'll be back in Emby web but without LastPass signed-in and again, this will trick Emby in seeing it as a new browser in town.

 

 

Left unchecked for a year or two, that's how it got to over 700 and growing.

 

Does LassPass clear your browser cache/history by default or is it a setting?

 

But auto removal after X days inactive would seem appropriate.

Edited January 12, 2019 by Happy2Play

[CharleyVarrick 283]

Does LassPass clear your browser cache/history by default or is it a setting?

Hi Happy-New Year

Give me a moment, I'll see what info I can grab on their "specs" page.

[CharleyVarrick 283]

It doesn't look like LastPass is involved at all with cache/history. My settings and preferences checked out. I googled "Does LassPass clear browser cache/history", to no significant hit.

Edited January 12, 2019 by jlr19

[CharleyVarrick 283]

But auto removal after X days inactive would seem appropriate.

You mean a feature request?

[Happy2Play 9781]

You mean a feature request?

 

Yes but not positive if there is one already.

[CharleyVarrick 283]

But auto removal after X days inactive would seem appropriate.

I can see ahead how this would not please everyone and their mothers too.

I presume a majority of users have not experienced my ever growing devices list issue.

They would lose list history functionality without gaining anything back in return.

Admins managing large numbers of users might prefer to keep this control manual.

For a user like me that just handle a handful of devices, granted, it would automate the cleanup.

 

 

I would rather suggest researching why Emby reacts like this, as if it turns out to be an easy codefix, its a win-win.

Eliminating the problem at the source means no cleanup required (manual or automated).

Edited January 12, 2019 by jlr19

[Happy2Play 9781]

It is a issue as you described.  Easy to replicate by clearing your browser history, a new device is added.  I clean them up occasionally as there is one for every beta version.

 

Well there is really nothing unique about a browser though.  How would you know these are actually two different system browsers?

 

Edited January 12, 2019 by Happy2Play

[Luke 42080]

There's no way to know.

[CharleyVarrick 283]

Browser's IP address?

 

As in:

Chrome on 192.168.0.111

Chrome on 192.168.0.222

 

etc

Edited January 12, 2019 by jlr19

[Luke 42080]

No, that could change. There is no way to permanently uniquely identify a browser instance.

[CharleyVarrick 283]

By browser/computer name then?

 

Which, incidentally, is how I manually edit their names.

Edited January 12, 2019 by jlr19

[Luke 42080]

There's no way for the web app to get the computer name that it's running on. yes it can get the browser name, but that's obviously not unique enough.

[CharleyVarrick 283]

Shouldn't a emby cookie help keep track of who's who?

Of course deleting this cookie would be counter-productive; it would need to be white listed.

Edited January 12, 2019 by jlr19

[Luke 42080]

Yes, but all of that gets erased when clearing browsing data, as well as incognito mode. Try to avoid doing that, and then you won't see the duplicates.

[CharleyVarrick 283]

It doesn't get erased if the user white list it. As for this suggestion "Try not to clear browsing cache/history", I'm afraid that its not a viable option for most.

 

I guess there's no solution to prevent this.