@
webmaher i have some information now, it's not your credentials. I can't recreate the problem here, for me is still working but i have a direct subscription (which use a different api call for login, but was the same request/response). So i don't have a solution for this yet, and not sure what is causing the problem. More debug logs from ppl experiencing the problem might be helpfull.
log:
2019-07-14 21:33:41.915 T:9632 DEBUG: [plugin.video.hbogoeu] DEVICE REGISTRATION
2019-07-14 21:33:41.915 T:9632 DEBUG: [plugin.video.hbogoeu] GET FROM HBO URL: https://si.hbogo.eu/services/settings/si...ister.aspx
2019-07-14 21:33:41.915 T:9632 DEBUG: [plugin.video.hbogoeu] GET FROM HBO RESPONSE FORMAT: json
2019-07-14 21:33:42.140 T:9632 DEBUG: [plugin.video.hbogoeu] GET FROM HBO ERROR: ConnectionError(ProtocolError('Connection aborted.', BadStatusLine("''",)),)
The device registration fail and is a connection problem. Tested and found they removed that api call and i can recreate that, so is consistent.
But that was optional, some operators required an individualization and device id before login and some don't and it gets returned upon login. So that might be what's going on.
On the login api call a status 400 get returned Bad request
log:
2019-07-14 21:33:42.378 T:9632 DEBUG: [plugin.video.hbogoeu] SEND LOGIN URL: https://sigwapi.hbogo.eu/v2.1/Authentica...n/ENG/COMP
2019-07-14 21:33:42.378 T:9632 DEBUG: [plugin.video.hbogoeu] SEND LOGIN RESPONSE FORMAT: json
2019-07-14 21:33:42.556 T:9632 DEBUG: [plugin.video.hbogoeu] SEND LOGIN RETURNED STATUS: 400
2019-07-14 21:33:42.557 T:9632 DEBUG: [plugin.video.hbogoeu] SEND LOGIN RETURNED RAW:
...
<p class="heading1">Request Error</p>
<p>The server encountered an error processing the request. See server logs for more details.</p>
...
So the error is server side with status bad request.
But since i can't recreate and experiment not sure what is missing or what is wrong with the request sent by the add-on, nothing changed on that part in the add-on for a long time.
They might have changed something for 3th party operator login or changed something only for some operators idk. Or that operator requires a device id and individualization to be generated before login.
If you can save al the request responses with the developer tools of your browser while logging in on the website (edit out sensitive information) and send it to me, would help to solve this.
I can try to generate client side the individualization UUID and device id UUID and send it in the login request an see if it works. Is done like that for the spain-nordic version and it works.
To test that theory you could edit/create manually the setting.xml file in user data in the add-on folder (
this is just for this specific test).
xml:
<settings version="2">
<setting id="country_code">si</setting>
<setting id="customerId">RANDOM_UUID_V4</setting>
<setting id="deflang" default="true">false</setting>
<setting id="delsetup" default="true"></setting>
<setting id="FavoritesGroupId"></setting>
<setting id="forcescrap" default="true">false</setting>
<setting id="forcesubs">true</setting>
<setting id="individualization">RANDOM_UUID_V4</setting>
<setting id="is_settings" default="true"></setting>
<setting id="KidsGroupId" default="true"></setting>
<setting id="lastsearch" default="true"></setting>
<setting id="logout" default="true"></setting>
<setting id="operator_id">93a542b5-b4d8-4c76-bf3b-1eb261e39cfe</setting>
<setting id="operator_is_web">false</setting>
<setting id="operator_name">Telemach</setting>
<setting id="operator_redirect_url" default="true"></setting>
<setting id="origtitles">true</setting>
<setting id="password"></setting>
<setting id="sensitivedebug" default="true">false</setting>
<setting id="sessionvalid">2</setting>
<setting id="username"></setting>
</settings>
Generate RANDOM_UUID_V4 using
https://www.uuidgenerator.net/ one for device_id and a different one for individualization
Don't try to edit manually username and password the add-on will still prompt for one on login attempt if its empty or undecryptable or malformatted and then properly save an encrypted version to setting.xml.
This will take some guesswork and trial and error to solve.
