Announcement

Collapse
No announcement yet.

Jon00 Voice Monkey - Easy Alexa TTS (Announcements) for Homeseer 3 & Homeseer 4

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Jon00 Voice Monkey - Easy Alexa TTS (Announcements) for Homeseer 3 & Homeseer 4

    Voice Monkey is Alexa skill which allows you to trigger Alexa Routines remotely by simulating a doorbell press through its web API. In turn this allows (via the use of Alexa routines) to send Speech, Notifications (and in the case of Alexa devices with screens), Images, Video & Web sites.

    This unmanaged plugin allows Voice Monkey integration with Homeseer 3 & 4 allowing you to make announcements to all Alexa devices, groups of Alexa devices or individually. In addition, you have the option to send images/URL/Video to screen enabled devices.

    Speech is sent to Voice Monkey via normal ‘Speak Something’ in events etc. It uses ‘Virtual Speaker Clients’ to direct speech to individual or groups of Alexa devices.

    Plugin supports Alexa Speech Synthesis Markup Language (SSML) Tags (Voice change, Pause, Sounds, Volume, Whisper etc).

    This plugin also supports triggering Alexa routines from Homeseer not related to TTS (Alexa speech).

    The plugin also supports TTS Web based Speaker clients using HomeSeer’s built-in SAPI/Flite speech engines and/or via VoiceRSS online TTS service which will give improved speech quality on Linux systems. VoiceRSS has a free tier of 350 daily requests.

    HS4 users can fully integrate the TTS Speaker Clients into all/selected HS4 pages using either SAPI/Flite or VoiceRSS. There are also standalone TTS speaker client web pages which can be used in both HS3 or HS4.

    Web Based speaker clients allow you to hear Text to Speech messages on any hardware which supports a modern browser. This includes Android/Apple phones/tablets and ideal for headless HomeSeer systems which do not have a speaker client running.

    Note: Web Speaker Clients run independently to Voice Monkey and you do NOT need Alexa/Voice Monkey or any associated Hardware/Software to function.

    EDIT : As of January 21st 2022, Voice Monkey introduced a Pro version with a annual fee of $6 a year. Pro is required for Text To Speech operation. You do get a 14 day free trial when you sign up. Triggering Alexa Routines is still available for free with their basic package.

    EDIT1: As of May 2023, Voice Monkey dropped the Pro version for new users. This was replaced with Premium which costs $2.99 Month.Triggering Alexa Routines is still available for free

    Compatible with Windows & Linux installations.

    As always, it can be downloaded from my site (click on my banner below). Please post any comments here.

    (No Banner seen?- check your Forum Settings - User Settings, Account, Tick 'Show Signature')

    Click image for larger version  Name:	Capture.png Views:	1365 Size:	57.8 KB ID:	1572088
    Jon


    #2
    Hi Jon thank you. Security wise, do you know if it is safe, like access key and etc, are they exposed?

    Thanks

    Sent from my SM-G973U1 using Tapatalk

    Comment


      #3
      Not sure what you mean by exposed?
      Jon

      Comment


        #4
        Originally posted by jon00 View Post
        Voice Monkey is Alexa skill which allows you to trigger Alexa Routines remotely by simulating a doorbell press through its web API. In turn this allows (via the use of Alexa routines) to send Speech, Notifications (and in the case of Alexa devices with screens), Images, Video & Web sites.

        This unmanaged plugin allows Voice Monkey integration with Homeseer 3 & 4 allowing you to make announcements to all Alexa devices, groups of Alexa devices or individually. In addition, you have the option to send images/URL/Video to screen enabled devices.

        Speech is sent to Voice Monkey via normal ‘Speak Something’ in events etc. It uses ‘Virtual Speaker Clients’ to direct speech to individual or groups of Alexa devices.


        Note: At the time of writing, Voice Monkey is free, however may charge in the future.

        Compatible with Windows & Linux installations (but only tested on Ubuntu).

        As always, it can be downloaded from my site (click on my banner below). Please post any comments here.
        Great!! all things go well I should be testing it on Windows for you by Monday.

        Comment


          #5
          Oh wow! This sounds really cool Jon!!!! I'm definitely adding this to the list of things to work on this weekend.

          Comment


            #6
            I didn't get a chance to look at it yet but assume it is an api and some point you will need to enter a key or password. If it is a black box, I wanted to make sure security wise was OK.

            Sent from my SM-G973U1 using Tapatalk

            Comment


              #7
              Originally posted by alphatech View Post
              I didn't get a chance to look at it yet but assume it is an api and some point you will need to enter a key or password. If it is a black box, I wanted to make sure security wise was OK.

              Sent from my SM-G973U1 using Tapatalk
              Yes it is sent as part of the the https string like most api's that provide you with personal keys.
              Jon

              Comment


                #8
                Hi jon00


                i installed voicemonkey on HS3 and went through the setup. My speak-all money works if i trigger it from the VoiceMonkey website and via URL, but not from HS3. My HS3touch clients all speak, but the voicemonkey trigger from HS3 does not appear in the VoiceMonkey log or the Alex Activity log.

                (I have tried it with no speaker selected and I have tried entering ALEXA:ALL as my speaker but neither seem to send a trigger to Voicemonkey.)

                when my event runs, it looks like it should work based on what is in the log?

                Apr-30 2:17:17 PM TTS Speak: ():testing. please ignore me.
                Apr-30 2:17:17 PM Event Event Trigger "Test Speak All"
                Apr-30 2:17:17 PM Event Event Test Speak All triggered by the event page 'Run' button.



                Apr-30 2:23:00 PM TTS Speak: (ALEXA:ALL):testing. please ignore me.
                Apr-30 2:23:00 PM Event Event Trigger "Test Speak All"
                Apr-30 2:23:00 PM Event Event Test Speak All triggered by the event page 'Run' button.


                when i run this script in HS3 to call the voicemonkey API url it does work, so i don't think it is a connectivity problem
                &hs.GetURL("https://api.voicemonkey.io","/trigger?access_token=#masked#&secret_token=#masked#&monkey=s peak-all&announcement=Hello%20monkey",TRUE, 80)


                in my HS3 log it looks like the plugin is starting up correctly?

                Apr-30 2:06:14 PM Jon00_VMonkey Version 1.0.0
                Apr-30 2:06:14 PM Jon00_VMonkey Ready
                Apr-30 2:06:14 PM Jon00_VMonkey Starting plugin...
                Apr-30 2:06:14 PM Jon00_VMonkey Connected


                I don't know whether i am supposed to see the plugin create speakers in the log, but i do not see any Alexa speakers being created. I only see my HSTouch clients and local HS3 speaker client being created (I realize this might be normal but wanted to mention it just in case it isn't):

                Apr-30 2:06:16 PM Speaker Speaker host added, Name: Hercules Instance: Default IP address: 127.0.0.1
                Apr-30 2:06:14 PM Speaker Speaker host added, Name: Hercules Instance: downstairs IP address: 192.168.1.32
                Apr-30 2:06:14 PM Speaker Speaker host added, Name: Hercules Instance: Laundry IP address: 192.168.1.34
                Apr-30 2:06:14 PM Speaker Speaker host added, Name: Hercules Instance: WC IP address: 192.168.1.67
                Apr-30 2:06:08 PM Speaker Speaker host added, Name: Hercules Instance: upstairs IP address: 192.168.1.49


                I have confirmed that my access token and secret token are correct in the .ini file and Monkey1 is set to speak-all (and speak-all is the name of the money in VoiceMonkey, as you can see in the URL i pasted above that works). Logging is set to 1. Can i enable debug logging or try anything else to help figure this out?

                Thanks for your help!

                System info:

                Current Date/Time: 4/30/2021 2:39:23 PM
                HomeSeer Version: HS3 Pro Edition 3.0.0.548
                Operating System: Microsoft Windows 10 Pro - Work Station
                System Uptime: 0 Days 0 Hours 33 Minutes 55 Seconds
                IP Address: 192.168.1.5
                Number of Devices: 1017
                Number of Events: 746
                Available Threads: 1200
                HSTouch Enabled: True
                Event Threads: 2
                Event Trigger Eval Queue: 0
                Event Trigger Priority Eval Queue: 0
                Device Exec Queue: 0
                HSTouch Event Queue: 0
                Email Send Queue: 0
                Anti Virus Installed: Windows Defender
                In Virtual Machine: No MFG: hp
                Enabled Plug-Ins
                3.0.0.32: Autelis
                2.0.61.0: BLBackup
                2.0.11.0: BLEditor
                3.0.55.0: BLGData
                2.0.28.0: BLOccupied
                1.0.5.0: BLShutdown
                3.1.3.0: Device History
                3.0.0.73: EasyTrigger
                3.0.0.36: Ecobee
                5.0.0.58: Global Cache Pro
                3.0.0.325: Life360
                3.1.0.18: MeiHarmonyHub
                3.0.1.0: MyHSToken
                1.2020.705.1301: MyQ
                3.0.0.14: NetCAM
                3.0.0.48: PHLocation2
                0.0.0.52: Pushover 3P
                1.0.0.7: Restart
                30.0.0.37: RFXCOM
                3.1.0.1: SDJ-Health
                3.1.0.57: Sonos
                1.6.0.5: Tesla Vehicles
                3.0.7616.22302: UltraLighting3
                3.0.1.0: Vista Alarm
                3.0.0.31: WeatherFlow
                3.0.1.19: weatherXML
                3.0.1.262: Z-Wave

                Comment


                  #9
                  Your log formatting for speech commands looks odd.

                  As this picks up the speak command from the log, I can see it would not trigger.

                  You seem to have an additional colon:

                  Mine on both Windows and LInux:

                  Speak ():Hello World

                  You:

                  Speak: ():testing. please ignore me.

                  Not sure how that could be?

                  There have been quite a few downloads already. Have others got this working?



                  Jon

                  Comment


                    #10
                    I experienced the same thing. I believe I followed all instructions correctly, but I don't hear anything from any of my Echo devices when using "Speak Something", although the VoiceMonkey trigger does work.

                    Comment


                      #11
                      I also see the same line in my log:

                      Code:
                      Speak: ():This is a test of Jon's Alexa TTS plugin

                      Comment


                        #12
                        OK, easy to fix. I will post an updated version tomorrow .
                        Jon

                        Comment


                          #13
                          Thanks Jon!

                          Comment


                            #14
                            Getting late here but I made the change (but not tested). Try V1.0.1 on my site and let me know.

                            To bed......
                            Jon

                            Comment


                              #15
                              That fixed it. 🙂 Now it's time to play!

                              Comment

                              Working...
                              X