hart2hart

I usually get away by making sure everyone knows I’m doing a test and get a good count. If no one is doing it, it’s likely coming from programs so disable top most folder(s). If motion detectors or leak sensors are part of your setup, it’s more difficult to control. Also, you can look at log during the time frame to see what device had activity and then determine how to stop it for test.

The show PLM links and count needS to be done with no Insteon traffic occurring.

Sorry, I’m just now seeing this update. Virtual is a fabulous plugin. I’ve been using it for great things and it got so much better when you took over development. Is any additional input or testing needed before you public it to production store?

The if folder true will be reevaluated every time the noaa temp changes.

Yes, It’s 401BC51 Insteon address. Those starting my with n are nodes created by plugins.

Take a look in admin console its node address will be something link n02_99 and what you show is its name.

The only update I would like in programming is synchronous execution for runif. As in wait for called program to exit/return before going to next step in current program.

You can update variables via REST interface.

Was the scene turned on by a program? If so it’s a common issue. The eISY sends the scene on/off command but there is no direct feedback from each device in scene so eISY reports that all onto the desired state. I typically issue the scene command followed by a wait of 5 or 10 second and then same scene command again. If it happens a lot for a specific device in a scene then other more detailed trouble shooting should occur to locate underlying cause.

I moved to Rachio this Spring to control 10 zone system because I wanted master valve across the 10 zones. It has been good and I’ve written several programs to integrate it with Flume so I can detect a zone that has locked open or a zone that is not opening. Additionally, in my box of stuff, I have the two retired ez-flora if you’re interested.

Do you have eISY config for catch up at restart?

Restoring PLM fixed it. Hadn’t seen other symptoms of that issue. Will watch it for issues.

@Goose66I've got a few scenes with Insteon switches as Controller with Bond Fan Ligh and Fan. They were working yesterday many times but do not work as of this morning. I have Restarted node server Rebooted eISY Recreated scenes Restarted the Bond puck Confirmed local token You can: Turn Bond devices off/on from AC Turn scenes on/off with Insteon switch and Bond Device from AC Control all devices from Bond iOS app You just can't (and most importantly) Turn on/off at Insteon switches (I tried 3 fan/lights) for a total of 6 scenes and none worked

@bpwwer not a big deal but I can confirm that after two power outages during rain events, plugin reported the Nearcast rain amounts instead of what was recorded by device.

Turn on event viewer at level 3 and then remove scene. Maybe you’ll get more details in underlying issue.

If it’s all Insteon devices, it’s simple but zwave complicates it a bit. Still doable but not a give me. Also, didn’t see which isy firmware you are on so may need to move to last versions for it to make the migration to eISY. It is a great upgrade and it’s getting better.

Thanks @Geddy . I had forgot that Run at Startup would evaluate that it was within the timeframe and not just at the From and To times.

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?