Plex: error calling service configurator/configure. invalid boolean value None

Configuration
1

Hi everybody,

I am trying to integrate Plex to my home assistant.

configuration.yaml

media_player:
  - platform: plex

manually created plex.conf

{"<myip>:32400": {"token": "claim-<my-token>", "ssl": false, "verify": true}}

When I (re)start home assistant, I get a prompt to set up plex (which I should have already done via the plex.conf, right?). When I click it, there is a popup with

(x) Plex Media Server
Enter the X-Plex-Token
X-Plex-Token
(input box) => my token
Use SSL
(input box) => false
Do not verify SSL
(input box) => true

When I click save, I’ll get Fehler beim Aufrufen des Service configurator/configure. invalid boolean value None, which should roughly translate to error calling service configurator/configure. invalid boolean value None. There is no “None” value. There is false and then true. When I enter something non-boolean in the Use SSL box, I’ll get Fehler beim Aufrufen des Service configurator/configure. invalid boolean value testing.

However! No matter what I enter in the Do not verify SSL box, I’ll always get that invalid boolean value None error. It seems to me like no matter what I put there, it does not register but submit an empty box instead.

Has anybody else encountered this error and knows how to fix it? I initially set up Plex via the docs. I assumed manually creating the plex.conf would mean that I wouldn’t even have to insert anything else via webGUI, but apparently I do. This is a bit confusing.

Thanks in advance for your help :slight_smile:

2

Does plex integration work for anybody else just fine? I have tried different hosts as well as pulling the latest docker image to assure this wasn’t a problem with my particular version of home assistant, but it still won’t work.

3

Have you checked the file permissions for plex.conf? I would assume Read and maybe Execute are needed, but that’s just a guess.

I’m not too familiar with the Plex component nor with Docker but I’d thought I’d chime in since nobody else has yet.

1 Like
4

The default permissions for plex.conf should be 744.

@prankousky is plex.conf getting generated at all?

If not you can manual create the file so you can at least get it working using this format:

{
    "PLEX_IP:32400": {
        "ssl": false,
        "token": "YOUR_TOEKEN_HERE",
        "verify": false
    }
}
2 Likes
5

Thank you both!

I don’t know what did it. I changed user rights to 744 as well as manually re-generated the plex.conf, but set both values to false. I then changed some settings in plex as well (multiple connections allowed for my user, added hass server ip to trusted devices), and now it seems to work :slight_smile: Awesome! Now to automate some stuff like dimmed lights when playing media on plex.

2 Likes