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?
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
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 customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor

TTS in MSR?

Scheduled Pinned Locked Moved Solved Multi-System Reactor
33 Posts 12 Posters 7.7k 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.
  • 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
        • 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!

          toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #21

          @fanan OK. So it turns out that this has (much) more to do with the way the Alexa Media Player service works than anything. You can simply use the call_service action on the controller's system object to call the notify.alexa_media service (or its variants, more on that below). If you do it through the system entity, you don't need to make exceptions in your local configuration to add the service -- you can run a service against any entity from the system entity, and if it's not supported, the (Hass) entity will either ignore it or log an error, but nobody dies, missiles do not launch, gravity still works, the sun continues to rise and set, etc.

          2ffaac01-0768-430b-bd18-8d2c6056831a-image.png

          Above are two different versions of the service call that do about the same thing. I'll work backwards because that's the way I figured it out...

          The green-circled "short" version of the service name requires that you specify the target in the service data. The service data is a structure as shown (always). Also see the docs for the component for more info about this service and its data. The target field must be specified when using this short form of the service name, and its value is an array of HomeAssistant entity IDs (not Reactor entity IDs) for the players (Dots and Echos) that will speak the phrase. The data substructure must be given as shown.

          The red-circled variant uses a longer service name that includes the Amazon device's name. Apparently the component creates a set of aliased services, each with the device name appended to the base service name. I find this annoying, because I have over a dozen Dots/Echos, so and it creates a bunch of data pollution. But, it's there, and it's usable. When you use a "long" service name, you don't need to specify target in the data, but it's otherwise the same, as shown.

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

          therealdbT F T 3 Replies Last reply
          1
          • toggledbitsT toggledbits

            @fanan OK. So it turns out that this has (much) more to do with the way the Alexa Media Player service works than anything. You can simply use the call_service action on the controller's system object to call the notify.alexa_media service (or its variants, more on that below). If you do it through the system entity, you don't need to make exceptions in your local configuration to add the service -- you can run a service against any entity from the system entity, and if it's not supported, the (Hass) entity will either ignore it or log an error, but nobody dies, missiles do not launch, gravity still works, the sun continues to rise and set, etc.

            2ffaac01-0768-430b-bd18-8d2c6056831a-image.png

            Above are two different versions of the service call that do about the same thing. I'll work backwards because that's the way I figured it out...

            The green-circled "short" version of the service name requires that you specify the target in the service data. The service data is a structure as shown (always). Also see the docs for the component for more info about this service and its data. The target field must be specified when using this short form of the service name, and its value is an array of HomeAssistant entity IDs (not Reactor entity IDs) for the players (Dots and Echos) that will speak the phrase. The data substructure must be given as shown.

            The red-circled variant uses a longer service name that includes the Amazon device's name. Apparently the component creates a set of aliased services, each with the device name appended to the base service name. I find this annoying, because I have over a dozen Dots/Echos, so and it creates a bunch of data pollution. But, it's there, and it's usable. When you use a "long" service name, you don't need to specify target in the data, but it's otherwise the same, as shown.

            therealdbT Offline
            therealdbT Offline
            therealdb
            wrote on last edited by
            #22

            @toggledbits Speaking of that, is there a way to easily compose re-usable actions, so I could just pass the arguments (message and device) and call the same function? I'll use for the very same purpose, since I have a couple of endpoints doing notifications/TTS. Thanks!

            --
            On a mission to automate everything.

            My MS Reactor contrib
            My Luup Plug-ins

            1 Reply Last reply
            0
            • toggledbitsT toggledbits

              @fanan OK. So it turns out that this has (much) more to do with the way the Alexa Media Player service works than anything. You can simply use the call_service action on the controller's system object to call the notify.alexa_media service (or its variants, more on that below). If you do it through the system entity, you don't need to make exceptions in your local configuration to add the service -- you can run a service against any entity from the system entity, and if it's not supported, the (Hass) entity will either ignore it or log an error, but nobody dies, missiles do not launch, gravity still works, the sun continues to rise and set, etc.

              2ffaac01-0768-430b-bd18-8d2c6056831a-image.png

              Above are two different versions of the service call that do about the same thing. I'll work backwards because that's the way I figured it out...

              The green-circled "short" version of the service name requires that you specify the target in the service data. The service data is a structure as shown (always). Also see the docs for the component for more info about this service and its data. The target field must be specified when using this short form of the service name, and its value is an array of HomeAssistant entity IDs (not Reactor entity IDs) for the players (Dots and Echos) that will speak the phrase. The data substructure must be given as shown.

              The red-circled variant uses a longer service name that includes the Amazon device's name. Apparently the component creates a set of aliased services, each with the device name appended to the base service name. I find this annoying, because I have over a dozen Dots/Echos, so and it creates a bunch of data pollution. But, it's there, and it's usable. When you use a "long" service name, you don't need to specify target in the data, but it's otherwise the same, as shown.

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

              @toggledbits That's great news! My only problem is that my Hass entity don't have any actions... :
              1580fec2-cbbb-45a3-b434-c4fe00eeb03d-image.png I don't know how you activated the x_hass_system.call_service?

              Do I have to change anything in my reactor.yaml?

                - id: hass
                  enabled: true
                  implementation: HassController
                  name: Home Assistant
                  config:
                    source: 'wss://f_______'
                    access_token: "eyJ0eXAi_______________________________________________________________________________________________________________________________2-nLoI369-iYcJf9z_3sviSiWA"
                    #
                    # ignore_cert - If true, suppresses certificate validation when using wss:// (Websocket
                    #               with SSL/TLS) and thus allows a self-signed certificate to be used on
                    #               the Hass system.
                    #ignore_cert: false
                    #
                    # dump_all_states - This is for troubleshooting. Do not enable unless asked.
                    #dump_all_states: false
                    log_events: false
              
              toggledbitsT 1 Reply Last reply
              0
              • F Fanan

                @toggledbits That's great news! My only problem is that my Hass entity don't have any actions... :
                1580fec2-cbbb-45a3-b434-c4fe00eeb03d-image.png I don't know how you activated the x_hass_system.call_service?

                Do I have to change anything in my reactor.yaml?

                  - id: hass
                    enabled: true
                    implementation: HassController
                    name: Home Assistant
                    config:
                      source: 'wss://f_______'
                      access_token: "eyJ0eXAi_______________________________________________________________________________________________________________________________2-nLoI369-iYcJf9z_3sviSiWA"
                      #
                      # ignore_cert - If true, suppresses certificate validation when using wss:// (Websocket
                      #               with SSL/TLS) and thus allows a self-signed certificate to be used on
                      #               the Hass system.
                      #ignore_cert: false
                      #
                      # dump_all_states - This is for troubleshooting. Do not enable unless asked.
                      #dump_all_states: false
                      log_events: false
                
                toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by toggledbits
                #24

                @fanan That's not the system entity. It's probably named "Home Assistant" based on your configuration, and you can also filter by the sys_system capability.

                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

                  @fanan That's not the system entity. It's probably named "Home Assistant" based on your configuration, and you can also filter by the sys_system capability.

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

                  @toggledbits Ahh..! I see it now. Thanks! I'm struggeling with the indentation, but I guess it will come around after a few tries... 🙂
                  The best of all is as you so well put it: "...and if it's not supported, the (Hass) entity will either ignore it or log an error, but nobody dies, missiles do not launch, gravity still works, the sun continues to rise and set, etc."
                  Even Shakespeare him self would be impressed!

                  1 Reply Last reply
                  0
                  • F Fanan marked this topic as a question on
                  • F Fanan has marked this topic as solved on
                  • W Offline
                    W Offline
                    whyfseeguy
                    wrote on last edited by
                    #26

                    What did I do wrong?

                    The service works in HA scripts but not in Reactor
                    cf98e30f-bc95-4b3c-8e3f-60ea0d96d470-image.png

                    toggledbitsT 1 Reply Last reply
                    0
                    • W whyfseeguy

                      What did I do wrong?

                      The service works in HA scripts but not in Reactor
                      cf98e30f-bc95-4b3c-8e3f-60ea0d96d470-image.png

                      toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by
                      #27

                      @whyfseeguy said in TTS in MSR?:

                      What did I do wrong?

                      Well, you didn't post what the action logged. Did you look?

                      Off the top of my head looking at it, you've wrapped data in data. I think you just need it to be:

                      {
                          "entity_id": "media_player.media_room_tv",
                          "message": "hello there"
                      }
                      

                      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
                      • W Offline
                        W Offline
                        whyfseeguy
                        wrote on last edited by
                        #28

                        It is working now with your recipe. I had too many "data" in data field. I was following the examples above and got confused.

                        1 Reply Last reply
                        1
                        • toggledbitsT toggledbits referenced this topic on
                        • toggledbitsT toggledbits

                          @fanan OK. So it turns out that this has (much) more to do with the way the Alexa Media Player service works than anything. You can simply use the call_service action on the controller's system object to call the notify.alexa_media service (or its variants, more on that below). If you do it through the system entity, you don't need to make exceptions in your local configuration to add the service -- you can run a service against any entity from the system entity, and if it's not supported, the (Hass) entity will either ignore it or log an error, but nobody dies, missiles do not launch, gravity still works, the sun continues to rise and set, etc.

                          2ffaac01-0768-430b-bd18-8d2c6056831a-image.png

                          Above are two different versions of the service call that do about the same thing. I'll work backwards because that's the way I figured it out...

                          The green-circled "short" version of the service name requires that you specify the target in the service data. The service data is a structure as shown (always). Also see the docs for the component for more info about this service and its data. The target field must be specified when using this short form of the service name, and its value is an array of HomeAssistant entity IDs (not Reactor entity IDs) for the players (Dots and Echos) that will speak the phrase. The data substructure must be given as shown.

                          The red-circled variant uses a longer service name that includes the Amazon device's name. Apparently the component creates a set of aliased services, each with the device name appended to the base service name. I find this annoying, because I have over a dozen Dots/Echos, so and it creates a bunch of data pollution. But, it's there, and it's usable. When you use a "long" service name, you don't need to specify target in the data, but it's otherwise the same, as shown.

                          T Offline
                          T Offline
                          tbully
                          wrote on last edited by
                          #29

                          This thread has been super helpful. I have a few questions that are somewhat related:

                          1. Similar to @therealdb 's request. Is there a way to call this from the Alexa entity vs. a "call service" from the controller entity? I tried adding the TTS service but it's still not showing up under the entity. (see below - ignore multiple entries - was trying a few formats of the name)
                          2. In the service call, is there a way to make the announcement at a certain volume? Even better if it could snap back. You can see I'm setting the volume, delaying, and then announcing but was wondering if someone has a more elegant solution.

                          I realize this isn't all an MSR issue (much more HASS) but thought there are good minds here that may be able to help. Thanks.

                          9c294515-42be-4e95-84e6-6fd2b948980f-image.png

                          8f350c35-979b-4ef3-81e1-64796d65032d-image.png

                          T 1 Reply Last reply
                          0
                          • T tbully

                            This thread has been super helpful. I have a few questions that are somewhat related:

                            1. Similar to @therealdb 's request. Is there a way to call this from the Alexa entity vs. a "call service" from the controller entity? I tried adding the TTS service but it's still not showing up under the entity. (see below - ignore multiple entries - was trying a few formats of the name)
                            2. In the service call, is there a way to make the announcement at a certain volume? Even better if it could snap back. You can see I'm setting the volume, delaying, and then announcing but was wondering if someone has a more elegant solution.

                            I realize this isn't all an MSR issue (much more HASS) but thought there are good minds here that may be able to help. Thanks.

                            9c294515-42be-4e95-84e6-6fd2b948980f-image.png

                            8f350c35-979b-4ef3-81e1-64796d65032d-image.png

                            T Offline
                            T Offline
                            tbully
                            wrote on last edited by
                            #30

                            Here's everything from the entity page:

                            av_repeat.repeat_mode="unknown"
                            av_repeat.shuffle=null
                            av_transport.album_art=null
                            av_transport.current_album=null
                            av_transport.current_artist=null
                            av_transport.current_title=null
                            av_transport.current_track=null
                            av_transport.state="standby"
                            muting.state=false
                            power_switch.state=true
                            volume.level=0.15
                            x_hass.domain="media_player"
                            x_hass.entity_id="media_player.office_echo"
                            x_hass.services=["media_player"]
                            x_hass.state="standby"
                            x_hass_attr.available=true
                            x_hass_attr.bluetooth_list=[]
                            x_hass_attr.connected_bluetooth=null
                            x_hass_attr.friendly_name="Office Echo"
                            x_hass_attr.is_volume_muted=false
                            x_hass_attr.last_called=true
                            x_hass_attr.last_called_summary=""
                            x_hass_attr.last_called_timestamp=1660318076357
                            x_hass_attr.media_content_type="standby"
                            x_hass_attr.media_position_updated_at="2022-08-12T16:05:58.870619+00:00"
                            x_hass_attr.source="Local Speaker"
                            x_hass_attr.source_list=["Local Speaker"]
                            x_hass_attr.supported_features=56253
                            x_hass_attr.volume_level=0.15
                            Capabilities: av_repeat, av_transport, media_navigation, muting, power_switch, toggle, volume, x_hass, x_hass_media_player
                            Actions: av_repeat.repeat_all, av_repeat.repeat_off, av_repeat.repeat_one, av_repeat.set_repeat, av_repeat.set_shuffle, av_repeat.shuffle_off, av_repeat.shuffle_on, av_transport.fast_forward, av_transport.pause, av_transport.play, av_transport.rewind, av_transport.stop, media_navigation.next_chapter, media_navigation.next_media, media_navigation.next_track, media_navigation.previous_chapter, media_navigation.previous_media, media_navigation.previous_track, muting.mute, muting.set, muting.toggle, muting.unmute, power_switch.off, power_switch.on, power_switch.set, toggle.toggle, volume.decrease, volume.increase, volume.relative, volume.set, volume.set_db, x_hass_media_player.clear_playlist, x_hass_media_player.join, x_hass_media_player.media_next_track, x_hass_media_player.media_pause, x_hass_media_player.media_play, x_hass_media_player.media_play_pause, x_hass_media_player.media_previous_track, x_hass_media_player.media_seek, x_hass_media_player.media_stop, x_hass_media_player.play_media, x_hass_media_player.repeat_set, x_hass_media_player.select_sound_mode, x_hass_media_player.select_source, x_hass_media_player.shuffle_set, x_hass_media_player.toggle, x_hass_media_player.turn_off, x_hass_media_player.turn_on, x_hass_media_player.unjoin, x_hass_media_player.volume_down, x_hass_media_player.volume_mute, x_hass_media_player.volume_set, x_hass_media_player.volume_up
                            

                            df96e3dd-01bf-4718-a3f4-255706ec260b-image.png

                            1 Reply Last reply
                            0
                            • N Offline
                              N Offline
                              noelab
                              wrote on last edited by
                              #31

                              Hi, just playing around this topic with Alexa and I share it:
                              Example that works:

                              image.png

                              image.png

                              Still no lucky to play with "random" announce.
                              This example not work:

                              image.png

                              image.png

                              -Reactor (Multi-hub) 25082-3c348de6
                              -Docker on Synology NAS
                              -Ezlo firmware version 2.0.59.2471.8
                              -HASS Docker 2025.2.5
                              -ZWaveJSUI 10.1.3
                              -Update 30/03/2025

                              therealdbT 1 Reply Last reply
                              0
                              • N noelab

                                Hi, just playing around this topic with Alexa and I share it:
                                Example that works:

                                image.png

                                image.png

                                Still no lucky to play with "random" announce.
                                This example not work:

                                image.png

                                image.png

                                therealdbT Offline
                                therealdbT Offline
                                therealdb
                                wrote on last edited by toggledbits
                                #32

                                @noelab ciao! I randomize them in Reactor. Just use this:

                                messages[ floor( random() * len( messages) )

                                where messages is a local variable like this:

                                [
                                "Bentornato a casa",
                                "Casa, dolce casa!",
                                "Ciao!",
                                ]
                                

                                --
                                On a mission to automate everything.

                                My MS Reactor contrib
                                My Luup Plug-ins

                                N 1 Reply Last reply
                                0
                                • therealdbT therealdb

                                  @noelab ciao! I randomize them in Reactor. Just use this:

                                  messages[ floor( random() * len( messages) )

                                  where messages is a local variable like this:

                                  [
                                  "Bentornato a casa",
                                  "Casa, dolce casa!",
                                  "Ciao!",
                                  ]
                                  
                                  N Offline
                                  N Offline
                                  noelab
                                  wrote on last edited by
                                  #33

                                  @therealdb said in TTS in MSR?:

                                  [
                                  "Bentornato a casa",
                                  "Casa, dolce casa!",
                                  "Ciao!",
                                  ]

                                  Grazie! and thanks to @toggledbits for the new dark theme, also my eyes are happy!

                                  -Reactor (Multi-hub) 25082-3c348de6
                                  -Docker on Synology NAS
                                  -Ezlo firmware version 2.0.59.2471.8
                                  -HASS Docker 2025.2.5
                                  -ZWaveJSUI 10.1.3
                                  -Update 30/03/2025

                                  1 Reply Last reply
                                  0
                                  • toggledbitsT toggledbits unlocked this topic on
                                  • toggledbitsT toggledbits locked this topic on
                                  Reply
                                  • Reply as topic
                                  Log in to reply
                                  • Oldest to Newest
                                  • Newest to Oldest
                                  • Most Votes


                                  Recent Topics

                                  • Caution: zwave-js-ui docker 11.4.0 is broken
                                    toggledbitsT
                                    toggledbits
                                    0
                                    2
                                    11

                                  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                                    toggledbitsT
                                    toggledbits
                                    0
                                    68
                                    4.8k

                                  • Shelly Wall Display XL
                                    therealdbT
                                    therealdb
                                    2
                                    6
                                    83

                                  • Handling Dead Entities and Renamed Entities
                                    PablaP
                                    Pabla
                                    0
                                    5
                                    69

                                  • Strange behavior for MQTT templates using payload and attributes
                                    toggledbitsT
                                    toggledbits
                                    0
                                    6
                                    127

                                  • [MSR] reactor-mqtt-contrib package for additional MQTT templates
                                    therealdbT
                                    therealdb
                                    1
                                    46
                                    8.2k

                                  • HA 2025.9.4 Supported Yet?
                                    toggledbitsT
                                    toggledbits
                                    0
                                    2
                                    85

                                  • The reaction stopped working (Google Nest max playing a video)
                                    toggledbitsT
                                    toggledbits
                                    0
                                    7
                                    351

                                  • Rule Set UI bug - RESOLVED
                                    toggledbitsT
                                    toggledbits
                                    1
                                    2
                                    231

                                  • [Reactor] Copy&Paste of Rules
                                    therealdbT
                                    therealdb
                                    0
                                    1
                                    299

                                  • [Reactor] Help with screne controller cycling logic
                                    toggledbitsT
                                    toggledbits
                                    0
                                    5
                                    401

                                  • Stop the MSR by an external switch on Hubitat.
                                    Tom_DT
                                    Tom_D
                                    0
                                    6
                                    735
                                  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