JeffWLeach Posted June 15, 2014 Posted June 15, 2014 I want to test the date before going into a program folder but I don't want the year. The example is Halloween happens every year and I don't want to keep updating the year in the If test every year. I just want Month and Day without the year.
MWareman Posted June 15, 2014 Posted June 15, 2014 Take a look at this: http://wiki.universal-devices.com/index ... _Variables Its what I use to do this. Michael.
JeffWLeach Posted June 16, 2014 Author Posted June 16, 2014 Will this be supported in the Firmware it would be much cleaner and simple to do.
MWareman Posted June 16, 2014 Posted June 16, 2014 I think it was talked about at one point - but the presence of the workaround pushed it to a low priority - and there are plenty of more pressing changes IMO. I do agree, the programs are a pain to setup. Once going though they work very well.
apostolakisl Posted June 17, 2014 Posted June 17, 2014 I wrote those programs, so maybe it is my fault that ISY has not integrated this function into the firmware. I agree, it would be nice if ISY firmware had permanent variables for all of the parameters of date and time. To those programs I have since added variables for hour and minute of day which allows comparison of a time of day to a variable instead of a set value. If you are interested, I posted those a couple weeks ago to another thread.
MWareman Posted June 17, 2014 Posted June 17, 2014 To those programs I have since added variables for hour and minute of day which allows comparison of a time of day to a variable instead of a set value. If you are interested, I posted those a couple weeks ago to another thread. Missed that.... And Tapatalk is apparently not up to finding it at the moment. Can you post a thread link? Let me also take the opportunity to thank you for the programs! I use them throughout my programs. Hopefully, they won't be necessary in 5.x though...
MWareman Posted June 17, 2014 Posted June 17, 2014 Found it! Don't worry about posting. Its here: viewtopic.php?p=116049#p116049 Thanks again.
larryllix Posted June 18, 2014 Posted June 18, 2014 I agree, it would be nice if ISY firmware had permanent variables for all of the parameters of date and time. Even if UDI would allow the system information they current support in notifications to be written to variables, or just generally used in programs in place of direct values, it would resolve lots of these painful workarounds.
Xathros Posted June 18, 2014 Posted June 18, 2014 I agree, it would be nice if ISY firmware had permanent variables for all of the parameters of date and time. Even if UDI would allow the system information they current support in notifications to be written to variables, or just generally used in programs in place of direct values, it would resolve lots of these painful workarounds. I believe this is coming in 5.X -Xathros
JeffWLeach Posted June 28, 2014 Author Posted June 28, 2014 Is the ID important for State Variables? I have 3 State Variables that must have been add for MobiLinc. State ID 1-3 are for my mobile devices like the IPhone, IPad and ITouch that use MobiLinc.
JeffWLeach Posted June 28, 2014 Author Posted June 28, 2014 I don't think ID matters for State Variables it looks like you use the name. Here is a good reason to put this in the Firmware. When I imported your programs the Day of the Month in the Then and Else clause replaced $iDay.of.Month with Jeff's_4S_IPhone_Arlington_Heights because that was in ID 2 from MobiLinc being installed first. Also would this being in the Firmware eliminate the problem with the unit being off at midnight and having to run Advance one? How much work would this be to do in the firmware since you have already written this code?
apostolakisl Posted June 28, 2014 Posted June 28, 2014 ISY uses the ID number, not a name to reference variables internally. The name is only there for your convenience. If you import the programs I wrote, or for that matter any program that references a variable, it references the variable at an ID # location and then whatever name you have assigned to that number gets substituted for the number in the GUI. So, if the variable at an ID# is already being used for something else, you will either have to point my program to a different ID# or point your previous program to that different ID#. It is not terribly complicated, however, since ISY has a find/replace feature. Prior to importing the program, do a find/replace on your current programs to move their variables to locations that won't be used by the importing programs. It can be done in a minute or two. All the ID's that are used in my programs can be seen in the included screen shots.
Recommended Posts