TTS not working after upgrade to 1.1.4.119

I just created a new TTS trigger that is super basic. If a door opens, speak Door Opened. didn't work.

I chose the Kegorator door because its right next to my desk, makes for easy testing!

1 Like

I don't either..., will have a look.

Selecting a speech device works, music device doesn't....
I'll file a bug report...

In the mean time just flip over to speech device, unless you need the volume setting.

4 Likes

Yep...same here. Moving to speech device as prescribed worked fine.

I wonder if it has anything to do with my double announcements issue. Maybe some clues. Let me know what I can do or provide in order to figure it out.

@mike.maxwell - The issue seems to be related to private boolean not work, as music play seems to be working fine when triggered by a button instead of private boolean truth.

I created a new Rule 2.5 trigger with the action on speech device, worked fine, action on music player no go.

Odd. I can trigger via virtual button, just not via private boolean

do other private bools work?

Haven’t had the time to test this morning. Will do when I can

1 Like

Made two test triggers. Didn't trigger the action, but odd because the log shows it was set to true.

26%20PM02%20PM

Trigger log

app:15342018-09-18 12:55:58.482:infotest private bool Triggered

app:15342018-09-18 12:55:58.429:infotest private bool: Test button pushed 1

app:15342018-09-18 12:55:49.960:infotest private bool Triggered

app:15342018-09-18 12:55:49.847:infotest private bool: Test button pushed 1

app:15342018-09-18 12:51:38.364:infotest private bool: Resumed

Action log

app:15352018-09-18 12:55:58.472:infotest private bool part 2: Set Boolean true from test private bool

app:15352018-09-18 12:55:49.919:infotest private bool part 2: Set Boolean true from test private bool

I could be wrong here, but aren't the Boolean's true by default? Maybe you need to set the Boolean to false first so that the boolean changes to true.

My understanding is they are neither until something tells them to be one or the other, which is what the first rule does. This is how I did it before the update and it worked.

However, not a bad suggestion. I just tried it with private boolean becomes false, and it still fails to trigger.

The bug with Private Boolean in a trigger has been found and fixed. Will be released soon.

2 Likes

The RM bug with TTS on a music device has been found and fixed.

1 Like

6 posts were split to a new topic: Dashboard issues with 1.1.4.119

The fix for this issue has been released:

I can verify that it now works again. Thank you!

1 Like