[Released] Rule 4.0

[corerootedxb]

Quick question. How do you turn off the lights after they have come on? Do you want them on a timer or is it always going to be manual (aside from the lux reading)?

[pcgirl]

The lights will go off if the Lux goes above 4500. They will also go off at night when my house changes modes.

[ourmessages]

How do I get RM 4 ( or motion lighting ) to have it go back to how it was before motion occurred after a 5 minute delay. Like I had in RM 3. I think I need an action for false, but can’t figure out how to accomplish this with the latest RM.

[2ac16mo]

Try this Rule 4 rule.

[ourmessages]

thanks, RM3 was so much less "work" to create. I understand RM4 has more capabilities overall but a lot of people (like myself as i can never figure out the order) create logic statements from scratch.

[bravenel]

@ourmessages

RM3 was so much less "work" to create

You can still use RM3. If you created a Rule 3.0 Clone Master before updating to 2.1.5, you can go on creating RM3 rules (see this post). If you updated to 2.1.5 before doing that, you can roll back to 2.1.4 and create the Clone Master rule, and then update again to 2.1.5. The Clone Master rule allows you to continue to use Rule 3.0. This ability and all existing Rule 3.0 rules will continue to work.

[mike]

This is what I ended up with.....seems to work well. The other example I posted you didnt work. I run my own virtual zone motion controllers to do things like this and specific cancellable times.

[jaffa_brown]

Hi all,

I seem to be having the exact same problems as everyone else with motion sensors - but I dont get why mine is not working.

I have 2 motion sensors and a power monitor - basically I want that if either of the 2 motion sensors are tripped OR the power is >= 3 then set a flag (virtual switch) that we are still up - but if these conditions are not met, after 50 minutes, change the flag of Still Up to Off.

It sets the flag correctly (when I trigger the sensor) but wont reset the flag after an hour of no activity. What am I doing wrong?

[corerootedxb]

Can you enable logging on the rule? I wonder if perhaps the power meter might be throwing it for a loop.

[homeauto2112]

Did you ever get an answer to this? I'm trying to build a HTTP GET line to use the search function of my Sonos and I need to insert a variable in the URL.

[Ryan780]

It was ":" screwing things up in the %now% field. Other variables work fine.

How are you going to parse the response from your Sonos?

[homeauto2112]

Sono Integration: How do I play music from HE to Sonos?

okay...Here's what I have so far. I created a variable called music_search and then created a connector for it. I put it on the dashboard and then created a rule to add a plus when more than one word is typed into the box. I can't seem to get the http line to accept the variable. [09%20PM] [20%20PM] [53%20PM] Any ideas?

[homeauto2112]

Were you ever able to get his working as a GET? I asked you in another thread and you mentioned something about time. I'd love to have a solution to:

Sono Integration: How do I play music from HE to Sonos?

@bravenel Well, I am running the node.js on a Mac and I setup tcpdump to watch for incoming traffic from the HE hub to trying to emulate your experiment. When I use any of the commands I have programmed, I see traffic between the HE and my server. All seems to work well. When I include a % as a variable indicator no traffic is seen coming into the server. The only time it does is if it's followed by a 20 (as in %20 to denote a white space). No incoming traffic from the hub to the Mac. As s…

[Ryan780]

If you set the URL formatting yourself, it still doesn't send the request? That's a little surprising. I would have thought that would have worked. The only solution I cam up with is to change over to sending POST messages instead of GET. That way I could send anything I wanted in the field since they'll be quoted.

[kv1]

I want to go back to RULE 3.0. Not a fan of 4.0 so far. Thing is I updated the firmware last night and it looks like I no longer have the option to create a 3.0 rule. How do I do that?

Thoughts? and THANKS!!!

[aaiyar]

@kv1

I want to go back to RULE 3.0.

Revert to an earlier platform version. Create a clone master as described by @bravenel here:

Pending Retirement of Rule 3.0

Rule 3.0 Retirement At some point in the not distant future, we will retire the ability to create new Rule 3.0 rules (most likely in Release 2.1.5). This retirement in no way will affect existing Rule 3.0 rules. All existing rules will continue to function as before, and will continue to be editable. There is no need to convert Rule 3.0 rules to Rule 4.0. The only difference will be that the main page of Rule Machine will no longer offer a means to create a new Rule 3.0. Because of the sha…

Then update to 2.1.5. You will have a permanent clone master to create Rule 3.0 rules.

[kv1]

Thank you.

[arnoud]

I am really struggling with rule 4.0
I get the if then else...but I want 2 conditional actions after 1 condition.

Select Actions for Home Lights ON when lux<500

IF ( NOT Mode is Night(T) [TRUE]) THEN
ELSE-IF (Illuminance of Illumination Sensor(250) is < 500(T) [TRUE]) THEN
On: Lights@Night
ELSE-IF (Illuminance of Illumination Sensor(250) is > 550(F) [FALSE]) THEN Off: Lights@Night END-IF

I am not sure if this is actually correct. What is better to do this multiple conditions? I do skip 50 lux to avoid lights on and off all the time if around a treshold value..
I also have to say that the interface is very confusing and pretty unforgiving if a line is placed in a wrong space. No real way to move a condition or action.

Feedback is appreciated and hopefully I will get the hang of this 4.0.

[jabecker]

You want to use a nested IF rather than ELSE-IF, I think. Something like this:

IF ( NOT Mode is Night) THEN
    IF illumination < 500 THEN
        turn on lights
    ELSE
        turn off lights
    END-IF
END-IF

The ELSE could be an ELSE-IF, but it's not really necessary since that IF contains only 2 conditions.

[arnoud]

thanks, there is a second condition..the illumination > 550. this rule above would only switch lights off at 500. Maybe the else must have the if added there?