Multi-System Reactor

691 Topics 6.8k Posts
  • Virtual Devices for lamellas in Vera

    3
    0 Votes
    3 Posts
    126 Views

    I toyed with the idea of writing my own VirtualController, but findEntity and such are only valid within the controller, so an entity from another controller is not callable. After a couple of hours flidding with code, I've just added two virtual devices like this, supporting the main features I need:

    - id: "cover_lamellas2" name: 'Frangisole Matteo: lamelle' capabilities: cover: actions: open: - target: 'position.value' value: '1' - target: 'state' value: 'true' close: - target: 'position.value' value: '0' - target: 'state' value: 'false' set: - target: 'position. Value' expr: 'parameters.state?1:0' - target: 'state' expr: 'parameters.state' position: actions: set: - target: 'value' expr: 'parameters.value' - target: 'cover. State' expr: 'parameters.value != 0'

    And two reactions like this, watching for position. Value changes:
    88a26f94-fad7-4367-b6ce-8ed5780e6f82-image.png

    It's working lovely, even if I wish it were possible to avoid two reactions. I'll move to zwavejs, eventually, so this is acceptable as a short-term solution.
    I hope this can be helpful to other people in the future.

  • Feature request: user authentication

    1
    0 Votes
    1 Posts
    70 Views
    No one has replied
  • 0 Votes
    13 Posts
    253 Views

    Yup, many thanks to @toggledbits for the quick fix!

  • 0 Votes
    4 Posts
    163 Views

    Appreciate it!

  • Odd behavior in Weekday checkmarks (MSR)

    3
    0 Votes
    3 Posts
    114 Views

    @Crille said in Odd behavior in Weekday checkmarks (MSR):

    "Date formatting extras. The weekday and month names are derived from the JavaScript locale, so
    they do not need to be defined here." I missed that change and still have them defined in the Swedish translation and that shows correct in the UI.

    If they are defined in the locale data, Reactor will prefer that over asking JavaScript/Node.

    This is now fixed in my dev version and the fix will be in the next build. It's cosmetic only. Until that build is released, just assume the order is Sun - Sat regardless of the label (the days are handled by number, not by name). It will also fix itself next week (the bug only occurs when the most recent Sunday is in the prior month).

  • 0 Votes
    9 Posts
    246 Views

    Fixable. Exercise for the readers.

  • Z Wave JS - Not Connecting

    Solved
    5
    0 Votes
    5 Posts
    448 Views

    @toggledbits got it. So basically if you navigate to Settings -> Add-Ons -> Z Wave JS UI and on the top where it says Info, Documentation, Configuration, and Logs click Configuration. Then under Network section turn the toggle on to show unused ports (not sure if that is the correct verbiage) then add port 3000 and hit save. Once the add-on restarts it should work.

  • 0 Votes
    2 Posts
    86 Views

    Strange, I deleted the Global Expression and created it again and now the HTTP API commands are working OK again.

    In the browser for example I now see a response like this and the variable is set with my data OK.

    {"name":"scene","expr":"","index":9,"mdt":1689950652569,"serial":22,"value":"backcam","since":1689950659980}

  • Reactor Ex Machina II (2023-July Update)

    3
    3 Votes
    3 Posts
    160 Views

    very cool. any plans for an import/export feature in the UI?

  • 0 Votes
    3 Posts
    141 Views

    @Pabla This post inspired me.

    After poking at this a bit I went a different route and have my MSR backing up to a Github repo. The only thing it's unhappy about is backing up the storage directory due to the sheer number of files so I circumvented that and have that directory tarred into an archive and then the archive itself is backed up. Github is happy, I'm happy.

  • Possible Typo/Correction in Manual

    2
    0 Votes
    2 Posts
    88 Views

    Yeah, that's a carry over from the Vera Reactor plugin (R4V)... the docs for MSR started from R4V and got edited, and I missed that. Apologies, but darned good sleuthing on your part to find the correct thing. You are awarded 10 XP!

  • 0 Votes
    10 Posts
    234 Views

    @Pabla The original Conditions were <= .25 whereas the working version had to be flipped to >= .25. That's what ultimately made it work.

  • 1 Votes
    6 Posts
    174 Views

    @gwp1 If your reactor folder is /home/user/documents/reactor your tar.gz file should be in home/user/documents. But thats not what the error is showing, looks like the Reactor update file isn't in .gz compressed format, I know with certain browsers like Safari they will auto decompress downloaded files.

  • 0 Votes
    3 Posts
    95 Views

    Hmm, looks OK to me, but I'm hardly an authority

    C

  • Couldn't Copy Few Files from Reactor Directory

    4
    0 Votes
    4 Posts
    123 Views

    I suspect they can be ignored indeed

    C

  • Moving the IP of an HA install

    3
    0 Votes
    3 Posts
    67 Views

    Super, thanks. Makes things easier (as I've come to expect!)

    C

  • 1 Votes
    40 Posts
    1k Views

    I've just updated a bunch of templates, and added:

    shelly_relay_simple: you know, a simple template for a shelly relay shelly_scenecontroller: to map Shellies as scene controllers/buttons shelly_uni_adc: to map Shelly Uni's capabilities to measure ADC. GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor

    Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

  • Home Assistant add-on

    30
    3 Votes
    30 Posts
    1k Views

    Restarting reactor from reactor itself after changing any global expressions or making new global expressions is doing the trick for me currently.

  • Expressions page showing old data

    10
    0 Votes
    10 Posts
    276 Views

    Restarting reactor from reactor itself after changing any global expressions or making new global expressions is doing the trick for me currently.
    But I am using MSR via the unofficial addon by @mrw298 .

  • Help with Logic Routines SW1/SW2

    9
    0 Votes
    9 Posts
    261 Views

    Hi @Pabla 🙂

    Thank you for your time, but let me try to better explain the situation I have using the air conditioner.

    My equipment can be operated/command in three ways:

    Remote control, which basically each function just turns on and off (let's call it SW1); APP on the phone, which in this case knows the status of the device by WiFi integration / Samsung cloud (SW2); Or by the dashboard mounted on Hubitat (SW3).

    I will detail the use case of the actions and impacts.

    a. Turning on the a/c through the HE dashboard (SW3), the virtual button activates the Samsung integration drive, setting the mode ON, this integration with the cloud updates the status of the APP (SW2), but the remote control thinks it is off ( SW1), as it has no integration, but the air will be turned on and it will work normally.
    b. Turning on the air through the APP (SW2), through the integration with HE, the status of the drive is modified, so my rule turns on the SW3, aligning the dashboard.
    c. The same thing happens if you use the control (SW1), the Samsung cloud is triggered, it updates the APP status, and the HE drive with the status modification triggers the rule that turns on the SW3 virtual button. In this case, the control now knows that air is connected.

    As you can see, I have a rule that when switching SW1 or SW2 or SW3, it will in ON ways inform the status change and align the 3 SW for all to be ON.

    In the case of turning off, it is the opposite way, any of the 3 SW can turn off, and a second rule makes the alignment to put the 3 SW in an OFF state.

    As our friend @toggledbits mentioned, cave-mode is the easiest, create two rules, one for each situation and everything works, that's what I have today.

    My puzzle is that since one rule is the opposite of the other, I thought of trying to have just one, using the SET and RESET situation.

    As I demonstrated, the SET is easy, because anyone with the OR condition solves, one that is triggered, turns it ON and puts all the others in the same status, now turning OFF is the complicated thing, because it changes the condition from OR to AND, that is, SW1 and SW2 and SW3 have to be ON to keep the device ON, if any of them turns OFF you have to turn OFF all the others.

    Well let's to follow the cave-mode which is easier for now, in the future our genius @toggledbits maybe create a Latch in reverse 🙂

    Thanks.

Recent Topics