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: September 4, 2021)

    • Multidimensional Array

      W

      Hi @toggledbits it is possible to have an array in the following way

      ["Window 1"]["Status On"]
      ["Window 2"]["Status On"]
      ["Window 3"]["Status Off"]
      ["Window 4"]["Status On"]

      That is, bidirectional.

      How would this array be loaded? Normally we use Variable = ${{ ["Window 1", "Window 2", "Window 3", "Window 4"] }}, how would the array pair be loaded?.

      Then the use, how would be a looping where I want to ask who has "Status On" and it returns me a new array with the part 1, that is the list of "Window"?

      Or another search, I provide the information of the content of part 1, as "Window 2" and it would return me an array with the part 2 "Satus On".

      Is it possible to have something like this?

      Could you give the examples?

      Thanks.

      Multi-System Reactor

    • [SOLVED] Help required updating nodejs on Raspberry Pi 4B - Bare Metal (without Docker)

      J

      I've recently updated to latest build 21332 and notice in the Readme file that I should update nodejs to 16.13.0 or higher before end of March. I've had a go at doing this, but think I've not done it correctly as I get the following responses in the terminal:

      pi@raspberrypi:~ $ node -v
      v14.17.0
      pi@raspberrypi:~ $ nodejs -v
      v16.13.0

      Is this correct? If not then what steps do I need to carry out to update nodejs properly.

      Any help from the group would be much appreciated.

      Multi-System Reactor

    • [SOLVED] How do I: delay a notification to fire only if the ruleset actually fires

      G

      Use case: Honeywell API gets easily flustered resulting in either one or both of my t-stats not receiving the change command/s. As such, I've written some "course correction" rulesets that basically look at the present situation and, if not matching what should be there, resends the command.

      Now... logic says if the first send didn't get thru then APIs generally aren't going to like another one right on it's heels. To combat this, I've added a Restriction to the correction ruleset that says the status must exist for 420 seconds before it will fire. This (hopefully) also prevents a race state when the real rule set AND the correction spring into action at the same time.

      I set a notification reaction to let me know a course correction had to be implemented but I've noticed that it fires even if the Restriction on the actual reaction never completes (is found unnecessary) and, as such, the correction ruleset never actually needs to fire.

      The ask: can a notification be tied to fire ONLY if/when the action actually fires?

      Hopefully that is clearer than mud.

      Solved here https://smarthome.community/post/10319.

      Multi-System Reactor

    • Using `format()` to build notification and other strings

      toggledbits

      A few new functions have worked their way into Reactor's expression language over the last couple of months, and while they are documented in the change logs and documentation, it seems some of you are not aware of them, so I'm going to pick one out and highlight it, maybe do others later...

      A lot of you build strings in expressions by simple concatenation, and there's nothing wrong with that, but there's a new function in the expression language that can help you clean things up, in particular when handling numeric values.

      I've noticed many of you will round your results either on the calculation, or in some cases, in a separate variable. For example, say we have a pair of expressions that retrieves the indoor and outdoor temperature from a sensor and the weather service:

      indoor = getEntity( 'hubitat>144' ).attributes.temperature_sensor.value' ) outdoor = getEntity( 'weather>home' ).attributes.wx.temperature

      The weather service, since it converts from degrees K in its reporting to degrees C, may have an irrational or repeating value (e.g. 8.233333333...). As a result, when you compute the difference, it, too, may have an irrational or repeating result, so you decide to round it to one decimal:

      tempDiff = round( outdoor - indoor, 1 )

      Then, perhaps you have a rule that if the differential is greater than 10 degrees, you send a notification, and the notification uses all three variables in the message string:

      ${{ 'The outdoor temperature is ' + outdoor + 'C and the indoor temperature is ' + indoor + 'C; the difference is ' + tempDiff + 'C' }}

      This is fine, except that the outdoor temperature isn't rounded, so you decide to fix that. There are at least three ways: add a round() to the outdoor variable expression, or create a third variable like outdoorRounded = round( outdoor, 1 ), or, use the round() function into the substitution expression

      ${{ 'The outdoor temperature is ' + round( outdoor, 1 ) + 'C and the indoor temperature is ' + indoor + 'C; the difference is ' + tempDiff + 'C' }}

      It's all getting very messy... Let's use format() instead of string concatenation, and not worry about rounding the difference, so we keep the maximum precision possible for any calcs or tests that use it. We go back to:

      indoor = getEntity( 'hubitat>144' ).attributes.temperature_sensor.value' ) outdoor = getEntity( 'weather>home' ).attributes.wx.temperature tempDiff = outdoor - indoor

      Now our string substitution:

      ${{ format( "The outdoor temperature is {0:.1f}C and the indoor temperature is {1:.1f}C; the difference is {2:.1f}C", outdoor, indoor, tempDiff ) }}

      Here, format() is building the message string. Each {} (curly-brace) pair denotes the substitution of a parameter to follow. The number first inside the opening curly brace is the parameter number, starting from 0 as the first parameter. So parameter 0 in this example refers to the variable outdoor, and 1 is indoor, and 2 is tempDiff. Using the numbers, parameters can be inserted in any order.

      Each of these substitutions in the example includes an optional format specification. If no format specification is given (e.g. {0}), then the parameter is converted to a string with no special formatting, but since we can get numbers like 8.233333... it's desirable to use some formatting to make it pretty. The format is separated from the parameter number by the : (colon) in the substitution. The format we're using for all three parameters is .1f, which is <width>.<precision>f. Any number before the dot is a fixed field width, but since we want no extra spaces, we just don't specify a width (it's blank for our example), and the value will take as much space as it needs. The f at the end tells format() that the value is going to be formatted as a floating point number, and the .1 before the f tells the formatter to display a single decimal digit. So our 8.23333333 value would be displayed as 8.2, without using extra functions or variables, or dropping precision in a calculation. For clarity, 10.875 would be displayed/inserted as 10.9 in this example, because the formatter will round the displayed result to the specified number of decimal digits.

      Tip: for simple string insertions that require no special formatting, format() will let you skip the parameter numbers if the parameters are in the same order as the substitutions, and the default format is (generic) string (s), so format( "{} x {} = {}", "alpha", "beta", "gamma" ) produces the string alpha x beta = gamma.

      Docs for format are in the Reactor documentation under the heading Special Reactor Functions.

      Multi-System Reactor

    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.

      Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
      Multi-System Reactor

    • Rule for devices battery level ?

      cw-kid

      Hi

      Wanted to create a rule for monitoring the battery level of Z-Wave devices on my Vera hub.

      I can select the battery level as the trigger OK.

      But not sure how to handle the Reaction to send an alert / notification ?

      If in the triggers I have multiple devices monitored for their battery level

      39a2f0af-c2e4-450b-a1ce-f542df31d02d-image.png

      How could I create say a TTS announcement or text alert that mentions the name of the device who's battery level has dropped below 10% ? The device that has triggered the rule.

      I'd rather not have to create an individual rule for each device etc.

      Any ideas?

      Thanks

      Multi-System Reactor

    • Recommendation for new hub

      S

      My trusty vera plus is starting to have some issues that are making me think that it is about to die. i now get constant luup reloads even though i've moved almost everything except for z-wave devices and the iphone locator off that machine. it is even booting off an ssd drive to minimize wear and tear on the internal memory. I've moved all my logic off box to MSR, so it is just a glorified zwave adapter. I would love to hear any ideas that would make moving 60ish devices off that box to something else as painless as possible. the thought of excluding and including the devices sends shivers down my spine, so anything that helps me migrate the network would be greatly welcomed. anyone have any suggestions?

      Multi-System Reactor

    • Pick the middle of 3 values.

      Tom_D

      I have 3 outside temperatures and I would like to pick the middle value of the 3 to use as the outside air temperature for calculations and logic.

      MSR-OSATemps.png

      The obvious, to me, mid() function does not seem to exist. What function can I use to pick the middle of the three values?

      Thanks,
      Tom

      Multi-System Reactor

    • MQTT interface... time for some testing. Where are my experts?

      toggledbits

      I'm probably going to release my first pass at the MQTTController for Reactor (aka MSR) this week. It doesn't yet intrinsically know about a lot of devices, but you can train it for pretty much anything, I think, and it would be great if a couple of our heavy MQTT users could help check it out and maybe help contribute some device templates.

      I'm hoping to package it up for mid-week, assuming the rest of life stays on track.

      Success factors for the test: solid familiarity with MQTT, a big mix of devices, and comfortable editing YAML (for creating the templates/mappings).

      Multi-System Reactor

    • MQTTController issue with reconnect to openLuup

      Crille

      Whenerver openLuup restarts or reloads Luup MQTTController can't reconnect and I have to restart Reactor to solve it.

      [latest-21321]2021-11-24T07:39:17.842Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:39:17.844Z <MQTTController:ERR> Controller MQTTController#mqtt is off-line! [latest-21321]2021-11-24T07:39:32.849Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:40:15.473Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:40:30.475Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:40:52.696Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:41:07.702Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:41:40.213Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:41:55.217Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:57:39.113Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:57:54.114Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:58:16.396Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:58:31.399Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:58:37.271Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:58:52.278Z <MQTTController:NOTICE> attempting reconnect
      Multi-System Reactor

    • MQTTController map different values from same topic?

      Crille

      I have multiple sensors connected to via Bluetooth to a Tasmota device.
      All sensors report their values in the SENSOR topic, how do I map those to individual entities?

      Multi-System Reactor

    • Safari Mac Rule Sets Menu after upgrade build 21275

      S

      I can no longer access the Rule Sets menu after upgrading to build 21275. Nothing happens when I click on Rule Sets. Other menu options work fine. I have cleared history, hard refreshed the browser, Rebooted. Works fine in Firefox and google chrome. I have always used Safari.
      Suggestions?

      Safari for Mac version 15.0
      MSR Version 21275-df3d784
      Synology Docker

      Multi-System Reactor

    • Setting Z-Wave configuration parameters for devices in EzloPlus

      N

      Hi, in Reactor there is "SendData" actions to change value for device's configurations without to use Lua. Is this possible also for MSR?
      If not, which is the possible way to do it?

      Thanks in advance

      Multi-System Reactor

    • [Solved] Logic check for the braintrust: splitting time/date triggers between rulesets

      G

      Goal: xmas tree/mantel lights go on with outdoor lights (if mode = Evening) but shut off at 23:00 whilst outdoor remain until sunrise -20. Tree and mantel should only go one when someone is home, outdoor go on no matter what, hence the mode trigger.

      Configurations
      Ruleset "Arm For Xmas" triggers = date ranges (all vetted/proven in prior years, good to go here) and sunset/sunrise:

      Screen Shot 2021-11-21 at 12.05.18 PM.png

      Ruleset "Xmas tree/mantel lights" triggers =

      Screen Shot 2021-11-21 at 12.07.29 PM.png

      Seeking confirmation that my use of start time from the "Arm For" and end time from the "Xmas tree/mantel" scene will play well together.

      Multi-System Reactor

    • [Solved] Is there a cap or max number of devices a Global Reaction should not exceed?

      G

      Noticed in the last few nights that my Global Reaction to turn on a mere six lights in the evenings the same two devices no longer turn on. One is a dimming smart bulb, the other is a wall outlet.

      This has been running flawlessly for months - just in the last few nights I've noticed these two devices being left behind and yes, it's always these two devices only.

      "What changed?"

      No Hubitat firmware updates No new devices added to Hubitat list itemTwo MSR updates (the last two, I keep up with the latest) list itemHome Assistant releases (should have zero bearing, HA is nothing more than pretty dashboards) list itemAdded MQTT to MSR

      I did do a z-wave "repair" last night and am waiting to see if this helps.

      Is there any maximum or cap on number of devices that should be included in a Global Reaction?

      *Marked as solved as the question asked was answered. The issue persists but the question was answered.

      Multi-System Reactor

    • Standard Instruction All Hubs (binary_sensor.state)

      W

      @toggledbits

      I would like to consult, and maybe even suggest, the possibility that all devices have the common attribute binary_sensor.state.

      I am in the process of switching from Vera to Hubitat, and I see huge benefits in Hubitat having very few attributes available to the devices, which makes the device lighter, and faster in my opinion.

      But one point that bothers me is for example plug and switch has binary_sensor.state which basically replicates the state of the Tripped Vera.

      In Hubitat motion devices don't have it (similar Tripped), the status is motion_sensor.state, in this case my suggestion is if it would be possible that MSR creates in these devices the attribute binary_sensor.state and equals automatically the motion_sensor.state.

      Expandindo a solicitacao (asking is not prohibited 🙂 ) to thermostats for example, I imagine that the hvac_control.mode attribute, other than "off" which means the device is "on (heat, cool)", also has the binary_sensor.state set to "true" (heat, cool) for "on" and "false" for "off".

      In summary, regardless of the hub, or type of device a standard attribute to indicate and command the "on" or "off" status, similar to Tripped that has Vera that creates a standard of the devices.

      Thanks.

      Multi-System Reactor

    • MQTTController "tasmota_generic_relay" power_switch.state always false

      Crille

      I can't get power_switch.state to reflect current state in the UI for Tasmota sonoff basic/dual/4channel pro.
      It triggers a green glow in the Entities for the device but the value is never changed to true.

      Config:

      "larmlampa_takfläkt_hall": name: "Larmlampa Takfläkt Hall" topic: "TakfläktHall" unit: "1" uses_template: tasmota_generic_relay

      Log:

      [latest-21314]2021-11-16T18:03:02.003Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=tele/TakfläktHall/STATE, payload={"Time":"2021-11-16T19:03:00","Uptime":"35T11:31:51","Vcc":3.170,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Orion","RSSI":52,"APMac":"60:F4:45:E7:68:E6"}} [latest-21314]2021-11-16T18:03:02.006Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/tele, payload={"Time":"2021-11-16T19:03:00","Uptime":"35T11:31:51","Vcc":3.170,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Orion","RSSI":52,"APMac":"60:F4:45:E7:68:E6"}} [latest-21314]2021-11-16T18:03:02.007Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/Uptime, payload=35T11:31:51 [latest-21314]2021-11-16T18:03:02.008Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/Time, payload=2021-11-16T19:03:00 [latest-21314]2021-11-17T10:30:48.246Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=cmnd/TakfläktHall/POWER2, payload= [latest-21314]2021-11-17T10:30:48.246Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=cmnd/TakfläktHall/POWER1, payload= [latest-21314]2021-11-17T10:30:48.247Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.247Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.249Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.297Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER2, payload=OFF [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER2 for takfläkt_hall: OFF [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.304Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=OFF [latest-21314]2021-11-17T10:30:48.304Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: OFF [latest-21314]2021-11-17T10:30:50.592Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.593Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.593Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.596Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=ON [latest-21314]2021-11-17T10:30:50.597Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: ON [latest-21314]2021-11-17T10:30:52.585Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.586Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.587Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.588Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=OFF [latest-21314]2021-11-17T10:30:52.588Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: OFF

      power_switch.state.PNG power_switch.state2.PNG

      I've also tried some best guessing with a custom template without success, probably because of lacking knowledge from my side.

      OT: Is ìnit in an upcoming build? Because how to handle a system restart is my next puzzle.

      Multi-System Reactor

    • Build 21313 question

      cw-kid

      I am curious what this means ?

      "New system capability button to express state of a single button or contact closure."

      Thanks

      Multi-System Reactor

    • Import Vera Rules in Docker Containers?

      LibraSun

      Did MSR running on Docker ever gain the ability to do the R4V import? I recall it being a platform limitation for those who installed it on Synology NAS in particular.

      EDITOR'S (@toggledbits) NOTE: This post was made in this thread: How To: Send TCP packet in Reaction
      To my good friend @LibraSun , SHAME! This is a textbook example of thread-jacking: question/post in a topic that has nothing to do with the OP's topic/title, starting a second thread of discussion within that topic. Bad dog! No treats for you! 🐶
      And yes, to the best of my knowledge, I'm getting all your DMs. I don't see any on this subject.

      Multi-System Reactor

    • Is it possible for MSR to act on Nest hello (doorbell pressed)?

      F

      Hi!
      I have a Nest hello, and as a integration in Home Assistent. I would want to be able to create a automation/reaction when someone press the doorbell button. The problem is that this event/service will only appear as triggers (in HA):
      3a763870-d062-4de7-be32-619120e3f90a-image.png I can't access the doorbell as an entity. I can only access it if I open the 'doorbell' device in HA.
      My question is therefor; is it possible to access the doorbell and it's triggers within MSR?
      I have MSR build 21307-1746e27 and HA core-2021.11.2.
      Have a great day!
      /Fanan

      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

    Release 1.0.0

    Multi-System Reactor
    6
    9
    340
    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.
    • toggledbits
      toggledbits last edited by toggledbits

      Well, it's July 19th, and as previously advertised, Reactor (Multi-System, aka MSR) has been published at release 1.0.0.

      Docker images are on DockerHub, and download package for bare-metal installs is available at https://reactor.toggledbits.com/download/

      Those of you with access to the Mantis Bug Tracker for the project, please continue to use it, particularly if you stick with the "latest" docker image tag (which will continue to be updated periodically, as will the bare-metal tarball). Feel free to open issues there on behalf of other users who do not have accounts if it seems appropriate.

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      1 Reply Last reply Reply Quote 11
      • PerH
        PerH last edited by

        Haven't been able to do much helping on this for a while, but after installing the release docker, and moving the rest my automation to MSR i feel the need to say:
        GOOD JOB!
        Especially to Patrick, but also to all contributors.

        Automation is now very fast and intuitive to set up, and I still havent found anything i can't do with this. No bugs as far as i've seen yet either!

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

          Thanks, @PerH , and indeed, a lot of effort by many went to get it this far. And miles to go before (we) sleep...

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          G B 2 Replies Last reply Reply Quote 1
          • G
            gwp1 @toggledbits last edited by

            @toggledbits +1 for the Robert Frost reference.

            Hubitat C-7, Home Assistant, MSR on RPi4 bare metal Model B 2GBs reactor-latest-21321-c2fda1c

            1 Reply Last reply Reply Quote 1
            • B
              Buxton @toggledbits last edited by

              @toggledbits I was able to install the container through compose, however, I had to make some changes to get it working. See below for my compose file:

               MSR:
  container_name: reactor
  image: toggledbits/reactor:latest-generic-amd64
  restart: "on-failure"
  environment:
   REACTOR_DATA_PREFIX: /var/reactor
   TZ: America/Los_Angeles
  expose:
   - 8111
  ports:
   - 8111:8111
  volumes:
   - /home/username/reactor:/var/reactor
   - /etc/localtime:/etc/localtime:ro
  tmpfs: /tmp
#  logging:
#   driver: "json-file"
#   options:
#    max-file: 5
#    max-size: 2m

              The changes I made are:
              1.) substitute "MSR" for "web" for the service name. This was just a precaution against a generic service name interfering with container management programs I use, and was not a needed/critical change to get things working.
              2.) simplify the volume syntax for binding a data volume. The syntax you have on your website caused a yaml compile error with version: '3.7' compose.
              3.) comment out the logging options. These options compiled, but threw a runtime JSON error that stopped the container from coming up:

              ERROR: for MSR  Cannot create container for service MSR: json: cannot unmarshal number into Go struct field LogConfig.HostConfig.LogConfig.Config of type string
ERROR: Encountered errors while bringing up the project.

              I hope to cut out some time next week to start forming some logic. The web UI looks great.

              B 1 Reply Last reply Reply Quote 1
              • PerH
                PerH last edited by

                There will be some syntax differences for different versions of compose, but I would suggest that you reinstate the logging options in order to control/restrict the storage space the container uses for logs. 🙂

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

                  Just installed 1.0.0 (21200), which seems to run fine on Debian chroot. Didn't find "reactor.service-example" file that was supposed to be included in the installation package?

                  EDIT: found an example from documentation, but it turned out that you cannot run systemctl under chroot 😞

                  @toggledbits or anyone, any advice on running sysinit style startup script?

                  Using MSR, VeraPlus (7.32), Netatmo, dataMine2, Sonos

                  1 Reply Last reply Reply Quote 0
                  • N
                    noelab last edited by

                    Hi everybody!
                    I was following this web site as non-member. Finally I have a new Synology Nas to try the new @toggledbits 's reactor project and this post is first of all to thank @toggledbits for his effort and passion to share his projects and to make them accessible even for those who are not a programmer. I know many of you reading the posts from the vera community and would like to express my gratitude for the advice you give to understand things. So a big Thanks and congratulations to Patrick for this new project !!!
                    I just installed MSR and I am excited to try it out!

                    1 Reply Last reply Reply Quote 6
                    • B
                      Buxton @Buxton last edited by

                      @buxton Just a follow-up to the docker compose file I listed above. The error I received for the logging option occurred because I used an integer for the "max-file" field. The proper notation should be:

                        logging:
    driver: "json-file"
    options:
      max-file: "5"
      max-size: 2m

                      Also note that for the logging section only, there are two spaces for the indents instead of one . YAML is unforgiving with formatting, so this too was corrected in my YAML file

                      1 Reply Last reply Reply Quote 0
                      • 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