2019-08-28, 21:13
(2019-08-28, 21:10)tuvx Wrote: So am I beyond help?
The log you posted was empty, you need to click "help" in my signature below and follow instructions to submit a log, THX.
(2019-08-28, 21:10)tuvx Wrote: So am I beyond help?
(2019-08-31, 18:41)45thr.james Wrote: Any reason I should expect the locast plugin to not use my location as determined/defined by my locast.org account?
I can access the NY market via my laptop/browser.
I allowed locast.org to access my current location from my browser when subscribing.
However, when running Kodi on the same network, the locast plugin sets my location to Litchfield (about 60mi. north of my actual location).
I am going to look into running the api calls via curl to confirm my assumptions, just wanted to see if there is any knowledge about this issue while I am investigating.
I have tried this with both the 1.0.5 from Kodi repo and your beta repo (same version 1.0.5).
Also, was using locast plugin and worked very well a few months ago, and was watching with the nag ads for subscribing.
Any info appreciated.
Thank you.
(2019-08-31, 18:54)Lunatixz Wrote:I just checked using https://www.iplocation.net/proxy-check and it reports that I *AM* behind a proxy - assuming my ISP is responsible for this.(2019-08-31, 18:41)45thr.james Wrote: Any reason I should expect the locast plugin to not use my location as determined/defined by my locast.org account?
I can access the NY market via my laptop/browser.
I allowed locast.org to access my current location from my browser when subscribing.
However, when running Kodi on the same network, the locast plugin sets my location to Litchfield (about 60mi. north of my actual location).
I am going to look into running the api calls via curl to confirm my assumptions, just wanted to see if there is any knowledge about this issue while I am investigating.
I have tried this with both the 1.0.5 from Kodi repo and your beta repo (same version 1.0.5).
Also, was using locast plugin and worked very well a few months ago, and was watching with the nag ads for subscribing.
Any info appreciated.
Thank you.
Location detection is handled by Locast and reinforced by your IP.
The plugin hasn't changed, so If it worked in the past either the Locast service is at fault or your IP is part of a proxy.
(2019-08-31, 19:49)45thr.james Wrote: I just checked using https://www.iplocation.net/proxy-check and it reports that I *AM* behind a proxy - assuming my ISP is responsible for this.Not sure if this is the same thing but I might be getting the same thing with Pluto TV, works ok on browser but not in Kodi. IP check says I am behind an ISP proxy
Not sure why locast.org using a web browser would different information that the plugin coming from the same netwo
(2019-10-20, 23:43)silvertonesx24 Wrote: Same thing here, it blocks me by location, even though Locast works fine in browser using location.
(2019-10-25, 07:01)jbecker Wrote: I did a clean install of KODI 18.4 on a (mid-2017 release) S905X-based Android TV box and then installed only Locast and Kodi log uploader addons. After configuring the Locast addon w/ the correct Locast login credentials, I tried launching the Locast addon, but each time it aborted before anything Locast-related had appeared on the screen and was accompanied by an error saying check the KODI log file.Please verify you entered the correct credentials into locasts settings, THX
Since repeating the process was yielding the identical failure every time, I enabled debugging for both the Locast addon & the KODI System Debug, exited KODI, then relaunched KODI, ran the Locast addon and once it had crashed again, I uploaded the KODI logfile here.
I then installed a few other Lunatix-authored KODI video addons and all of them loaded normally & streamed video w/o any issues. Also, the Locast app runs fine on this box. So does every other app I've ever installed on the box and I've never had any issues running any stable version of KODI on it.
@Lunatixz, when you have a spare moment, I'd very much appreciate if you'd look at the posted logfile and tell me if you have any suggestions on what is causing this addon to abort loading. When I view the log, I don't understand how it can be generating a "GetDirectory - Error getting plugin://plugin.video.locast/" error, because I've verified that the directory is present, has the proper files in it, and is definitely accessible to KODI. Thank you.
(2019-10-25, 16:55)jbecker Wrote: They're correct. Before I'd even run the addon, I verified the credentials were correct by using File manager to view the relevant (Locast addon data) settings.xml, since that's the simplest way that I know of to confirm that the password I'd entered was correct. I just rechecked the credentials again and they're still the same / correct.
I don't think it's worth spending any more of your or my time on to try to sort of this problem on this particular TV box. I have a Fire TV Pendant and 4K Stick that I'll can KODI on to and see what happens when I try to install, configure, & run the addon on them.
The main reason I posted was just to see if anyone else had experienced this problem and have your expertise check my logfile to see if anything in it pointed to the source of the problem. Thanks for all the hard work you do.
2019-10-25 19:27:49.619 T:140318738695936 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.ValueError'>
Error Contents: No JSON object could be decoded
Traceback (most recent call last):
File "/home/media/.kodi/addons/plugin.video.locast/default.py", line 24, in <module>
if __name__ == '__main__': locast.Locast(sys.argv).run()
File "/home/media/.kodi/addons/plugin.video.locast/resources/lib/locast.py", line 99, in __init__
if self.login(USER_EMAIL, PASSWORD) == False: sys.exit()
File "/home/media/.kodi/addons/plugin.video.locast/resources/lib/locast.py", line 133, in login
data = self.postURL(BASE_API, param={'action':'member_login','username':user,'password':password}, headers=self.buildHeader())
File "/home/media/.kodi/addons/plugin.video.locast/resources/lib/locast.py", line 115, in postURL
return json.loads(cacheresponse)
File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
-->End of Python script error report<--
(2019-10-26, 22:39)alphatitanium Wrote: It looks like locast has completely changed their API. Now everything is done through a more RESTful API via api.locastnet.org. e.g., login is now a post to https://api.locastnet.org/api/user/login, getting epg is now /api/watch/epg/[DMA], getting station/m3u8 info is now /api/watch/station/[ID]/[lat]/[lon]
JSON responses seem to be the same or at least mostly the same.