[RELEASE] Follow Me - Speaker control with priority messaging, volume controls, voices and sound files!

greg · May 1, 2019, 12:06pm

Deleted and reinstalled, same error

app:4592019-05-01 08:05:25.112 am debugIn motionSensorHandler - sZone: true - Status: inactive

app:4592019-05-01 08:05:25.100 am debugIn motionSensorHandler...

app:4592019-05-01 08:05:24.732 am debugIn motionSensorHandler - sZone: true - Status: inactive

app:4592019-05-01 08:05:24.728 am debugIn motionSensorHandler...

app:4592019-05-01 08:04:54.758 am debugIn motionSensorHandler - setting sZone to true

app:4592019-05-01 08:04:54.757 am debugIn motionSensorHandler - sZone: true - Status: active

app:4592019-05-01 08:04:54.730 am debugIn motionSensorHandler...

app:4592019-05-01 08:04:53.046 am debugIn motionSensorHandler - sZone: true - Status: inactive

app:4592019-05-01 08:04:53.032 am debugIn motionSensorHandler...

app:4592019-05-01 08:04:48.580 am errorjava.text.ParseException: Unparseable date: "7:30" on line 453 (lastSpokenHandler)

app:4592019-05-01 08:04:48.576 am debugIn checkTime - 7:30 - 2019-05-01T20:30:00.000-0400

app:4592019-05-01 08:04:48.570 am debugIn letsTalk...

app:4592019-05-01 08:04:48.569 am debugIn lastSpoken - Priority: fam - lastSpoken: family room window 3 is now closed

app:4592019-05-01 08:04:48.564 am debugIn lastSpoken...

app:4592019-05-01 08:04:44.911 am errorjava.text.ParseException: Unparseable date: "7:30" on line 453 (lastSpokenHandler)

app:4592019-05-01 08:04:44.900 am debugIn checkTime - 7:30 - 2019-05-01T20:30:00.000-0400

app:4592019-05-01 08:04:44.899 am debugIn letsTalk...

app:4592019-05-01 08:04:44.898 am debugIn lastSpoken - Priority: fam - lastSpoken: family room window 3 is now open

app:4592019-05-01 08:04:44.893 am debugIn lastSpoken...

app:4592019-05-01 08:04:29.508 am debugIn motionSensorHandler - setting sZone to true

app:4592019-05-01 08:04:29.507 am debugIn motionSensorHandler - sZone: true - Status: active

app:4592019-05-01 08:04:29.503 am debugIn motionSensorHandler...

app:4592019-05-01 08:04:23.081 am debugIn motionSensorHandler - setting sZone to true

app:4592019-05-01 08:04:23.079 am debugIn motionSensorHandler - sZone: false - Status: active

app:4592019-05-01 08:04:23.063 am debugIn motionSensorHandler...

app:4592019-05-01 08:03:45.882 am debugIn setDefaults...

app:4592019-05-01 08:03:45.880 am debugInstalled with settings: [pauseApp:false, messageDest:Speakers, logEnable:true, gvDevice:What Did I Say Tile, volRestore:55, messagePriority:false, speechMode:Music Player, triggerMode:Motion_Sensor, volSpeech:65, sZoneWaiting:5, myMotion:[Kitchen Motion 2, Kitchen Motion, Dining Room Motion, Family Room Motion, Dining Room Motion 2, Living Room Motion], speaker:Kitchen Sonos, fromTime:7:30, echoSpeaks:false, toTime:2019-05-01T20:30:00.000-0400]

bptworld · May 1, 2019, 12:29pm

It definitely something going on with your From Time... it's saving as 'fromTime:7:30' when it should be something like 'fromTime:2019-05-01T06:00:00.000-0400'

I can't seem to reproduce it, so for now just delete the child app and recreate it without the times to get you going. I can't work on it today, going to the Red Sox game (day game), so won't be home until later tonight.

Thanks

This is a test child app I just created and it's saving just fine... I'm at a total lose right now...
app:56772019-05-01 08:34:39.307 am debugInstalled with settings: [pauseApp:false, messageDest:Speakers, logEnable:true, gvDevice:What Did I Say, volRestore:50, messagePriority:false, speechMode:Speech Synth, triggerMode:Always_On, volSpeech:50, gSpeaker:false, speaker:Work Room Speaker, fromTime:2019-05-01T07:00:00.000-0400, toTime:2019-05-01T22:00:00.000-0400]

greg · May 1, 2019, 12:37pm

Yeah. removing the time restriction makes everything work fine. Adding it back in breaks it.

