Awesome, thank you! I’ll try it this evening. That sounds correct - I think your explain action jives with how it functioned in the openHAB 1 binding.
This is my production environment so per the WAF I’m on the latest stable build.
This is probably a function of not being on the latest snapshot build, but most of the commands do not work (including volume, input, sleep timer). Power off works well.
2017-12-04 11:28:37.686 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command 2 on sharptv:sharptv:1601af5526a:sleep-timer channel
2017-12-04 11:28:37.688 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling sleep timer command 2
That’s odd. I would not have expected that power off would work and other commands would not work. Rather, I thought the binding might not start, or that it would throw errors. The fact that you can power it off suggests the binding is able to send commands to the TV. There’s really nothing different in how power commands are handled compared to volume, input, etc.
Unfortunately, I shutdown my dev box by mistake. Since I did it remotely, and because wake-on-lan doesn’t seem to work at the moment, I won’t be able to get into it until later this week to make changes.
Just curious why this binding isn’t documented on the openHAB site and available for installation via PaperUI?
Probably because I haven’t had the time to clean up the code, write the documentation, and submit a PR to have it included in the distro. 
@omatzyo Sorry, but I completely forgot about the issue you were having. We’re you able to get it sorted out?
No, I have not tried it again recently. Although I am now on the 2.3.0 snapshot build. I’ll give it a go when I have some time and let you know. Thanks for checking in!
I don’t seem to be having as much luck as you guys and am hoping someone can quickly see what I’m doing wrong here?
Power Off works when the TV is already on, but that’s it.
2018-01-08 18:01:06.761 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command ON on sharptv:sharptv:c83c1843:power channel
2018-01-08 18:01:06.768 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: ON
2018-01-08 18:01:06.772 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.0.97:10002 with timeout 1500
2018-01-08 18:01:06.781 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing command: 'POWR1 '
2018-01-08 18:01:06.786 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for command response
2018-01-08 18:01:06.793 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: ERR
2018-01-08 18:01:06.796 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing input stream
2018-01-08 18:01:06.802 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing output stream
2018-01-08 18:01:06.805 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing socket
2018-01-08 18:01:22.271 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command OFF on sharptv:sharptv:c83c1843:power channel
2018-01-08 18:01:22.297 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: OFF
2018-01-08 18:01:22.301 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.0.97:10002 with timeout 1500
2018-01-08 18:01:22.306 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing command: 'POWR0 '
2018-01-08 18:01:22.311 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for command response
2018-01-08 18:01:22.315 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: ERR
2018-01-08 18:01:22.318 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing input stream
2018-01-08 18:01:22.321 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing output stream
2018-01-08 18:01:22.324 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing socket
2018-01-08 18:03:12.015 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command ON on sharptv:sharptv:c83c1843:power channel
2018-01-08 18:03:12.019 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: ON
2018-01-08 18:03:12.022 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.0.97:10002 with timeout 1500
2018-01-08 18:03:13.528 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - IOException opening socket to TV: connect timed out
2018-01-08 18:03:32.215 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command ON on sharptv:sharptv:c83c1843:power channel
2018-01-08 18:03:32.221 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: ON
2018-01-08 18:03:32.239 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.0.97:10002 with timeout 1500
2018-01-08 18:03:33.745 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - IOException opening socket to TV: connect timed out
2018-01-08 18:04:00.310 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command OFF on sharptv:sharptv:c83c1843:power channel
2018-01-08 18:04:00.316 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: OFF
2018-01-08 18:04:00.321 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.0.97:10002 with timeout 1500
2018-01-08 18:04:01.828 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - IOException opening socket to TV: connect timed out
2018-01-08 18:04:07.393 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command ON on sharptv:sharptv:c83c1843:power channel
2018-01-08 18:04:07.397 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: ON
2018-01-08 18:04:07.403 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.0.97:10002 with timeout 1500
2018-01-08 18:04:07.411 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing command: 'POWR1 '
2018-01-08 18:04:07.415 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for command response
2018-01-08 18:04:07.418 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: OK
2018-01-08 18:04:07.420 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing input stream
2018-01-08 18:04:07.423 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing output stream
2018-01-08 18:04:07.426 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing socket
2018-01-08 18:04:13.229 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handle command OFF on sharptv:sharptv:c83c1843:power channel
2018-01-08 18:04:13.237 [DEBUG] [nding.sharptv.handler.SharpTVHandler] - Handling power command: OFF
2018-01-08 18:04:13.242 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Opening socket to 192.168.0.97:10002 with timeout 1500
2018-01-08 18:04:13.247 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Writing command: 'POWR0 '
2018-01-08 18:04:13.250 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Waiting for command response
2018-01-08 18:04:13.253 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Got: ERR
2018-01-08 18:04:13.255 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing input stream
2018-01-08 18:04:13.258 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing output stream
2018-01-08 18:04:13.261 [DEBUG] [arptv.internal.hardware.SharpTVProxy] - Closing socket
Eco mode at work. There’s a way to disable it.
Define a switch item like this
Switch SharpTV_DisableEco "Disable Eco Mode" { channel="sharptv:sharptv:c83c1843:disable-eco" }
Then send an ON command to it. The easy way is to do it from the Karaf console.
smarthome:send SharpTV_DisableEco ON
Hopefully that will do the trick. Let us know how it works out.
What is eco mode up to here? What does turning it on do? This might work for me too…
It’s a power saving mode, which renders the TV incapable of receiving commands when it’s off. Disabling it, should allow it to accept an ON command when it’s off.
Eco mode at work. There’s a way to disable it.
Define a switch item like this
Switch SharpTV_DisableEco “Disable Eco Mode” { channel=“sharptv:sharptv:c83c1843:disable-eco” }
Then send an ON command to it. The easy way is to do it from the Karaf console.
smarthome:send SharpTV_DisableEco ON
Bingo! That worked perfectly.
Hi Mark - Hope your well mate.
I have just updated to the latest openhabian and unfortunately this has broken the Sharp Add-on. Is there a potential workaround for the new version 2.3 I am missing?
Much appreciated.
-Lewis
Can you describe how it’s not working? Maybe post a debug log. If I find out why it’s not working, I’ll make a new build.
1 Like
@mhilbush, will this binding work with older Sharp Aquos TVs without UPnP? I have scripts for controlling the TV via IPControl, but a binding would be nice.
@5iver I’m not really sure. The SharpTV thing can be configured manually. And, if the TV supports the rather basic IPControl protocol, it might work.
The binding source is here, in case you want to see how it works.
And there’s some rather basic documentation here.
I just haven’t had time to package this up in a PR yet.
If you decide to give it a try, let me know if you run into any problems.
Hi Mark,
Much appreciated. I am testing it now.
I lost my original Openhab set up with a corrupted SD card so had to reinstall. The original Snapshot versions after updating to the new 2.3 were just not showing up at all in the bindings / things.
I will report back shortly.
Thank you
Hi Mark
This one is working - However it is doing the double discovery thing like when we were first testing - It shows two Sharp TV’s up for the same one.
The other thing is the Input Section is doubled up. So there is 2 different inputs but both do the same thing. They also only go in sequential numbers instead of HDMI 1, HDMI2 etc… I can’t remember if this is something I had to change or was in the original Binding.
Really appreciate your help mate - would be great if they put this as an official binding too.
Let me know if you need any logs etc.
Lewis
Yes, a debug log would be helpful. I forget what was causing this.
You mean there are two channels named Input? That’s a bug. One should be named AV Mode.
I think it always used numbers since that’s what the Sharp API expects.
Hi Mark,
I have forwarded a long log to you, let me know if you need anymore info etc.
Yes both channels are named Input - one would need to be named AV Mode.
From the original Binding somewhere I thought it pulled the name of what input it was on and displayed there, however, being such a long time since I configured it I am not sure if this is something I did myself or not?
Thanks mate - talk soon.
Lewis