Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upon restart of HA the Plex sensor shows as unknown instead of 0 when there are no streams #28485

Closed
dshokouhi opened this issue Nov 2, 2019 · 9 comments
Assignees

Comments

@dshokouhi
Copy link
Member

Home Assistant release with the issue:

0.101.2

Last working Home Assistant release (if known):

0.100.2

Operating environment (Hass.io/Docker/Windows/etc.):

venv

Integration:

plex

https://www.home-assistant.io/integrations/plex/

Description of problem:

When plex is setup and the HA server is restarted when there are no active streams, the sensor shows as unknown instead of 0. If I start a stream and stop it, it will properly reflect 0 streams. In version 0.100.x the sensor would default to 0 upon HA restart if there were no active streams.

image

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

plex:
  token: !secret plex_token

Traceback (if applicable):

n/a

Additional information:

@ObiKaiKenobi
Copy link

Home Assistant release with the issue:
0.101.2

Last working Home Assistant release (if known):
0.100.2

Operating environment (Hass.io/Docker/Windows/etc.):
Home Assistant in Docker (on Ubuntu on Intel NUC)

Integration:
plex https://www.home-assistant.io/integrations/plex/

Description of problem:
Same here.
Already removed all plex configurations from files, removed plex integration and readded it through integration page (recomended).
After restart of HASS the state is unknown again.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
none - configured through "add integration" in GUI.

@probot-home-assistant
Copy link

Hey there @jjlawren, mind taking a look at this issue as its been labeled with a integration (plex) you are listed as a codeowner for? Thanks!

@jjlawren
Copy link
Contributor

jjlawren commented Nov 3, 2019

I can't reproduce locally so it appears to be some kind of race condition. I'll need to think about how this could be happening.

@SPCulhane

This comment has been minimized.

@jjlawren

This comment has been minimized.

@SPCulhane

This comment has been minimized.

@jjlawren

This comment has been minimized.

@jjlawren
Copy link
Contributor

Please check when 0.102.2 is released. I think I've finally figured out the reason and applied a fix.

@jjlawren
Copy link
Contributor

This is fixed as of 0.102.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants