hart2hart

Thanks. Ages ago there was advice that it created issues of its own. Do you think that has all been resolved or maybe it was just the logic got out of sync so no real "fix" was coming.

I knew this was an issue but I've never taken time to think it out. Can I get your thoughts? I've got HVAC programs that run primarily by time of day to set temps. Following is an example for Master Suite sleeping temps. Last night about 10:00, I discovered the eISY was "hung" so pulled power and it restarted -- looked good on restart. However, I noticed my setpoint temps for Master Suite were not properly set when I was getting ready for bed a little later. The program to set sleeping temps runs at 9:00 so it is ready when I turn in. What do you put in programs in case eISY was hung like my case or maybe if a power failure occurred while it was supposed to run? I learned after I wrote these that the time function is only used to schedule running (if) start time and the end time. A state variable could be included in if it was within that time frame is my first thought (no sure what it would be other than something that ticked a variable on/off and forced all stuff like this to evaluate the If every 10, 15, or 30? minutes) but I'm sure one of you has a superior method to accomplish this so it's good in event of an issue at start time. HVAC:Master Temp For Night If From 9:00:00PM To 6:29:59AM (next day) And $HVAC_MasterSuite_Override_Programming is $Not_Overridden_I Then $Thermostat_Master_Temp_Setting = $Thermostat_Master_Night_Temps_I Else - No Actions - (To add one, press 'Action')

The knowledge of how to migrate from one platform to the next ages / gets dim quickly. Therefore, you may wake up one day to a relatively complex task with little current support. Same story for all technology and especially when it’s getting to be 10-15 years old.

Has anyone tried the Eyez-on DSC clone board?

Thanks. I’ll try to pay a bit of attention to it and report to them if they are mixing it up.

Thanks @bpwwer . So that I'm clear, are you describing when I restarted the eISY that the plugin requested data to populate fields and that WeatherFlow responded with the NC rainfall? EDIT: My plugin config is for local but it reported the NC amount. Does that mean on restart that it got remote data to populate fields (NC)but that data should have been updated with local data?

Thank you @Goose66 for updates to Schlage and EnvisLink-DSC plug-ins. Now unlocking the door can use a code to disarm security. Great when you have your hands full coming into the house! Using Entry Delay worked great to trigger Force Update instead of lowering short poll which would potentially cause issues.

What node are you calling NC? I only see/have Daily Rain in eISY. Do you have NC rain enabled in the WeatherFlow Tempest app? I do not have NC enabled. We have lots of highly scattered storms here in middle Tennessee, so NC is often off since it averages around you -- manual rain gauge verified that at Tempest haptic station readings are much closer most of the time. I get a daily message (right after midnight) with rainfall from previous day that I use to decide whether to run sprinklers the next day. Yesterday's rainfall message looked lower than recalled from glance during a hard pop-up rain event. Looked back and sure enough it was the NC amount and not the local at the station amount. Is this what you are describing? That said, maybe WeatherFlow have decided to always substitute it, or they have done it accidently. EDIT: I restarted the eISY a couple times yesterday working on a ZWave issue and it was well after the rainfall. Is this suggesting plugin may have picked up the NC amount after the restart even though we don't have NC enabled?

@Goose66 , this is fantastic! It worked as wanted and expected! Following are two test programs that uses Schlage Encode opening to disarm DSC Security system via your very own EnvisaLink-DSC. Garage:Entry Delay Disarm With Schlage Code - Catches Entry Delay so it can Force Update If 'Security System / Security System:Partition' Partition State is Entry Delay And 'Security System / Zone:Interior Garage Door' Zone State is Open Then Set 'Garage / Garage Door' Force Update Garage:Internal Deadbolt Unlocked By User 1 - Catches user that opened Schlage deadbolt so we can use their code to disarm alarm panel* If 'Garage / Garage Door' Last Access Code Used is '$Security_Code_User_1_I User Number' Then Set 'Security System / Security System:Partition' Disarm USER CODE* *Now that part about disarming with user code of person that opened Schlage Encode deadbolt takes us back a couple years to a request for EnvisalLink-DSC. https://forum.universal-devices.com/topic/41353-disarm-with-multiple-codes/ So as not to break for anyone, could we set if USER CODE is not supplied it continues to use the one in the params? Again, thank you!

Great! I'll try it out when it shows up to install.

I’ve upgrade a couple times and its still say I need to upgrade to 3.3.15. No big deal... just wanted to let you know.

@Goose66 , I contacted the pyschlage library creator David Knowles via email about needing Python 3.11 support. He asked me to enter an issue in GitHub. I did and a couple hours later he marked it as closed and I can see activity on it. It’s issue 259 here https://github.com/dknowles2/pyschlage/issues/259. Once this is officially a release, can we explore options we discussed in this thread?

Just updated to 5.9.1. It took 10-15 minutes and then rebooted. I waited several more minutes and then connected with AC. No issues after connect so far. Thanks UD

Still going. It appears that water hammer feature only works for a Rachio Schedule and not individual zones like I posted above. I’ll work with node server author to see if we can expand it to send a schedule or to execute a schedule stored in Rachio. I can watch for irrigation on to potentially grab the water usage via Flume.

I located Rachio Minimize Water Hammer setting that open next valve about 10 seconds before closing. I’ll do some adjustments and testing to confirm the feature has impact when using API vs their schedule feature.