Skip to content

Multi-System Reactor

791 Topics 7.5k Posts
  • Random off delay in MSR

    Locked
    3
    1
    0 Votes
    3 Posts
    257 Views
    E
    Thanks for quick response !
  • system capability zwave_scene_controller

    Locked
    46
    0 Votes
    46 Posts
    5k Views
    E
    Thanks for the quick response. It works!
  • Expression value trigger not working ?

    Locked
    5
    1
    1 Votes
    5 Posts
    310 Views
    cw-kidC
    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
    300 Views
    LibraSunL
    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.
  • Home Assistant, ReferenceError: auth is not defined

    Locked
    14
    0 Votes
    14 Posts
    913 Views
    F
    @toggledbits. My HA installation is on a VM (VirtualBox) on Windows 10. That shouldn't be problem I guess?
  • PR #0000137: Expression Value Condition - Comparison not working

    Locked
    1
    0 Votes
    1 Posts
    118 Views
    No one has replied
  • New to MSR, my observations

    Locked
    1
    0 Votes
    1 Posts
    137 Views
    No one has replied
  • Hubitat and MSR

    Locked
    3
    0 Votes
    3 Posts
    260 Views
    S
    I Understand, Thanks
  • Preview of Multi-System Reactor

    Locked Moved
    58
    2 Votes
    58 Posts
    5k Views
    toggledbitsT
    There is currently no limit on the response size, but it's probably going to get one in similar fashion to RFV. I think it's time to close this thread and start encouraging new threads for new topics. I think this thread accomplished its mission and now seems to be meandering a bit.
  • MSR Interface Remotely?

    Locked
    17
    0 Votes
    17 Posts
    938 Views
    LibraSunL
    I failed to mention that I was thinking of this in the context of you potentially creating a paid service whereby MSR users could login remotely without steering those dollars toward established services. I'm sure that's just a pipe dream but I'm all about potential revenue sources for guys who deserve to reap the reward of their hard labor.
  • Playing playlist in Sonos

    Locked
    3
    1
    0 Votes
    3 Posts
    238 Views
    MatohlM
    Yes, you are right. I figured it out. It should be InstanceID: 0
  • MSR on Synology without Docker

    Locked
    4
    0 Votes
    4 Posts
    298 Views
    tunnusT
    @kfxo said in MSR on Synology without Docker: I am using virtual machine manager on synology to host a Debian 10 VM. Works well. Neither Docker nor virtual machine manager is supported, so I guess I just have to jump in and test...
  • MSR Backup

    Locked
    14
    0 Votes
    14 Posts
    745 Views
    therealdbT
    @cw-kid it should be zero, if you don’t touch scenes/code/devices. I’m now at 1 every 5-6 days, unless I’m adding devices or editing code.
  • MSR Docs Corrections -- Post here

    Locked
    8
    0 Votes
    8 Posts
    439 Views
    LibraSunL
    FEATURE REQUEST Include link to lexpjs documentation in MSR docs for easy access. Not everyone will be aware of the underlying engine at work, nor its bounteous capabilities.
  • Entities issue 2 bridged vera units?

    Locked
    9
    1 Votes
    9 Posts
    599 Views
    toggledbitsT
    Awesome.
  • Why can you select Vera scenes as a trigger?

    Locked
    2
    1
    0 Votes
    2 Posts
    174 Views
    toggledbitsT
    You can trigger on any entity, and since a script is an entity, it's on the list. That said, I've found Vera's reporting of scene state to be very inconsistent, so caveat emptor.
  • Feature Request: Hass service call action

    Locked
    11
    0 Votes
    11 Posts
    708 Views
    toggledbitsT
    Apologies. That's correct. I'll change the example. You should be able to extrapolate this to any other entities. It's akin to doing the configuration on Hass with the "platform" key as you showed me in your config. I do wish they'd expose that data somehow. Hopefully, this will suffice. There are other things you can do in this file, but we'll get to that later.
  • Vera device extended attributes ?

    Locked
    38
    2
    0 Votes
    38 Posts
    3k Views
    rafale77R
    @cw-kid Yeah, one of the notorious problems with vera I have extensively posted about in the old place. There is a command queuing issue, I begged them to fix with the zwave serial API, combined with an excessive amount of unnecessary traffic generated by the controller from their "maintenance" and your network becomes very prone to inclusion process lags and failures forcing you to often have to retry inclusions and relying on luck.
  • How to auto start on Rpi reboot ?

    Locked
    26
    0 Votes
    26 Posts
    2k Views
    cw-kidC
    @toggledbits said in How to auto start on Rpi reboot ?: rpi-install.sh [image: 1615890461336-9f322ffb-ca93-464b-9c47-fbec7c7e12b4-image.png] This is the reactor.service file it created: # This file allows you to run your Reactor installation under systemd, # so it can be started at boot. Copy this file (as root or under sudo) # to /etc/systemd/system, and then run "systemctl daemon-reload". You # can then able Reactor to start at boot "systemctl enable reactor". # The usual systemctl subcommands can also be used to start, stop, and # restart reactor at will (e.g. "systemctl restart reactor"). [Unit] Description=Multi System Reactor After=network.target [Service] Type=simple User=pi WorkingDirectory=/home/pi/Documents/reactor ExecStart=/usr/bin/node app -p Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.target I followed the rest of the instructions and I could see a reactor.pid file had been created and reactor was running again. I then rebooted my Pi and after it rebooted MSR is running again. So everything appears to have worked OK. Thanks
  • The x_vera_state capability is gone

    Locked
    22
    0 Votes
    22 Posts
    2k Views
    CrilleC
    @librasun I believe that is fixed in Vera fw 7.32 "12. Fixed the issues with not being able to remove or set an attribute or variable to the empty value".

Recent Topics