Sunrise/Sunset if/then

[CPrince]

I would like to do some more advanced sunrise/sunset programs.  Sunrise/sunset is relative to the earth and the sun, but not really the time of day.  Time of day is a constant and sunrise/sunset is variable.  With that being said if I want to to turn my porch light on at sunset -30 minutes and off 6 hours later in the month of December it will be different in July.  In the winter the light would come on around 4:30 and turn off around 10:30.  This is good.  However running this is July will turn the lights on around 8:00 and off at 2AM.  This is bad.  I thought of breaking this down in to 2 separate programs.  One to turn on the lights and 1 to turn off the lights.  However I don't want them going off at the exit same time every day.  Maybe 10 PM plus or minus 30 random minutes.  I can't see how to do a plus or minus random number.  Every controller I have worked with has had this function.

 

Another issue is the lights in th AM.  Lets say I want the lights to come on at sunrise -30 minutes but not before 5:30.  Sunrise right now is 5:30.  So the lights turn on at 4:45.  This is bad.  In December the lights would come on at 5:45.  This is good.

I am new to this device, sorry if this has been asked many times.

 

[MrBill]

For the First issue:

Schedule 10:30Pm or whatever then insert a random Wait before the action.

A random 30 minute wait till wait between 1 and 30 minutes.

aaa Test - [ID 00E6][Parent 0001]

If
        Time is 10:30:00PM
 
Then
        Wait  30 minutes  (Random)
        Set 'Pool Lights' Off
 
Else
   - No Actions - (To add one, press 'Action')
 

--------------------

For the second issue use AND

EDIT:  Actually I'm not sure that simple method will work, but this will:

Of course 6 hours is much longer than needed but I just used that value randomly.

You will not want to use an ELSE clause with this type of program.  This IF is evaluated 4 times, only once is it true, the other three times it will be false which would cause ELSE to run each time.

Also note that this type of logic can also be used with OR which would cause the THEN to run at the earliest of Sunrise-30min or 5:30AM

 

 

Edited July 25, 2021 by MrBill

[CPrince]

MrBill, thanks for the fast response.  You first solution is spot on.  I had to poke around to find the settings.  It was a great learning experience. 

The second example makes some sense, but is not clicking. I may be a bit slow. Sorry.  So it has to be sunrise -30 (4:45 currently) and 5:30. to hold off turning the light on at 5:30.  It should work today and for a few months.  But the window from 4:45 to 5:30 will be locked in because of the and 5:30?  So what happens in December? Sunrise -30 (6:00 December time) and 5:30. Won't the 5:30 make the logic false?  Doesn't the and 5:30 kinda hardwire it in?

Thanks so much!

[CPrince]

MrBill, sorry I did not see you full response to the second part.  let me review,

[CPrince]

Mr Bill,

My brain is fried.  The second example worked fine.  At first I thought it didn't.  Review of the security cameras proved that it did.  I am at a lose with the "for" argument.  I did a lot of reading on it and am no better off.  I am reading the 700 page ISY Automation Cookbook. What does the 6 represent?  I changed it to 2 as I thought it was going shut the lights off in 2 hours.  Wrong.

[gzahar]

3 hours ago, CPrince said:

Mr Bill,

My brain is fried.  The second example worked fine.  At first I thought it didn't.  Review of the security cameras proved that it did.  I am at a lose with the "for" argument.  I did a lot of reading on it and am no better off.  I am reading the 700 page ISY Automation Cookbook. What does the 6 represent?  I changed it to 2 as I thought it was going shut the lights off in 2 hours.  Wrong.

Think about it as two horizontal bars representing a start time and end time.

One is fixed and starts at 5:30 and lasts for 6 hours (ends at 11:30)

The second starts at a changing time (sunrise -30 minutes) and also has a length of 6 hours.

The program will trigger at the beginning and end of each bar, but will only be true (execute THEN) when the start of one overlaps the other.  This will be at the start of the last occurring bar.  As mentioned by @MrBill all 3 other cases will be false and execute ELSE.

