New Plugin: SamsungTV_2016

---

@amit-patel
still not works:
log after restart pimatic:

15:03:39.342 2017-11-13 Monday
15:04:06.989 [pimatic] info: Starting pimatic version 0.9.42
15:04:09.056 [pimatic] debug: settings.debug is true, showing debug output for pimatic core.
15:04:14.802 [pimatic, ppm] info: 2.15.12
15:04:14.927 [pimatic] info: Loading plugin: “pimatic-mobile-frontend” (0.9.12)
15:04:17.172 [pimatic] info: Loading plugin: “pimatic-z-way” (1.4.3)
15:04:17.337 [pimatic] info: Loading plugin: “pimatic-sysinfo” (0.9.4)
15:04:17.827 [pimatic] info: Loading plugin: “pimatic-cron” (0.8.8)
15:04:19.066 [pimatic] info: Loading plugin: “pimatic-shell-execute” (0.9.11)
15:04:19.195 [pimatic] info: Loading plugin: “pimatic-wakeonlan” (0.9.4)
15:04:19.356 [pimatic] info: Loading plugin: “pimatic-pushbullet” (0.9.0)
15:04:21.198 [pimatic] info: Loading plugin: “pimatic-amazing-dash-button” (0.9.13)
15:04:21.368 [pimatic] info: Loading plugin: “pimatic-samsung-tv-2016” (0.2.0)
15:04:25.466 [pimatic] error: SamsungTV_2016_Switch.property is not a function
15:04:25.486 [pimatic] debug: TypeError: SamsungTV_2016_Switch.property is not a function
15:04:25.486 [pimatic] debug:> at /home/pi/pimatic-app/node_modules/pimatic-samsung-tv-2016/samsung-tv-2016.coffee:45:6
15:04:25.486 [pimatic] debug:> at module.exports (/home/pi/pimatic-app/node_modules/pimatic-samsung-tv-2016/samsung-tv-2016.coffee:223:5)
15:04:25.486 [pimatic] debug:> at PluginManager.loadPlugin (/home/pi/pimatic-app/node_modules/pimatic/lib/plugins.coffee:83:16)
15:04:25.486 [pimatic] debug:> at /home/pi/pimatic-app/node_modules/pimatic/lib/plugins.coffee:485:25
15:04:25.486 [pimatic] debug:> at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
15:04:25.486 [pimatic] debug:> at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31)
15:04:25.486 [pimatic] debug:> at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
15:04:25.486 [pimatic] debug:> at Promise._settlePromiseCtx (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:606:10)
15:04:25.486 [pimatic] debug:> at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:138:12)
15:04:25.486 [pimatic] debug:> at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
15:04:25.486 [pimatic] debug:> at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
15:04:25.486 [pimatic] debug:> at processImmediate [as _immediateCallback] (timers.js:383:17)
15:04:25.507 [pimatic] info: Loading plugin: “pimatic-charts” (0.0.2)
}}

Hi,
I have the same issue like @dk00000. And I would like to try it with my J series TV, @amit-patel. I have at least a working API endpoint at http://TV:8001/api/v2/channels/ which is promising…

@mmore @dk00000
can you please try it now?

@amit-patel at least the error message is gone. But it did not work with my SAMSUNG UE 48 JU 6450 UXZG. It only detects whether device is switched on or off.

BTW: I needed to install it via specifying github repo. Seems that you missed to publish this version.

Please publish a new plugin version

Thank you so much for this plugin - v0.2.1 from the repo works fine with my KS7090 while 0.2.0 from npmjs.com does not.

How can I send additional commands to the TV? I dream of Alexa dimming the lights (already implemented), turning on my TV, switching to HDMI3 and turning on my PS4. I enabled echo-support for the samsung-tv-2016-device and Alexa finds it, but unfortunately it does not work (server not responding / function not supported).

Anyone who would like to assist me?

Thanks, Arthur

@arthurdent https://forum.pimatic.org/topic/3074/python-how-to-integrate-cheap-broadlink-rm3-mini-ir-blaster-with-pimatic

Whenever i turn my ps4 on, my lights dim(via pimatic ping) and switch to hdmi2 through the broadlink infrared blaster.

Nice, I will look into that mini-ir-blaster-thing!

I just re-published the package as a new version, and I see it picked up by npm, so this should resolve issues.

@gleno0h said in New Plugin: SamsungTV_2016:

@arthurdent https://forum.pimatic.org/topic/3074/python-how-to-integrate-cheap-broadlink-rm3-mini-ir-blaster-with-pimatic

Whenever i turn my ps4 on, my lights dim(via pimatic ping) and switch to hdmi2 through the broadlink infrared blaster.

i thought i had written (an unpublished) plugin adapter for the Broadlink IR blasters based on the broadlinkjs lib. As it turns out I started it, but never finished it. Maybe one day.

@arthurdent said in New Plugin: SamsungTV_2016:

Thank you so much for this plugin - v0.2.1 from the repo works fine with my KS7090 while 0.2.0 from npmjs.com does not.

How can I send additional commands to the TV? I dream of Alexa dimming the lights (already implemented), turning on my TV, switching to HDMI3 and turning on my PS4. I enabled echo-support for the samsung-tv-2016-device and Alexa finds it, but unfortunately it does not work (server not responding / function not supported).

You’re welcome. When you just turn on your PS4, doesn’t your TV automatically turn on and then move to the appropriate HDMI input via hdmi-cec? Because it should. And so, the question you should really be asking is, how can I get Alexa to turn on the PS4? Just to make it simpler, not that I have thought about how to do it.
(btw, huge fan of the your handle. I used to own first editions of all five in the trilogy. sadly though, I gave them away as a present)

@amit-patel Thanks for the update, v0.4.0. works out-of-the-box. The idea of having the PS4 turning on the TV is fine and I really do not need any assistance via Alexa for it, as I will always have a controller in my hands BTW, I think ps4-waker is the plugin which - theoretically - should be able to turn on the PS4, but I think I read of some unmet dependencies (if I remember correctly ps4-waker needs Node >6).

I disabled HDMI-CEC on my PS4 some time ago (because the TV always turned on my PS4, even when my wife only wanted to watch Netflix), but maybe I should give it a try and enable it again. Maybe I am able to finetune the CEC behaviour. Thanks for your input!

@arthurdent i took a quick look at the lib, and i might be able to get it to work on node 4

@amit-patel There is pimatic plugin for ps4-waker, as I saw on this thread; I can try to get it to work, before you waste your precious time to port ps4-waker to node4. But I really appreciate your kindness and support!!

@arthurdent said in New Plugin: SamsungTV_2016:

try

It might work…

Long story short: The plugin pimatic-ps4waker works. The used version of ps4-waker is rather old (0.9.1) and throws some errors, while the original github repo already reached 1.4.3, but it works. But let us focus on samsung-tv-2016 in this thread, I begin to feel bad for abusing this thread… Thank you so much.

@arthurdent see https://forum.pimatic.org/post/31768

Thanks! I will give it a try when I am back home and report!