![]() There are other programs on github that do this too, but mine was first. CHROMECAST WITH GOOGLE TV REMOTE BUTTONS HOW TOThus, to add a new capability to it just requires figuring out that new capability and all the rest (loading the configuration file, figuring out how to send and receive messages, running as a service, handling signals from the OS, thread management, etc.) is already done for you. Communicators are independent so with the one exception it doesn’t matter what sensor_reporter uses to send and receive messages. So it has a core that is reused by everything. I wrote sensor_reporter to be modular so I only have to figure out how to do things once. However, because of the dynamic nature of the Govee add-on, I don’t have a good way to use that communicator with it so for now MQTT is the only choice for that specific sensor. CHROMECAST WITH GOOGLE TV REMOTE BUTTONS TVBut sensor_reporter has another openHAB communicator that uses the openHAB REST API and SSE feed to send/receive Item states. I show you how to pair (sync, connect) the remote control on the Chromecast with Google TV directly from the button on the Chromecast device itself. There’s the D-Pad at the top, with a back button, home button, Google Assistant button and mute button. In particular the LWT and careful use of retained messages and the fact that it’s a standard not tied to any specific home automation system makes it very powerful. Google is still keeping the remote pretty simple with the Chromecast with Google TV (HD). MQTT has some advantages that make me choose it over other options most of the time. ![]() Would MQTT be necessary, and simpler than, say, triggering something over the REST API? (At least as a first step.) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |