Skip to content
  • Custom capabilities in MQTT templates

    Multi-System Reactor
    6
    1 Votes
    6 Posts
    76 Views
    toggledbitsT

    Showing off all your cool toys, eh?

    Thanks for letting me know. I'll see what I can do to make it look more presentable.

  • 0 Votes
    16 Posts
    105 Views
    toggledbitsT

    The alerts persisting is a sync problem with the alerts data object. I've found and (hopefully) fixed it for the next build. Both it and the Controller Status widget need special handing when the API connection is restarted.

  • [SOLVED]Logs permissions for Docker Install

    Multi-System Reactor
    8
    0 Votes
    8 Posts
    54 Views
    toggledbitsT

    @vezinpi said in [SOLVED]Logs permissions for Docker Install:

    from the dist-config/logging.yaml that the default is 0644 (which would work just fine)

    Yes, and that needs to read 0o644 now -- I've fixed that for the next build. The default is actually 0o640 in the code, so I've fixed the distribution template for that as well.

  • Button.Since Revisited

    Multi-System Reactor
    1
    0 Votes
    1 Posts
    36 Views
    No one has replied
  • 0 Votes
    9 Posts
    183 Views
    CatmanV2C

    Oooh thanks!

    C

  • Hello and first network question

    Unsolved General Discussion
    9
    1 Votes
    9 Posts
    210 Views
    CatmanV2C

    Apologies for the delay. Unless you've done some vlanning, those two networks cannot see each other directly so they must be communicating via China. Unless I'm missing something!

    C

  • Lights switches for warehouse

    Unsolved General Discussion
    6
    0 Votes
    6 Posts
    70 Views
    PablaP

    @sammybizz there are quite a few options out there, best to look into what suits your needs best

  • Catch-all lights rule

    Multi-System Reactor
    7
    0 Votes
    7 Posts
    78 Views
    G

    @toggledbits sorry for the delay, day job has a rude habit of interfering in fun.

    This solution worked perfectly for this need. It's actually quite similar to how I control the outdoor garden fountain, HVAC, and some other things. As usual, I tried to over-complicate things.

    EDIT: in fact, I find I am using this EXACT method for my outdoor LIFX lights. sigh

    I am still looking for that context. Will provide when I locate it.

  • Throttled problem

    Multi-System Reactor
    15
    0 Votes
    15 Posts
    156 Views
    toggledbitsT

    OK. That's enough info to determine it's a NUT problem (or driver problem), at least.

    You may want to look at this. You should be troubleshooting at the Network UPS Tools level, looking at your (operating) system log files. Restarting the service isn't going to fix it.

  • Dynamic Alert Based on Tripped Expression

    Multi-System Reactor
    3
    0 Votes
    3 Posts
    58 Views
    T

    This is fantastic (and I’m sure is covered in the manual - oops). Thank you, @tunnus

  • 0 Votes
    6 Posts
    76 Views
    CrilleC

    Thank you! toggle.toggle is back in business.

  • [Solved] Local expression evaluation

    Multi-System Reactor
    7
    0 Votes
    7 Posts
    81 Views
    V

    @tunnus @toggledbits Thank you both for all your explanation.

    Much appreciated.

  • Apple Home Automation Issue

    How-To
    2
    1 Votes
    2 Posts
    58 Views
    CatmanV2C

    What is the trigger for the Apple Home automation? Any screen shots might help

    C

  • 0 Votes
    7 Posts
    175 Views
    M

    @gwp1 I have no doubts that MSR is a great tool for sure when you use more than one platform.
    But sorry I repeat myself... my goal is to only use Home Assistant in the near future and I will migrate step by step from Vera.
    If I can not do all automations in HA I will most certainly seriously consider combining HA with MSR.

    In the meantime I have found the answers on my question myself.

    http luup request to get values of sensor data/variables from Vera.
    Example for a rain sensor:

    http://192.168.1.xxx:3480/data_request?id=variableget&DeviceNum=xx&serviceId=urn:upnp-org:serviceId:RainSensor1&Variable=CurrentRain

    Within Home Assistant I created RESTful sensors to get the data in.

    And it works great.

  • [Solved] Migrating MSR to Docker on Proxmox

    Multi-System Reactor
    12
    0 Votes
    12 Posts
    241 Views
    G

    To bring this all full circle, I had installed Portainer just to see what it was/did. Rereading the manual for MSR I stumbled across Portainer-specific instructions.

    Short story long, I deleted the original container and created a new one thru the Portainer path. Done in mere minutes, runs flawlessly and I don't need to worry about the docker-compose errors I was getting.

    Going to mark this topic as solved as all of the three issues were addressed.

  • 0 Votes
    6 Posts
    95 Views
    B

    Confirming that 25016 has indeed resolved the error.

    Thank you !!

  • 5 Votes
    116 Posts
    16k Views
    toggledbitsT
    Reactor build 25016

    HOME ASSISTANT NOTE: Versions of Home Assistant earlier that 2024.1.0 are no longer supported. They may continue to work, but I won't be troubleshooting any issues that come up with them. Generally speaking, HA releases are supported one year in arears from current.

    NODEJS V18 EOL: If you are using nodejs version 18, it will go off maintenance on April 15, 2025, and is therefore now deprecated. Please update to a more recent version before this date. Even-numbered LTS versions are recommended. Version 20 will go EOL in April 2026, and version 22 (recommended) in 2028.

    Reaction List: Fix an error thrown when creating a new Reaction. Dashboard: improve display of ValueSensor class objects for capabilities temperature_sensor, humidity_sensor, battery_level, and volume. HassController: Support new vacuum activity attribute and values (see HA 2025.1 release info). HassController: Support state for lawn mowers. HassController: Add x_hass_system.reload_configuration and x_hass_system.restart actions. HassController: Bless Hass to 2025.1.2
  • 'Random' lights turning on

    Unsolved General Discussion
    12
    0 Votes
    12 Posts
    139 Views
    M

    Have you asked the wife? Mine likes to randomly turn lights on (never off!) just to get me confused 😁
    Cheers Rene

  • 0 Votes
    3 Posts
    121 Views
    CatmanV2C

    That's fabulously clear. Thanks, as ever

    C

  • 0 Votes
    6 Posts
    124 Views
    cw-kidC

    OK thanks, I think that works!

    So I have two rules now the main 1st rule that detects Motion on the IP Camera and also a Virtual Switch must be True, those are the two triggers, this is the rule with the Actions in it.

    In the Constraints I am referencing the "Rule State" of the 2nd new rule and that must be False.

    ffb990d2-5b0f-419f-88e3-4cde28ed51b0-image.png

    This is the new 2nd rule and I have just used the Triggers with the "Changes" operator.

    So if any of these devices change their state within the X number of Seconds the OR group will be True thus the 1st main rule would NOT run its Actions in that case.

    But if none of these devices have changed their state within the X number of Seconds the OR group will be False thus the 1st main rule would run its Actions.

    e972131c-82e8-44b6-819f-dfe9a217692a-image.png

Recent Topics