New device notification

[gitthangbaby]

The problem

the script triggers "New device" Plex notification on every run:

New Device

_User_ used a new device to access _Server_: _Server_ (PlexTraktSync)

Error trace

-

Expected behavior

Identify as the same client each time

Steps to reproduce the behavior

Run the configured script

Inspect of problematic items

No response

Workarounds

add plexapi.BASE_HEADERS['X-Plex-Client-Identifier'] = "PlexTraktSync" recommended by Plex employee - that made the notification diseappear

Install method

pip

Version

0.18

Python Version

3.7

Operating System and Version

Linux

[gitthangbaby]

Related to #168, #200, pkkid/python-plexapi#620,706.
i've changed the workaround to have the constant string there, not sure why platform is used in config.py (it didn't fix #476).

[glensc]

the script triggers "New device" Plex notification on every run:

where is that? screenshot? version of plex?

[glensc]

what are those related issues/pull requests? I see no relation to this at all. where or how or why you took those arbitrary items to be listed here?

[gitthangbaby]

The notification arrives on the users' mobile phone from Plex company whenever new client identifier is used for any access with the same token.

Re mentions: it looks like headers could impact history or cause duplicit processing. 706 is from plexapi (edited above).
Couldn't figure out why all of these header changes exist, especially 168, but seems important to the project so i mention it in case there's a will to change this header as well. This X-Plex-Client-Identifier header record stabilization stops sending endless notification to Plex users on all Plex projects using python-plexapi. As i look at 620 (edited above), it might be python-plexapi issue in the end.

[glensc]

706 is still unclear what, use urls to be crystal clear. and if you out URLs to own line with preceding dash (list item), github includes title for them.

The only change this project does is to use an identifiable device:

• Identify as PlexTraktSync for X-Plex-Platform header #168

so, in the future (still nothing implemented) are able to determine that the watch record was filled b this app, not the actual player.

if anything, it should have made changes better, not worse.

ps: maybe you want to link to commits or code lines instead of the tickets?

[glensc]

Can you send pull request with a fix?

[gitthangbaby]

this should be fixed in plexapi i think, plexapi/init.py uses randomizer per session:
X_PLEX_IDENTIFIER = CONFIG.get('header.identifier', str(hex(getnode())))

here : uuid.getnode will return the same value for every call wthinin a single run of your app. If it has to defer to the random algorithm, then you will get a different value when you start a new instance of your app.

[glensc]

You can get link to specificv line if you click on the line number:

and holding down shift when clicking, you can select range of lines.

[glensc]

Send a pull request for improvement if this is an issue.