If you make the 6 too small (bar length), you run the risk of one bar ending before the other starts (no overlap) so the program will never be true.  Not knowing how far your sunrise (-30 min) drifts from 5:30, I can't say what a safe minimum value is.  Also if you are using any WAIT logic in THEN; you need to make sure that after the latest bar starts, the earlier bar doesn't end less than any wait time you may have in the THEN or it will get interrupted and never finish the rest of the program.

[MrBill]

@CPrince

The explanation by @gzahar is correct.  Let us know if you have questions.  another way to write this might be using TO rather than "for"

If
        From    Sunrise - 30 minutes
        to         10:30 AM
    And From     5:30:00AM
        to          10:30 AM
Then
   Turn Light on
 

In which case the later of the two times gets the light turned on

If we instead use OR it will mean the Earlier of the two times

If
        From    Sunrise - 30 minutes
        to         10:30 AM
    OR From     5:30:00AM
        to          10:30 AM
Then
   Turn Light on

In this simple case we could probably even get away with an ELSE to turn the light off.  But keep in mind the ISY is event based, whatever events are programed in the IF clause that cause the program to "run" are going to make the IF statement be evaluated.  When it is evaluated it's either going to be TRUE or FALSE, and anytime the evaluation occurs either THEN (True) or ELSE (False) is going to run.   Else is usually happening more than people realize.

For Example, lets say you manually turned the light on in the wee hours of the morning because something special was going to happen, it's winter time so Sunrise is late, say 8am, (or sunrise -30 is 7:30).  Your expecting your friend to arrive from the airport so you walk over and put the light on at the switch at 5:15am... normally that's perfectly legal maneuver and has no effect, the light would already be ON when it was supposed to turn on.   BUT if this program had and Else to turn the light off at 10:30am, it would also turn the light off at 5:30am because 5:30AM AND 7:30AM evaluates to False and False makes the Else get executed.  So turn it on manually, at 5:30 the program runs and turns the light back off.

So when using a compound IF statement, its best to only use the THEN block and leave the ELSE block blank.  Then you would have a second program

If

   Time is 10:30 AM

then

    Turn light off.

 

 

[gzahar]

4 hours ago, gzahar said:

I am at a lose with the "for" argument.

I think I may better understand your confusion about FOR.

In a simple program

If FROM 8am FOR 2 hrs

   THEN turn lights on

   ELSE turn lights off

The FOR would control when the lights were turned off (ELSE statement).  If the ELSE statement is blank, the FOR becomes meaningless.  You have not given the ISY anything to do at the end of the FOR time.  It will not assume you want to "undo" the turn lights on (THEN statement).

[apostolakisl]

You need to understand how ISY works.  The items in an "if" clause are triggers as well as conditions.  Whenever any of the items in an "if" clause happen, the program "triggers".  At that point, if the program is currently running, it terminates where it is and starts over from scratch.  It will then evaluate the entirety of the "if" clause and the result will either be true or false.  ISY programs only are running at the instant of a trigger, or, should the "then/else" clause contain waits or repeats, it will continue running while those are valid.

IF time is 8am     . . . .8am will be a trigger and will be true only at that instant.  This program can never be true except at that instant.

If status is 25%   . . . any changes in status will be a trigger, true if it is 25%, otherwise false

If control is switched on . . . pushing the "on" side of a paddle is the trigger, no other action on the paddle does anything.  Similar to "if time is 8am", it is an instantaneous event that is only true at the instant ISY "hears" from the switch that someone hit the on paddle.

 

A program can contain lots of items, when any one of those items triggers, the entire "if" clause is evaluated as either true or false based on the entirety of the conditions.

IF time is 8am  . . . . trigger is 8am, it will only be true at that instant

If time is from 8am to 10am. . . .     two triggers, 8am and 10am, but,  It will be true if any other trigger happens between 8 and 10

If time is 8am and control x is switched on . .. .never works  both a single time event and a control event are "instantaneously" true.  So they would never happen at the exact same time.

 

Your original question seemed to say you had outside bounds that you wanted your lights to turn on.  So, you can set those outside bounds by saying 

From x time to y time.  Now the program will never be true outside of those times.

