When I touch my Tastsensor near my bed with the “Wake up” scene, the light swiches on, the bathroom lights switches on and in the Kitchen the Light and the TV should switch on.
Problem with Samsung TVs (and a lot of other brands) is that they don’t do Wake-on-Lan (WOL). Since I don’t want to use a Raspberry Pi here (which I have to maintain with latest software, a command-line interface, etc), I chose a Chromecase Dongle.

1) Put the Chromecast Dongle on permanent power

2) Enable HDMI-CEC (Samsung calls it “Anycast”) in the settings menu of the TV.

3) Create an IP Webanfrage in the Gira Homeservers and use the IP address of the Chromecast. (It would be best to give the Chromecast a Static Lease in the DHCP Server)

4) Add the following Send Data Blocks

POST /apps/00000000-0000-0000-0000-000000000000 HTTP/1.1
Content-Type: application/json
Host: 192.168.4.23:8008      (change to your chromecast IP!)
Content-Length: 297
                             (this is an empty line!)
{
      "use_channel":true,    (these lines are prefixed by six spaces!!)
      "allow_restart":true,
      "allow_empty_post_data":true,
       "app_id":"00000000-0000-0000-0000-000000000000",
       "url":"chrome://home?remote_url=https%3A%2F%2Fclients3.google.com%2Fcast%2Fchromecast%2Fhome%3Fchs%3D1",
       "dial_enabled":true
 }

5) Now create some logic, i.e. When someone touches a button, the Webanfrage is executed and so the TV is switched on.

Notes:

  • The Chromecast starts in the above example on the Default Chromecast Page (App ID: 0000…0001).  You can call a different APP ID to start Netflix, HBO or another app.
  • If you just want to swith on the TV to ‘HDMI 4’ or ‘Channel 1’. You can use the above logic in combination with Baustein 11881
  • Please be carefull with the Content-Length, that is very sensitive, If you change something, this will probably also change.  To debug you can use Wireshark (to see what happens if it isn’t executed) and Fiddler (to experiment and compose the requests).