Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    (Last Updated: April 22, 2021)

    • Cant reach MSR after mowing my Pi

      M

      I decided to move my MSR pi to a permanent place and after that i cant connect to it. I can se in the logs that it has connection with hubitat ..

      I says
      2021-04-22T20:11:54.649Z Controller:ERR SystemController#reactor_system disk usage not available: Error: Cannot find module 'diskusage-ng

      What has happened? I did a hard remove by powercable....
      /Mattias

      Full log

      2021-04-22T20:10:56.493Z Controller:NOTICE Controller HubitatController#hubitat is now online.
      2021-04-22T20:10:56.497Z app:NOTICE Starting Reaction Engine...
      2021-04-22T20:10:56.498Z Engine:INFO Reaction Engine starting
      2021-04-22T20:10:56.499Z Engine:INFO Checking rule sets...
      2021-04-22T20:10:56.514Z Engine:INFO Checking rules...
      2021-04-22T20:10:56.559Z default:ERR [IndividualFileStrategy#/home/pi/reactor/storage] failed to read cs-rule-knbyvokt in /home/pi/reactor/storage/states/cs-rule-knbyvokt.json: SyntaxError: Unexpected end of JSON input
      Trapped unhandled Promise rejection SyntaxError: Unexpected end of JSON input
      at JSON.parse (<anonymous>)
      at IndividualFileStrategy.getDataObject (/home/pi/reactor/server/lib/IndividualFileStrategy.js:126:38)
      at Container.getDataObject (/home/pi/reactor/server/lib/Container.js:91:53)
      at Rule.getRuleStates (/home/pi/reactor/server/lib/Rule.js:601:98)
      at Rule.getConditionState (/home/pi/reactor/server/lib/Rule.js:626:46)
      at new Rule (/home/pi/reactor/server/lib/Rule.js:491:47)
      at Function.getInstance (/home/pi/reactor/server/lib/Rule.js:500:36)
      at /home/pi/reactor/server/lib/Engine.js:584:50
      at Array.forEach (<anonymous>)
      at Engine.checkData (/home/pi/reactor/server/lib/Engine.js:582:36)
      SyntaxError: Unexpected end of JSON input
      at JSON.parse (<anonymous>)
      at IndividualFileStrategy.getDataObject (/home/pi/reactor/server/lib/IndividualFileStrategy.js:126:38)
      at Container.getDataObject (/home/pi/reactor/server/lib/Container.js:91:53)
      at Rule.getRuleStates (/home/pi/reactor/server/lib/Rule.js:601:98)
      at Rule.getConditionState (/home/pi/reactor/server/lib/Rule.js:626:46)
      at new Rule (/home/pi/reactor/server/lib/Rule.js:491:47)
      at Function.getInstance (/home/pi/reactor/server/lib/Rule.js:500:36)
      at /home/pi/reactor/server/lib/Engine.js:584:50
      at Array.forEach (<anonymous>)
      at Engine.checkData (/home/pi/reactor/server/lib/Engine.js:582:36)
      Promise {
      <rejected> SyntaxError: Unexpected end of JSON input
      at JSON.parse (<anonymous>)
      at IndividualFileStrategy.getDataObject (/home/pi/reactor/server/lib/IndividualFileStrategy.js:126:38)
      at Container.getDataObject (/home/pi/reactor/server/lib/Container.js:91:53)
      at Rule.getRuleStates (/home/pi/reactor/server/lib/Rule.js:601:98)
      at Rule.getConditionState (/home/pi/reactor/server/lib/Rule.js:626:46)
      at new Rule (/home/pi/reactor/server/lib/Rule.js:491:47)
      at Function.getInstance (/home/pi/reactor/server/lib/Rule.js:500:36)
      at /home/pi/reactor/server/lib/Engine.js:584:50
      at Array.forEach (<anonymous>)
      at Engine.checkData (/home/pi/reactor/server/lib/Engine.js:582:36)
      }
      Trace
      at process.<anonymous> (/home/pi/reactor/app.js:197:151)
      at process.emit (events.js:315:20)
      at process.EventEmitter.emit (domain.js:467:12)
      at processPromiseRejections (internal/process/promises.js:245:33)
      at processTicksAndRejections (internal/process/task_queues.js:94:32)
      2021-04-22T20:10:56.599Z Controller:WARN HubitatController#hubitat 'Allow control of HSM' appears to be disabled in your Maker API configuration
      2021-04-22T20:10:56.604Z Controller:NOTICE HubitatController#hubitat current mode is Kv\u00e4ll (131)
      2021-04-22T20:11:54.649Z Controller:ERR SystemController#reactor_system disk usage not available: Error: Cannot find module 'diskusage-ng'
      Require stack:

      /home/pi/reactor/server/lib/SystemController.js
      2021-04-22T20:12:16.879Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
      Multi-System Reactor

    • Why can't I run this LUA code ?

      cw-kid

      I have created a Global Reaction with this LUA code for my Vera to run.

      However when I run the Reaction nothing happens. I can't see anything in the log file either about this rules ID number.

      If I run the same LUA code on Vera in the test window it works OK.

      OR any other suggestions how I can set this up in a global Reaction (Scene) in MSR ?

      Instead I could use the VeraScenes.lua file in the Vera startup library, but I am wondering why I can't just paste the LUA code directly in to the MSR rule.

      Thanks

      local status = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1", "Status", 419) --Status of Safe to Arm virtual switch if status == "0" then --Safe to Arm luup.inet.wget("http://SOME-HTTP-REQUEST") luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","SetHouseMode", {Mode = 2}, 0) --Set House Mode to Away luup.inet.wget('SOME-HTTP-REQUEST' ,5); else --Not Safe to Arm luup.inet.wget("SOME-HTTP-REQUEST") luup.inet.wget('SOME-HTTP-REQUEST' ,5); end
      Multi-System Reactor

    • Setting up Pushover in MSR

      J

      Hi,

      I've been using Pushover in VeraAlerts, but now want to send my notifications from MSR.
      I see in the reactor config directory that the notification. yaml file includes Pushover, but is showing #TBD. Is this where I need to set up my Pushover user key etc. and if so what and how should the information be entered?

      Any help would be appreciated.

      Multi-System Reactor

    • Posting from log files

      toggledbits

      For years of participating in the other community, I've watched people post a single error message from a log file when asking for help. I'm now seeing the same behavior (I guess not surprisingly, given the genesis of this community) here. But it's got to stop.

      When you post just the error message, you leave out vital context that may give clues to more quickly troubleshoot whatever problem you are having. Very often, by the time someone responds to ask for more, the message is gone (e.g. rotating logs on Vera) or has become too difficult to locate.

      Please, when posting anything from a log file, you should be giving context with the message by including, let's say at least 10, messages before, and a few after. Particularly in the case of MSR, almost every exception that is logged is accompanied by a context-defining message immediately before, and in many cases, a follow-on additional data dump related to the error.

      Thanks for listening.

      P.S. My weekly (it seems) reminder: when things go wrong that obviously aren't just the UI doing something dumb, you must look at the logs.

      Multi-System Reactor

    • Reset Reaction evaluate Contraints?

      cw-kid

      I have a rule that closes my curtains when I start my Xbox activity on the Harmony hub.

      In the Contraints I have that it's day time.

      In the Reset Reaction it opens the curtains when I end the Xbox activity etc.

      Today it was day time and I started the Xbox activity and the curtains closed.

      When I turned off the Xbox it was night time, however my curtains then opened.

      I expected the curtains to remain closed as by then it was night time.

      Not sure the best way to handle this? But I want a rule that closes the curtains if it's day time and I want to play on the Xbox. If it's still day time when I end that Harmony Activity then open the curtains again. Or if it's night time then keep the curtains closed.

      I figure if I start playing the Xbox and it's already night time then the curtains would already be closed anyway via the sunset offset schedule that closes the curtains.

      Multi-System Reactor

    • Running reactions /Blocked?

      M

      What does Blocked mean in running reactions?

      Anyone having a lot of empty alerts that is not possible to erase?

      Hubitat - MSR
      /Mattias!
      Skärmavbild 2021-04-22 kl. 12.09.15.png

      Multi-System Reactor

    • PR #178 In-place modification of arrays in "each"

      toggledbits

      I'm moving the discussion on this out of the Mantis PR #178 for the benefit of all/documentation, and also because it's easier to type and format here.

      @LibraSun wrote in that PR:

      I'm 99% certain you'll explain this one away as "expected" but I naively believed it would yield different results:
      In an expression defined by:
      a=[1,2,3],
      each i in a:
      shift(a)
      // result (array) [1,2] (unexpected
      // expected [1,2,3]

      This has me thinking that 'each' is leaving items on the table, as I tried unsuccessfully pointing out above.

      The issue here is that your expression shift(a) is modifying the iteration subject array in place. Basically, here are the iteration steps that are run, starting with a=[1,2,3]

      First iteration: a=[1,2,3]; the local i is assigned the first array element 1, but it is not used in the expression. The expression shift(a) results in 1 and causes a to be reduced to [2,3] (the first element is shifted off and becomes the result). Since this is the last value in the expression, 1 is added to the each result array. Second iteration: a is now [2,3] because the previous iteration modified it. So i is assigned 3, because the iteration is on the second element/iteration through the array, but i is not used in the expression. The shift(a) causes a to be reduced to [3] and its return value is 2, so the value 2 is added to the iteration result array. Third iteration: a is now [3], and we are on the third iteration, but the iteration index of 3 (third iteration) is now off the end of the array (only 1 element long), so iteration stops.

      The result of this each is therefore [1,2] because those are two values that were shifted out, and a is left at [3] because there was no third run of shift() to remove it.

      As I said in the PR, modifying an array you are iterating through can be dangerous and confusing in many languages, because iterators keep state during iteration, and some operations you can do inside the iteration can and will invalidate that state in some way. In Lua on Vera, this often leads to deadlocks and crashes so bad that the box reboots, not just a Luup reload. It's a Bad Idea, and programmers who know are very wary of doing this type of thing in any language unless they are certain of the side-effects/lack of side-effects.

      Your additional example:

      a=[1,2,3], // The array 'a' is [1,2,3]
      a=unshift(a,0), // The array 'a' is [0,1,2,3]
      a=push(a,4), // The array 'a' is [0,1,2,3,4]
      each i in a: // Iterating over the 5 elements of 'a'
      shift(a) // Take the first element of 'a' and append it to result array [ ]
      // result [0,1,2] (unexpected)
      // and array 'a' is now [3,4]! (also unexpected)

      Also correct result. All of the gyrations before the each are not relevant to behavior here. At the start of the each, the array is [0,1,2,3,4] (5 elements). Iterations:

      a=[0,1,2,3,4], i=0, shift(a) returns 0 and modifies a to [1,2,3,4]; the each result array is now [0] a=[1,2,3,4], i=2, shift(a) returns 1 and modifies a to [2,3,4]; the each result array is now [0,1] a=[2,3,4], i=4, shift(a) returns 2 and modifies a to [3,4]; the each result array is now [0,1,2] Iteration stops because the iteration index/step is 4, but there remain only two elements in a=[3,4] (we're off the end of the array).

      So the each result is [0,1,2] and a is left with [3,4] and this is correct operation.

      Key points:

      each keeps state during the iteration (as most iterators do) about the subject of the iteration; if the subject changes in a way that affects the state, unexpected results may occur; The functions push(), pop(), shift() and unshift() modify the array in place. If you say b=shift(a) you get a value in b and a modified (shorter) a.
      Multi-System Reactor

    • Feature request: drag & drop between "triggers" and "constraints"

      PerH

      I've imported all reactors from openLuup, and find myself moving a lot of entity-actions from triggers to constraints.. It would help a lot to have "drag & drop", or a move function for this?

      Multi-System Reactor

    • Low-priority GUI feedback

      PerH

      Just thought i'd mention it, as I've walked into it multiple times when editing rules:
      dbc9e2c8-887e-46bd-8e3c-1364eb99bb03-image.png

      When I make/edit rules, i'm used to pressing "save" through the process, and when I do that, theres only the red one left to press. It does make sense, as its already saved, but I'll stop and think one more time when it says w/o saving.
      In my head, a exit button which causes a pop-up warning if changes are not saved makes more sense - like in vera reactor.

      Feel free to discard the idea, its just something to get used to mabye. 🙂

      Multi-System Reactor

    • Problems with Up grading existing MSR.

      Black Cat

      Followers will be aware of the problems I had setting up MSR, so it won;t come as a surprise that now I have problems Upgrading to the latest version. (How much I wish for a "Click to Upgrade" Button.....)
      I've been stuck on this for 6 days and am ready to throw in all into the to hard basket, surely HA shouldn't be this problematic?
      There, I've said it now I feel better....
      So what's the problem, I can upload the file using WINSCP but no matter what I've tried it won't un-tar and over write the existing files in the Reactor Directory.
      I receive the following error message which may as well be written in Martian 🙂 in my case.
      Command 'tar -xz --directory="reactor" -f "reactor-0.1-21101-0db64f0-generic.tar.gz"'
      failed with return code 2 and error message
      tar: reactor: Cannot mkdir: Permission denied
      tar: reactor: Cannot mkdir: Permission denied
      tar: reactor/INSTALL.md: Cannot open: No such file or directory
      tar: reactor: Cannot mkdir: Permission denied
      tar: reactor/LICENSE.md: Cannot open: No such file or directory
      tar: reactor: Cannot mkdir: Permission denied
      cut for sanity sake....

      This goes on for ad infinitum for every file.

      I tried with both users, no change, can anyone decipher this and explain why WINSCP won't untar the file?

      Multi-System Reactor

    • Adding Homeseer as a Controller

      Black Cat

      How can I do this?
      The topic in the instructions is very limited.

      Other Controllers
      Other controllers that you may find as add-ins will each have their own specific configuration instructions. Please refer to their accompanying documentation.

      What information should I be looking for?

      I've tried port 1880 which is used for node-red, assuming that this is a listening port - no go. Really not sure how to go about this as everything I do is mostly trial & error.

      BTW, I added my Vera Lite into the mix successfully, HS4 would make it a trifecta!

      Multi-System Reactor

    • Vera vs MSR lock code logic

      MikeReadington

      Hi Everyone,

      In the Vera Reactor logic, I used to use the operator "updates" in a lock condition.

      If I entered the door and the code used was "Mike," it would hold the condition true indefinitely because "Mike" was the last stored value. Since it is held indefinitely, setting the condition to pulsed would not allow the condition to fire again because it never went false. If I entered a different code, the condition would go false, then entering "Mike" again would cause the condition to go true.

      I did this using the operator "updates" in an AND condition along with the lock code. The code condition would stay true with "Mike," and when "Mike" is entered consecutively, the "updates" condition will go true each time, and then the whole condition would go true, triggering the action.

      Since "updates" no longer appears to be an operator, how would I do this in the new logic? I think I remember a discussion about this, but I searched and can't seem to find it.

      I'm not a programmer, so I am probably missing the easy way to do this.

      Screen Shot 2021-04-18 at 4.54.27 PM.png

      Multi-System Reactor

    • Replacing SiteSensor Plugin (Vera) with MSR

      LibraSun

      For MSR users with SiteSensor still installed back on Vera, you might want to consider letting MSR take over those duties. Here's a quick run-down of how I imported one of my SiteSensor recipes into a Rule on MSR, using OpenWeather API* as an example.

      STEP 1: Copy the Basics from Vera
      (a) Go to your Vera > Devices, locate SiteSensor (the main instance, not one of its children devices) and click ► for details then click SETTINGS.
      (b) Copy and paste (into Notepad or other text editor) the Request URL along with each of the defined expressions.

      STEP 2: Create a Rule on MSR
      (c) Jump into Rule Sets and click "Create Rule". Click its title to rename the rule 'OpenWeather (API)" and click 'Rename'.
      (d) Decide on appropriate Triggers (in my case, it's an OR group that includes an [INTERVAL] set to "Every 3 hours" plus a few [ENTITY ATTRIBUTE] entries reacting to things like entering/leaving home, waking up, etc.).
      (e) In Set Reacion, create an [HTTP REQUEST] > [GET] action.
      (f) Paste your old "Request URL" into the "Request URL" box.

      FYI GET calls to OpenWeather API* take the form:

      http://api.openweathermap.org/data/2.5/weather?zip=<your_ZIP_code>&id=<your_Wx_ID>&appid=<app-id>&units=imperial

      (g) Create four new blank Expressions (name them openWx, Tx, Hx and Rx).
      (h) Click SAVE & EXIT

      STEP 3: Process the Response
      (i) Re-open rule "OpenWeather (API)" by clicking the 'Edit' icon.
      (j) Within the [HTTP REQUEST] action, assign "Capture response to:" ► openWx
      (k) Down in Expressions, click "[+]Add Expresssion" then enter the following:
      Tx := round(openWx.main.temp,1)
      // yields current outdoor temperature
      Hx := round(openWx.main.humidity)
      // yields current humidity conditions
      Rx := openWx.rain ? ( openWx.rain['3h'] ? openWx.rain['3h'] : 0) : 0
      // yields predicted rainfall, if present; otherwise 0
      (l) Click SAVE & EXIT. Enjoy!

      Naturally, your specific needs and workflow will differ from the one I've outlined here. For instance, you may wish to explore the contents of the JSON object in openWx for additional data of interest to you, and define variables to match.

      My goal here has been to illustrate some key concepts needed for moving from SiteSensor over to MSR:

      Some syntax is the same, such as dot notation for object.item.access; Other syntax has changed, such as the use of ternary A ? B : C in place of IF (A, B, C); Manually setting an [INTERVAL] in lieu of SiteSensor's timed schedule;

      Pro tip: If your workflow demands that other Rules react to the output of the "OpenWeather (API)" rule, then be sure to create all of the aforementioned Expressions under "Global Expressions" instead, so they become accessible across all Rule Sets.

      Once the transition is complete, you can either DISARM SiteSensor on Vera or remove it entirely with "Remove Device" (which will automatically remove all of its child devices).

      *Additional reading:
      OpenWeather API : https://openweathermap.org/api
      FREE SUBSCRIPTION REQUIRED TO USE THIS SERVICE

      PRO TIP: See below for optimal way to incorporate OpenWeatherMap into your MSR workflow(s), by enabling the service directly in the reactor.yaml config file.

      Multi-System Reactor

    • Rethinking HVAC moving from Reactor (Vera) to MSR

      G

      In my Vera config I have two SiteSensors (one for Ambient Wx, one for OpenWxMap) that point to two unique Reactor devices for controlling HVAC in my home. This is done for redundancy - if the Ambient API drops it returns zero data which then triggers a standalone Master API Reactor device to flip on the OWM SiteSensor and corresponding HVAC Reactor device to continue controlling the house conditions.

      Once the Ambient API returns to available the Master API Reactor device flips back to the Ambient SiteSensor and corresponding HVAC Reactor device, turning OFF the SiteSensor for OWM to save on API calls.

      I've been able to duplicate one half of this, including the Master API role, in MSR. But... here's the tricky part... I can't turn "off" the MSR Rule Sets for the OWM version. As such, HVAC is sent conflicting data and doesn't know what to do.

      Before I go alls deep into explaining how all of this currently works, am I missing something somewhere that would allow me to trigger the on/off of MSR Rule Sets?

      Multi-System Reactor

    • Expressions and LuaXP Functions

      LibraSun

      Knowing that MSR Preview may not yet fully implement LuaXP (CORRECTION: MSR uses a different language lexpjs), I could not resist whipping up some text expressions for fun. Whereupon two things popped out at me:

      The new scaling (0.00 - 1.00) of Dimming Level will require a rewrite of certain Expressions that I use to balance my light levels. For example, it was my custom to monitor one lamp's brightness (0 - 100) with Reactor Luup, then set another lamp to 93% of that level, using this Expression: floor(getstate( 9, "urn:upnp-org:serviceId:Dimming1", "LoadLevelTarget" ) * 0.93)

      Now, in MSR, it will become necessary to modify that to read:

      floor ((getEntity( "vera>device_9" ).attributes.dimming.level * 0.93)*100)/100

      which effectively scales the value up x 100 (so that floor() can act upon it correctly), then downscale it / 100. Just an FYI to ponder.

      I'm noticing that every edit, however minor, of an Expression in MSR requires an immediate SAVE click before the 'Run' button will become active. That is to say, I cannot repeatedly evaluate the Expression during editing, without clicking SAVE first.

      Only mentioning this latter behavior since it departs so dramatically from Reactor Luup's paradigm.

      Multi-System Reactor

    • MSR API functions and documentation

      cw-kid

      Hi

      I am assuming in time MSR will have some API documentation.

      I am going to ask Bill the developer of the Home Remote dashboard app if he can add support for MSR.

      Specifically support for MSR global Reactions (Scenes), where hopefully they can be imported in to the Home Remote Designer application and then we can more easily create dashboard tiles that when pressed would run a particular MSR global Reaction etc.

      Currently in Home Remote it's possible but not so easy to create a tile that runs a http request when pressed and I have tested this and it does work and will run an MSR global Reaction.

      But I'd much prefer if in the Home Remote Designer application MSR could be added as a device type and then all its global Reactions
      imported as it does with Vera and other systems.

      Multi-System Reactor

    • Global Reactions - Constraints ?

      cw-kid

      Hi

      Will Global Reaction rules have Constraints added at some point?

      And maybe the other functions like Reset Reaction and Expressions.

      Thanks

      Multi-System Reactor

    • Creating Rules with Conditional Logic

      K

      How are folks handling situations where they want to have Conditional Actions or Branching Logic in their Set Reactions for a rule? Are you creating Duplicating the same trigger and setting different conditions and Actions?

      Is there an approach where you combine a main rule with your entity triggers with sub rules that trigger off Expressions? You then could write your conditions as Set Variable actions in the Main Rule for the Expressions that evaluate to true or false. Each sub rule would trigger based on the expression changing to true and then could also change it back to false after.

      Not sure if that's worth the complexity for the reusability and control over duplicate triggers.

      Multi-System Reactor

    • Multi-System Reactor Developer Preview AVAILABLE

      toggledbits

      OK, people, here we go! At long last, Multi-System Reactor developer preview is available!

      The package can be downloaded from the Reactor bug tracker, a MantisBT system (at https://reactor.toggledbits.com/mantisbt/). There is a download button in the left margin, as well as links to the documentation, which you will need for installation.

      UPDATE 2021-02-24 -- To keep spammers off, I've locked down registration on the Bug Tracker. To get access to the Bug Tracker and preview downloads, please PM me (not reply here) your full name and email address and I will set up an account for you.

      This version of MSR will run on Linux systems, including RPi's under Raspios Buster, running node.js version 12.10 or higher (v14.15.1). For RPi users, there is an installation script that will install a local copy of node.js (for the logged-in user).

      Bugs reports will be handled through the bug tracker only. Discussion and questions in this forum are fine, though (if that leads to a bug report, we'll transition).

      This version supports Vera (and openLuup to the degree it's compatible with Vera Luup), Hubitat, and Home Assistant. Some of the device support on the H platforms is still a bit basic, but it is largely controlled by configuration and progress can be made quickly.

      The documentation beyond installation is a mess. Of course, I started with the existing documentation and have been massaging into MSR's particulars, but it still has a long way to go on the detail.

      I know I don't have to say this, but I will anyway... let me know how it goes!

      Multi-System Reactor

    • Feature Request - Reaction to MQTT

      S

      I looked through the forum, but could not find it, so my apologies if this has been asked. It would be nice to be able to push a message to MQTT for further upstream integrations.

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

    Setting up Pushover in MSR

    Multi-System Reactor
    3
    7
    64
    Loading More Posts
    • 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.
    • J
      jsimmo last edited by

      Hi,

      I've been using Pushover in VeraAlerts, but now want to send my notifications from MSR.
      I see in the reactor config directory that the notification. yaml file includes Pushover, but is showing #TBD. Is this where I need to set up my Pushover user key etc. and if so what and how should the information be entered?

      Any help would be appreciated.

      1 Reply Last reply Reply Quote 0
      • toggledbits
        toggledbits last edited by

        Look in /dist-config/notifications.yaml for the latest guide on configuring for Pushover

        1 Reply Last reply Reply Quote 0
        • J
          jsimmo last edited by

          Thanks. Should have known to look there. Will give it a try.

          1 Reply Last reply Reply Quote 0
          • J
            jsimmo last edited by

            Followed the guide and Pushover is now set up and working fine.

            1 Reply Last reply Reply Quote 1
            • LibraSun
              LibraSun last edited by LibraSun

              I've got my Pushover config up and running (and dare I say, working great) in MSR, except for one minor "thing"...

              ...all my notifications keep coming to the default device (my cellphone) rather than the device explicitly declared in the "Device:" field of my Rule. I've double-checked the spelling (HP_mini, which matches the label assigned to my Web browser on pushover.net), verified that the Pushover client is open in Chrome and receiving messages -- particularly those I send from the Pushover web UI "as MSR", and that all keys are current and in the right places, etc.

              Like I say, the messages DO get sent. Only to the wrong endpoint. Is anyone else with multiple endpoints defined getting misdirected notices from MSR??

              • Libra "Edge Case" Sun

              P.S. I don't reckon these associated lines from Reactor.log shed any light on the URL sent (and MSR cannot capture Pushover's response, so far as I know):

              2021-04-22T22:11:10.717Z <Rule:5:Rule.js:750> Rule#rule-kntf80qj dependency notification entity-changed Entity#vera>device_110 from Entity#vera>device_110
2021-04-22T22:11:10.718Z <Rule:5:Rule.js:756> Rule#rule-kntf80qj requesting eval; entity-changed Entity#vera>device_110
2021-04-22T22:11:10.719Z <Rule:5:Rule.js:750> Rule#rule-kntf80qj dependency notification entity-changed Entity#vera>device_110 from Entity#vera>device_110
2021-04-22T22:11:10.720Z <Rule:5:Rule.js:756> Rule#rule-kntf80qj requesting eval; entity-changed Entity#vera>device_110
2021-04-22T22:11:10.721Z <Rule:5:Rule.js:951> Rule#rule-kntf80qj (rule-kntf80qj) evaluate() acquiring mutex
2021-04-22T22:11:10.722Z <Rule:5:Rule.js:951> Rule#rule-kntf80qj (rule-kntf80qj) evaluate() acquiring mutex
2021-04-22T22:11:10.723Z <Rule:5:Rule.js:955> Rule#rule-kntf80qj._evaluate() mutex acquired, evaluating
2021-04-22T22:11:10.724Z <Rule:5:Rule.js:959> Rule#rule-kntf80qj update rate is 3/min limit 60/min
2021-04-22T22:11:10.725Z <Rule:5:Rule.js:881> Rule#rule-kntf80qj evaluateExpressions() with 0 expressions
2021-04-22T22:11:10.725Z <Rule:5:Rule.js:971> Rule#rule-kntf80qj._evaluate() trigger state now false (was false)
2021-04-22T22:11:10.726Z <Rule:5:Rule.js:973> Rule#rule-kntf80qj._evaluate() constraints state true
2021-04-22T22:11:10.727Z <Rule:null> Rule#rule-kntf80qj rule state now false, changed no
2021-04-22T22:11:10.728Z <Rule:5:Rule.js:955> Rule#rule-kntf80qj._evaluate() mutex acquired, evaluating
2021-04-22T22:11:10.729Z <Rule:5:Rule.js:959> Rule#rule-kntf80qj update rate is 3/min limit 60/min
2021-04-22T22:11:10.730Z <Rule:5:Rule.js:881> Rule#rule-kntf80qj evaluateExpressions() with 0 expressions
2021-04-22T22:11:10.731Z <Rule:5:Rule.js:971> Rule#rule-kntf80qj._evaluate() trigger state now false (was false)
2021-04-22T22:11:10.732Z <Rule:5:Rule.js:973> Rule#rule-kntf80qj._evaluate() constraints state true
2021-04-22T22:11:10.733Z <Rule:null> Rule#rule-kntf80qj rule state now false, changed no
2021-04-22T22:11:10.850Z <Rule:5:Rule.js:750> Rule#rule-kntf80qj dependency notification entity-changed Entity#vera>device_110 from Entity#vera>device_110
2021-04-22T22:11:10.851Z <Rule:5:Rule.js:756> Rule#rule-kntf80qj requesting eval; entity-changed Entity#vera>device_110
2021-04-22T22:11:10.852Z <Rule:5:Rule.js:750> Rule#rule-kntf80qj dependency notification entity-changed Entity#vera>device_110 from Entity#vera>device_110
2021-04-22T22:11:10.853Z <Rule:5:Rule.js:756> Rule#rule-kntf80qj requesting eval; entity-changed Entity#vera>device_110
2021-04-22T22:11:10.854Z <Rule:5:Rule.js:951> Rule#rule-kntf80qj (rule-kntf80qj) evaluate() acquiring mutex
2021-04-22T22:11:10.855Z <Rule:5:Rule.js:951> Rule#rule-kntf80qj (rule-kntf80qj) evaluate() acquiring mutex
2021-04-22T22:11:10.856Z <Rule:5:Rule.js:955> Rule#rule-kntf80qj._evaluate() mutex acquired, evaluating
2021-04-22T22:11:10.856Z <Rule:5:Rule.js:959> Rule#rule-kntf80qj update rate is 4/min limit 60/min
2021-04-22T22:11:10.857Z <Rule:5:Rule.js:881> Rule#rule-kntf80qj evaluateExpressions() with 0 expressions
2021-04-22T22:11:10.859Z <Rule:5:Rule.js:1579> cond cond7hpkrvd evaluation state false->true
2021-04-22T22:11:10.860Z <Rule:5:Rule.js:1579> cond trig evaluation state false->true
2021-04-22T22:11:10.860Z <Rule:5:Rule.js:971> Rule#rule-kntf80qj._evaluate() trigger state now true (was false)
2021-04-22T22:11:10.861Z <Rule:5:Rule.js:973> Rule#rule-kntf80qj._evaluate() constraints state true
2021-04-22T22:11:10.862Z <Rule:INFO> Rule#rule-kntf80qj (rule-kntf80qj) triggered!
2021-04-22T22:11:10.863Z <Rule:null> Rule#rule-kntf80qj rule state changed, was false now true
2021-04-22T22:11:10.863Z <Rule:null> Rule#rule-kntf80qj rule state now true, changed true
2021-04-22T22:11:10.865Z <Rule:5:Rule.js:955> Rule#rule-kntf80qj._evaluate() mutex acquired, evaluating
2021-04-22T22:11:10.866Z <Rule:5:Rule.js:959> Rule#rule-kntf80qj update rate is 4/min limit 60/min
2021-04-22T22:11:10.867Z <Rule:5:Rule.js:881> Rule#rule-kntf80qj evaluateExpressions() with 0 expressions
2021-04-22T22:11:10.868Z <Rule:5:Rule.js:971> Rule#rule-kntf80qj._evaluate() trigger state now true (was false)
2021-04-22T22:11:10.869Z <Rule:5:Rule.js:973> Rule#rule-kntf80qj._evaluate() constraints state true
2021-04-22T22:11:10.869Z <Rule:INFO> Rule#rule-kntf80qj (rule-kntf80qj) triggered!
2021-04-22T22:11:10.870Z <Rule:null> Rule#rule-kntf80qj rule state now true, changed no
2021-04-22T22:11:10.872Z <Rule:5:Rule.js:999> Rule#rule-kntf80qj enqueueing reaction rule-kntf80qj:S
2021-04-22T22:11:10.873Z <Engine:INFO> Enqueueing "rule-kntf80qj<SET>" (rule-kntf80qj:S)
2021-04-22T22:11:10.874Z <Engine:5:Engine.js:948> Engine#1 queueReaction() starting Promise for rule-kntf80qj:S rule rule-kntf80qj task 368
2021-04-22T22:11:10.875Z <Engine:5:Engine.js:1059> _process_reaction_queue() wake-up!
2021-04-22T22:11:10.877Z <Engine:5:Engine.js:1020> _process_reaction_queue() running task 368 { "tid": 368, "id": "rule-kntf80qj:S", "rule": "rule-kntf80qj", "__reaction": [RuleReaction#rule-kntf80qj:S], "next_step": 0, "status": 0, "ts": 1619129470873, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
2021-04-22T22:11:10.878Z <Engine:NOTICE> Starting reaction rule-kntf80qj<SET> [RuleReaction#rule-kntf80qj:S]
2021-04-22T22:11:10.879Z <Engine:5:NotifyPushover.js:208> NotifyPushover sending profile default notification request: Test
2021-04-22T22:11:10.882Z <Engine:INFO> rule-kntf80qj<SET> all actions completed.
2021-04-22T22:11:10.883Z <Engine:5:Engine.js:1024> _process_reaction_queue() task returned, new status -1; task 368
2021-04-22T22:11:10.885Z <Engine:5:Engine.js:1059> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
2021-04-22T22:11:11.288Z <Engine:5:NotifyPushover.js:216> NotifyPushover successful endpoint exchange (message sent)
2021-04-22T22:11:14.936Z <Rule:NOTICE> Rule#rule-kntf80qj configuration changed; reloading
2021-04-22T22:11:14.937Z <Rule:5:Rule.js:715> Rule#rule-kntf80qj reloading with new data
2021-04-22T22:11:14.937Z <Rule:NOTICE> Rule#rule-kntf80qj stopping rule
2021-04-22T22:11:14.938Z <Rule:5:Rule.js:696> Rule#rule-kntf80qj acquiring semaphore
2021-04-22T22:11:14.938Z <Rule:NOTICE> Rule#rule-kntf80qj configuration changed; reloading
2021-04-22T22:11:14.939Z <Rule:5:Rule.js:715> Rule#rule-kntf80qj reloading with new data
2021-04-22T22:11:14.940Z <Rule:NOTICE> Rule#rule-kntf80qj stopping rule
2021-04-22T22:11:14.940Z <Rule:5:Rule.js:696> Rule#rule-kntf80qj acquiring semaphore
2021-04-22T22:11:14.941Z <Rule:5:Rule.js:699> Rule#rule-kntf80qj semaphore acquired; releasing timer
2021-04-22T22:11:14.942Z <Rule:5:Rule.js:699> Rule#rule-kntf80qj semaphore acquired; unsubscribing from condition dependencies
2021-04-22T22:11:14.943Z <Rule:5:Rule.js:701> Rule#rule-kntf80qj saving states
2021-04-22T22:11:14.944Z <Rule:5:Rule.js:705> Rule#rule-kntf80qj stopped
2021-04-22T22:11:14.944Z <Rule:NOTICE> Rule Rule#rule-kntf80qj stopped
2021-04-22T22:11:14.945Z <Rule:5:Rule.js:699> Rule#rule-kntf80qj semaphore acquired; releasing timer
2021-04-22T22:11:14.945Z <Rule:5:Rule.js:699> Rule#rule-kntf80qj semaphore acquired; unsubscribing from condition dependencies
2021-04-22T22:11:14.946Z <Rule:5:Rule.js:701> Rule#rule-kntf80qj saving states
2021-04-22T22:11:14.948Z <Rule:5:Rule.js:705> Rule#rule-kntf80qj stopped
2021-04-22T22:11:14.948Z <Rule:NOTICE> Rule Rule#rule-kntf80qj stopped
              1 Reply Last reply Reply Quote 0
              • LibraSun
                LibraSun last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • toggledbits
                  toggledbits last edited by

                  Confirmed bug on the device in the Pushover notification. Open a PR!

                  1 Reply Last reply Reply Quote 1
                  • First post
                    Last post

                  Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

                  Powered by NodeBB | Contributors
                  Hosted freely by PointPub Media Communications Inc. | Contact us