Now add, in other conditions, understand, these other conditions will also be triggers.

and time is from sunrise minus 20 minutes to y time.

Now you have 3 triggers, x time, y time and sunrise minus 20.  All 3 will trigger the program.  x time and sunrise minus 20 are "true" conditions, and y time is a "false" condition.  For a program to be true, all conditions must be true at time of the trigger.  The program is not constantly running.  Only runs at trigger events.  From 8am to 10am does not mean the program is running from 8am to 10am, it only runs at 8am and 10am.

Realize that if something else turns the light off after it has been turned on (like you manually turn it off), it will stay off.  This program only runs at those 3 trigger times.  Similarly, if you turn the light on outside of those conditions, it will stay on.

Edited July 29, 2021 by apostolakisl

[CPrince]

@gzaharYour explanation was spot on.  I read the first three words and it instantly made sense.   @MrBilland @apostolakislYou guys really drove it home with your in-depth explanations.

Thanks so much

[theojt]

I used an IOLInk and a light sensor - as you have pointed out, daylight and dusk change year round - and sometimes during storms it also gets REALLY dark - a light sensor addresses that issue.  There are various sensors - I made my own little sensor with a couple of components many years ago, but you can buy them also.  The CAO Wireless tags (Light Sensor version) works well to trigger, and if you go that route you don't need the IOLink.  Just hang the tag in an exposed window, then you create a small "KUMO" program (see wirelesstag.net) to upload the value to ISY with a REST statement.  I use two ISY programs one for dusk one for dawn - similar to the described programs above.  Works a treat and I never have to monitor/update for seasonal changes.  You will however need to replace the battery in the tag every 9-12 months.

Edited November 2, 2021 by theojt

[MrBill]

23 minutes ago, theojt said:

 then you create a small "KUMO" program (see wirelesstag.net) to upload the value to ISY with a REST statement.

A better method nowadays is to use the Wireless tag node server and not a Kumo App, although Kumo app method will still work.  (when I had 10 tags reporting temps and battery voltages via Kumo apps there were A LOT of errors and issues ongoing, since switching the the Wireless Tags Nodeserver I've had many fewer issues.)

[CPrince]

Thanks  to @MrBill and others I have pretty much mastered the sunrise sunset thing.  How every I have been toying with idea of a light sensor to work in conjunction with sunrise/sunset, for those heavy overcast days.

I am stuck in the past. I have an ISY994i IR Pro with a 300 series Z-Wave module running 4.9.0 firmware.  I want to upgrade to like 5.0.13 or something (the first 5x version) so I can incorporate my sirens and keep my Z-Wave.  On the other hand I can't find much that will operate on the Z-Wave 300 platform; so I could do without the Z-Wave.  I am just not sure where to begin.  I have read articles in this forum about going to 5, to do this you need that, and the horror stories of upgrading.  I can't find the 5.0.13 firmware anywhere.  Anyway I am not sure what KUMO and Wireless Tag Node Server is.  I am thinking I need to really do a major upgrade to use either.  My current system does about 99% of what I want it to do.  So you know, what they say, if it aint broke, don't fix it.  They also say no guts, no glory!

Anyway I was thinking of using a Raspberry Pi light sensor with a IOLink to write a value to a variable.  The sensor has 3 wires. 5 volt, ground and signal.  There is a variable resistor on it to adjust the level.   Using logic I think I can get what I need.  @theojtthanks for posting this as I will give it a try.  I just needed motivation.

[MrBill]

3 minutes ago, CPrince said:

I want to upgrade to like 5.0.13 or something (the first 5x version)

No.  You want to upgrade to 5.0.16C since you have a 300 series z-wave board.

5 minutes ago, CPrince said:

I can't find the 5.0.13 firmware anywhere.

Because you shouldn't be using it.

5 minutes ago, CPrince said:

so I could do without the Z-Wave.

If you remove the Z-wave board from your ISY then you should install 5.3.4

7 minutes ago, CPrince said:

Anyway I am not sure what KUMO and Wireless Tag Node Server is.  I am thinking I need to really do a major upgrade to use either.

Do you HAVE wireless tags?  If not, you need neither.

8 minutes ago, CPrince said:

Anyway I was thinking of using a Raspberry Pi light sensor with a IOLink to write a value to a variable.  The sensor has 3 wires. 5 volt, ground and signal.  There is a variable resistor on it to adjust the level.   Using logic I think I can get what I need.  @theojtthanks for posting this as I will give it a try.  I just needed motivation.

That's do-able...  for what it's worth... I thought i was going to augment sunrise/sunset time with a light sensor....   Truth is I just don't need it.  Where I live there might be one storm a year where it gets dark enough during the day that we might want outside lighting, but even during that storm there is really no need.

---

at this point in the game my specific advice to you... would be upgrade to 5.0.16C.   Do not upgrade your z-wave at this time.  In the future buy a Polisy, the standard version is fine, you don't need pro.

Today Polisy will run local nodeservers that work with your current ISY, in the not too distant future Polisy will also be your next ISY... running both the nodeserver software and the ISY software in one box.

Whats a nodeserver?  Curently your ISY can pretty much just have Insteon and Z-wave nodes in the device tree.  The nodeserver allows you to add more type of nodes for other devices.  Once you upgrade to 5.0.16C you will immediatly be able to use the nodesever that are available in the UDI cloud (assuming that you have a UDI portal account). You can view the node servers available in the cloud store here: https://polyglot.isy.io/store  To view the nodeservers available in the Polisy (local) store check here: https://polyglot.universal-devices.com/  (why 2 lists? some nodeservers can only run in the cloud--on UDI's servers, and some can only run on your local network--on Polisy).

It should also be noted that the local nodeservers can currently be run by installing Polyglot2 on a raspberry pi, so you can get started that way too...  At the same time tho it should also be noted Polyglot3 is almost here and that only runs on Polisy-- no Pi option anymore.

---

Upgrading is not as bad as it once was.  The single biggest problem is programs the use the "Adjust Scene" feature, they will have to be manually fixed.

(Disclaimer: Follow the real instructions in the release post as well.... I don't have z-Wave, if there is a z-wave step it won't be in my overview below.)

1) Backup your ISY

