Multi-System Reactor

691 Topics 6.8k Posts
  • 0 Votes
    11 Posts
    383 Views

    @motsie
    [SOLVED] this problem; it was in the upgrade from 22080 to 22203 where the Docker file got renamed.

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    5 Views
    No one has replied
  • Evaluation of time() comparisons

    12
    0 Votes
    12 Posts
    220 Views

    Yes it makes total sense when looked at from that perspective. I just need to find the right perspective 😉

    FWIW I am very much impressed by MSR, despite not actually having anything other than OpenLuup / Z-wave on my system (yet)!

    C

  • 0 Votes
    3 Posts
    490 Views

    @toggledbits I'm guessing the default is somewhere in the code and adding the http_request_action_timeout entry to the config overrides? I only ask because I had no entry like that in my reactor.yaml file.

    In any case - I've added this line and bounced MSR. Will monitor. Thanks very much for this guidance!

  • Vera -> HASS Migration Strategy (question)

    4
    0 Votes
    4 Posts
    170 Views

    @toggledbits read through the noise and got it. I'm depending on Vera (and their app) to manually execute certain scenes (which I think should be converted MSR Reactions or Rules) until I can fully get off the platform. I'm also trying to figure out how to do the same from a Hass dashboard. I agree that I'm sure it's possible. I just need to dig a little more.

    The virtual switch idea is interesting. Basically using them as a variable. But I think a direct call from the Vera scene may work. I'll look in to the wget function.

    Thanks for the feedback, both.

  • Variables for fun and profit

    19
    0 Votes
    19 Posts
    346 Views

    @toggledbits that's super. Thanks again for all your help!

    C

  • Idiot questions. Feel free to ignore.

    19
    0 Votes
    19 Posts
    319 Views

    @toggledbits said in Idiot questions. Feel free to ignore.:

    there's a "repeat...while" group

    I didn't mention that because I had some issues/questions about it that I have not found time to test futher, so this is a heads up. I will try to find time to test more and create a new topic soon. 🙂

  • 0 Votes
    5 Posts
    144 Views

    Thanks for the replies. I assumed that I would have to go about it a different way that what I was doing on the Vera with Reactor.

  • 0 Votes
    3 Posts
    171 Views

    @fanan there's a big difference.

    Rule with two conditions: switch turned on, time between sunrise and sunset.

    If both are triggers, any time both become true, the rule sets. So, if the switch is on but it's 2am, not set. When sunrise arrives, rule sets.

    If sunrise/sunset is a constraint, the rule only sets when the switch changes state to on between sunrise and sunset. If the switch is on at 2am, not set. When sunrise comes and goes, the rule remains not set.

  • The Home Remote with MSR

    6
    0 Votes
    6 Posts
    251 Views

    @cw-kid I was thinking along these lines myself when I asked that question. Any device brought into MSR could then be brought into Home Remote regardless of Home Remote's native support.

    Unless I am not understanding something correctly, MSR could be brought in essentially as a hub. If MSR could talk to it, Home Remote could talk to it. More importantly, for something I would like to do, I would like a specific triggered Home Remote function to interact with MSR. (I think you had done this already if I remember correctly)

    I think this would open lots of additional automation avenues.

  • 1 Votes
    3 Posts
    115 Views

    @toggledbits, can confirm that this build fixed the problem

  • 0 Votes
    2 Posts
    86 Views

    Found this. Old bug since 22118 plus some odd conditions to trigger it, but I think I've got it. Build later today after I look at some other things.

  • Using InfluxDB with MSR

    3
    1 Votes
    3 Posts
    137 Views

    I have a version of the InfluxDB plugin that can query and populate the attributes of an entity, just as many other controllers do in Reactor. That's still experimental, and requires some depth of knowledge of what I regard as a rather poorly-documented query language (theirs) that is yet another learning curve. At the moment, I see it as little more than a high bar for users and a huge technical support nightmare for me, so the jury is still out on if that ever sees daylight beyond my bench.

  • git hub docker container not available?

    2
    0 Votes
    2 Posts
    114 Views

    It may be that you need to pull "latest-[flavor]" and not just "latest" eg: latest-amd64 etc. dependent on the image specific to your installation type.
    -bh

  • Synology NAS docker image replacement

    6
    0 Votes
    6 Posts
    212 Views

    @toggledbits

    Fair enough
    🙂

  • 0 Votes
    13 Posts
    323 Views

    Sorry @toggledbits . I tied it again after a good break and it appears to work fine. I honestly don't know what was going wrong but things seem to now be in order:

    pi@raspberrypi:~ $ cd reactor
    pi@raspberrypi:~/reactor $ ls
    config docker-compose.yml logs storage
    pi@raspberrypi:~/reactor $ docker-compose down
    Stopping reactor ... done
    Removing reactor ... done
    Removing network reactor_default
    pi@raspberrypi:~/reactor $ docker-compose pull
    Pulling reactor ... done
    pi@raspberrypi:~/reactor $ docker-compose up -d
    Creating network "reactor_default" with the default driver
    Creating reactor ... done

    docker-compose.yml below FYI:

    Multi-System Reactor template docker-compose.yml (version 22160) Change the lines indicated by "DO"...

    version: '3'

    services:
    reactor:
    container_name: reactor
    environment:
    # DO change the TZ: line to set your local time zone.
    # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
    TZ: GB
    #
    # DO NOT change this path. Your directory location is in "source" below.
    REACTOR_DATA_PREFIX: /var/reactor

    # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
  • Alexa TTS via Home Assistant?

    Locked
    2
    0 Votes
    2 Posts
    118 Views
  • Reactor as tab in Hass sidebar

    6
    0 Votes
    6 Posts
    232 Views

    @matohl Yessir - figured that out way too late into the night to reply 😉 Also used this to add my two Hubitats to the mix.

  • Documentation>Network Status

    4
    0 Votes
    4 Posts
    188 Views

    @Fanan Thanks for the info.
    @toggledbits Thanks for the detailed documentation. I have it working.

  • 0 Votes
    6 Posts
    268 Views

    So, following:

    cd \path\to\reactor node tools\install_reactor_windows_service.js -u . del /s /f node_modules npm rm -g node-windows npm uninstall node-windows npm uninstall -g node-windows npm install -g node-windows@1.0.0-beta.6 npm link node-windows

    ...extract the Reactor.zip over the old directory...

    node tools\install_reactor_windows_service.js -i .

    I'm now running fine with Reactor (Multi-hub) stable-22136.

    Thank you @toggledbits for your support and amazing product.

    Bonus is the SSL now works too (CertifytheWeb with LetsEncrypt will renew it and drop the key files in the correct location). That means I can have Reactor as a tab in the Hass sidebar (previously https Hass --> http reactor would not work).
    bdb4b2e7-f193-4fe1-9012-fdba37630a3e-image.png

    Ractor.yaml:
    99a5f802-c3e4-4bfa-9a29-975de1da4d28-image.png CertifyTheWeb:
    621270ab-242f-47c4-a7ee-d547ce9eb4cf-image.png Browser:
    0f4ac4f9-f330-4186-bb30-fd9cd559da39-image.png

Recent Topics