MrBill

Right Click My Programs and pick Find/Replace. Change the first dropdown to Variable.

I also have a ridiculous number of integer variables because I decided to have two per wireless transmitter to count total transmissions and battery days. That was a nerd curiosity thing since open/close sensors don't send low battery-- i did it for the recessed door sensors tho too... (17 transmitters x 2 variables each = 34)

Curiosity... I added 55 state variables the other day for CAO gadget tags... My list is now just over 100... I'm actually going to drop 22 of those because I'll never use some of the functions and why have the tags update something i'l never use... and another 11 could fall into that category too.. it was worth setting up that way to start to understand and experiment. I wonder if I need to be conservative with variable creation, or don't care because I'll never run out.

Actually I never knew the real inside temp of any freezer in the house before this point. "Settings" on 3 of the 4 freezers consist of an arbitrary number.. the forth does have a digital control degrees is actually set. The temp sensors are all mounted "almost" suspended in air..that is they have a velco strip mounting, and they are all attached on the ceiling away from air vent flow. The icing occurs on the INSIDE of bags or containers that contain air... factory or food saver sealed vacuum packages (most of it) doesn't show icing inside. On the other hand, ziplock a steak, squeeze as much air out as possible and freeze it...it will ice crystal inside the bag in no time at all. I've never understood why until now. I've always been under the perception this was the coldest best deep freeze in the house. I'm now learning it's the opposite, wide temp delta's over short time and now that i've maxed out the control, it "averages" closer to zero than the manufactures "suggested" setting of "4" to achieve 0 degree's F. You did make me think though... moving the sensor around some to see other results... I don't really care about burried in a pile off packages, or a bag of sand) i'm sure that will be more consistent... i do want to find out of the 14 degree surface temp change is real tho.

Actually that sounds like how I had this visualized as working at one point. Then I kinda stumbled into how I did it, It actually works great, and i think for the most part is better with the added advantage of instant on/off from the KPL's and the fact that the scene would still work manually if the ISY is gone or not working). [i could always work around the issue if I was home, however a design consideration is always how the system could/might fail if I was out of town and my wife tried to turn on the fire, for example. Because the scene remains intact under my method it would still work if programs didn't.. a better situation than my wife reporting...THERE WAS NO WAY IN HELL TO MAKE THE FIRE COME ON LAST NIGHT...] The only part that doesn't work is changing scene status via mobilinc (or the admin console but I don't care about that).... I'm surprised there is not a if STATUS "scene"... or CONTROL via system/isy...