2) click the Programs tab in the admin console and click the top folder (Usually "My Programs" but you could have changed it), then right click it and pick "Copy Folder to Clipboard")

3) now open any simple text editor that won't add formatting (Windows Notepad is perfect) and paste the clipboard (ctrl-v) into the editor.  Save that file.  Now you also have a text backup of all your programs to refer to.

3A) Make sure you've read the Z-wave sections of the release page instructions (disclaimer again: I don't have Z-wave, my instructions don't include z-wave.)

4) Download the correct zip file (if you have insteon you want the first file, the second file is when you don't have an Insteon PLM) and do NOT unzip it, leave it as a compressed folder

5) Use Admin Console Help > Manually Upgrade ISY and upload the .zip file/compressed folder.

6) before logging back in after the upgrade you need to clear your Java cache and install the ISY Launcher. Basically clear your cache including "Installed Applications and Applets" (that box won't be checked by default) then once java is cleared click this link: https://isy.universal-devices.com/start.jnlp

7) the first time the ISY Launcher runs it will install an icon on your desktop called ISY Launcher in the future, use this Icon to start the admin console.

7a) You should also do Java runtime memory section of the release instructions adding -Xmx512m to the appropriate place in the java control panel.  (the 5.x admin console takes more memory than the 4.9 version you're using... personally my system is large and I use -Xmx1024m).  (Keep in mind you need to redo this anytime you clear the Java cache or after most Java updates.)

NOTE: It's in the detailed release instructions but a lot of people seem to miss it, your admin console credentials after the upgrade will be reset to admin/admin.

8 ) First thing to do when you get logged back into the admin console after the upgrade is check Help > About and make sure both the firmware AND the UI version are the same.. 5.0.16C in your case.  If you're sill on a version 4 admin console, do not proceed to the next step until you've fixed that.