What is really weird is that I have another zone with a time restriction and there is no error.

Thanks for your help, I'll just leave the restriction off for this zone

bptworld · May 1, 2019, 12:38pm

Curious, if you create another child app with a different name... does it work? Just wondering if that setting is someone surviving the delete and recreate process.

greg · May 1, 2019, 12:43pm

Recreated child app from scratch with time restrictions, new child name but same error.

bptworld · May 9, 2019, 9:55pm

New version on Github...

V1.1.4 - 05/09/19 - Added ability to change the voice used by priority - speechSynth only

This is a fun one. If you use the Message Priority feature, you can now select the voice you want the message spoken in!

Thanks to @mike.maxwell for posting the example code for the TTS interface!

dwspmail · May 12, 2019, 7:13am

Hi @bptworld, hope all is well.

I can't seem to get this to work for me. I have a rule setup that sends a speech synth message every hour to announce the time. The message is sent to my 'what did i say' virtual speaker, which is, in turn, sent to my follow me enabled speakers. I get the message every hour, but it starts by saying 'm the time is 10 am'. It seems that it is not stripping out the priority identifier from the message as well as changing the voice. After updating the code for the child app do I need to create a new child task within the app or can I just modify the existing child tasks?

bptworld · May 12, 2019, 10:06am

@dwspmail
Please show me the rule and the follow me child app. Also, are there any errors in the log?

Thanks

dwspmail · May 13, 2019, 7:47pm

Hi @bptworld, my rule is as follows:-

And the followMe child app:-

I get no errors in the log.

bptworld · May 13, 2019, 7:55pm

In your rule, select actions... there should be no spaces around the ; separator.

example:
[M]Great Scots, Have you... %time% ; [M]Rock on Tommy

Should be...
[M]Great Scots, Have you... %time%;[M]Rock on Tommy

aryvin · May 13, 2019, 10:49pm

Hi Bryan,

I'm trying to use Follow Me in voice language switching mode, but it looks like it doesn't work. All text to speech announcements volume is correct according to set priorities, but voices don't switch for some reason and all announcements are pronounced in the default system voice regardless of voices I've configure in Follow Me.

Below is my test example in English, Spanish and Italian.

bptworld · May 13, 2019, 11:20pm

Hi,
Your rule is wrong under Select Actions.

You have...
HHello ... ;LChao

Each Priority needs to be in brackets...
[H]Hello;[L]Hola

Edit: looks like you might have found a bug with RM 3.0. It's stripping out the brackets!

@bravenel Looks like RM 3.0 is stripping out any brackets entered into the "Message to Send" field. Please see screenshots in post #68.

Thanks

bravenel · May 13, 2019, 11:32pm

Yep, good catch. Will fix that.

aryvin · May 13, 2019, 11:44pm

I also observed that [] brackets were stripped in the trigger and that's why I've attached the action body where they were present. But in this case I still don't understand why the sound level of announcement was working correctly in every case according to set Follow Me priorities if sound switch problem is related to the brackets stripping bug. Volume by priority is also defined by the variable inside [H][M][L]. Maybe it is just UI bug in RM

bravenel · May 13, 2019, 11:58pm

The brackets are being stripped in the UI, not for the message. Look at the app status for the rule, and you should see the message in the settings. You can easily see there if it has the brackets or not.

aryvin · May 14, 2019, 12:05am

I can confirm that brackets are present in app state, so the problem in switching voice languages most likely is not related to this UI bug.

bptworld · May 14, 2019, 12:07am

Would you please let Bruce fix the issue with the brackets first. Trust me, this works just fine in RM 2.5.

aryvin · May 14, 2019, 12:09am

OK, no problem

dwspmail · May 14, 2019, 8:44pm

Hi,

I have removed the spaces from around the square brackets in RM. I can also confirm that I am using RM 2.5 for the 'hourly chime' but it still refuses to work with regard to changing the TTS Voice. I have updated RM to version 3.0, however the rule is showing as RM 2.5. I guess I will have to wait for Bruce to fix the issue as the 2.5 rule will be running with the RM 3.0 code.

bptworld · May 15, 2019, 1:13am

Had some time to play around with this today...

Good news is I got the voices to change correctly. Even added a random option.

Bad news...@aryvin this won't fix your problem with languages. Each voice is just that, a voice. The message will still speak in english, just with a different accent. Don't know why I thought it would change the language... I blame it on the new meds.

New Version on Github...

V1.1.6 - 05/14/19 - Changed voice options to just one Fun (F) and a Random (R)