Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. TTS in MSR?
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor

TTS in MSR?

Scheduled Pinned Locked Moved Solved Multi-System Reactor
33 Posts 12 Posters 4.5k Views 12 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F Offline
    F Offline
    Fanan
    wrote on last edited by
    #1

    Hi!

    In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
    But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
    Thanks!
    /Fanan

    1 Reply Last reply
    0
    • LibraSunL Offline
      LibraSunL Offline
      LibraSun
      wrote on last edited by
      #2

      In MSR, try the following action (assuming you have the Sonos_TTS plug-in running on Vera):

      [ Entity Action ] [ Sonos device ] [ x_vera_svc_micasaverde_com_Sonos1.say ]
      where these fields are all (mostly) optional:
      Text:, Language:, Engine: [AZURE], Volume:, SameVolumeForAll:, GroupDevices:, GroupZones:, Chime:, Repeat:, UnMute:, UseCache:
      

      Hope I'm pointing you in the right direction, as that's what I see in my (only) rule that produces TTS output.

      1 Reply Last reply
      0
      • cw-kidC Offline
        cw-kidC Offline
        cw-kid
        wrote on last edited by
        #3

        Reactor for Vera has support for sending TTS to Google Home speakers?

        I'm currently using Node Red for Google Home TTS and I am sending Http requests from MSR rules to Node Red etc to initiate a TTS announcement.

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #4

          Home Assistant does not enumerate the full list of services supported by a device in any of its APIs. It's a bit of a hole (but not unusual -- Hubitat is the same).

          You can tell MSR that a device supports a service by creating a file local_hass_devices.yaml with contents similar to the following (modify the entity ID as needed):

          # This file has local definitions for HomeAssistant devices.
          
          entities:
            # This media player is a Sonos device, so it supports the Hass "tts" service
            "hass>media_player_portable":
              services:
                - tts
          

          Remember YAML indenting is done with spaces, not tabs; two spaces per level. Use yamlchecker.com for check/diagnostics.

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          F M 2 Replies Last reply
          1
          • toggledbitsT toggledbits

            Home Assistant does not enumerate the full list of services supported by a device in any of its APIs. It's a bit of a hole (but not unusual -- Hubitat is the same).

            You can tell MSR that a device supports a service by creating a file local_hass_devices.yaml with contents similar to the following (modify the entity ID as needed):

            # This file has local definitions for HomeAssistant devices.
            
            entities:
              # This media player is a Sonos device, so it supports the Hass "tts" service
              "hass>media_player_portable":
                services:
                  - tts
            

            Remember YAML indenting is done with spaces, not tabs; two spaces per level. Use yamlchecker.com for check/diagnostics.

            F Offline
            F Offline
            Fanan
            wrote on last edited by
            #5

            @toggledbits That worked as a charm! 🙂
            A new question; I send the TTS-message to a Nest smart display. Is it possible to have the text visible on the screen? Or even a selected picture? Maybe that's to much... But it would still be cool!

            Thanks for giving me the TTS option!

            1 Reply Last reply
            1
            • F Offline
              F Offline
              Fanan
              wrote on last edited by
              #6

              @toggledbits, I wounder if it's possible to use the "PlayURI" command, as in the Reactor in Vera. The aim is to play a certain Sonos playlist. My Sonos is visible both as a Vera integration and a HA integration. The Vera integration shows up as an option, but doesn't work. The HA integration don't seem to have that option in MSR. I tried to add it using the same method as you descriped above, but that didn't work. Do you know how to fix this?
              Best regards,
              /Fanan

              MatohlM 1 Reply Last reply
              0
              • F Fanan

                @toggledbits, I wounder if it's possible to use the "PlayURI" command, as in the Reactor in Vera. The aim is to play a certain Sonos playlist. My Sonos is visible both as a Vera integration and a HA integration. The Vera integration shows up as an option, but doesn't work. The HA integration don't seem to have that option in MSR. I tried to add it using the same method as you descriped above, but that didn't work. Do you know how to fix this?
                Best regards,
                /Fanan

                MatohlM Offline
                MatohlM Offline
                Matohl
                wrote on last edited by
                #7

                @fanan To play a Sonos-playlist I use the SQ:xxx command and it works well.
                Skärmavbild 2021-05-21 kl. 17.33.58.png

                1 Reply Last reply
                1
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #8

                  For Hass, the x_hass_media_player.play_media action is the one to use, but the parameters are platform (Sonos) dependent and you need to figure them out. The Hass documentation for the Sonos component has some information, but it's anything but user-friendly. Google is your friend.

                  For Hubitat, I've never had any luck getting Sonos to play queues, even from the Hubitat's own UI.

                  I will say, this is a reflection of how much the Sonos plugin on Vera simplifies the use of the zone player, because the Hass and Hubitat interfaces are pretty raw/low-level, and Sonos is complex.

                  Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                  1 Reply Last reply
                  1
                  • toggledbitsT toggledbits

                    Home Assistant does not enumerate the full list of services supported by a device in any of its APIs. It's a bit of a hole (but not unusual -- Hubitat is the same).

                    You can tell MSR that a device supports a service by creating a file local_hass_devices.yaml with contents similar to the following (modify the entity ID as needed):

                    # This file has local definitions for HomeAssistant devices.
                    
                    entities:
                      # This media player is a Sonos device, so it supports the Hass "tts" service
                      "hass>media_player_portable":
                        services:
                          - tts
                    

                    Remember YAML indenting is done with spaces, not tabs; two spaces per level. Use yamlchecker.com for check/diagnostics.

                    M Offline
                    M Offline
                    Matteburk
                    wrote on last edited by
                    #9

                    @toggledbits And in Hubitat? 🙂

                    M 1 Reply Last reply
                    0
                    • toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by
                      #10

                      I think I answered that.

                      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                      1 Reply Last reply
                      0
                      • M Matteburk

                        @toggledbits And in Hubitat? 🙂

                        M Offline
                        M Offline
                        Matteburk
                        wrote on last edited by
                        #11

                        @matteburk sorry missed your last post

                        1 Reply Last reply
                        0
                        • F Offline
                          F Offline
                          Fanan
                          wrote on last edited by
                          #12

                          Thanks everyone - I'll give it a try in the weekend!

                          1 Reply Last reply
                          0
                          • LibraSunL Offline
                            LibraSunL Offline
                            LibraSun
                            wrote on last edited by LibraSun
                            #13

                            This news just in from Microsoft:

                            "Thanks for using Azure Text-to-Speech. We would like to share the great news that we have recently released 12 new regions. We also released neural Text-to-Speech in 10 more languages, a new neural voice (Jenny Multilingual) that speaks 14 languages, 11 more neural voices in American English and 5 more neural voices in Chinese. When using neural voice, synthesized speech is nearly indistinguishable from human recordings."

                            F 1 Reply Last reply
                            1
                            • LibraSunL LibraSun

                              This news just in from Microsoft:

                              "Thanks for using Azure Text-to-Speech. We would like to share the great news that we have recently released 12 new regions. We also released neural Text-to-Speech in 10 more languages, a new neural voice (Jenny Multilingual) that speaks 14 languages, 11 more neural voices in American English and 5 more neural voices in Chinese. When using neural voice, synthesized speech is nearly indistinguishable from human recordings."

                              F Offline
                              F Offline
                              Fanan
                              wrote on last edited by Fanan
                              #14

                              @librasun . I'm trying to add Microsofts TTS service, but it doesn't work. I got a API key and everything. Still doesn't work. My aim is to use a swedish neural voice instead of Googles voices. Is it working for you?

                              EDIT: I got it working! The neural voices don't support my region, so I had to change the region (created a new service), when I was logged in at Azure.

                              1 Reply Last reply
                              1
                              • Tom_DT Offline
                                Tom_DT Offline
                                Tom_D
                                wrote on last edited by toggledbits
                                #15

                                I am trying to enable MSR TTS on Google home devices. I found the local_hass_devices.yaml file already existed with the above example.
                                So in the true spirit of cutting and pasting while not knowing what I am doing I ended up with the following file:

                                # This file has local definitions for HomeAssistant devices.
                                ---
                                entities:
                                  # Entry shows how an entity can have a service added and its name forced
                                  "hass>sensor_connected_clients":
                                    name: "WebSocket Clients"
                                    services:
                                      - homeassistant
                                  # Sample Sonos device, add the Hass "tts" service for text-to-speech capability
                                  "hass>media_player_sonos_living_room":
                                    service:
                                      - tts
                                  # Sample Sonos device, add the Hass "tts" service for text-to-speech capability
                                  "hass>media_player.family_room_speaker":
                                    service:
                                      - tts
                                

                                latest-25082-3c348de6

                                1 Reply Last reply
                                1
                                • toggledbitsT Offline
                                  toggledbitsT Offline
                                  toggledbits
                                  wrote on last edited by toggledbits
                                  #16

                                  What you've done here (correct approach, one little error, see below) is declare that those two media_player devices have the tts service as an additional declared service. That will cause MSR to bring in the attributes and actions of that service as supported for the device.

                                  Hass doesn't publish what Hass services a Hass entity supports through its API. The only service that can be known for certain is the one that is part of the Hass entity ID (e.g. the Hass entity ID media_player.family_room_speaker tells you that it will support the media_player service). Any other supported services (like tts) aren't enumerated by the API, sadly (in a few cases, they can be inferred as related in a bit mask, but this is an extension and highly implementation/component dependent, not consistent at all, but I try to pick this up when known). This manual way of connecting additional services/capabilities to the entities is the best I could do at the moment.

                                  Other things you can do in this file are override the name of the device (by supplying name: "myoverridename" at the same indent level as service:), and change the primary attribute (primary_attribute: "servicename.attributename"). When setting/overriding the primary attribute, the service must be supported by the device (so known by the device ID or added via services: in this file).

                                  One small correction, though: the canonical ID for the third entry hass>media_player.family_room_speaker -- the dot (.) should probably be an underscore (_). Confirm on the Entities list.

                                  Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                  1 Reply Last reply
                                  1
                                  • F Offline
                                    F Offline
                                    Fanan
                                    wrote on last edited by
                                    #17

                                    Picking up on my old thread. I just got Alexa working with tts in Home Assistant. Is it possible to get it to work with MSR as well? I added the speakers to my local_hass_devices.yaml, and then I got the same tts options as with google speakers. But that don't work for sending tts messages. In HA I have to add "Type: tts" for it to work. I also don't see the native Alexa voice as an option, only the same as the google speakers. It's not a personal big deal, but would be a fun and maybe useful feature in the future.

                                    1 Reply Last reply
                                    0
                                    • toggledbitsT Offline
                                      toggledbitsT Offline
                                      toggledbits
                                      wrote on last edited by
                                      #18

                                      Let me play around with this a bit. You can add the notify service to the entity (have you done this?), but I'm not sure about the rest of the parameters. Some are tricky. But I want to get something like this going in my house, so good excuse to figure it out...

                                      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                      F 1 Reply Last reply
                                      0
                                      • toggledbitsT toggledbits

                                        Let me play around with this a bit. You can add the notify service to the entity (have you done this?), but I'm not sure about the rest of the parameters. Some are tricky. But I want to get something like this going in my house, so good excuse to figure it out...

                                        F Offline
                                        F Offline
                                        Fanan
                                        wrote on last edited by
                                        #19

                                        @toggledbits said in TTS in MSR?:

                                        You can add the notify service to the entity (have you done this?)

                                        @toggledbits No, I haven't used the notify service. I might give it a try later this week. If you (or anyone else) figure it out, please share!

                                        B toggledbitsT 2 Replies Last reply
                                        0
                                        • F Fanan

                                          @toggledbits said in TTS in MSR?:

                                          You can add the notify service to the entity (have you done this?)

                                          @toggledbits No, I haven't used the notify service. I might give it a try later this week. If you (or anyone else) figure it out, please share!

                                          B Offline
                                          B Offline
                                          Buxton
                                          wrote on last edited by
                                          #20

                                          @fanan Per this topic https://smarthome.community/topic/744/sending-a-service-request-to-home-assistant?_=1638829172919 I couldn't get Alexa tts to work in MSR, but I do have it working in openLuup with the following code that sits inside a simple plugin:

                                          myEchoDevice = "alexa_media_".. myEchoDevice
                                          myEchoMessage = table.concat(myEchoMessage)
                                          	
                                          local request_body = json.encode {message = myEchoMessage, data = {["type"] = "announce",method = "all"}}
                                          
                                          local response_body = {}
                                          	
                                          local theURL = 'http://'..HomeAssistantIP..':'..HomeAssistantPort..'/api/services/notify/'..myEchoDevice  
                                          	
                                          r, c, h = http.request {
                                             url = theURL,
                                             method = "POST",
                                             headers = {
                                             ["Content-Type"]   = "application/json",
                                             ["Authorization"] = "Bearer ".. HomeAssistantToken,
                                             ["Content-Length"] = request_body:len()
                                             },
                                          source = ltn12.source.string(request_body),
                                          sink   = ltn12.sink.table(response_body)
                                          }
                                          

                                          The variable "myEchoDevice" is the exact name of the specific echo device (or device group) as presented in the Amazon Alexa app. I typically broadcast to all my devices via a group, intercom style, so I catch the message wherever I am in my home. The variable "HomeAssistantToken" needs to be created in HA. "myEchoMessage "is a lua table in the above code, but you could just as easily capture the message as a string, and then trim the string prior to sending it to the HTTP post request.

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Set Reaction > Script Action
                                            therealdbT
                                            therealdb
                                            0
                                            6
                                            77

                                          • Wiring Samotech SM308-S into light fitting
                                            akbooerA
                                            akbooer
                                            0
                                            2
                                            41

                                          • Errors after updating to MQTTController build 25139
                                            toggledbitsT
                                            toggledbits
                                            0
                                            6
                                            69

                                          • 🎉 My very first MSR controller: OpenSprinkler
                                            therealdbT
                                            therealdb
                                            5
                                            13
                                            631

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            93

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            122
                                            37.3k

                                          • Z-Wave Future....
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            176

                                          • Can´t restart or upgrade/deploy MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            131

                                          • [Solved] Limit HA Entity in MSR
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            7
                                            259

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            699

                                          • Remote access of Zwave stick from Z-wave server
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            422
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Unsolved