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

Problems with saving the config-file #166

Open
pimpmytechno opened this issue Jun 5, 2024 · 14 comments
Open

Problems with saving the config-file #166

pimpmytechno opened this issue Jun 5, 2024 · 14 comments
Labels
bug Something isn't working

Comments

@pimpmytechno
Copy link

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:

screen_id: dj************************
name: YouTube on TV
screen_id: ak************************
name: YouTube on TV

In the "Options" section of the plugin, it looks like this:

apikey: *********************************
devices:

screen_id: dj************************
name: YouTube on TV
screen_id: dj************************
name: YouTube on TV
channel_whitelist: []
skip_categories:
sponsor
skip_count_tracking: false
mute_ads: false
skip_ads: true

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?

  • Docker on linux Arm64
  • Device: LG OLED C1
  • OS: WebOS FW 03.40.87
    1
    2
@pimpmytechno pimpmytechno added the bug Something isn't working label Jun 5, 2024
@dmunozv04
Copy link
Owner

This seems to be related with the home assistant add-on. I'm sure @bertybuttface can be more helpful than me debugging this issue

@bertybuttface
Copy link
Contributor

I did take a look when this was posted but didn't see the root cause, apologies for not responding.

@pimpmytechno
Copy link
Author

Do you need any additional information from me?

@bertybuttface
Copy link
Contributor

No idea why its not working, here is an example config:

apikey: <redacted>
devices:
  - screen_id: <redacted>
    name: Device 1
  - screen_id: <redacted>
    name: Device 2
  - screen_id: <redacted>
    name: Device 3
channel_whitelist: []
skip_categories:
  - sponsor
  - selfpromo
  - exclusive_access
  - interaction
  - preview
  - filler
  - music_offtopic
  - intro
  - outro
skip_count_tracking: false
mute_ads: false
skip_ads: true
data_dir: data

@pimpmytechno
Copy link
Author

pimpmytechno commented Jun 21, 2024

Yes, in the Configuration > Options section, I clicked on the three dots and selected "Edit in YAML", after which I inserted this config.
Here's what I got in the add-on menu. It seems that all the settings are saved except for skip_categories. If I select from the dropdown list, I still get the save error "Failed to save add-on configuration, Invalid list for option 'skip_categories' in iSponsorBlockTV add-on".

Also, if it matters, in the YouTube app under 'Settings > Connected devices' there are no connected devices.

2 Снимок экрана 2024-06-22 в 02 33 46

@bertybuttface
Copy link
Contributor

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.

@pimpmytechno
Copy link
Author

pimpmytechno commented Jun 21, 2024

Yes, i commit all categories

  • sponsor
  • selfpromo
  • exclusive_access
  • interaction
  • preview
  • filler
  • music_offtopic
  • intro
  • outro
Снимок экрана 2024-06-22 в 02 55 31

Also, if it matters, in the YouTube app under 'Settings > Connected devices' there are no connected devices.

@dmunozv04
Copy link
Owner

No connected devices appearing is completely normal

@pimpmytechno
Copy link
Author

Maybe I can log in via SSH and manually enter the information into the configuration file?
Where is the configuration file located?

@pimpmytechno
Copy link
Author

I opened the file options.json, and here is its content. I don't see any errors.

{
"apikey": "myapikey",
"devices": [
{
"screen_id": "myid1",
"name": "Device 1"
},
{
"screen_id": "myid2",
"name": "Device 2"
}
],
"channel_whitelist": [],
"skip_categories": [
"sponsor",
"selfpromo",
"exclusive_access",
"interaction",
"preview",
"filler",
"music_offtopic",
"intro",
"outro"
],
"skip_count_tracking": false,
"mute_ads": false,
"skip_ads": true
}

@bertybuttface
Copy link
Contributor

Looks fine to me, what happens when you try and start the addon?

@pimpmytechno
Copy link
Author

The addon starts without errors, here is the information from the logs.

[00:31:57] INFO: Starting...
s6-rc: info: service legacy-services successfully started
2024-06-24 00:31:58,790 - iSponsorBlockTV-myid1 - INFO - Starting device
2024-06-24 00:31:58,790 - iSponsorBlockTV-myid2 - INFO - Starting device

@pimpmytechno
Copy link
Author

Hello! Any updates?

@bertybuttface
Copy link
Contributor

Unable to reproduce sorry mate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants