You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have iSponsorBlockTV running in docker on my Synology NAS,
I ran the setup and added a single User/TV and its working as intended
I however want to add more devices however am unsure if running setup again will break anything, so I might want to reinstall the docker and run setup again, adding all the devices in one go.
Alternatively if there is an easy method to convert the YouTube link code to a screen id, I could amend the config file to add more devices.
Of course if there was any way to automatically cover any device on the same LAN that would be the most ideal.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is the same for all platforms, but I created mine in a docker and this works for me, the only difference should be main.py vs main.pyc
Anyways,
Open a console inside the container or whatever is running iSponsorBlockTV,
If not already, change directory to /app with cd /app
Then run python main.pyc --setup
This should load the standard GUI setup, if that doesn't work, you may have main.py instead, and if the GUI isn't working, try --setup-cli instead.
If that's not clear enough let me know! Just did this myself and figured I'd post about it
I have iSponsorBlockTV running in docker on my Synology NAS,
I ran the setup and added a single User/TV and its working as intended
I however want to add more devices however am unsure if running setup again will break anything, so I might want to reinstall the docker and run setup again, adding all the devices in one go.
Alternatively if there is an easy method to convert the YouTube link code to a screen id, I could amend the config file to add more devices.
Of course if there was any way to automatically cover any device on the same LAN that would be the most ideal.
The text was updated successfully, but these errors were encountered: