Rasbperry Issues

[greensouth]

Hi!

Does the installation works under Raspbian? I'm trying to run the setup process and I found a lot of error messages.

running install running bdist_egg running egg_info writing requirements to samsungctl.egg-info/requires.txt writing samsungctl.egg-info/PKG-INFO writing top-level names to samsungctl.egg-info/top_level.txt writing dependency_links to samsungctl.egg-info/dependency_links.txt writing entry points to samsungctl.egg-info/entry_points.txt package init file 'samsungctl/remote_encrypted/py3rijndael/init.py' not found (or not a regular file) reading manifest file 'samsungctl.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'README.rst' writing manifest file 'samsungctl.egg-info/SOURCES.txt' installing library code to build/bdist.linux-armv7l/egg running install_lib running build_py creating build/bdist.linux-armv7l/egg creating build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/key_mappings.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/remote.py -> build/bdist.linux-armv7l/egg/samsungctl creating build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted creating build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael copying build/lib.linux-armv7l-2.7/samsungctl/remote_encrypted/py3rijndael/constants.py -> build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael copying build/lib.linux-armv7l-2.7/samsungctl/remote_encrypted/py3rijndael/paddings.py -> build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael copying build/lib.linux-armv7l-2.7/samsungctl/remote_encrypted/py3rijndael/rijndael.py -> build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael copying build/lib.linux-armv7l-2.7/samsungctl/remote_encrypted/init.py -> build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted copying build/lib.linux-armv7l-2.7/samsungctl/remote_encrypted/keys.py -> build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted copying build/lib.linux-armv7l-2.7/samsungctl/remote_encrypted/command_encryption.py -> build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted copying build/lib.linux-armv7l-2.7/samsungctl/remote_encrypted/crypto.py -> build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted copying build/lib.linux-armv7l-2.7/samsungctl/config.py -> build/bdist.linux-armv7l/egg/samsungctl creating build/bdist.linux-armv7l/egg/samsungctl/upnp creating build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/instance_singleton.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/service.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/icon.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/data_type.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/upnp_class.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/main.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/init.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/xmlns.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/embedded_device.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/listen.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/discover.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/UPNP_Device/action.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device copying build/lib.linux-armv7l-2.7/samsungctl/upnp/init.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp copying build/lib.linux-armv7l-2.7/samsungctl/upnp/discover.py -> build/bdist.linux-armv7l/egg/samsungctl/upnp copying build/lib.linux-armv7l-2.7/samsungctl/interactive.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/remote_legacy.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/websocket_base.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/main.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/init.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/remote_websocket.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/application.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/exceptions.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/utils.py -> build/bdist.linux-armv7l/egg/samsungctl copying build/lib.linux-armv7l-2.7/samsungctl/wake_on_lan.py -> build/bdist.linux-armv7l/egg/samsungctl byte-compiling build/bdist.linux-armv7l/egg/samsungctl/key_mappings.py to key_mappings.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote.py to remote.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael/constants.py to constants.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael/paddings.py to paddings.pyc File "build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael/paddings.py", line 7 def encode(self, source: bytes) -> bytes: # pragma: nocover ^ SyntaxError: invalid syntax

byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael/rijndael.py to rijndael.pyc File "build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/py3rijndael/rijndael.py", line 12 def init(self, key, block_size: int = 16): ^ SyntaxError: invalid syntax

byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/init.py to init.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/keys.py to keys.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/command_encryption.py to command_encryption.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_encrypted/crypto.py to crypto.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/config.py to config.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/instance_singleton.py to instance_singleton.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/service.py to service.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/icon.py to icon.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/data_type.py to data_type.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/upnp_class.py to upnp_class.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/main.py to main.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/init.py to init.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/xmlns.py to xmlns.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/embedded_device.py to embedded_device.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/listen.py to listen.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/discover.py to discover.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/UPNP_Device/action.py to action.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/init.py to init.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/upnp/discover.py to discover.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/interactive.py to interactive.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_legacy.py to remote_legacy.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/websocket_base.py to websocket_base.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/main.py to main.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/init.py to init.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/remote_websocket.py to remote_websocket.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/application.py to application.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/exceptions.py to exceptions.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/utils.py to utils.pyc byte-compiling build/bdist.linux-armv7l/egg/samsungctl/wake_on_lan.py to wake_on_lan.pyc creating build/bdist.linux-armv7l/egg/EGG-INFO copying samsungctl.egg-info/PKG-INFO -> build/bdist.linux-armv7l/egg/EGG-INFO copying samsungctl.egg-info/SOURCES.txt -> build/bdist.linux-armv7l/egg/EGG-INFO copying samsungctl.egg-info/dependency_links.txt -> build/bdist.linux-armv7l/egg/EGG-INFO copying samsungctl.egg-info/entry_points.txt -> build/bdist.linux-armv7l/egg/EGG-INFO copying samsungctl.egg-info/not-zip-safe -> build/bdist.linux-armv7l/egg/EGG-INFO copying samsungctl.egg-info/requires.txt -> build/bdist.linux-armv7l/egg/EGG-INFO copying samsungctl.egg-info/top_level.txt -> build/bdist.linux-armv7l/egg/EGG-INFO creating 'dist/samsungctl-0.8.0b-py2.7.egg' and adding 'build/bdist.linux-armv7l/egg' to it removing 'build/bdist.linux-armv7l/egg' (and everything under it) Processing samsungctl-0.8.0b-py2.7.egg removing '/usr/local/lib/python2.7/dist-packages/samsungctl-0.8.0b-py2.7.egg' (and everything under it) creating /usr/local/lib/python2.7/dist-packages/samsungctl-0.8.0b-py2.7.egg Extracting samsungctl-0.8.0b-py2.7.egg to /usr/local/lib/python2.7/dist-packages File "/usr/local/lib/python2.7/dist-packages/samsungctl-0.8.0b-py2.7.egg/samsungctl/remote_encrypted/py3rijndael/paddings.py", line 7 def encode(self, source: bytes) -> bytes: # pragma: nocover ^ SyntaxError: invalid syntax

File "/usr/local/lib/python2.7/dist-packages/samsungctl-0.8.0b-py2.7.egg/samsungctl/remote_encrypted/py3rijndael/rijndael.py", line 12 def init(self, key, block_size: int = 16): ^ SyntaxError: invalid syntax

samsungctl 0.8.0b is already the active version in easy-install.pth Installing samsungctl script to /usr/local/bin

Installed /usr/local/lib/python2.7/dist-packages/samsungctl-0.8.0b-py2.7.egg Processing dependencies for samsungctl==0.8.0b Searching for ipaddress Reading https://pypi.python.org/simple/ipaddress/ Best match: ipaddress 1.0.22 Downloading https://files.pythonhosted.org/packages/97/8d/77b8cedcfbf93676148518036c6b1ce7f8e14bf07e95d7fd4ddcb8cc052f/ipaddress-1.0.22.tar.gz#sha256=b146c751ea45cad6188dd6cf2d9b757f6f4f8d6ffb96a023e6f2e26eea02a72c Processing ipaddress-1.0.22.tar.gz Writing /tmp/easy_install-R5AapY/ipaddress-1.0.22/setup.cfg Running ipaddress-1.0.22/setup.py -q bdist_egg --dist-dir /tmp/easy_install-R5AapY/ipaddress-1.0.22/egg-dist-tmp-CIaAZM zip_safe flag not set; analyzing archive contents... Adding ipaddress 1.0.22 to easy-install.pth file

Installed /usr/local/lib/python2.7/dist-packages/ipaddress-1.0.22-py2.7.egg Searching for pycryptodome==3.7.3 Best match: pycryptodome 3.7.3 Processing pycryptodome-3.7.3-py2.7-linux-armv7l.egg pycryptodome 3.7.3 is already the active version in easy-install.pth

Using /usr/local/lib/python2.7/dist-packages/pycryptodome-3.7.3-py2.7-linux-armv7l.egg Searching for ifaddr==0.1.6 Best match: ifaddr 0.1.6 Processing ifaddr-0.1.6-py2.7.egg ifaddr 0.1.6 is already the active version in easy-install.pth

Using /usr/local/lib/python2.7/dist-packages/ifaddr-0.1.6-py2.7.egg Searching for six==1.8.0 Best match: six 1.8.0 Adding six 1.8.0 to easy-install.pth file

Using /usr/lib/python2.7/dist-packages Searching for lxml==3.4.0 Best match: lxml 3.4.0 lxml 3.4.0 is already the active version in easy-install.pth

Using /usr/lib/python2.7/dist-packages Searching for requests==2.4.3 Best match: requests 2.4.3 requests 2.4.3 is already the active version in easy-install.pth

Using /usr/lib/python2.7/dist-packages Searching for websocket-client==0.54.0 Best match: websocket-client 0.54.0 Adding websocket-client 0.54.0 to easy-install.pth file

Using /usr/local/lib/python2.7/dist-packages Finished processing dependencies for samsungctl==0.8.0b

