-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
NPOstart login failed #1842
Comments
I need a debug retrospect.log. |
kodi.log.zip |
Sorry here the debug log |
This is a kodi.log. Please provide a debug |
Ok, thanks https://paste.kodi.tv./gufibixoma One more time |
Did you configure a NPO account within Retrospect? |
No, I never needed that, it worked fine for years without, |
NP. I am still in doubt how to handle this. For users abroad it is required, for users in NL not always. I will leave this issue open as a reminder to think on a solution. But good to hear it is working now. |
I'm outside of NL but to see the Live channels sinds a couple of months I use a dedicated VPN to a private server and IP in the house of family in NL, before I used a normal VPN service but I had never this problem till I noticed it some weeks ago |
well i created a npo account, configured it in retrospect and still get the error could not log in? It used to work to just ignore this error but since yesterday (21-10-2024) none of the npo channnels will play |
I need a debug log for that. Double check you are not mixing up the Retrospect pin and NPO password. So enable debug logging in Retrospect, reproduce the issue and provide a Retrospect.log here as attachment. ALSO: I released a fix for NPO yesterday. Make sure you have 5.7.20 installed |
I also do have the issue that NPO says that log-in is required, but nonetheless it is working. I'm located in NL. |
I know, so please create a login in, and configure it in Retrospect to resolve the issue. |
Same issue here. Maybe a good solution to change the XbmcWrapper.show_dialog function for a Toast style. That way it will not require any user input but the user will still recieve a warning.
|
@spacie2136 Thanks for that, changing as follows removed the message for me.
|
I could change that. |
Please don't do this, as it will impact all channels and will cause issues. I will change the pop-up into a notification. BUT: Just create an NPO login and configure it. NPO requires accounts for some streams and always require accounts when watching from abroad. |
Please try this: https://github.com/retrospect-addon/plugin.video.retrospect/archive/refs/heads/1842-npostart-login-failed.zip Or just create an NPO account. |
Thanks for the fix: the notification is better than a dialog box. However, According to https://npo.nl/start/aanmelden it seems not required to PS In het bestand channels/channel.nos/nos2010/chn_nos2010.json is |
I will double check. But I do remember there was a thing. |
Please check: https://github.com/retrospect-addon/plugin.video.retrospect/archive/refs/heads/1842-npostart-login-failed.zip I now only use a login if you configured one. EDIT: In deze zip zit nog niet #1874 |
It works like a charm! |
Will push an official release soon. |
This is the best approach i guess. Thanks! |
Great! The PIN you only need once every couple of months. It is just to keep your log-in secure. |
I meant the retrospect pin vault |
I know: but you only need it to get a session token for NPO, and then not for a long time. |
mm that is not my experience, pin is asked after every boot of libreelec for every channel and channel change So your solution to only use a configured login is for me the best approach, no account, no pin vault and no warning, great! |
That should not be, unless you manually delete stuff in the profile folder. But hey, if you are happy now. |
Selecting NPOstart live TV, any channel gives a error message Retrospect Login Failed: 'Could not log on the selected channel'
Selecting 'OK' will opening the channel anyway
Expected Behavior
Actual Behavior
Possible Fix
To Reproduce
Steps to reproduce the behavior:
Debuglog
The debug retrospect.log can be found here:
Your Environment
Used Operating system:
Used versions:
The text was updated successfully, but these errors were encountered: