Multi-System Reactor

711 Topics 7.0k Posts
  • 0 Votes
    1 Posts
    214 Views
    No one has replied
  • How to HTTPS

    6
    0 Votes
    6 Posts
    454 Views

    @gwp1 Your certificate won't work then

    C

  • 0 Votes
    7 Posts
    299 Views

    This code is now obsolete because the latest versions of both MSR and MQTTController have this behavior natively. I'll leave it just in case someone wants to look at some code enumerating/saving attributes.

  • 0 Votes
    16 Posts
    862 Views

    Awesome, that did the trick!

    Screenshot 2024-04-25 at 9.31.15 AM.png

  • Can't Restart Reactor - Corrupted SD Card?

    7
    0 Votes
    7 Posts
    405 Views

    To close this thread out, it wasn't a Reactor issue. My Rpi 3B+ was simply overheating and throttling processes. Moved to an Odroid N2+ with a heatsync running Ubuntu and everything is running smoothly!

  • Post-DST and MSR not reflecting local time

    18
    0 Votes
    18 Posts
    2k Views

    @toggledbits yeah, I just got new hardware and am considering moving to the containerized version. But that's going to take some time as it's tech I've not played with before and my day job + new puppy haven't left much dev hours these months. 🙂

    MSR is now very integral to the operation of this house so I need to tread carefully when poking the proverbial bear.

  • 0 Votes
    3 Posts
    231 Views

    Rene,

    You don't need all that, this should be sufficient:

    select_capabilities: power_sensor: attributes: value: true

    or the equivalent, using an array of attribute names (my favorite):

    select_capabilities: power_sensor: attributes: [ 'value' ]

    or using the other YAML array syntax:

    select_capabilities: power_sensor: attributes: - value

    You can also use a negative to suppress an attribute:

    select_capabilities: power_sensor: attributes: [ '-units' ]

    Also, can I ask that you go back and fix the formatting of the code sections of your posts, for the benefit of future readers looking at your question and example solution?

  • Need guidance on local MQTT capabilities

    5
    0 Votes
    5 Posts
    274 Views

    Ah, if I only known what to search for or had a really good memory I would have found ev_charger announced here but not listed in Standard Capabilities 🙂

    My charger seems to ignore out of range values as well so ev_charger was the missing piece in my quest, thank you @therealdb.

  • 0 Votes
    5 Posts
    391 Views

    Just finding this but defo interested.

  • Hubitat "hubitat" is reconnecting alert

    2
    0 Votes
    2 Posts
    200 Views

    I have also encountered this problem on a recurring basis. I tried many different approaches - reboot RPI, restart MSR, reboot hubs - to correct the issue, usually without success. Earlier is week I decided to try something different. I "repaired" the "Hub Information Driver" using the Hubitat Package Manager. As so I the "repair" was complete on the hub, the problem disappeared.

  • JS Zwave / Kwikset PIN codes

    2
    0 Votes
    2 Posts
    197 Views

    You would likely need to use the x-hass.call-service action on the lock entity and your service ID would be zwave_js.set_lock_usercode. In the data portion you'd have to fill out the code_slot and code. Note that this will not work if your lock isn't securely included with your HASS controller.

  • 0 Votes
    4 Posts
    205 Views

    @apocalypsehobby please read the posting guidelines, a pinned post in this category. There are some specific requests for log files and snippets.

    Also rgbcolor.set takes a hex color code or decimal equivalent. It's probably not what you want to be using. set_rgb is more common.

  • 0 Votes
    5 Posts
    302 Views

    Thank you! That really helps. The zero-sized storage/states/cs-rule-ll4rewlj.json is the only file you need to remove. Just stop the container, remove the file, and restart. That should clear it. The data in that file will be rebuilt.

  • ZWaveJSController - open/close reversal

    3
    0 Votes
    3 Posts
    167 Views

    @toggledbits It seems that the blinds reversed direction. There's a setting in HA's ZWaveJS UI:

    22849767-a6c2-43f1-8850-86a75b2e1c29-image.png

    This was set to No and the result was the blinds closing tilted up on the inside. After deploying 23326 they close tilted down on the inside. I needed to change this setting to yes for each blind in ZWave JS UI and also any Reactions that had partial open percentages from .8 to .2 (for instance) to have the blind open 20% from closed.

    I tested this thru MSR ZWaveJSController with cover.open and cover.close as well as position.set and the results were consistent: 180° opposite of what they were before 23326.

  • 0 Votes
    10 Posts
    401 Views
  • 0 Votes
    3 Posts
    153 Views

    That setting is in Users & Account Info - Security - Enable potentially unsafe lua code, like wget and RunLua.

    It was unchecked. I checked it again and Reloaded the engine and it started working again. I am not sure how that setting got turned OFF as I didn't do it.

    But thanks anyway for pointing me in the right direction !

  • Expression for Seconds Left in Day

    Solved
    3
    0 Votes
    3 Posts
    141 Views

    Exactly what I needed thanks Patrick!!

  • Widgets and filtering

    10
    0 Votes
    10 Posts
    302 Views

    @toggledbits I was thinking of the list of running tasks as "Set Rules", a simple way of having this query.

  • Feature Request: Disable Individual Actions

    2
    1 Votes
    2 Posts
    132 Views

    If you use groups in your reactions, you can disable those individual groups, might help a little

  • Actionable notification question

    7
    0 Votes
    7 Posts
    192 Views

    I realize the documentation on configuring event handlers isn't great. I've made some updates and will post them later today, but I still feel it needs work. Feel free to ask questions and make suggestions; then I'll know what holes to fill.

Recent Topics