9) Second thing to do is go to the "Programs" tab, "Summary" sub-tab then look for the Color YELLOW, any program with a Yellow trouble icon/message will need to be manually fixed.

10) you should be done pretty much.

 

[asbril]

51 minutes ago, CPrince said:

Thanks  to @MrBill and others I have pretty much mastered the sunrise sunset thing.  How every I have been toying with idea of a light sensor to work in conjunction with sunrise/sunset, for those heavy overcast days.

I am stuck in the past. I have an ISY994i IR Pro with a 300 series Z-Wave module running 4.9.0 firmware.  I want to upgrade to like 5.0.13 or something (the first 5x version) so I can incorporate my sirens and keep my Z-Wave.  On the other hand I can't find much that will operate on the Z-Wave 300 platform; so I could do without the Z-Wave.  I am just not sure where to begin.  I have read articles in this forum about going to 5, to do this you need that, and the horror stories of upgrading.  I can't find the 5.0.13 firmware anywhere.  Anyway I am not sure what KUMO and Wireless Tag Node Server is.  I am thinking I need to really do a major upgrade to use either.  My current system does about 99% of what I want it to do.  So you know, what they say, if it aint broke, don't fix it.  They also say no guts, no glory!

Anyway I was thinking of using a Raspberry Pi light sensor with a IOLink to write a value to a variable.  The sensor has 3 wires. 5 volt, ground and signal.  There is a variable resistor on it to adjust the level.   Using logic I think I can get what I need.  @theojtthanks for posting this as I will give it a try.  I just needed motivation.

Others are more qualified, but these are my 2 cents.

1. First you find the upgrades here .  Be VERY CAREFUL to exactly follow each of the steps.

2. You will need to upgrade the Zwave dongle to 500 series. However, depending on your urgency to upgrade and budget, you may consider to wait for ISY on Polisy to be released (no known eta) which will require a Zwave series 700 dongle.

3. It has been a long time since I upgraded from ISY 4.X to 5.X, but I had few issues, other than having to update some of my programs. Always make sure to make backups before making any change.

4. If you do upgrade to 5.X, I suggest that you go straight to 5.3.4

5.  I see that @MrBill just replied as well and he is way more qualified than I am, so he will for sure to have a better answer to your questions.

[asbril]

3 minutes ago, MrBill said:

No.  You want to upgrade to 5.0.16C since you have a 300 series z-wave board.

Because you shouldn't be using it.

If you remove the Z-wave board from your ISY then you should install 5.3.4

Do you HAVE wireless tags?  If not, you need neither.

That's do-able...  for what it's worth... I thought i was going to augment sunrise/sunset time with a light sensor....   Truth is I just don't need it.  Where I live there might be one storm a year where it gets dark enough during the day that we might want outside lighting, but even during that storm there is really no need.

---

at this point in the game my specific advice to you... would be upgrade to 5.0.16C.   Do not upgrade your z-wave at this time.  In the future buy a Polisy, the standard version is fine, you don't need pro.

Today Polisy will run local nodeservers that work with your current ISY, in the not too distant future Polisy will also be your next ISY... running both the nodeserver software and the ISY software in one box.

Whats a nodeserver?  Curently your ISY can pretty much just have Insteon and Z-wave nodes in the device tree.  The nodeserver allows you to add more type of nodes for other devices.  Once you upgrade to 5.0.16C you will immediatly be able to use the nodesever that are available in the UDI cloud (assuming that you have a UDI portal account). You can view the node servers available in the cloud store here: https://polyglot.isy.io/store  To view the nodeservers available in the Polisy (local) store check here: https://polyglot.universal-devices.com/  (why 2 lists? some nodeservers can only run in the cloud--on UDI's servers, and some can only run on your local network--on Polisy).

It should also be noted that the local nodeservers can currently be run by installing Polyglot2 on a raspberry pi, so you can get started that way too...  At the same time tho it should also be noted Polyglot3 is almost here and that only runs on Polisy-- no Pi option anymore.

---

Upgrading is not as bad as it once was.  The single biggest problem is programs the use the "Adjust Scene" feature, they will have to be manually fixed.

