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

community_app

#41

I have managed to get this working with my Sonos Speaker, however my Google Speakers seem to be a bit hit or miss. Mostly miss i'm afraid.

@bptworld , is your setup primarily with Google Mini's? If so what is your recommended config in the Follow Me child task?


#42

I have several mini's and two hubs. I use the 'Initialize Google devices every X minutes?' set to 4. They still drop off every now and then but they have been much better. Anything over 5 and they drop right off.

Until Mike throws us some more magic with the Chromecast integration, there isn't anything else we can do to keep them alive.


#43

Thanks @bptworld, do you also use the 'initialise before sending speech' setting?


#44

Nope, just the every 4 minutes.


#45

By the way, I am using the tile which indicates the speaker status, although during my tests I have removed follow me child tasks but the speaker status that the child task relates to is not removed. How do you reset this?


#46

Please update the driver 'What Did I Say', the reset switch is in the new version.

BTW, I assume you mean child apps :wink::sunglasses:


#47

Any tips on getting Sonos to work? I'm getting this error

[dev:270](http://10.0.1.45/logs#dev270)2019-04-07 08:25:51.629 am [error](http://10.0.1.45/device/edit/270)groovy.lang.MissingMethodException: No signature of method: user_driver_BPTWorld_What_Did_I_Say_355.playTextAndRestore() is applicable for argument types: (java.lang.String, java.lang.Long) values: [Garage Door is closed, 50] Possible solutions: playTextAndRestore(java.lang.Object) (playTextAndRestore)


#48

Ok I'm getting real close here.

I've got my speech properly displaying in "what did I say" but I can't get it to output at my speaker using "follow me". Here is my current error

2019-04-08 07:43:13.871 am [error](http://10.0.1.45/installedapp/configure/372)java.text.ParseException: Unparseable date: "7:30" on line 476 (lastSpokenHandler)

Line 476 has to do with times that speech is allowed.

I do have this section filled out in the child app

Thoughts?


#49

Please make sure you're on the latest version, V1.1.1 as of 4/8/19. Just tested mine again and everything seems to be working.

If it doesn't work after installing latest version, please post a debug log.

Here is mine, showing that it worked. :thinking:

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:23.389 am [debug](http://192.168.7.91/installedapp/configure/4883)In letsTalk - Speech Synth - Living Room display

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:23.326 am [debug](http://192.168.7.91/installedapp/configure/4883)In letsTalk - continuing

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.716 am [debug](http://192.168.7.91/installedapp/configure/4883)In letsTalk - pause: 603

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.699 am [debug](http://192.168.7.91/installedapp/configure/4883)In checkVol - priority volume: 80

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.696 am [debug](http://192.168.7.91/installedapp/configure/4883)In checkVol - priority: [H]

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.694 am [debug](http://192.168.7.91/installedapp/configure/4883)In checkVol - volume: 60

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.686 am [debug](http://192.168.7.91/installedapp/configure/4883)In checkVol...

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.684 am [debug](http://192.168.7.91/installedapp/configure/4883)In checkTime - timeBetween: true

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.667 am [debug](http://192.168.7.91/installedapp/configure/4883)In checkTime - 2019-04-08T06:00:00.000-0400 - 2019-04-08T22:00:00.000-0400

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.597 am [debug](http://192.168.7.91/installedapp/configure/4883)In alwaysOnHandler - setting sZone to true

[app:4883](http://192.168.7.91/logs#app4883)2019-04-08 09:42:22.596 am [debug](http://192.168.7.91/installedapp/configure/4883)In alwaysOnHandler...

Also curious why yours looks so different? This is what mine looks like using Chrome.

Thanks


#50

Thanks. Updated child works now!!!

Mine is safari.

Thanks for the app!


#51

Just got some google home minis to dedicate to announcements. Testing this app out tonight. Just starting, but looks promising!

Very minor, but I thought I'd mention the first green label appears to be incorrect:


#52

I'm having some minor trouble with the app. Been playing for a while and I think I have it figured out so it can be reproduced. I've noticed some similar comments in this thread.

I have a speaker being enabled by a light being on. When I first create the child app for that speaker, even though the light was on when I created the child app, the speaker doesn't talk. After playing with it a while, I noticed if after I create the child app I change the value of the switch from off then back to on, it will start speaking. Almost like it doesn't register the switch value until the first change?

I also tried using the pause app switch at the top of the child app. It appears to have a similar issue - if I turn on the pause with a speaker based on a switch, the pause does nothing - the speaker still talks. However, if I then change the value of the switch it appears the Pause command is then recognized.

Hope that makes sense!


#53

Using the info in my last post, I've been able to get all the speakers initialized by toggling the switches that control them. Took a while to figure out why I was having trouble, but now they all appear to be working well!

If I could suggest a feature: I'm not sure if others would find it useful or not, but I love being able to control apps from dashboards. You already have an option to disable the child apps via switch. Would it also be possible to link the volume to a level device? Then once you had the app set up, you could modify it from a dashboard without ever having to log back into Hubitat. Obviously not critical, just thought it might be a good idea!

Thanks for the great app! I'm looking forward to making my house lousy with announcements!


#54

I'm getting this error.

2019-04-30 06:46:15.654 pm [error](http://10.0.1.45/installedapp/configure/403)java.text.ParseException: Unparseable date: "7:30" on line 451 (lastSpokenHandler)

My settings for time restrictions are

Any thoughts on what else I should check? I'm on version 1.1.2


#55

Please try V1.1.3 - 04/30/19 - Attempt to fix bug in checkTime

Be sure to have Debug logging on. If you still get the error please paste in the logs. Also please do not format (</>) the log, simply paste it in.

Thanks


#56

Version 1.1.3

So this speech would have been outside the permissible time frame, but it is still giving an error.

app:4032019-05-01 07:21:21.813 am errorjava.text.ParseException: Unparseable date: "7:30" on line 453 (lastSpokenHandler)

app:4032019-05-01 07:21:21.808 am debugIn checkTime - 7:30 - 2019-05-01T20:00:00.000-0400

app:4032019-05-01 07:21:21.805 am debugIn letsTalk...

app:4032019-05-01 07:21:21.793 am debugIn lastSpoken - Priority: gar - lastSpoken: garage door is now closed

app:4032019-05-01 07:21:21.781 am debugIn lastSpoken...

app:4032019-05-01 07:20:57.889 am debugIn motionSensorHandler - sZone: true - Status: inactive

app:4032019-05-01 07:20:57.876 am debugIn motionSensorHandler...

app:4032019-05-01 07:20:56.334 am debugIn motionSensorHandler - sZone: true - Status: inactive

app:4032019-05-01 07:20:56.328 am debugIn motionSensorHandler...

app:4032019-05-01 07:20:49.897 am debugIn motionSensorHandler - sZone: true - Status: inactive

app:4032019-05-01 07:20:49.876 am debugIn motionSensorHandler...

app:4032019-05-01 07:20:40.140 am errorjava.text.ParseException: Unparseable date: "7:30" on line 453 (lastSpokenHandler)

app:4032019-05-01 07:20:40.106 am debugIn checkTime - 7:30 - 2019-05-01T20:00:00.000-0400

app:4032019-05-01 07:20:40.080 am debugIn letsTalk...

app:4032019-05-01 07:20:40.079 am debugIn lastSpoken - Priority: Gar - lastSpoken: Garage Door is now open

app:4032019-05-01 07:20:40.073 am debugIn lastSpoken...

Also, I do not have priority set up for this zone, but it seems to think so in the log

Here are the app settings. Which shows priority is not set. But I also notice that the from time is -5:30pm instead of the 7:30am that is set.


#57

Can you try deleting this child app and recreating it? Something just doesn't seem right with the times.

Thanks


#58

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]


#59

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]


#60

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