[Mark-Sellwood]

Hi, I have tried, the steps I used are as follows:- Download the Raspbian Stretch Lite image (November 2018) release Configured Image using sudo raspi-config Updates & upgraded using sudo apt-get update sudo apt-get upgrade Setup networking to give it a fixed IP sudo nano /etc/dhcpcd.conf Installed some dependencies sudo apt-get install python3-pip sudo python3 -m pip install setuptools sudo apt-get install libxml2-dev sudo apt-get install libxslt-dev Copied the Master Zip, unpacked it then copied to a new directory on the Pi Executed sudo python3 setup.py install from the new directory. This takes some time, may be 30 mins. No errors this way.

I then ran samsungctl -v --host 192.168.1.66 --key KEY_VOLDOWN The TV (a UE55KS9000) asked me to allow the connection, I did this but nothing happened If I use samsungctl -v --host 192.168.1.66 --key KEY_VOLDOWN all i get is: - Available keys

Note: Key support depends on TV model.

Volume Keys
---------------------------------------------------
    KEY_VOLDOWN:                        Volume Down

But nothing happens on the TV, same with any other command. I don't know if K series are supported yet.

Don't know if this helps.

[greensouth]

I don't know how I finally did it, but I was able to install.

Same is happening to me. Some commands for K series seems unable to work. Can't control neither brightness nor contrast, sharpness and probably choosing HDMI entries.

[kdschlosser]

this is not a valid command line entry

samsungctl -v --host 192.168.1.66 --key KEY_VOLDOWN

please read the documentation spcifically the section on command line use,

[kdschlosser]

I am also going to have to check and see if i can stop the byte compiling of the files.

[kdschlosser]

