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. Reactor not showing full vera device parameters
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
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
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
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
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

Reactor not showing full vera device parameters

Scheduled Pinned Locked Moved Multi-System Reactor
13 Posts 3 Posters 693 Views 3 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
    #4

    Unfortunately I can't see your screen shots, they're too small (basically same size as thumbnail when reading, for whatever reason). But that's probably not useful or conclusive anyway. I would look at the attributes listed for the entities in the Entities list. VeraController just copies whatever it gets for state variables from the Vera to extended attributes, so if they are not listed there, it seems they may not be coming over for whatever reason, or there was an error trying to process them for some reason (I assume you looked in the logs for errors and didn't mention any because you didn't find any? They would occur during the initialization phase after startup). You can also check the vera-user_data-initial.json and vera-status-initial.json files to see exactly what the Vera sent to Reactor for states. They should be listed 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
    • T Offline
      T Offline
      Talisker
      wrote on last edited by
      #5

      Please find my responses below. I fear you may be frustraited by my lack of knowlege but I have done my best based on your guidance. I am not able to upload the logs. Do you need these?

      Sorry about the thumbnail screen shots - I could not find a better way to capture them!

      'I would look at the attributes listed for the entities in the Entities list.' So the unreadable thumbnail images showed that the expected entities for the two new vera multistring devices are not available in Reactor.

      I have looked at the vera logs (http://192.168.XX.XXX/cgi-bin/cmh/log.sh?Device=LuaUPnP after a luup reload. If I search for the two new multistring devices (1056 & 1057) the entries looked quite normal compared to the log entries for similar devices. So I assume no vera error?

      I have looked at the two Reactor logs (vera-user_data-initial.json and vera-status-initial.json files) again, comparing the entries for 1056 and 1057 against other devices, the respective lines don't seem out of place. All entities are listed for the two multistring devices.

      Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

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

        Entities are (in effect) devices. Attributes are values (like state variables on a device). It sounds like you're missing attributes. The logs I want you to look at are the Reactor logs.

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

        T 1 Reply Last reply
        0
        • MikeReadingtonM Offline
          MikeReadingtonM Offline
          MikeReadington
          wrote on last edited by
          #7

          Hi Patrick,

          I don't know if this might be related, but I just saw something strange with a missing attribute as well. It looks like after the last update the Schlage lock attribute on Vera systems lost:

          x_vera_svc_micasaverde_com_DoorLock1.sl_UserCode_updated

          (missing) is after it when looking in rule>entities>triggers.

          Something just came up at work as I was writing this, so I'll look through the logs when I am freed up.

          1 Reply Last reply
          0
          • MikeReadingtonM Offline
            MikeReadingtonM Offline
            MikeReadington
            wrote on last edited by
            #8

            False alarm with both work and MSR. I went back to look and it cleared up on it's own.

            1 Reply Last reply
            0
            • toggledbitsT toggledbits

              Entities are (in effect) devices. Attributes are values (like state variables on a device). It sounds like you're missing attributes. The logs I want you to look at are the Reactor logs.

              T Offline
              T Offline
              Talisker
              wrote on last edited by
              #9

              @toggledbits it appears that I used the wrong terminology. I have looked at the two Reactor logs (vera-user_data-initial.json and vera-status-initial.json files) again, comparing the attributes for 1056 and 1057 against other devices, the respective attributes don't seem out of place. All attributes are listed for the two multistring devices (or should I say they appear to be listed). See below for device 1056. Does this confirm that the attributes for the two new entities (devices) are being read correctly by reactor?

              vera-status-initial.json

              {
              "id": 1056,
              "states": [
              {
              "id": 334,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName1",
              "value": "Y'day Gas kWh"
              },
              {
              "id": 335,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable1",
              "value": "99"
              },
              {
              "id": 336,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName2",
              "value": "V2"
              },
              {
              "id": 337,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable2",
              "value": "0"
              },
              {
              "id": 338,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName3",
              "value": "V3"
              },
              {
              "id": 339,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable3",
              "value": "0"
              },
              {
              "id": 340,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName4",
              "value": "V4"
              },
              {
              "id": 341,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable4",
              "value": "0"
              },
              {
              "id": 342,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName5",
              "value": "V5"
              },
              {
              "id": 343,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable5",
              "value": "0"
              },
              {
              "id": 344,
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Options",
              "value": ""
              },
              {
              "id": 345,
              "service": "urn:micasaverde-com:serviceId:HaDevice1",
              "variable": "Configured",
              "value": "0"
              }

              vera-user_data-initial.json:

              {
              "id": 1056,
              "device_type": "urn:schemas-upnp-org:device:VContainer:1",
              "id_parent": 0,
              "embedded": 0,
              "disabled": 0,
              "device_file": "D_MString.xml",
              "manufacturer": "",
              "model": "",
              "altid": "",
              "ip": "",
              "mac": "",
              "time_created": "1662320801",
              "plugin": "8231",
              "states": [
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName1",
              "value": "Y'day Gas kWh",
              "id": 0
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable1",
              "value": "99",
              "id": 1
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName2",
              "value": "V2",
              "id": 2
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable2",
              "value": "0",
              "id": 3
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName3",
              "value": "V3",
              "id": 4
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable3",
              "value": "0",
              "id": 5
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName4",
              "value": "V4",
              "id": 6
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable4",
              "value": "0",
              "id": 7
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "VariableName5",
              "value": "V5",
              "id": 8
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Variable5",
              "value": "0",
              "id": 9
              },
              {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "variable": "Options",
              "value": "",
              "id": 10
              }
              ],
              "impl_file": "I_MString.xml",
              "ControlURLs": {
              "service_514": {
              "service": "urn:upnp-org:serviceId:VContainer1",
              "ControlURL": "/upnp/control/dev_514",
              "EventURL": "/upnp/event/dev_514",
              "serviceType": "urn:schemas-upnp-org:service:VContainer:1"
              }
              },
              "device_json": "D_MString.json",
              "name": "Gas_Params",
              "room": "11",
              "local_udn": "uuid:4d494342-5342-5645-0420-000002fc93e7"
              },

              Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

              T 1 Reply Last reply
              0
              • T Talisker

                Please find my responses below. I fear you may be frustraited by my lack of knowlege but I have done my best based on your guidance. I am not able to upload the logs. Do you need these?

                Sorry about the thumbnail screen shots - I could not find a better way to capture them!

                'I would look at the attributes listed for the entities in the Entities list.' So the unreadable thumbnail images showed that the expected entities for the two new vera multistring devices are not available in Reactor.

                I have looked at the vera logs (http://192.168.XX.XXX/cgi-bin/cmh/log.sh?Device=LuaUPnP after a luup reload. If I search for the two new multistring devices (1056 & 1057) the entries looked quite normal compared to the log entries for similar devices. So I assume no vera error?

                I have looked at the two Reactor logs (vera-user_data-initial.json and vera-status-initial.json files) again, comparing the entries for 1056 and 1057 against other devices, the respective lines don't seem out of place. All entities are listed for the two multistring devices.

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

                OK. But in all your screen shots, you are showing actions not state variables or conditions trying to use state variables. The state variables will not be listed in actions. You're mixing up so much terminology that I'm not sure of what you're looking for or what you're trying to do.

                Maybe a good start would be to have you review the Concepts and Terminology page of the documentation, then try to describe again what you are trying to do and what you are not getting that you expect. I'm lost.

                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
                • T Talisker

                  @toggledbits it appears that I used the wrong terminology. I have looked at the two Reactor logs (vera-user_data-initial.json and vera-status-initial.json files) again, comparing the attributes for 1056 and 1057 against other devices, the respective attributes don't seem out of place. All attributes are listed for the two multistring devices (or should I say they appear to be listed). See below for device 1056. Does this confirm that the attributes for the two new entities (devices) are being read correctly by reactor?

                  vera-status-initial.json

                  {
                  "id": 1056,
                  "states": [
                  {
                  "id": 334,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName1",
                  "value": "Y'day Gas kWh"
                  },
                  {
                  "id": 335,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable1",
                  "value": "99"
                  },
                  {
                  "id": 336,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName2",
                  "value": "V2"
                  },
                  {
                  "id": 337,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable2",
                  "value": "0"
                  },
                  {
                  "id": 338,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName3",
                  "value": "V3"
                  },
                  {
                  "id": 339,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable3",
                  "value": "0"
                  },
                  {
                  "id": 340,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName4",
                  "value": "V4"
                  },
                  {
                  "id": 341,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable4",
                  "value": "0"
                  },
                  {
                  "id": 342,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName5",
                  "value": "V5"
                  },
                  {
                  "id": 343,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable5",
                  "value": "0"
                  },
                  {
                  "id": 344,
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Options",
                  "value": ""
                  },
                  {
                  "id": 345,
                  "service": "urn:micasaverde-com:serviceId:HaDevice1",
                  "variable": "Configured",
                  "value": "0"
                  }

                  vera-user_data-initial.json:

                  {
                  "id": 1056,
                  "device_type": "urn:schemas-upnp-org:device:VContainer:1",
                  "id_parent": 0,
                  "embedded": 0,
                  "disabled": 0,
                  "device_file": "D_MString.xml",
                  "manufacturer": "",
                  "model": "",
                  "altid": "",
                  "ip": "",
                  "mac": "",
                  "time_created": "1662320801",
                  "plugin": "8231",
                  "states": [
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName1",
                  "value": "Y'day Gas kWh",
                  "id": 0
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable1",
                  "value": "99",
                  "id": 1
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName2",
                  "value": "V2",
                  "id": 2
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable2",
                  "value": "0",
                  "id": 3
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName3",
                  "value": "V3",
                  "id": 4
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable3",
                  "value": "0",
                  "id": 5
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName4",
                  "value": "V4",
                  "id": 6
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable4",
                  "value": "0",
                  "id": 7
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "VariableName5",
                  "value": "V5",
                  "id": 8
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Variable5",
                  "value": "0",
                  "id": 9
                  },
                  {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "variable": "Options",
                  "value": "",
                  "id": 10
                  }
                  ],
                  "impl_file": "I_MString.xml",
                  "ControlURLs": {
                  "service_514": {
                  "service": "urn:upnp-org:serviceId:VContainer1",
                  "ControlURL": "/upnp/control/dev_514",
                  "EventURL": "/upnp/event/dev_514",
                  "serviceType": "urn:schemas-upnp-org:service:VContainer:1"
                  }
                  },
                  "device_json": "D_MString.json",
                  "name": "Gas_Params",
                  "room": "11",
                  "local_udn": "uuid:4d494342-5342-5645-0420-000002fc93e7"
                  },

                  T Offline
                  T Offline
                  Talisker
                  wrote on last edited by
                  #11

                  I have a number of rules which using entity actions I write values into multistring devices in my vera plus. Below is an example of how I do this in Reactor:

                  Untitled.png

                  If I add a new multistring device in my vera plus I cannot set the device variables as I can with 'old' multistring devices. The below screen shot shows that the same drop down menu options in reactor for the new multistring device are not present as they are for the old device above:

                  Untitled.png

                  If I look at the reactor entities for an old multistring entity (device #887) and a newly created multistring entity (device number '1056) I can spot a difference as per the screen shot below. I guess my question is 'why are the available actions not listed for new multistring devices (entities))?

                  Capture.JPG

                  Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

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

                    OK. I'm seeing some clarity now.

                    It looks like Gas Params may be misconfigured on the Vera. I would compare the settings in the control panel Advanced > Params for device 887 and 1056 and see if you spot a difference. If I had to guess, I'd say that the name of the device_file is incorrect on 1056. I don't know how you create new devices in MultiString, since I don't use the thing, but it seems it went wrong at that step.

                    Edit: if they seem identical, then it's possible that VeraController received an update while the device was being created, and it was in an intermediate state (there's no way for VeraController to know). Try deleting the entity in Reactor using the DELETE button in the entity detail (in the entity on the Entities page). Then restart Reactor and let it recreate the entity from scratch (you'll need to hard refresh your browser as well).

                    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
                    • T Offline
                      T Offline
                      Talisker
                      wrote on last edited by
                      #13

                      So, I have found my missing parameters! They appeared following a reactor update. Perhaps next time I add new vera devices, I should stop reactor and re-start it after I have added the new devices and things have settled down. Anyhow, thanks again for your assitance Patrick.

                      Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

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


                      Recent Topics

                      • Gradually turn on lights.
                        G
                        gwp1
                        0
                        4
                        93

                      • Stop the MSR by an external switch on Hubitat.
                        wmarcolinW
                        wmarcolin
                        0
                        1
                        16

                      • Error After Upgrade
                        G
                        gwp1
                        0
                        4
                        84

                      • Reset attribute value of entity in event handler
                        R
                        RHCPNG
                        0
                        5
                        170

                      • Need help figuring out how to delay a reset on reaction
                        G
                        gwp1
                        0
                        22
                        858

                      • Way to search for rules (rule state) in other rules
                        T
                        tamorgen
                        0
                        3
                        91

                      • Links to MSR from HA
                        Tom_DT
                        Tom_D
                        0
                        1
                        77

                      • Set Reaction > Script Action
                        wmarcolinW
                        wmarcolin
                        0
                        11
                        416

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

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

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

                      • Advice reqeusted to migrate MSR from Bare Metal to Container
                        T
                        tamorgen
                        0
                        5
                        246
                      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