# Chromecast announcement

**URL:** <https://community.openhab.org/t/chromecast-announcement/33942>\
**Category:** Bindings\
**Tags:** chromecast, tts, audio\
**Created:** [September 5, 2017, 12:49pm UTC](https://community.openhab.org/t/chromecast-announcement/33942 "2017-09-05T12:49:31Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![MDAR](https://community.openhab.org/user_avatar/community.openhab.org/mdar/32/57900_2.png) [@MDAR](https://community.openhab.org/u/MDAR)\
**Post date:** [November 27, 2019, 11:48am UTC](https://community.openhab.org/t/chromecast-announcement/33942/9 "2019-11-27T11:48:48Z")

</div>

In case anyone comes looking for an option, I have just created a NodeRed flow that works for me.

> [@Chromecast: Get current URL](https://community.openhab.org/t/chromecast-get-current-url/37476/3):
>
> Hi I had forgotten that I’d programmed a doorbell sound to trigger on one of my Chomecast units. This has worked well, until I was listening to the radio recently, when the doorbell was pressed (have these people no respect???) So it got me wondering how I could get the Chromecast to resume. With NodeRed it turned out to be quite easy. I assume I could translate this to DSL if I needed to. For anyone that is interested, here is the flow I used. [ { "id": "6e725766.ab…

---

_[View the full topic](https://community.openhab.org/t/chromecast-announcement/33942)._