using this to run the setup program will disable byte compiling the files. The reason why you are getting the error. is because the encrypted websocket connection (H, and J TV's) is not supported yet for python 2. so when it goes to compile the files an error gets thrown. by using the -B it will skip byte compiling the files.

python -B setup.py install

[kdschlosser]

I modified the library to now auto detect the connection method, the port as well as the mac address. so the only parameters needed are going to be the --host and the key name if you want to use a key.

here are 2 examples of changing the volume

samsungctl --host 192.168.1.66 KEY_VOLDOWN

and

samsungctl --host 192.168.1.66 --volume 20

If your TV is 2014 and newer. You will encounter the TV asking to pair each and every single time you use the command line.. UNLESS You specify a path and filename to save the config data to.

samsungctl --host 192.168.1.66 --config-file "/PATH/FILE.NAME"

This will automatically detect all of the setting needed to connect to your TV and set everything up so that repeated connections to the TV will not cause the pairing process to happen again. Every time you want to send a command after hat initial setup process you will need to enter the config-file parameter and the command you wish to use (NOTHING ELSE).

examples of changing the volume.

samsungctl --config-file "/PATH/FILE.NAME" KEY_VOLDOWN

and

samsungctl --config-file "/PATH/FILE.NAME" --volume 20

when you use thee config-file parameter all of the needed information will be saved to the config file each and every time you send a command to the TV. so if there is a token update. the new token data gets saved.

NOTE: be sure to wrap the path to your config file in double quotes (") this will ensure there are no problems for odd characters or spaces in the path during the parsing process of the command line parameters.

[matthieut59]

Working like a charm on my raspberry

[Mark-Sellwood]

I cant get it working on my Raspberry with a UE55KS9000 @matthieut59 What did you do?

I run samsungctl --host 192.168.1.66 --config-file "/home/pi/Lounge.conf" KEY_VOLDOWN I get asked by the TV to confirm the connection, I accept. A config file gets made with the following in it:- description = SPARE-PI host = 192.168.1.66 port = 8001 id = None method = websocket timeout = 0 token = None device_id = None upnp_locations = http://192.168.1.66:9119/screen_sharing, http://192.168.1.66:7676/rcr/, http://192.168.1.66:9197/dmr, http://192.168.1.66:7678/nservice/ paired = True mac = e4:7d:bd:95:07:a1 name = samsungctl

If i run samsungctl --config-file "/home/pi/Lounge.conf" KEY_VOLDOWN nothing happens on the TV but i notice that the time stamp on the config file gets updated.

Am I missing something?

[kdschlosser]

try it again using this command. and remember you are able to do multiple button presses

samsungctl --config-file "/home/pi/Lounge.conf" KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN

I am wondering if the first one is being ignore by the TV for some reason.

[matthieut59]

try also a --volume -1 to check if upnp is working well (as key press and upnp command are not using the same endpoint), if one is working the other should also work

[Mark-Sellwood]

Ok, so samsungctl --config-file "/home/pi/Lounge.conf" KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN turns the Volume up 2 samsungctl --config-file "/home/pi/Lounge.conf" KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN turns the volume down 1 samsungctl --config-file "/home/pi/Lounge.conf" KEY_VOLUP KEY_VOLUP KEY_VOLUP turns the volume up 1 samsungctl --config-file "/home/pi/Lounge.conf" KEY_VOLUP KEY_VOLDOWN KEY_VOLUP turns the volume up 1 So it looks as if the TV is ignoring the first 2 commands.

samsungctl --config-file "/home/pi/Lounge.conf" --volume -1 returns Volume: [None] %

[kdschlosser]

Ok, so samsungctl --config-file "/home/pi/Lounge.conf" KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN turns the Volume up 2

??? it turn it up 2???

an this response

Volume: [None] % means that direct input of the volume does not work on your TV.. YET!

[kdschlosser]

try also a --volume -1 to check if upnp is working well (as key press and upnp command are not using the same endpoint), if one is working the other should also work

hate to burst your bubble on this.. not a true statement.. the remote key presses should work always..the UPNP side of things all depends on if the TV supports it.

[kdschlosser]

but the end game is that we have a skipping command issue. I am going to go and poke about and see if I can locate where the problem is. I think I have a feeling I know where it is.

[kdschlosser]

OK I increased the wait time to 0.3 seconds between key presses. and I also added a wait a of a 1/2 a second at the end of the authentication, to let the TV do what it it needs to do.

lets see if that fixes the skipped commands issue. library has been updated.

[Mark-Sellwood]

My bad, samsungctl --config-file "/home/pi/Lounge.conf" KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN KEY_VOLDOWN turns the Volume down 2

[Mark-Sellwood]

Thanks, just updated and it works with the first KEY_ what ever.

What I have noticed is that it takes 20 seconds between pressing enter and the command being executed, is this normal?

[kdschlosser]

OK i wanted to make sure you were right.. give the librar a shot again and tell me if the keys are sending better,

unfortunately Samsung did not code in a response for getting a key code. so I have no way to know if the code was successfully received by the TV. and due to the large number of TV models and years one TV may be faster at processing the keys then another TV. I think the best way to handle this is maybe to add a Config item called key_wait_interval and this is something the user can adjust to get the best possible performance from their TV. if i hard code the wait i will have to set the wait to the slowest processing TV. Each and every rear that passes the processors in the TV's get faster.. I am sure you would not want to have to wait the interval between key presses that are needed on my 2012 model if you have a 2016 model that can process the key presses in half the time. I need to make this a user adjustable setting. so it can be dialed in to give the absolute best performance..

going to take me a half a day or so to do..

and yes that is normal. that is because of the UPNP end of things firing up. I will be fixing that as well.

this fork of the library is going to run much better when it only has to fire up a single time and stays running.. the latency using the command line if because the connection has to get established over and over again.

I will key up a very simple console script that will hold the connection open. and all you will have to eenter are things like.

KEY_POWER KEY_VOLUP volume 10 help exit

stuff like that.

if you want to be able to access samsungctl from another program that is going to be a whole other animal. and one of the reasons I am going to make a REST API wrapper for it.

[GeorgyErm]

I have spent all the weekend trying to get it work, but i can not. I have tried on UE40MU6100 and UE65MU6100. I have successfully installed the latest update of your library.

• When I am trying to connect via websocket: samsungctl --host 192.168.1.4 --port 8002 --method websocket --name myremote KEY_VOLDOWN terminal freezes for infinity (i tried all different ports)

• When I am trying to connect via standard settings: samsungctl --host 192.168.1.4 --name myremote KEY_VOLDOWN I get: "Unable to pair with TV.. Is the TV on ?!?" - And yes, it is on

• When I am trying to connect via encrypted settings: samsungctl --host 192.168.1.4 --method encrypted --name myremote KEY_VOLDOWN I get: "Unable to power on the TV, check network connectivity"

Please advise me on further steps, or MU series are not supported yet?

[kdschlosser]

the develop branch is going to contain the latest code. and will most likely not be in an operable state at the moment.

also. I would strongly recommend you read the documentation. specifically the section about command line use.

for starters 2016 TV's do not use an encrypted method they use a websocket method 2016 TV's do not use port 8002, they use port 8001.

I have to add the new detection system to the command line code. when i finish it up you will only have to supply a config file save/load path and the command. the library is going to handle everything else for you. you have to give me a day to finish it up.

[GeorgyErm]

So, is there any news on the update?