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?
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor

TTS in MSR?

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

                      • How to upgrade from an old version of MSR?
                        cw-kidC
                        cw-kid
                        0
                        1
                        1

                      • Access control - allowing anonymous user to dashboard
                        toggledbitsT
                        toggledbits
                        0
                        2
                        57

                      • VEC Virtual Switch Auto Off
                        S
                        SweetGenius
                        1
                        1
                        48

                      • Upcoming Storage Change -- Got Back-ups?
                        toggledbitsT
                        toggledbits
                        2
                        1
                        38

                      • Oddness in Copy/Move of Reactions
                        G
                        gwp1
                        0
                        1
                        68

                      • [Solved] function isRuleEnabled() issue
                        CrilleC
                        Crille
                        0
                        4
                        106

                      • [Reactor] Problem with Global Reactions and groups
                        therealdbT
                        therealdb
                        0
                        3
                        118

                      • Possible feature request 2?
                        CatmanV2C
                        CatmanV2
                        0
                        3
                        89

                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        133
                        80.2k

                      • Genuinely impressed with Zigbee and HA / Reactor
                        CatmanV2C
                        CatmanV2
                        1
                        9
                        397

                      • Copying a global reaction
                        toggledbitsT
                        toggledbits
                        0
                        3
                        122

                      • [HowTo] Using HABridge with Reactor
                        CatmanV2C
                        CatmanV2
                        0
                        9
                        460
                      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