Skip to content

Multi-System Reactor

748 Topics 7.1k Posts
  • ARM61 Supported?

    Locked
    2
    0 Votes
    2 Posts
    150 Views
    toggledbitsT

    I don't even see a binary for ARM61 for node.js in a current supported version. I think that's a non-starter.

  • Simple Time action running late

    Locked
    6
    0 Votes
    6 Posts
    204 Views
    toggledbitsT

    I never assume people do what I ask them to do. LOL

  • Why is this Green and ticked when its not true ? And how to do OR

    Locked
    19
    0 Votes
    19 Posts
    446 Views
    cw-kidC

    @toggledbits Just updated to 0.1.21051 and I can confirm its now working with my Thermostat and the trigger >10

    10 or below is false and 11 or above is true.

    Thank you

  • Sunset with offset didn't run

    Locked
    34
    0 Votes
    34 Posts
    1k Views
    cw-kidC

    The sunset never became true the lights didn't turn on. I changed it to "after"

    I've deleted the rule and created it again from scratch. See what happens tomorrow.

    UPDATE:

    This worked today using Constraints instead of having everything in Triggers.

    ed4317d5-d33b-4ea2-91a1-51e05a76d5cd-image.png

  • Units

    Locked
    2
    1 Votes
    2 Posts
    92 Views
    toggledbitsT

    Yes! Please open a PR for this. I had a feeling that something like that was going to come up, so I already have some hooks that I just need to finish.

  • Can anyone confirm this bug

    Locked
    2
    0 Votes
    2 Posts
    137 Views
    toggledbitsT

    A bug of a sort... the Set Variable condition has not yet been implemented as of this release. The open PR/reminder for that is 0000005, and you can click the "Monitor" button on that bug to get an email when its status changes.

  • Continuous triggering

    Locked
    2
    0 Votes
    2 Posts
    108 Views
    toggledbitsT

    OK. Can you open a PR on the bug tracker? I'll take a look...

  • Play buttons on the Set Reaction area

    Locked
    9
    0 Votes
    9 Posts
    238 Views
    toggledbitsT

    @therealdb said in Play buttons on the Set Reaction area:

    actions are not shown, in fact.

    Right, if it doesn't know the capabilities of the device, it can't show actions because it doesn't know what they are. But it can copy existing attributes, which is the "x_vera" stuff.

    It exists today that you can write your own rules for defining a device (for all HA controllers types, not just Vera). I'm not releasing this as a documented feature yet because I still have much other work to do, and I'm trying to keep the number of variables down for the moment until things stabilize. It's also the case that if you have a local device definition and later a system definition is added, your local config would hide the system config and make debugging more difficult: for any device problem, I first have to investigate if you've made a local override or not. There are many administrative/logistical issues that go beyond just what's possible in the code.

    For things like thermostats, though, very necessary for you to be able to self-configure, because Vera itself does not provide sufficient information. You really can't reliably tell from looking at a Vera thermostat device if it's auto-changeover, dual setpoint or single with differential (or not), has fan control or not, what fan modes it has, has humidifer, has dehumidifier, etc. I don't see not relying on local user intelligence to get this done, at least for Vera. But that's slightly different from defining a device class. Overrides for a single device are planned as well, so that will encompass not just defining what capabilities the device has, but other convenience things like giving the device a nicer or more distinct name than the source controller uses (no 20 char limits!).

Recent Topics