Announcement

Collapse
No announcement yet.

Daily Reminders

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wadenut
    replied
    A week later, I've been keeping a close eye on my own reminders (over 50) and things do appear to be working as expected.

    One thing I've been thinking about is the redirection function. I have little use for it myself although I think I could apply it to several of my items.
    The function itself might be worked on. I'm thinking a separate field might be preferable to incorporating redirection into the reminder text itself (this, remember was an afterthought and done on request). The modification should be simple enough.
    Last edited by Wadenut; March 15, 2016, 09:32 AM.

    Leave a comment:


  • Wadenut
    replied
    V2.31 was a bad version. I'd left some test code in place and didn't notice until after several of my working reminders executed and were rescheduled to a much later date than intended. SORRY. It would be a good idea to check the new dates on any reminders which may already have run.

    The ASP Page header works now in HS3. You'll want to change the configuration option to TRUE in order to use it.

    Fixed the bug mentioned in my last post.

    Leave a comment:


  • Wadenut
    replied
    Ran into a small bug.
    When entering a reminder, and using Start and Stop dates, the Next Date field may be left blank by design. If this is done, the script will attempt to fill in the missing data with the next valid date for the reminder.

    If the Start Date is a defined date, and the Next field is left blank, you may encounter an error. This is simple to avoid by entering your own Date in the "Next" field for now.

    I have this repaired, but I'll hold off posting another update until other potential bugs have had a bit of time to surface.

    I apologize for any inconvenience.

    Leave a comment:


  • rprade
    replied
    Originally posted by Wadenut View Post
    I assume you mean the devices created by the script.

    I just had a check; there should be no problem changing the locations.

    The script does check to see if the devices exist but only looks at the Device Code. If you were to change that without updating the INI file, then the devices would be recreated; but the location is only used in the initial creation of the devices.

    If the need arises to update again, I'll include this in the doc. Thanks for bringing it up.
    Yes, the three devices.

    Thanks. I just wanted to make sure before I moved them to new locations. There other plug-ins that I've broken by changing the locations. I won't change the device code.

    Leave a comment:


  • Wadenut
    replied
    I assume you mean the devices created by the script.

    I just had a check; there should be no problem changing the locations.

    The script does check to see if the devices exist but only looks at the Device Code. If you were to change that without updating the INI file, then the devices would be recreated; but the location is only used in the initial creation of the devices.

    If the need arises to update again, I'll include this in the doc. Thanks for bringing it up.

    Leave a comment:


  • rprade
    replied
    I just installed and am beginning to configure. Something I do not see covered in the docs - can I change Location 1 and Location 2 without breaking the function?

    Leave a comment:


  • Loup
    replied
    Originally posted by Wadenut View Post
    Version 2.3.1 for both HS2 and HS3 is posted in the library.

    There are quite a few modifications and improvements including Date Range validity for reminders, some format changes and a few more added features.

    Redirection is now fully supported in HS3 as well as in HS2. This is quite a powerful option and deserves study/attention.
    Great, thank you.

    Leave a comment:


  • Wadenut
    replied
    V 2.3.1 Posted.

    Version 2.3.1 for both HS2 and HS3 is posted in the library.

    There are quite a few modifications and improvements including Date Range validity for reminders, some format changes and a few more added features.

    Redirection is now fully supported in HS3 as well as in HS2. This is quite a powerful option and deserves study/attention.

    Leave a comment:


  • Wadenut
    replied
    Looking at the Redirection function I've realized it's much more powerful than I'd remembered. I've decided to update it to make it compatible with some of the changes I've made to the main script, and at the same time, develop a version for HS3.

    The work on the Redirection script shouldn't be too involved. I have the main script running on two machines now and it seems to be where I want it to be. The second machine is testing a variety of Date combinations (15 permutations in all) so any problems should appear there.
    Last edited by Wadenut; February 25, 2016, 06:15 AM.

    Leave a comment:


  • Wadenut
    replied
    On putting the new documentation together, I realized one function of this package had been unjustly overlooked. That being it's ability to redirect output to other programs or plugins, send SMS or email messages, and to control Homeseer devices and run other Events or scripts when reminders execute. I admit, I don't use this function myself, but it was included originally at the request of a user.

    An example script had been provided originally but had never been fully tested nor, I admit, completed. I've just looked at this script and found I'd added a number of notes and trace logs to my copy some time in the past.

    My question is this: Is it worth my time to put any more effort into this auxiliary script (while at the same time producing a version specific to HS3) or not?

    If there are no responses, I'll assume there is no value to be added and won't waste my time on it. Regardless, the existing example version will still be included.

    Leave a comment:


  • Wadenut
    replied
    Looks like we're a GO.
    I put a copy on my production machine this morning. If all goes well for a few days (and I don't think of anything more to add), the new version will be posted within a few days.
    All that remains now is to update the documentation.

    Leave a comment:


  • Wadenut
    replied
    Originally posted by Loup View Post
    Wow, talk looks promising.
    Shouldn't be long now. A few finishing touches & a couple of new additions.

    Leave a comment:


  • Loup
    replied
    Originally posted by Wadenut View Post
    Sorry it took so long, but I've been working on this for the past day or two. Too many projects on the go at once. It's running now on HS3. I need to verify every possible condition, which could take a few more. Looking good so far. When I'm happy with this, I'll also test it under HS2.

    You'll be able to define a Start and Stop date for each reminder. The Start and Stop can be defined to occur on a yearly basis or can be defined as one time periods: June 3/2016 to July 9/2016 for example; or June 3/Y to July 9/Y to occur every year.

    Stay tuned.
    Wow, talk looks promising.

    Leave a comment:


  • Wadenut
    replied
    Originally posted by Loup View Post
    A small question: I remember the event that are only in the summer or else only the winter. When reminiscent of summer must end, I must simply remove the plugin and redo one by one when summer is back. Would it be possible to have an end date for certain event (Recalls)? thank you
    Sorry it took so long, but I've been working on this for the past day or two. Too many projects on the go at once. It's running now on HS3. I need to verify every possible condition, which could take a few more. Looking good so far. When I'm happy with this, I'll also test it under HS2.

    You'll be able to define a Start and Stop date for each reminder. The Start and Stop can be defined to occur on a yearly basis or can be defined as one time periods: June 3/2016 to July 9/2016 for example; or June 3/Y to July 9/Y to occur every year.

    Stay tuned.

    Leave a comment:


  • Wadenut
    replied
    Originally posted by Loup View Post
    A small question: I remember the event that are only in the summer or else only the winter. When reminiscent of summer must end, I must simply remove the plugin and redo one by one when summer is back. Would it be possible to have an end date for certain event (Recalls)? thank you
    You'll be happy to know that in the next version you will be able to schedule start and stop dates for reminders in addition to the current methods. You'll also be able to specify day/month start and stop for all years, as well as absolute start and stop dates.
    Ie: May 3, 2015 to Sep 12, 2015, or Nov 12, 2015 to Feb 15, 2017, as well as May 15, Y to Sep 30, Y Or June 1, 2015 to Oct 31, Y. (Where a 'Y' will fit any year). The schedules can span year end as well.
    There will be no loss of information and no need to manually adapt your current data file. The conversion will be automatic and should be backward compatible.

    I have all this working now, but I've had to shelve it for a while to work on other projects. I want to test various aspects of the new feature some more and also need to work on another planned feature before I can release this.

    HS2 and HS3 versions will be released.

    Leave a comment:

Working...
X