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

Plex Configurator mandatory or Always display in Notifications #22973

Closed
marc-gist opened this issue Apr 10, 2019 · 3 comments
Closed

Plex Configurator mandatory or Always display in Notifications #22973

marc-gist opened this issue Apr 10, 2019 · 3 comments

Comments

@marc-gist
Copy link

Home Assistant release with the issue:

0.91.2

Last working Home Assistant release (if known):
Unknown (has been like this for sometime, have to disable configurator in yaml to get it to go away.

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

Hass.io and Python VENV

Component/platform:

Plex

Description of problem:

Notification is always present to configure Plex. I don't want to configure plex into HA. Most have a dismiss option on the notification, This one does not.

image

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

Traceback (if applicable):


Additional information:

@fredrike
Copy link
Contributor

You should tell discovery to ignore plex as below, I think this is a configuration issue on your side..

discovery:
  ignore:
    - plex_mediaserver

@marc-gist
Copy link
Author

Thanks, but I shouldn't have to touch the configuration, or so says Paulus at his speech at ING and recently when I tried to make change to allow something from the configuration, he denied it, as modification should be in the GUI.
Also, this appears to be the only "discovery" item that doesn't have a dismiss button! (at least that I have on my network).

@stale
Copy link

stale bot commented Jul 9, 2019

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 9, 2019
@stale stale bot closed this as completed Jul 16, 2019
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

3 participants