# Smart Home Monitor all of a sudden doesn't recognize VLC Thing as an audio player

**URL:** <https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465>\
**Category:** Devices & Integrations\
**Created:** [December 16, 2016, 7:51am UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465 "2016-12-16T07:51:56Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![luder888](https://avatars.discourse-cdn.com/v4/letter/l/8c91f0/32.png) [@luder888](https://community.smartthings.com/u/luder888)\
**Post date:** [December 16, 2016, 7:51am UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/1 "2016-12-16T07:51:56Z")

</div>

So for months Smart Home Monitor audio notification was able to work with VLC Thing. Today I tested one of my water sensor and I did not get a voice notification. I went into SHM Leak setup, selected Audio Notifications, deselected my existing VLC Thing, then tried to select it again but got the error “None of the selected audio devices support text to speech notifications.” I’m using version 1.2.2 of VLC Thing. Speaker Notify with Sound continues to work, so it’s probably not my VLC Setup.

 ![](https://global.discourse-cdn.com/smartthings/original/3X/8/e/8e7febc70f864e9c25a79d13b2477a657b0916a7.png)

---

<div class="post-metadata">

**Author:** ![geko](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/geko/32/34862_2.png) [@geko](https://community.smartthings.com/u/geko)\
**Post date:** [December 23, 2016, 1:16am UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/2 "2016-12-23T01:16:26Z")

</div>

I’ve noticed that too. VLC can be selected as an audio device in “Security” section, but not in “Leaks” or “Smoke”. @slagle, any idea why?

Possibly related to this?

> [@SHM not allowing Audio Notifications for Smoke and Leaks](https://community.smartthings.com/t/shm-not-allowing-audio-notifications-for-smoke-and-leaks/62010):
>
> In Smart Home Monitor I can use my Aeon Doorbell as a Audio Notification player to play custom track for Security and Custom, but for some reason when I go to select Audio Notifications for Smoke or Leaks, it says None of the selected audio devices support text to speech notifications. It does not give me a chance to select a device.

---

<div class="post-metadata">

**Author:** ![gusmorgan](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gusmorgan](https://community.smartthings.com/u/gusmorgan)\
**Post date:** [January 3, 2017, 7:17pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/3 "2017-01-03T19:17:13Z")

</div>

yes, I came here too for the same reason. the audio notification stopped working for my leak sensors, so I removed them and now I can’t add them back. i thought it was because I was using Sonos speakers but they are working as audio notifications for Security, just not Smoke, Leaks, or Custom.

---

<div class="post-metadata">

**Author:** ![geko](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/geko/32/34862_2.png) [@geko](https://community.smartthings.com/u/geko)\
**Post date:** [January 3, 2017, 8:11pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/4 "2017-01-03T20:11:05Z")

</div>

Have you opened an issue with [support@smartthings.com](mailto:support@smartthings.com)?

---

<div class="post-metadata">

**Author:** ![gusmorgan](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gusmorgan](https://community.smartthings.com/u/gusmorgan)\
**Post date:** [January 4, 2017, 6:20pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/5 "2017-01-04T18:20:22Z")

</div>

Of course I did but its the same thing every time. Runaround silly steps that waste more time and take even more time to put everything back, then they are stumped and run out of ideas so they promise to escalate, then nothing, no communication, so I check back and find out that the engineers at ST have more important things to worry about, and a year later, nothing but crickets.  
I have worked in tech support on various levels for over 20 years and I am amazed at the lack of comprehension of the trouble before providing steps to resolve, lack of accountability of resolution, no or bad communication, no follow thru, and lack of accountability. So this time, I reported it, wasted more time doing the same things i have already tried and gotten the same apology and offer to escalate, so I won’t hold my breath this time either. So today, I have to spend about an hour adding all the things back that I removed yesterday. I give up.

---

<div class="post-metadata">

**Author:** ![geko](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/geko/32/34862_2.png) [@geko](https://community.smartthings.com/u/geko)\
**Post date:** [January 4, 2017, 6:32pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/6 "2017-01-04T18:32:31Z")

</div>

Tagging @slagle. Multiple users report SHM audio notifications stopped working and support is clueless. Any ideas? Thanks.

---

<div class="post-metadata">

**Author:** ![slagle](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/slagle/32/16950_2.png) [@slagle](https://community.smartthings.com/u/slagle)\
**Post date:** [January 5, 2017, 8:30pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/8 "2017-01-05T20:30:49Z")

</div>

Specifically in SHM or everywhere?

---

<div class="post-metadata">

**Author:** ![luder888](https://avatars.discourse-cdn.com/v4/letter/l/8c91f0/32.png) [@luder888](https://community.smartthings.com/u/luder888)\
**Post date:** [January 5, 2017, 8:43pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/10 "2017-01-05T20:43:23Z")

</div>

SHM for me. Speaker Notify with Sound still works fine.

---

<div class="post-metadata">

**Author:** ![slagle](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/slagle/32/16950_2.png) [@slagle](https://community.smartthings.com/u/slagle)\
**Post date:** [January 5, 2017, 8:51pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/11 "2017-01-05T20:51:30Z")

</div>

Ok, nothing has changes with SHM in nice November so my idea of there being a simple solution is shot.

Gonna have to dig into platform code.

---

<div class="post-metadata">

**Author:** ![gusmorgan](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gusmorgan](https://community.smartthings.com/u/gusmorgan)\
**Post date:** [January 5, 2017, 8:52pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/12 "2017-01-05T20:52:59Z")

</div>

Sonos speaker work elsewhere in the ST app but they ONLY appear as Audio Players in Security for SHM. When trying to configure them for Smoke and Leaks, I get “None of the selected audio devices support text to speech notifications”

---

<div class="post-metadata">

**Author:** ![luder888](https://avatars.discourse-cdn.com/v4/letter/l/8c91f0/32.png) [@luder888](https://community.smartthings.com/u/luder888)\
**Post date:** [January 5, 2017, 9:15pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/13 "2017-01-05T21:15:12Z")

</div>

Even though this post was created on Dec 16th, it could have stopped working since November. It’s one of those things that could go unnoticed for weeks because you only notice when there’s a leak/smoke/intrusion.

---

<div class="post-metadata">

**Author:** ![slagle](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/slagle/32/16950_2.png) [@slagle](https://community.smartthings.com/u/slagle)\
**Post date:** [January 5, 2017, 9:19pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/14 "2017-01-05T21:19:10Z")

</div>

Ok, some more digging is required. Nothing on the surface.

Funny thing is the audio notifications is a child app and all three (Security, Leaks, Smoke) all use the same child app… So this is some weird thing lol…

---

<div class="post-metadata">

**Author:** ![luder888](https://avatars.discourse-cdn.com/v4/letter/l/8c91f0/32.png) [@luder888](https://community.smartthings.com/u/luder888)\
**Post date:** [January 5, 2017, 9:26pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/15 "2017-01-05T21:26:06Z")

</div>

For me:

SHM Security:  
I can select VLC Thing as an Audio Player, but it doesn’t matter because it always shows the error “None of the selected audio devices support text to speech notifications.”

SHM Smoke/Leaks:  
I cannot select an Audio Player, it just shows the error “None of the selected audio devices support text to speech notifications.”

SHM Custom:  
No issues

Speaker Notify with Sound:  
No issues

---

<div class="post-metadata">

**Author:** ![slagle](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/slagle/32/16950_2.png) [@slagle](https://community.smartthings.com/u/slagle)\
**Post date:** [January 5, 2017, 9:54pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/16 "2017-01-05T21:54:20Z")

</div>

Ok, so we found two bugs in our traipsing of the code.

This one

> [@luder888](#):
>
> SHM Security:I can select VLC Thing as an Audio Player, but it doesn’t matter because it always shows the error “None of the selected audio devices support text to speech notifications.”

and this one

> [@luder888](#):
>
> SHM Smoke/Leaks:I cannot select an Audio Player, it just shows the error “None of the selected audio devices support text to speech notifications.”

We have fixes in the works and depending on QA load we will get it out asap. Expect Tuesday for a fix but if it goes out sooner I will let you know.

---

<div class="post-metadata">

**Author:** ![luder888](https://avatars.discourse-cdn.com/v4/letter/l/8c91f0/32.png) [@luder888](https://community.smartthings.com/u/luder888)\
**Post date:** [January 5, 2017, 10:54pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/17 "2017-01-05T22:54:51Z")

</div>

Thank you for looking into this and for the quick response.

---

<div class="post-metadata">

**Author:** ![geko](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/geko/32/34862_2.png) [@geko](https://community.smartthings.com/u/geko)\
**Post date:** [January 5, 2017, 11:57pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/18 "2017-01-05T23:57:59Z")

</div>

> [@slagle](#):
>
> Ok, so we found two bugs in our traipsing of the code.

Thank you for the quick response!

---

<div class="post-metadata">

**Author:** ![gusmorgan](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gusmorgan](https://community.smartthings.com/u/gusmorgan)\
**Post date:** [January 6, 2017, 6:02pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/20 "2017-01-06T18:02:51Z")

</div>

> [@luder888](#):
>
> SHM Security:I can select VLC Thing as an Audio Player, but it doesn’t matter because it always shows the error “None of the selected audio devices support text to speech notifications.”
> 
> SHM Smoke/Leaks:I cannot select an Audio Player, it just shows the error “None of the selected audio devices support text to speech notifications.”
> 
> SHM Custom:No issues
> 
> Speaker Notify with Sound:No issues

Same for me. Except I have tried with two diff Sonos speakers and VLC Thing. it was working for me until recently. I noticed it when I changed batteries in a leak sensor and tested it. I got a push notification but no sound notification.

---

<div class="post-metadata">

**Author:** ![geko](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/geko/32/34862_2.png) [@geko](https://community.smartthings.com/u/geko)\
**Post date:** [January 6, 2017, 7:47pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/21 "2017-01-06T19:47:23Z")

</div>

Yeah, it’s unfortunate that SmartThings still does not implement comprehensive regression testing and bugs like that can go unnoticed for months. Oh well… ☹

---

<div class="post-metadata">

**Author:** ![luder888](https://avatars.discourse-cdn.com/v4/letter/l/8c91f0/32.png) [@luder888](https://community.smartthings.com/u/luder888)\
**Post date:** [January 14, 2017, 6:52pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/22 "2017-01-14T18:52:54Z")

</div>

Any updates? Will this fix be released soon?

---

<div class="post-metadata">

**Author:** ![luder888](https://avatars.discourse-cdn.com/v4/letter/l/8c91f0/32.png) [@luder888](https://community.smartthings.com/u/luder888)\
**Post date:** [January 29, 2017, 9:41pm UTC](https://community.smartthings.com/t/smart-home-monitor-all-of-a-sudden-doesnt-recognize-vlc-thing-as-an-audio-player/68465/23 "2017-01-29T21:41:41Z")

</div>

I updated ST to the latest version today, and I was able to add VLC Thing back as an Audio Player in Audio Notification. I added it to Security, Smoke, and Leaks. However, when I tested Smoke and Leak, nothing got announced. There seems to be still an issue…
