-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
Problems with saving the config-file #166
Comments
This seems to be related with the home assistant add-on. I'm sure @bertybuttface can be more helpful than me debugging this issue |
I did take a look when this was posted but didn't see the root cause, apologies for not responding. |
Do you need any additional information from me? |
No idea why its not working, here is an example config:
|
Plausibly something to do with this commit from a recently accepted PR: bertybuttface/addons@a95c25e Try setting more than one skip_category, there may be a bug with setting exactly 1 skip category now. |
No connected devices appearing is completely normal |
Maybe I can log in via SSH and manually enter the information into the configuration file? |
I opened the file options.json, and here is its content. I don't see any errors. { |
Looks fine to me, what happens when you try and start the addon? |
The addon starts without errors, here is the information from the logs. [00:31:57] INFO: Starting... |
Hello! Any updates? |
Unable to reproduce sorry mate. |
I am using iSponsorBlock as an add-on for HomeAssistant.
The plugin starts successfully, but it does not work on my LG OLED C1.
My cfg file looks as follows:
In the "Options" section of the plugin, it looks like this:
When I try to put it into the correct format, I get an error:
Failed to save add-on configuration, Missing option 'devices' in root in iSponsorBlockTV add-on (932a64e5_isponsorblocktv). Got {'apikey': 'myapikey', 'channel_whitelist': [], 'skip_categories': ['sponsor'], 'skip_count_tracking': False, 'mute_ads': False, 'skip_ads': True}
Is there any solution for this problem?
The text was updated successfully, but these errors were encountered: