#GOOGLE CHROMECAST REMOTE BUTTONS HOW TO#

14:50:19.041 - Item 'CrashTV_MediaType' changed from NULL to GENERIC 14:50:19.033 - Item 'CrashTV_Duration' changed from NULL to UNDEF 14:50:19.027 - Item 'CrashTV_CurrentTime' changed from NULL to UNDEF 14:50:19.023 - Item 'CrashTV_MediaControl' changed from NULL to PAUSE 14:37:12.398 - Item 'CrashTV_Stop' changed from NULL to ON 14:37:12.203 - Item 'CrashTV_Volume' changed from NULL to 100 14:37:11.783 - Item 'CrashTV_Idling' changed from NULL to ON 14:37:11.595 - Item 'CrashTV_Mute' changed from NULL to OFF 14:12:10.555 - Item 'CrashTV_Stop' changed from NULL to ON 14:12:10.426 - Item 'CrashTV_Volume' changed from NULL to 100 14:12:10.130 - Item 'CrashTV_Idling' changed from NULL to ON 14:12:09.963 - Item 'CrashTV_Mute' changed from NULL to OFF 14:05:43.251 - Item 'CrashTV_Stop' changed from NULL to ON 14:05:43.011 - Item 'CrashTV_Volume' changed from NULL to 100 14:05:42.675 - Item 'CrashTV_Idling' changed from NULL to ON Looks like I was wrong about not seeing events when playing some the apps: 14:05:42.536 - Item 'CrashTV_Mute' changed from NULL to OFF There are other programs on github that do this too, but mine was first.

#GOOGLE CHROMECAST REMOTE BUTTONS HOW TO#

Thus, 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. But sensor_reporter has another openHAB communicator that uses the openHAB REST API and SSE feed to send/receive Item states. 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. 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.)

Google chromecast remote buttons