This freezer shows more what I would expect to see.... a 5 degree temperature variation over a slightly wider (per cycle) time period. (All that IS hard to digest because the graphs auto-scale... it's very difficult to compare graph A and graph B because the scales (may) change based on data.) in the FIRST example... the temp delta is almost 14 degree's over a shorter 45 minute cycle.. it really explains why icing occurs if there is ANY air in the package. The freezer is in an unfinished basement room, no direct sunlight..It full of dense food, but nowhere near packed to the point that air circulation is any sort of issue. I actually have 7 tags in refrigerators and freezers, all behave about as I would expect... Except the name brand (but I think on the low end of the product line) freezer that had a rebate from the power company for purchasing it...lol My son has a freezer in his garage... not only is it not healthy for it to sit in heat it creates more heat in the space.. it also doesn't help that the only time the coils ever get cleaned is if I notice them and just do it... I

A friend of mines company can't ship to Canada because they don't have a French website and French documentation for the product... they used to ship to Canada... until they got ordered not to.... it's Canada's weird bilingual laws AND the Canadian Govt's insistence on enforcing those...

A better restatement of the problem: Start with everything off... module, scene, buttons, and $FLAG.LivingRmFireplace.cycle = 0 (a.k.a. the OFF state) We press either KPL button... the scene turns on, the module turns on (the flame lights immediately), because the of that, the program "Fireplace downstairs on" runs and set's $FLAG.LivingRmFireplace.cycle = 1. This enables the "Fireplace-Cycle off" and "Fireplace-Cycle on" because $FLAG.LivingRmFireplace.cycle = 1. Those programs cycle the module alone on/off based on the temp of the room. All the while the scene (and KPL buttons) stay ON... indicating the system is ON, even if the fire is currently in an off state due to temp.... When the scene is turned off via a KPL button, the scene returns to the off state, and $FLAG.LivingRmFireplace.cycle = 0 again, which stops the cycling. This all works perfectly, until the scene gets turned on or off via mobilinc. AS discovered above, it appears the this can be half solved: From the Off state of the system, STATUS is NOT off of a KPL button can be used to set $FLAG.LivingRmFireplace.cycle = 1, but the opposite does NOT work STATUS of KPL button is OFF can't seem to trigger the program to get $FLAG.LivingRmFireplace.cycle = 0 back to zero.

That won't work... it's being cycled via cycle off and cycle on programs (it's a responder rather than controller in the scene) what we are trying to trigger in the "Off" program that sets $FLAG.LivingRmFireplace.cycle = 0 -- which then prevents the cycle programs from running...

Actually I spoke too soon.... STATUS is NOT off ... correctly works for the KPL button turning on and set the cycle variable to 1 however STATUS is off doesn't work to detect off and set the cycle variable to 0 weird...

Well you solved this in one post, after I've been thinking about it for 24 hours.... The reply I was typing said "but there is a no status (or control) for a "scene" .... BUT....as I was typing that sentence I wondered to myself..."HMMM, is it possible to check the "status" of a KPL button in a program. In fact, thats the answer--the scene status can be determined by the status of KPL buttons that is a controller in the scene. (actually I have used "status" of the on/off module itself in another program that makes certain the ceiling fans are running.. but i hadn't considered the "status" of the KPL buttons) thanks!

Is there a limit to the number of variables that can be created? I know from the graphic on this page that number of "programs" max out at 1000. Is there a limit (practical limit or hard limit) for the number of variables that can be created?

Gas Fireplaces is the topic. I almost have this working the way I want it to, except one detail that I can't seem to work out. Prior to yesterday, it was a simple manually controlled scene. Each fireplace has one 2635-222 on/off module that powers a relay with a 120v coil. Each 2635-222 belongs to an scene, along with 2 KPL buttons, all 3 devices are controllers. Works great. Habits formed, my wife almost always uses the KPL buttons, I most always use the scene on the mobilinc dashboard or today screen to control. I've always had on my list to automate the fireplaces based on room temperature but had trouble finding the best temperature sensing device for the project. This forum introduced me to CAO wireless tags and I ordered and received this week. What a wonderful product!! (I will say that although this product doesn't have a cloud dependency in the sense that it requires portal etc to work, it does have a cloud dependency in that if the company ever ceases to exist the product will no longer work without its cloud. It's also scary that the tag manager has the ability to generate http calls on the local network based on what the cloud servers instruction......) ((Off-topic: I always knew I hated the way our deep freeze keeps food, I never realized the REASON. The CAO tag tells the WHOLE STORY, every hour the temp variation inside the freezer is almost 15 degrees!! Time to buy a better freezer!!)) Anyway enough back-story and side-story...back to the topic... fireplaces: As mentioned, with habits already formed I thought that I would build new control programs based on those. A few quick programs and everything works exactly as expected. EXCEPT one thing, controlling the scene from mobilinc. (Current programs included at the bottom of this post). If the scene is turned "on" from the KPL button, The scene is turned on, and the "cycle" variable gets set, when temp is reached ONLY the on/off module is cycled off and on based on temp, the scene (and button backlights) stay on. If the scene is turned "fast-on" from the KPL button, The scene is turned on, and the "cycle" variable doesn't get set. The fireplaces just stay on. If the scene is turned "off" or "fast-off" via the KPL, then the scene is off and the variable is reset so that it won't come back on as the temp falls. This all works great. The problem is it only all works great when controlled via the KPL buttons, if I pull Mobilinc out of my pocket and turn on the fireplace scene (my habit), the cycle variable never gets set because it is triggered via "control" of the KPL buttons. So what's the best way to control this logic via Mobilinc--with a single button on the mobilinc dashboard? (I know that I can create programs and migrate to TWO "buttons" on the mobilinc dashboard--one for on and one for off. I resist that tho because the scene status is not as apparent, and because it's two buttons. I'm looking for a solution with one dashboard button, like this: However there is no "control" (or "status" for that matter) that allows for capturing scene control via an IF statement of a program. Suggestions? Thanks... =================================================================================== Fireplace-Downstairs - [ID 007C][Parent 0001] Folder Conditions for 'Fireplace-Downstairs' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. ----------------------------------------------------------------------------------- Fireplace-cycle off - [ID 0078][Parent 007C] If $FLAG.DownstairsFireplace.cycle is 1 And $DownFireplace.temp >= $DownstairsFireplace.setpoint Then Set 'DN Fireplace#' Off Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-cycle on - [ID 0079][Parent 007C] If $FLAG.DownstairsFireplace.cycle is 1 And $DownFireplace.temp < $DownstairsFireplace.setpoint Then Set 'DN Fireplace#' On Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-Downstairs-off - [ID 007B][Parent 007C] If Control 'DN Back Door Recessed+# / Fireplace Downstairs' is switched Off Or Control 'DN Back Door Recessed+# / Fireplace Downstairs' is switched Fast Off Or Control 'OUT Lower Fans - High / DN Fireplace' is switched Off Or Control 'OUT Lower Fans - High / DN Fireplace' is switched Fast Off Then $FLAG.LivingRmFireplace.cycle = 0 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-Downstairs-on - [ID 007A][Parent 007C] If Control 'Living Room Fan Lights+ / Fireplace' is switched On Or Control 'DN Back Door Recessed+# / Fireplace Downstairs' is switched On Then $FLAG.DownstairsFireplace.cycle = 1 Else - No Actions - (To add one, press 'Action')

Whenever I read threads like this one, I always want to ask "What Changed". The OP implies everything worked fine "before" but then "The last few days the wait time is screwing up the last action." Why did it work before and suddenly stop? Was a program changed? Did the batteries in the motion get changed? When a working system suddenly stops working, the first question always has to be "what changed?"

2 amp at 5 volts = 10VA 2 amps at 12 volts = 24VA 2 amps at 30 volts = 60VA huge differences there...

I do this with my attic fan. Attic Fan 4hr timer - [ID 003B][Parent 0001] If Control 'MBR Bedside1 / Attic Fan 4 Hr' is switched On Or Control 'MBR Bedside2 / Attic Fan 4 hr' is switched On Then Wait 4 hours Set Scene 'Attic Fan' Off Else - No Actions - (To add one, press 'Action') The actual attic fan switch is a 2477S that is not listed in the program. The two controls listed are buttons on a 8-button keypads. All 3 devices are 'Controllers' for an attic fan scene. Pushing the button on the KPL actually turns on the scene AND triggers the program that turns the scene back off. If the attic fan is activated by the 2477S that is actually switching the load, the timing program will NOT be triggered and the attic fan will stay on until turned off manually from any of the 3 locations.

I'd put the 2450 inside and run the low voltage wire out.

It's interesting this is all the fault of the ISY! I wonder why you didn't say "Is there really NO easy way to edit device links manually from Insteaon Hub?" The problem that you are encountering is there is no concept for multiple controllers/hubs in an Insteon system. It has nothing to do with the fact there is no easy way to manually edit links. There are many threads on this very topic in this forum. The ISY also works well with Alexa. The problem is not that you can't manually edit links using an ISY, the problem is that you don't want to learn how to migrate properly from one controller to another.

No doubt! Not in use anymore, but I still have a BSR branded maxi-controller, lamp module and appliance module from the late 70s.

To make the ISY less busy: Then Repeat Every 15 second $Sump_Pump_Run_Time += 15 $Sump_Pump_Run_Time Init To $Sump_Pump_Run_Time It's not EGGSACTLY the same granularity, but should be close enough...

I was definitely generalizing in the original context above yes. All the same I quoted the exact information that I had on the subject because I was told my statement was incorrect. I claim nothing more.

Please see attached. Also go to https://www.networksolutions.com/whois/index.jsp and look up the domain registrations for both smarthome.com and insteon.com and compare what you see there.

Done that way because I didn't want to manually adjust the clock, but wanted to test what happens "in this time period" and "outside this time period". I admit the original program works differently than I expected. I thought it was from this forum I learned that you can't use FROM TO and AND all in the same IF statement, and now I wonder why I think that doesn't work. in any case i still like the "dark" variable better... much easier for testing "after sunset" things at 1pm in the afternoon.

As a test I just created: AA test - [ID 0073][Parent 0001] If From Sunrise To Sunset (same day) And Status 'Door Switches / Costco Rm - Door Sensor' is On Then Set 'DN White Fridge Alcove#' On Else Set 'DN White Fridge Alcove#' Off Using Sunrise to Sunset since it's currently daytime for me. This works as expected. So then I modify to: AA test - [ID 0073][Parent 0001] If From Sunset To Sunrise (next day) And Status 'Door Switches / Costco Rm - Door Sensor' is On Then Set 'DN White Fridge Alcove#' On Else Set 'DN White Fridge Alcove#' Off And this does not work as I would expect. Now during a daytime time, the light does not turn on but the light will turn off if it was on for some reason. My actual garage light programs are separated into on and off programs anyway. If dark they turn on if any door is opens, and they turn off anytime the last door closes: =================================================================================== Garage Lights - [ID 0058][Parent 0001] Folder Conditions for 'Garage Lights' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. ----------------------------------------------------------------------------------- Auto Off - [ID 0059][Parent 0058] If ( Control 'Door Switches / Garage to House Door' is switched Off And Status 'Door Switches / Garage-North OHD' is Off And Status 'Door Switches / Garage-South OHD' is Off ) Or ( Control 'Door Switches / Garage-North OHD' is switched Off And Status 'Door Switches / Garage to House Door' is Off And Status 'Door Switches / Garage-South OHD' is Off ) Or ( Control 'Door Switches / Garage-South OHD' is switched Off And Status 'Door Switches / Garage to House Door' is Off And Status 'Door Switches / Garage-North OHD' is Off ) Then Set 'Garage Lights#' Off Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Auto On - [ID 0057][Parent 0058] If $DARK is 1 And ( ( Control 'Door Switches / Garage to House Door' is switched On And Status 'Door Switches / Garage-North OHD' is not On And Status 'Door Switches / Garage-South OHD' is not On ) Or ( Control 'Door Switches / Garage-North OHD' is switched On And Status 'Door Switches / Garage to House Door' is not 100% And Status 'Door Switches / Garage-South OHD' is not On ) Or ( Control 'Door Switches / Garage-South OHD' is switched On And Status 'Door Switches / Garage to House Door' is not 100% And Status 'Door Switches / Garage-North OHD' is not On ) ) Then Set 'Garage Lights#' On Else - No Actions - (To add one, press 'Action') So it really depends on what the desired behavior is, but I was trying to keep it simple.

I actually had another way "dark" could get set in v4.5.4 based on weather station data. v4.6.2 broke that tho (it takes too long for dark to happen), and when I complained Michael open called me a drama queen in the thread... so i quietly went away and didn't participate here for a long time. I ultimately came up with a method to get light and rain data from my weather station using a rPi and the ISY API. It's not reliable tho (because of an rPI issue) and i don't know enough about python error catching to fix it.