(Disclaimer: Follow the real instructions in the release post as well.... I don't have z-Wave, if there is a z-wave step it won't be in my overview below.)

1) Backup your ISY

2) click the Programs tab in the admin console and click the top folder (Usually "My Programs" but you could have changed it), then right click it and pick "Copy Folder to Clipboard")

3) now open any simple text editor that won't add formatting (Windows Notepad is perfect) and paste the clipboard (ctrl-v) into the editor.  Save that file.  Now you also have a text backup of all your programs to refer to.

3A) Make sure you've read the Z-wave sections of the release page instructions (disclaimer again: I don't have Z-wave, my instructions don't include z-wave.)

4) Download the correct zip file (if you have insteon you want the first file, the second file is when you don't have an Insteon PLM) and do NOT unzip it, leave it as a compressed folder

5) Use Admin Console Help > Manually Upgrade ISY and upload the .zip file/compressed folder.

6) before logging back in after the upgrade you need to clear your Java cache and install the ISY Launcher. Basically clear your cache including "Installed Applications and Applets" (that box won't be checked by default) then once java is cleared click this link: https://isy.universal-devices.com/start.jnlp

7) the first time the ISY Launcher runs it will install an icon on your desktop called ISY Launcher in the future, use this Icon to start the admin console.

7a) You should also do Java runtime memory section of the release instructions adding -Xmx512m to the appropriate place in the java control panel.  (the 5.x admin console takes more memory than the 4.9 version you're using... personally my system is large and I use -Xmx1024m).  (Keep in mind you need to redo this anytime you clear the Java cache or after most Java updates.)

NOTE: It's in the detailed release instructions but a lot of people seem to miss it, your admin console credentials after the upgrade will be reset to admin/admin.

8 ) First thing to do when you get logged back into the admin console after the upgrade is check Help > About and make sure both the firmware AND the UI version are the same.. 5.0.16C in your case.  If you're sill on a version 4 admin console, do not proceed to the next step until you've fixed that.

9) Second thing to do is go to the "Programs" tab, "Summary" sub-tab then look for the Color YELLOW, any program with a Yellow trouble icon/message will need to be manually fixed.

10) you should be done pretty much.

 

As I said, @MrBill knows better. This response should be kept visible for anyone having similar questions. Same as with some of @lilyoyo1 's detailled answers (when not debating to pros & cons of Insteon  ).

[MrBill]

14 minutes ago, asbril said:

2. You will need to upgrade the Zwave dongle to 500 series. However, depending on your urgency to upgrade and budget, you may consider to wait for ISY on Polisy to be released (no known eta) which will require a Zwave series 700 dongle.

At this point in the game, I'd recommend anyone with a 300 series board stick with it an move to 5.0.16C.  Save upgrade money and buy a Polisy instead (and 700 series z-wave stick).

16 minutes ago, asbril said:

4. If you do upgrade to 5.X, I suggest that you go straight to 5.3.4

Except as noted, if you have a 300 series z-wave board, go to 5.0.16C

[lilyoyo1]

17 hours ago, asbril said:

As I said, @MrBill knows better. This response should be kept visible for anyone having similar questions. Same as with some of @lilyoyo1 's detailled answers (when not debating to pros & cons of Insteon  ).

I've been staying out of those debates lately! That 1000+ post burnt me out from it

[lilyoyo1]

18 hours ago, CPrince said:

Thanks  to @MrBill and others I have pretty much mastered the sunrise sunset thing.  How every I have been toying with idea of a light sensor to work in conjunction with sunrise/sunset, for those heavy overcast days.

I am stuck in the past. I have an ISY994i IR Pro with a 300 series Z-Wave module running 4.9.0 firmware.  I want to upgrade to like 5.0.13 or something (the first 5x version) so I can incorporate my sirens and keep my Z-Wave.  On the other hand I can't find much that will operate on the Z-Wave 300 platform; so I could do without the Z-Wave.  I am just not sure where to begin.  I have read articles in this forum about going to 5, to do this you need that, and the horror stories of upgrading.  I can't find the 5.0.13 firmware anywhere.  Anyway I am not sure what KUMO and Wireless Tag Node Server is.  I am thinking I need to really do a major upgrade to use either.  My current system does about 99% of what I want it to do.  So you know, what they say, if it aint broke, don't fix it.  They also say no guts, no glory!

