BigTalker 2.1.3a (Dev Test / Beta release)

⚙️ Custom Apps and Drivers Custom Apps
1

BigTalker2 Beta update (Targeted 2.1.3 release).

Previous post with intro and instructions (for the non DEV / Beta version): BigTalker 2.1.0

!! THIS IS A TEST RELEASE !!
Settings will not transfer from test releases to final releases. Settings may need to be updated or the app uninstalled/reinstalled at final release to move from 2.1.0 to 2.1.3 or from Beta to final release. Backup your Hubitat before replacing your BigTalker code if you are using BigTalker2 or Copy/Save your current Parent/Child non-Dev and/or Dev code to a text file in case you need to put it back. If you are not using the dev code, then add a new app from code (Apps Code > Add App), it will be labeled as BigTalker2-DEV- Parent or Child and will not interfere with your non-DEV labeled BigTalker install unless you configure conflicting or competing events; don't overwrite your non-dev parent/child apps. The last non-DEV release was 5/24/2019 at version 2.1.0 though there have been a few DEV releases published since then. Below is the list of commits/changes since the last DEV release:

  • Code clean up, bug fixes and optimizations
  • Optimized parent calls for UI format handling, reducing redundant code.
  • Bug Fix related to start/end time restriction settings for Alarms, Routines, Filters, Power Meters and Valves.
  • Code clean up related to SHM state capture (Away, Home, Disarm, etc).
  • Optimizations of event handling (Switch on/off, Motion active/inactive, etc)

GitHub Root for version DEV 2.1.2.3a:
https://github.com/rayzurbock/BigTalker2/tree/2.1.2.3a

Parent App (Dev Test 2.1.2.3a (to be merged as 2.1.3 on release)):
https://github.com/rayzurbock/BigTalker2/blob/2.1.2.3a/smartapps/rayzurbock/bigtalker2.src/bigtalker2.groovy

Child App (Dev Test 2.1.2.5a (to be merged as 2.1.3 on release)): https://github.com/rayzurbock/BigTalker2/blob/2.1.2.3a/smartapps/rayzurbock/bigtalker2-child.src/bigtalker2-child.groovy

Here are all of the changes since the last non-Beta release (Scroll to the bottom to 2.1.2.2-DEV and beyond):
https://github.com/rayzurbock/BigTalker2/compare/master...2.1.2.3a

Introduction

Have you ever wanted a talking house? Now you can, easily! With the Big Talker SmartApp

When Hubitat is paired with a compatible audio device (such as a Sonos, Ubi, LANnouncer, VLCThing, etc) and the BigTalker SmartApp, your house can say what you want it to say when events occur.

Author's Hubitat Community Profile: Hubitat

Currently supported events:

  • Time: Time of Day + Day(s) of Week
  • Motion: Active/Inactive
  • Switch: On/Off
  • Presence: Arrive/Depart
  • Lock: Lock/Unlock
  • Contact: Open/Close
  • Mode: Change (Home, Away, etc)
  • Thermostat: Cooling/Heating/Fan/Idle(not running)
  • Acceleration: Active/Inactive
  • Water: Wet/Dry
  • Smoke: Detect/Clear/Test
  • Button: Press or Held ** I do not have a button and I understand Hubitat works differently than the original platform that BT2 was written on. Does this work?
  • Power Meter: High, Normal, Low Wattage
  • Alarm: Off, Siren, Strobe, Both
  • FilterStatus: Normal, Replace (Needs testing, supported in HE?)
  • OvenMode: Heating, Grilling, Warming, Defrosting (Needs testing, supported in HE?)

Phrase Tokens/Variables
Voice phrases support the following variables (will be replaced with actual phrase when triggered)

  • %date% = Current date; January 01
  • %day% = Current day; Monday
  • %devicename% = Triggering devices display name
  • %devicetype% = Triggering device type; motion, switch, etc…
  • %devicechange% = State change that occurred; on/off, active/inactive, etc…
  • %description% = The description of the event that is to be displayed to the user in the mobile application
  • %groupname% = Play Device group name (ie: group/room name that you have setup for this set of events)
  • %locationname% = Hub Location name; home, work, etc…
  • %lastmode% = Last home mode; home, away, etc…
  • %mode% = Current home mode; home, away, etc…
  • %mp3(url)% = Play hosted MP3 audio file from url. Example: %mp3(http://www.somesite.com/audio.mp3 )%
    • musicPlayer devices only (Sonos, etc). Does not support speechSynthesis devices such as Ubi and LANnouncer among others.
    • Cannot be mixed with any other text in the event's phrase
  • %time% = Current time; HH:mm am/pm
  • %value% = Wattage value (only applicable in Power Meter events)
  • %weathercurrent% - Current/Today's US weather for your hub location
  • %weathertoday% - Current/Today's US weather for your hub location
  • %weathertonight% - Tonight's US weather for your hub location
  • %weathertomorrow% - Tomorrow's US weather for your hub location

For example when turning off a switch named “Office Light” with a spoken phrase of "%devicename% %devicetype% has been turned %devicechange% " would speak " Office light switch has been turned off ".

Another example would be to create a simulated switch that is turned ON in the morning by your Good Morning routine, and then OFF at night with your Good Night routine. Then set up a Big Talker switch event group tied to that switch’s ON event that speaks " Good Morning. Today is %day%. The time is %time%. %weathertoday% ", or find an MP3 news stream for your daily briefing and use the speech phrase "%mp3(http://path/to/mp3 )%

Keep in mind, if you configure highly active or too many devices, it may get annoying or cut a previous message off!! We had a family gathering and the kids kept going in/out the back door to play in the yard. “Back Door has been opened, Back Door has been closed, Back Door has been opened, you get the idea.” I wouldn’t configure chatty motion sensors either, but that’s up to you.

Have Fun!

Installation via Hubitat

6 Likes
2

If you try this DEV release, please post here with: Hubitat firmware version, audio device type (Sonos / LANnouncer / etc), whether speech or music mode, any problems or success that you see — especially around TTS (Text to Speech), event handling (Switch on/off, etc), time restrictions.

To help focus further development or help others, can you explain what you use BigTalker for or want to use it for? (door alert, motion trigger, weather announcements (current, tomorrow, etc), BigTalker reacts to direct events as realtime as possible, it doesn't chain events or other logic.

This is a new user / new re-install / stable release candidate so please backup your hub/settings then report any unexpected issues along with the version of the parent and child app that you are using which is found at the bottom of the code for each. Report in this thread or in GitHub ( GitHub · Where software is built )