Multi-System Reactor

691 Topics 6.8k Posts
  • 0 Votes
    2 Posts
    98 Views

    Error on my part, forgot to update the splash screen. Soldier on...

  • Does this rule look correct ?

    Locked
    24
    0 Votes
    24 Posts
    493 Views

    @pabla said in Does this rule look correct ?:

    Well done @toggledbits

    I can't take credit. When I first made contact with Hass... four? really? OK... four years ago, it was something it had that looked pretty interesting.

  • 0 Votes
    11 Posts
    554 Views

    I can't comment on the ticket now its closed.

    Yes having the new copied rule disabled initially will work, you generally then want to edit and tweak that copied rule anyway and then you can enable it.

    This will stop the copied rule just firing when you don't want it to do so.

    Thanks.

  • ARM61 Supported?

    Locked
    2
    0 Votes
    2 Posts
    113 Views

    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
    147 Views

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

  • 0 Votes
    19 Posts
    323 Views

    @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
    797 Views

    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
    68 Views

    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
    115 Views

    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
    97 Views

    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
    194 Views

    @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