klattimer/LGWebOSRemote

lgtv scan not working

Person2099 opened this issue · 8 comments

Upon running the lgtv scan command I receive an unrecognisable output: (personal details are #'ed)

Unknown device
b'HTTP/1.1 200 OK\r\nHOST: ###.###.###.###:1900\r\nEXT:\r\nCACHE-CONTROL: max-age=100\r\nLOCATION: http://###.###.###.###:80/description.xml\r\nSERVER: Hue/1.0 UPnP/1.0 IpBridge/1.45.0\r\nhue-bridgeid: 001788FFFEAF4BEA\r\nST: upnp:rootdevice\r\nUSN: uuid:########-####-####-####-############::upnp:rootdevice\r\n\r\n' ('###.###.###.###', 1900)
Traceback (most recent call last):
File "/Users/keets/.local/bin/lgtv", line 8, in
sys.exit(main())
File "/Users/keets/.local/pipx/venvs/lgtv/lib/python3.9/site-packages/LGTV/init.py", line 111, in main
results = LGTVScan()
File "/Users/keets/.local/pipx/venvs/lgtv/lib/python3.9/site-packages/LGTV/scan.py", line 28, in LGTVScan
uuid = re.findall(r'uuid:(.*?):', line.decode('utf-8'))[0]
IndexError: list index out of range

Interesting, could you install a upnp browser/analyser and see what you find, looks like a rogue dnla device

I've done some snooping around and I believe the device is my Phillips Hue Hub, however I have still found no explanation as to why the scan appears like that as opposed to how it is meant to.

Commit 126d1cf should fix it.

Please report back here with the value for USN as reported by the updated scanning tool.

I have ensured the most recent commit is installed however the error still persists. The current error is below:
Screen Shot 2021-09-01 at 5 24 05 pm

That's great, I just pushed a small change should get you past that, you're right it's your hue bulb and it appears the /r/n's are confusing the regex. Please check and close issue when done.

Unfortunately that doesn't seem to be the only issue I'm running into.
I have attached the response I get now:
Screen Shot 2021-09-02 at 8 04 58 pm

I completely uninstalled and reinstalled the latest commit and that seems to have fixed the issue. Thank You!

cdam06 commented

I completely uninstalled and reinstalled the latest commit and that seems to have fixed the issue. Thank You!

I'm running into this issue still. This may be a dumb question, but how do I go about uninstalling and doing a fresh install again?