Multi-System Reactor

705 Topics 7.0k Posts
  • Installing build 0.1-21089

    Locked
    5
    0 Votes
    5 Posts
    166 Views

    @toggledbits ok, I thought I did that, but maybe I don't remember correctly. Not a Linux expert... yet! I am now up and running 🙂

  • TimeStamp variable in MSR

    Locked
    4
    0 Votes
    4 Posts
    153 Views

    Thanks for the quick response! I'm going to try to use it in my logic

  • Status Tab Preview

    Locked
    20
    2 Votes
    20 Posts
    495 Views

    Also, so as to minimize the number of "SET" (but otherwise inactive) Rules, I decided to change all of my

    [ Entity Attribute ] [ X ] [ is FALSE] // remains true indefinitely when OFF

    to

    [ Entity Attribute ] [ X ] [ changes ] [ (any) ] to [ FALSE ] // only true briefly when turned OFF

    Dunno if I'm OCD or just didn't want Status implying that something was "going on" when it's not. 🙂

  • This topic is deleted!

    Locked
    40
    0 Votes
    40 Posts
    123 Views
  • Parsing an expression

    Locked
    8
    0 Votes
    8 Posts
    214 Views

    Thanks guys, this worked just like I needed it to.

  • FEATURE REQUEST: URL Maker in 'Tools'

    Locked
    5
    1 Votes
    5 Posts
    169 Views

    @cw-kid said in FEATURE REQUEST: URL Maker in 'Tools':

    This website has a URL creator for Vera.

    interestingly they have several other HTTP link creators for other controllers at that site.

  • 0 Votes
    32 Posts
    693 Views

    You only care about what's in the "Device_Num_699" section of the file. You can "pretty up" the format in jsonlint.com, and if you look at that section, you'll find Armed is in there, state ID 621 at the very end of the states array.

    }, { "id": 621, "service": "urn:micasaverde-com:serviceId:SecuritySensor1", "variable": "Armed", "value": "0" }],

    The other devices are in the alerts section of the response, which isn't relevant to our work here.

  • 0 Votes
    18 Posts
    401 Views

    On my end I'll tighten up the UI so that option can't be selected when the changes operator is used.

  • Vera Run LUA Missing

    Locked
    10
    1 Votes
    10 Posts
    277 Views

    Appears to be fixed in version 21090. I can now see and select x_vera_sys.runlua on both Vera controllers.

    Thanks

  • 0 Votes
    8 Posts
    216 Views

    @cw-kid said in Can MSR be connected to more than one Vera controller?:

    @librasun

    Not heard of this Apilio thing before.

    So its like IFTTT for connecting unrelated HA devices and services ?

    Yes. They have provisions for logic flow, variable storage (and computation), triggers, etc. It's an IFTTT competitor in the same way Stringify once was. Apilio lets you interface with Tuya, LG, IFTTT (which interoperates rather deeply with Apilio), Webhooks, SmartThings, all the big guns.

    It's a paid service but cheap, under $1/mo. for a middle tier account.

  • 0 Votes
    1 Posts
    79 Views
    No one has replied
  • 0 Votes
    34 Posts
    952 Views

    Thanks for the added clarity. I plan to refactor some of my Rules accordingly.

  • updates as operator is missing in MSR

    Locked
    3
    0 Votes
    3 Posts
    114 Views

    I have set change as operator and left the input field empty. This also works. Thanks for the reply.

  • 0 Votes
    2 Posts
    98 Views

    I bumped into the inverse of that problem when I accidentally caused several devices to be removed from my Vera Plus. While MSR was happy to carry on as if nothing had happened (which I suppose could have been ruinous to my overall workflow, had I not intervened!), the truth was that Vera assigned all new Dev#s to those child devices once they reappeared to her.

    The only thing that saved my bacon in the process was being able to leverage MSR's memory of the old Dev#s, so I could systematically go change them back under Device > Advanced > Parameters > id, one by one. Took a while, caused uncountable Luup engine restarts, but honestly worth it in the end.

    How do you think MSR ought to handle future renaming events? I'm sure @toggledbits welcomes your suggestions. For starters:

    Should MSR gracefully detect the new controller name assignment from reactor.yaml and propagate that change to all Rules? Should controller renaming be done instead through a purpose-built 'Tool' inside MSR that handles such modifications? Should controller enumeration be abstracted one further level so they are referenced by, say, S/N behind the scenes?

    Glad you were able to reverse the change without losing your hard work!

  • Random off delay in MSR

    Locked
    3
    0 Votes
    3 Posts
    146 Views

    Thanks for quick response !

  • system capability zwave_scene_controller

    Locked
    46
    0 Votes
    46 Posts
    2k Views

    Thanks for the quick response. It works!

  • Expression value trigger not working ?

    Locked
    5
    1 Votes
    5 Posts
    132 Views

    I just edited the rule and ticked "ignore case" again and saved and the rule is still working and triggering, so that was a red herring as you say.

  • Using Google Forms to Store Data from MSR

    Locked
    2
    0 Votes
    2 Posts
    160 Views

    STEP 1: Create the Form

    Visit drive.google.com and click NEW > Form Give your Form a title and populate it with one or more "Questions" of type "Short Answer". I will refer to the question titles as Field A, FIeld B, etc. for brevity, but you can modify them to suit your purposes. Click SETTINGS and choose "Save Responses to > New Spreadsheet" (it will be automatically created in Drive) Optional: Turn on email notifications for each SUBMIT

    STEP 2: Generate the GET URL

    Click Preview ('eye' icon) to open completed live Form Copy-and-paste (into a text editor, like Notepad) the Form URL (ends with /viewform) Press F12 (in Chrome) and click Network pane Fill out Form with sample data and click SUBMIT Click formResponse in left column of Network pane With Headers highlighted, scroll down to FORM DATA Copy (into text editor) each field name of the form entry.1234567 in order Replace the /viewform in Form URL with /formResponse
    NOTE: This will serve as your GET base URL in Step 3.

    STEP 3: Prepare a Rule in MSR

    Create or Edit a Rule in MSR Add new blank Expressions of the form fieldA, fieldB, etc., one for each question appearing on your Form. Add the Expression getURL and paste in the modified URL from Step 2, surrounded by double quotes. Add the Expression getData and type the following formula: "?entry.1234567=" + fieldA + "&entry.7654321=" + fieldB (continuing as needed for all X fields)

    STEP 4: Send your data

    Add to Set Reaction as many [Set Variable] actions as needed to store future values in fieldA, fieldB, etc. (and/or pre-populate some Expressions with numbers or text now). Add an [HTTP Request] action in Set Reaction. Populate its "Request URL" field with ${{ getURL + getData }} SAVE and EXIT When triggered, the Rule will invisibly post the current field values to a new row of the assigned spreadsheet, using the Google Form.

    STEP 5: Review your data

    To view the stored values, simply open the receiving Spreadsheet and examine its FormResponses tab. Columns will be named Timestamp, Field A, Field B, etc. The timestamps in column A reflect when MSR posted data. You can easily use this data to generate graphs, add columns to calculate complex formulae, export as a .CSV file, etc.

    Enjoy! I may one day (in the distant future) post a follow-up tutorial on extracting values from Google Sheets for use in MSR. For now, I hope this serves as a fun, makeshift and FREE database for storing your important data directly from MSR.

  • 0 Votes
    14 Posts
    562 Views

    @toggledbits. My HA installation is on a VM (VirtualBox) on Windows 10. That shouldn't be problem I guess?

  • 0 Votes
    1 Posts
    70 Views
    No one has replied

Recent Topics