It should work now.
thanks, what is Karaf console and how to access it?
Hi @mhilbush! I just gave this a try again. Its been a while 
This is one of the last bindings I still have running in OH1.
I have the same issue I had last year where the power off works, but any other command does not. For example here is the DEBUG log when I press Mute.
2020-09-27 14:02:03.340 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for login success
2020-09-27 14:02:03.349 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got:
2020-09-27 14:02:03.349 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing command: 'MUTE2 '
2020-09-27 14:02:03.349 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for command response
2020-09-27 14:02:03.396 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: ERR
2020-09-27 14:02:03.396 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing input stream
2020-09-27 14:02:03.396 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing output stream
2020-09-27 14:02:03.397 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing socket
Just like before (oddly) the power off command works. Power ON was pressed when the TV was already on. Otherwise it is totally offline and won’t even respond to WOL.
2020-09-27 14:09:12.957 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command ON on sharptv:sharptv:mbrtv:power channel
2020-09-27 14:09:12.957 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: ON
2020-09-27 14:09:12.957 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Normalized command of length 8 is: 'POWR1 '
2020-09-27 14:09:12.957 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.1.60:10002 with timeout 1500
2020-09-27 14:09:12.963 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for Username prompt
2020-09-27 14:09:12.969 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: Login:
2020-09-27 14:09:12.969 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing user: myusername
2020-09-27 14:09:12.969 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for Password prompt
2020-09-27 14:09:12.976 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: Password:
2020-09-27 14:09:12.977 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing password: XXXXX
2020-09-27 14:09:12.977 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for login success
2020-09-27 14:09:12.984 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got:
2020-09-27 14:09:12.984 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing command: 'POWR1 '
2020-09-27 14:09:12.984 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for command response
2020-09-27 14:09:13.035 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: OK
2020-09-27 14:09:13.035 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing input stream
2020-09-27 14:09:13.036 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing output stream
2020-09-27 14:09:13.036 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing socket
2020-09-27 14:09:56.173 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command OFF on sharptv:sharptv:mbrtv:power channel
2020-09-27 14:09:56.173 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: OFF
2020-09-27 14:09:56.173 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Normalized command of length 8 is: 'POWR0 '
2020-09-27 14:09:56.174 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.1.60:10002 with timeout 1500
2020-09-27 14:09:56.177 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for Username prompt
2020-09-27 14:09:56.182 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: Login:
2020-09-27 14:09:56.183 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing user: myusername
2020-09-27 14:09:56.183 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for Password prompt
2020-09-27 14:09:56.189 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: Password:
2020-09-27 14:09:56.189 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing password: XXXXX
2020-09-27 14:09:56.189 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for login success
2020-09-27 14:09:56.194 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got:
2020-09-27 14:09:56.194 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing command: 'POWR0 '
2020-09-27 14:09:56.195 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for command response
2020-09-27 14:09:56.245 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: ERR
2020-09-27 14:09:56.245 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing input stream
2020-09-27 14:09:56.246 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing output stream
2020-09-27 14:09:56.246 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing socket
Here’s my binding:
271 │ Active │ 80 │ 2.5.5.202005041958 │ openHAB Add-ons :: Bundles :: Sharp TV Binding
I’m running OH 2.5.8 release build.
I forget what we did to try to debug this. Do you recall if we tried having you run the commands using telnet directly to the TV IP address and port?
No we never got that far. I think the initial thought was perhaps the issue was an interaction between the binding and the snapshot builds at the time. But newer OH versions didn’t change anything for me.
@5iver Did the binding work for you with an older Sharp Aquos TV? Mark says the Thing can be configured manually, which is great, but I’m looking for a template for the Thing. I installed the binding and it has found some UPNP devices on my network, but not the Sharp TV. It may not be UPNP, so I want to try the manual approach.
Thanks,
Mine is a slightly older Sharp 2011. Currently I can only turn it off.
Here is the manual Thing:
Thing sharptv:sharptv:mytv [ ipAddress=“192.168.1.200”, port=10002, user=“username”, password=“password” ]
Hi Mark,
First off I have to say, great work on this binding. Is it going to be added to the main repo in the future?
So I have a question about the auto-discovery. I downloaded and installed the 2.5.5-SNAPSHOT jar from your repo and it installed no problem. The only thing is it only discovers 1 of my 2 Sharp TV’s. The older one a LC-52LE640U it never discovers. I have setup the IP control access as per the manual with username admin and password openhab port is default 10002. I can PUTTY into it and issue commands. I even tried it with the username and password blanked out, could still issue commands via PUTTY, no auto-discover.
I have tried setting logging to DEBUG for your addon, the UPNP binding and the jUPnp library in the console, but I honestly can see nothing that looks like an attempt to discover this TV in the logs. I have tried with restarting each of the above bundles in the console and also a complete restart of the Openhab2 service from the Linux command line. Although I bet that resets the logging levels. I am running openHAB 2.5.9-1 (Release Build) on Linux Mint 19.3 Tricia. System is fully up to date via the Openhabian-config tool for both system and openhab updates.
How do I go about debuging this? Any Ideas on where I should start? As a work-around is there a way to manually define the Thing for the TV? I use the PaperUI for all my Things and I use VS Code to do all my items, rules, sitemaps, etc.
Sorry, I have no idea. Are you sure the older TV supports uPnP?
You should be able to add the TV manually using Paper UI, or with a .things file.
Hi, what’s the status of the binding? Has in been added to the distro in between? Does it run on OH 3.3?
Umm… I haven’t built it in a while, and I no longer have a Sharp TV.
Definitely not. But I should consider adding it to the marketplace.
Doubtful. But if you want to try it, I can try building a version for 3.3. I don’t think the binding did anything that would break in 3.3. And I recall building a version for an earlier version of 3.x, but I can’t seem to locate it right now.
Hmm. Look at that. I must’ve built a 3.3 version at some point. So I should just be able to rebuild a 3.3 version.
1 Like
Here’s the jar file. Note that it’s built for 3.4.0 because that’s what my dev environment is set up for. There should be no issue with it running on 3.3.0. 
works, great. 1 Try = 1 Success 