Anyway I was thinking of using a Raspberry Pi light sensor with a IOLink to write a value to a variable.  The sensor has 3 wires. 5 volt, ground and signal.  There is a variable resistor on it to adjust the level.   Using logic I think I can get what I need.  @theojtthanks for posting this as I will give it a try.  I just needed motivation.

You do not need the 500 board for new stuff. They'll still work with it. You just wouldn't take advantage of the features that 500 series devices have such as network wide inclusion, range, etc.... They'll still work though. 

I use the lux sensor in zwave motion sensor to determine when I turn my lights on. It works really well. Regardless of time, depending on occupancy of a room and situation, lights will automatically turn on off it's too dark. 

[CPrince]

@MrBillThanks again, the upgrade to 5.0.16C was painless.  Thanks for your trick on how to visually backup programs to a text file.  I actually had to use it for one program.  Now I am learning about the Node Server thing.  I am trying to set Open Weather Map up now..  

Just for the record I tried the IOLink and the Raspberry Pi sensor.  It worked, but not very well.  Very hard to adjust.  The other problem is the IOLink is very particular about where it is plugged in. I know it is old school single band. Even after plugging a dual band module into it, poor results.  It loves the outlet in the garage!

@lilyoyo1 "I use the lux sensor in zwave motion sensor"  What exactly are you using?  I found an Aeotec tri sensor.  I am looking for low light and not the absence of light.  Can your thing return a value or be set to trigger at a certain light level?

When I first stated out with ISY I bought it because of the weather module, which has since been discontinued.  I was going to use the weather to turn on the porch lights when a storm is approaching.  Here in Texas it can go from cloudy to darkness in minutes; especially in the summer.

[lilyoyo1]

1 minute ago, CPrince said:

@MrBillThanks again, the upgrade to 5.0.16C was painless.  Thanks for your trick on how to visually backup programs to a text file.  I actually had to use it for one program.  Now I am learning about the Node Server thing.  I am trying to set Open Weather Map up now..  

Just for the record I tried the IOLink and the Raspberry Pi sensor.  It worked, but not very well.  Very hard to adjust.  The other problem is the IOLink is very particular about where it is plugged in. I know it is old school single band. Even after plugging a dual band module into it, poor results.  It loves the outlet in the garage!

@lilyoyo1 "I use the lux sensor in zwave motion sensor"  What exactly are you using?  I found an Aeotec tri sensor.  I am looking for low light and not the absence of light.  Can your thing return a value or be set to trigger at a certain light level?

When I first stated out with ISY I bought it because of the weather module, which has since been discontinued.  I was going to use the weather to turn on the porch lights when a storm is approaching.  Here in Texas it can go from cloudy to darkness in minutes; especially in the summer.

The sensors that I use are fibaro motion sensors and yes they do it based off whatever value I set. I'd be surprised if yours did not do the same.

Aeotec is normally really good about their devices providing lots of information. Most likely, you'll need to download the full manual for your device to get the parameters to allow light level and set the corresponding parameter in the ISY

[CPrince]

@lilyoyo1 

On 11/5/2021 at 4:49 AM, lilyoyo1 said:

You do not need the 500 board for new stuff. They'll still work with it. You just wouldn't take advantage of the features that 500 series devices have such as network wide inclusion, range, etc.... They'll still work though.

 Did you go to 5.3.4 with the Z-wave 300 board in place?  Just curious.

 

[lilyoyo1]

26 minutes ago, CPrince said:

@lilyoyo1 

 Did you go to 5.3.4 with the Z-wave 300 board in place?  Just curious.

 

You can't go to 5.3.4 with the 300 board. I was speaking specifically about zwave devices not Isy firmware

Edited November 10, 2021 by lilyoyo1

[CPrince]

Got it.  I will get the 500 board in a few weeks and upgrade.  Thanks