48 replies to this topic

[ciciol]

There was an error in creating entry list! Maybe try other feeds...

 

 

 

Hello, VU + UNO 4K SE OpenPLi 7.2. I watched YouTube yesterday and everything worked fine. After an hour or so, I wanted to watch something again, and unfortunately only the message is shown: 

 

There was an error in creating entry list! Maybe try other feeds...

 

Restarting the receiver, uninstalling and reinstalling does nothing. The message is constantly displayed.

Attached Files

•  20200316_053807.jpg   59.14KB   24 downloads

[FRAP]

ciciol Hello .

 

You must have Google registration! Create your own keys and type them into YouTubeUI.py.

Google has reduced the number of requests for the keys that are in the plugin, so you have to create your own and then watch without restrictions.

 

https://github.com/j...rsonal-API-Keys              An example with pictures of how to do it!

 

 

To enter your credentials into the plugin, you need to edit the values of the variables

Код: [Выделить]

API_KEY =

YOUTUBE_API_CLIENT_ID = 

YOUTUBE_API_CLIENT_SECRET = 

  in lines 129-131 in /usr/lib/enigma2/python/Plugins/Extensions/YouTube/YouTubeUI.py Specify them in single brackets as in the original code. Save changes and make Restart GUI.

[ciciol]

Thank you very much and I wish you good health for this time.

[ciciol]

I did everything right. The problem is only editing the YouTubeUI.py file
How to edit it? Regards

[FRAP]

You must have three generated keys.

Open the YouTubeUi.py file with a text editor and find three lines in it (as in the picture) and replace them with your keys.

Everything as in the original file should only be with your keys.

 

API_KEY = 'AIzaSyCyIlbb0FIwoieEZ9RTShMVkRMisu-ZX0k'

YOUTUBE_API_CLIENT_ID = '411447027255-vbgs05u1o3m8mpjs2vcd04afrg60drba.apps.googleusercontent.com'

YOUTUBE_API_CLIENT_SECRET = 'fYE-8T3qf4DrLPLv3NTgvjna'

 

 

 

 

 

API_KEY = 'xxxxxxxxx'

YOUTUBE_API_CLIENT_ID = 'xxxxxxxx'

YOUTUBE_API_CLIENT_SECRET = 'xxxxxxxxxxx'

 

Attached Files

•  YouTubeUi.py.png   101.05KB   23 downloads

[ciciol]

I have already generated these 3 keys. Problem.nam, because in my YouTube folder there is only YouTubeUI.pyo file and there is no YouTubeUI.py file

[FRAP]

https://raw.githubus...rc/YouTubeUi.py

 

ready-made file for editing

 

 

Attached Files

•  YouTubeUi.zip   12.85KB   73 downloads

[ciciol]

Thank you

[Tech]

I have already generated these 3 keys. Problem.nam, because in my YouTube folder there is only YouTubeUI.pyo file and there is no YouTubeUI.py file

Just in case you want to solve the 'issue' by yourself instead of using the (great) service from FRAP.....

 

The needed files are not available because the sources from the youtube plugin are not installed.

You can install them by using a telnet client (putty) and type

enigma2-plugin-extensions-youtube-src

Just browse to the plugin folder and edit the py file, the pyo will be overwitten by the compiled (and edited) py when you restart enigma2.

[ciciol]

Now I have it, it's explained as for a child and I understood everything. Thank you very much for your help. Have a nice day

Edited by ciciol, 17 March 2020 - 07:10.

[FRAP]

How to create YouTube API Key 2020

 

(Video hints for those people who find it hard to do.)

 

[plecky]

HI, i need hepl. How do i edit YoutubeUi.pyo? What use software for edit? Thanks

[WanWizard]

You can't edit pyo and pyc files, you need the source, which is in the py file. Source packages can be installed seperately.

[Tech]

HI, i need hepl. How do i edit YoutubeUi.pyo? What use software for edit? Thanks

Just read a few messages above your reply to read the answer to your question!! 

In my opinion, it is quite amazing that people just start asking questions before reading.......

 

https://forums.openp...dpost&p=1177984

[s3n0]

- simple shell script to change the api key directly inside of the file:

#!/bin/sh

KEY_OLD='AIzaSyCyIlbb0FIwoieEZ9RTShMVkRMisu-ZX0k'    # original YoutubeDL key
KEY_NEW='AIza_NewKey_NewKey_NewKey_NewKey_NewKey'    # new generated key - use YOUR OWN NEW generated API KEY
sed -i -e "s/$KEY_OLD/$KEY_NEW/I" /usr/lib/enigma2/python/Plugins/Extensions/YouTube/YouTubeUi.pyo

- or single line:

sed -i -e 's/AIzaSyCyIlbb0FIwoieEZ9RTShMVkRMisu-ZX0k/AIza_NewKey_NewKey_NewKey_NewKey_NewKey/I' /usr/lib/enigma2/python/Plugins/Extensions/YouTube/YouTubeUi.pyo

 

 

[littlesat]

Brrr or install the py source file and change it there...
Wierd that the plugin does not have a config for that...!!!

[athoik]

Please read: https://stackoverflo...e-data-api-keys

Maybe it's possible to create more API keys and rotate them randomly?

[s3n0]

Thus, programming a configuration to insert an API user key in the GUI MENU is a simple matter. The Youtube plugin for most Enigma distributions has a basic configuration. There it would be easy to add one configuration item to change API_KEY that is currently declared as a fixed value. This item will always be stored in the Enigma configuration (file /etc/enigma2/settings), because of course the config python module from Enigma would be used. Easy as a slap. I'm just waiting to see if there is any other solution or when @Taapat adds it. I think most Enigma distributions draws the source code of the Youtube plugin directly from @Taapat - https://github.com/T...-plugin-youtube .

Edited by s3n0, 25 March 2020 - 14:14.

[Taapat]

I'm sorry!

Due to changes in OpenPLi development where for individual file changes you have to fight, i have stopped development process in OpenPLi.

So I haven't found the time to make changes in the plugin.

I hope to make changes in the coming days.

 

 

Brrr or install the py source file and change it there...
Wierd that the plugin does not have a config for that...!!!

YOUTUBE_API_CLIENT_ID is 72 characters long. Do you think it can be entered normally with the remote in config?

 

Please read: https://stackoverflo...e-data-api-keys

Maybe it's possible to create more API keys and rotate them randomly?

Each combination of API keys requires new authentication.

This means after each API keys rotation the user needs to approve the plugin using another device.

 

Thefore I plan to create a separate file for the keys in the enigma config folder.

It will be saved by creating enigma backup and will be easier to enter keys.

In addition, developers will be able to use their own keys and reduce the load on plugin keys.

 

 

[s3n0]

I don't know how many connections one API_KEY is limited, but if it's 1000, for example, it should be enough to generate a different API_KEY for each brand of device.

If this is limited to a smaller number (for example, 10), then this is a bigger problem, as each user will need to use their own Youtube / Google account for the YouTtube plugin. Since Enigma is not well secured, it is not good because it is difficult to protect the Youtube / Google account stored in the Enigma set-top box.