ldb

Set the device to the (binary) switch, not the button. Probably address ZY009_1 in your case.

I have read that the minimum zone run time of a Rachio controller is 1 minute. Will this plugin support a run time of just a few seconds?

Two rain events this week and the nc node is showing my Tempest local data, not the nearcast data. Restarting the plugin does update to the nearcast values.

Sorry for any confusion but my programs work fine. They are triggered by the button push, not a variable. I was responding to the original poster issue.

Are your variables STATE variables? No, integer variables Have you verified that the varable changes from 0 to 1 to 0 when you toggle the button(s)? Yes Program examples: Cooktop ON - [ID 01CC][Parent 0037] If 'Kitchen Scene Button 1' is switched On And $Button1 is 0 Then Set 'Kitchen / Cooktop Light' On $Button1 = 1 Else - No Actions - (To add one, press 'Action') Cooktop OFF - [ID 01CC][Parent 0037][Not Enabled] If 'Xtra / Kitchen / Kitchen Scene Button 1' is switched On And $Button1 is 1 Then Set 'Kitchen / Cooktop Light' Off $Button1 = 0 Else - No Actions - (To add one, press 'Action')

Think of the four small buttons on this switch as program triggers, not on/off switches. Depending on how many devices you want to control, you can initiate an ON command on one button and an OFF command on a second button. In order to control more devices, I have assigned variables related to button presses (nodes called Central Scene Control Button). My programs increment or decrement the button variable with each push of the button. For example, this allows execution of an ON command if the variable is 0 and an OFF command if the variable is 1. Thus, on and off from the same button. Some of my programs involve the setting of configuration parameters to control button color, etc. Consistent execution of these has been challenging due, I believe, to eisy's ability to process the command sequences reliably.

Following up to confirm successful operation of the nearcast data update. FWIW, I see that Weatherflow amends nearcast rainfall amounts after the fact. Thus, the rainfall reported in their app may be different from the amount captured by this node server. Thanks again.

Thank you! Rain is forecast for this week so I will confirm and report back.

What I am seeing is that today's value and yesterday's value do not change overnight. They remain stagnant until I restart the node server. The yesterday value did change to the previous today value after last week's rainfall when I restarted it manually.

I notice that the data fields for the Nearcast node updated regularly during a recent extended rain event but do not reset daily. I have to restart the node server in order to update the values. Would this be a Weatherflow or node server issue?

Got it! Thanks and good luck.

Just to clarify, is the enhancement you are suggesting to allow control of F lights AND back lighting? Thanks.

There was discussion regarding keypad back lighting in March 2024. Jimbo.Automates created an issue at that time. Is the addition of lighting control still in the queue? I would like to be able to turn the keypad back light on and off based on conditions in order to keep my bedroom dark overnight but have the keypad on during the day.

I set configuration parameters 1-5 (on/off) and 6-10 (color) within associated programs to indicate status.

I have both Homeseer LS100 and Zooz ZSE42 sensors. I exercise them every other month in conjunction with a EcoNet EVC200 valve actuator. I prefer the Zooz unit due to smaller size and use of a common battery. I have found battery status reporting to be unreliable for both devices but leak reporting has never failed.