Assigning A Random Variable Offset To Sunrise / Sunset


Hub Model: C-8. Platform Version: 2.3.7.146.

I read quite a few threads where individuals talk about how this function can be used so I must be overlooking something and could really use the community's clarification.

What I want to do is use the sunrise & sunset functions but assign a random offset to give the house that lived in appearance so I am attempting to use this function:

versus this function which appears to assign a fixed offset:

The issue that I am having is that when selecting the variable offset toggle the adjacent drop-down box is empty. I was anticipating a range of minutes to select from in the drop down list to limit the range of minutes that would be randomly changed (at what intervals I am not sure). This "range of minutes" would be so at sunset / sunrise + or - this random offset range would give the changing appearance (preferably daily) of someone turning the lights on & off at different times (sunset / sunrise + / - random range of minutes selected in the drop down box).

Am I way off on this one?

As always thanks for anyone's insight.

Don

Blame the English language ….one word having multiple meanings. Variable in this context means a predefined private or global hub variable, NOT a range of values.

2 Likes

Like @fritz mentioned, you need to create a Number variable and reference that from your rule. You can then use another rule to randomize the variable value.

image

2 Likes

I knew I was missing it. Thank you so much!

Don

2 Likes

if you are trying just to turn lights on and off randomly after sunset check out vacation lighting director

Thank you. I will check it out!

Don

yet wouldn't it be a nice feature in there (right where you need it) to allow some random variability in a given offset range, between say -x and + y, for exactly the very common use he was trying to achieve.

Zip zap zippity... done.

Agree. Having the ability to simply select an offset with the + or - option and have it randomize that range would be a nice enhancement to the product. This "build-in" would much more easily add an excellent security feature of having the "at home look" while at home or away.

Although writing two rules and creating a variable is not difficult to do, it would add the ease of use to a considerable population of people who would benefit from the simplicity of click and select for a basic premise of home automation such as lights on and off with a randomized offset. The reality is; the easier the product is to use, especially for these types of basic functions, the more people will use it.

That being said; like everything, the key is balance. I WOULD NEVER want to see HE be "dumbed down" to a point where it does not have flexibility of vast number options included HE and the integrations capabilities provided by Package Manager, etc. Flexibility and options bring with them complexity. However, there is also a large group of us who want these advance capabilities and understand the need to work through the logic to get there (and quite honestly enjoy it),

On a side note, I have seen no other app that is documented as well as HE (sometimes the document updates lag behind revisions but it is a work in progress). However; the documentation combined with the forum, and the monitoring of the forum by HE support I can genuinely say I have seen no other product that does what HE does. Just my opinion so no offense intended to anyone and I don't want to debate my opinion :slight_smile:

Way too much coffee this morning :-).

One last example of what seems to be another straight-forward use case I would like run by everyone. Would it be a reasonable expectation / desired to be able to programmatically; using a built in function, shutdown the hub upon loss of commercial power?. I say this since you can shut the hub down now through a build-in function through the setting interface.

Use case that many of us have talked about . I receive a notice that commercial power has been lost (open switch that is on its own battery). RM detects open switch and issues a graceful showdown of hub which is supplying power. Of course password would be needed for any such non-hands on keyboard requests. I do understand it can be done with 3rd party apps but this is another example this type of "built-in" functionality" would improve the improve the product's out-of-the-box ease of use and therefor would become even more receptive to a larger audience.

Something for the forum to provide input on and for HE support and the company to ultimately to consider.

As always thanks for your time.

Hope everyone has a great weekend!!

Don