larryllix

YEAH STRINGS! I think they would mostly be useful on I/O. I don't see them that useful in programming...yet? A simple method would be to just implement a string substitution on outputs, like email, and NS. eg. I would like to order some stringSub( ${var.2.78}, 'apples', 'pears', tomatoes', peaches' ) Inputting strings would be a whole 'nuther big deal trying to work out string input and converting to a numeric value. Implementing constant variables could help this.

I m excited to see "v6.0.1 beta" mounted on it and the big switch on the front.....Disable Zwave Snooping!

It may be on the back or embossed into the case plastic but it would have to be on the device somewhere. Quite expensive but I hope it does what you need. The smoke detector thing is a good indicator but strange.

I don't see any approval anywhere on the product pictures. No symbol for CSA, USULC, or even an Asian ETL. For a device that connects directly into your main panel, an electrician may refuse to install it. This is not like SquareD but with things made over the pond these days???

I just had my whole house go nuts at 4 am one night. All the technology and they cant wit until daylight?? LOL

We can't see inside your shopping cart, only our own items.

How old are your smoke detectors? Smoke detectors classically detect ionised air which is what lightning does to the air. Maybe the sensors are on the verge of expiring. SDs have expiry dates on paper stickers inside the units, usually. You could also have some wring closer to the SDs that arcs,ionising some air gap, during voltage disturbance events and the SDs are detecting it.

Fans can alleviate stratification, bring cooler air, or warmer air, down, especially in very high ceiling spaces. Continuous circulation can even out temperatures found in furniture and other high thermal mass items, especially floors. Fans can also dry out beds from the sweaty bodies sleeping in the beds each night. Circulating fans would need to be turned on an hour or two before room entry. On really cold winter days I find parts of the floor can be cold, if they are restricted from heated air circulation by furniture. Something I discovered years after building my own home is the space between the floating ceiling in the basement, and the main floor surface gets no heated air circulation and the joist pockets can cause accumulation of colder air, making the main floor surface cold. Circulating air via fan helps this greatly. I suppose this is why commercial buildings use that air gap for return air. It can even eliminate raining above the ceiling tiles after months of condensation forming above the ceiling tiles. Insulation does not stop heat loss, it only slows it down. With no replacement heat, even insulated spaces will freeze eventually. Fans in proper places can alleviate some of this effect. Economy of energy must also be considered, though.

@Geddy Try something like this. I always use a time out with manual overrides because people get familiar with being lazy and expect it to reset itself. BR Fan-Summer - [ID 003D][Parent 003C] If From 10:35:00AM To 7:45:00PM (same day) And Module 'Climate' Temperature > 90 °F Then Set 'Bedroom / BR Linc - Motor' High Else - No Actions - (To add one, press 'Action') BR Fan-Summer - Manual If whatever trigger or condition you want, maybe a double tap on one of the speed buttons? Then Program BR Fan_Summer disable Set Bedroom / BR Linc - Motor Off Wait 1 hour Program BR Fan_Summer enable run (if) Program BR Fan_Summer Else -----

Your program will only run once at sunset + 2 hours. You have no Repeat line.It also does not address your first post request. Re-enable your first program and follow lilyoyo1's suggestions. ISY is a trigger event based processing and easier to use natively instead of creating time delay looping.

I agree, in some cases like pulldown menus where text disappears and you spend hours looking for it. . OTOH I wouldn't want to see device selections that include every variable, devices, network resource, email notification etc.. etc.. for every type of command line. I do like the changeable menus that are in your face to limit your selection to valid ones, as the ISY admin console, though. Better changeable selection boxes than magic functions on touch-screens where you just touch everything you see, to see what happen,s because the manufacturers are too lazy to write a 4,568 page manual that nobody can even understand. Like all top notch software and things in life...the better ones take some time to learn.

In addition, add a following line to run the program (if) in case it needs to respond to the conditions immediately, instead of waiting for a temperature change that could take hours.

Don't forget the phantom All On ghost, and other scenes do not send any status updates, so ISY will not record them. PITA. I had what appeared t be an ALL ON last night at midnight. Then I noticed all my NRbridge RPi software bulbs went full on also. Wit a mix of Insteon and WiFi bulbs it had to come out of ISY. Looks like NR events are not recorded either. I do have routines based on single variables that could have done it but it appears my ISY screwed up somehow writing the wrong value to the variable.

Oh ya' big tease! When I used X10 back in the 1980s, the MSes would send both On and Off and the Off was not blockable. I used both techniques then. The MS on would directly turn on the light (for speed), trigger a program, and then both the program, and the MS off signal, would turn the light off, similar to what can be done with Insteon MSes today. The X10 MSes could be set for 1,2,4,8,16,32 etc... minutes of resettable On time and would act as a backup Off signal to the program, to turn lights off. I see this technique as a good combination of us 'control freaks' vs. you 'Hub bubs' , that could be used for the best of both worlds using Insteon technology and ISY superior. Having said that I only use ISY programmed Offs to control my lights and all MS Off signals are disabled. If my ISY/PLM failed, I would be missing the Off cycles. It may be really annoying but with LED technology now, nobody advertises HA for saving energy on lights anymore. hmmmm….. I wonder if amazon sells sleeping masks???

Without studying the binary Insteon codes myself, it would still seem that the All On command is just another Insteon predefined scene formerly built into all Insteon devices (remnant of the X10 protocol it was created from) . Also, scenes, especially the All On, must be very easy to create by noise and data collisions, and using no data security or else an Insteon device misinterprets it and "cleans it up', repeating a clean signal to everybody.

If I am understanding these devices they would not all be in scenes, or in particular, one common scene, and no other devices in your home turned on?

I still don't believe in the ALL ON phenomenon as thought of by others. However, I did have similar random events for about a year which I finally identified as a scene I had setup myself, by the particular level pattern of the many lights affected. Mine ended up roughly related to a plug-in OnOff module that appeared to be sending that scene code instead of an ACK sequence. Simply power cycling the module fixed it and I haven't seen it again for several years now. AFAIC the ALL ON signal is just another scene being manufactured from noise. These Chamberlain GDO are bad news for Insteon. The last one I installed (with MyQ) crippled my Insteon system at about 40-50% operational. A pair of FilterLincs solved that problem and my system worked better than it did from day 1 with an AC motor Chamberlain GDO causing some minor Insteon problems. I always blamed my OutBack inverters for those problems but it was minor and I never sleuthed it down. A GDO, with MyQ problem makes me suspect the GDO causing havoc with the IOLinc thinking it is seeing a scene command, it is involved in. @James Peterson is the IOLinc in an Insteon scene? Scenes do not create log lines in ISY. No status update is sent. There is no arbitrator in Insteon for the multiple devices that would clash status updates simultaneously.

It will get easier as you go. First you just have to get familiar with how the admin console works and what the capabilities are. You are on your way. Glad it is working out for you. Have lots of fun with it!!

$iUH_Temp and $iUH_Luminance are Integer variables. See the 'i' after the '$'? That is his way of indicating they are Integer types. Go to the Integer variable tab and Add two new variables. Rename them to suit your needs, as he has done to "iUH_Luminance" etc. Now go to your program and after selecting Action, select Variable in the pulldown. Click on the variable name box and scroll down until you see your variable name. Select it. In the third box, select '='. In the fourth box, click on the small caret symbol and it will rotate through all the types of elements that variable can have copy to that variable. The last two boxes you select the device parameter you won't to copy the value of. When you get the line you like, click on Add to Then. When done editing always click Save at the bottom of the program tree.

You may notice that others prefix (at least) their status variables. Integer variables do NOT cause triggered events and confusing the usage of the two can cause you a lot of grief. Some use $s.Variable, and $i.Variable. I use $sVariable and $variable (no prefix for integer types) I also use $cCONSTANT for integer variable names to identify a variable value that is preset and never changes. eg. $sLogicVariable = $cTRUE $sGathRm.mode = $cDIM

Scenes are like presets on your car radio. You select a preset or another and the result has been predefined. It takes a whole lot less protocol communication when the speed and co-ordination of timing between devices is needed.

The ISY logs don't show everything. They show most of the updated statuses and a few other things. IIRC Insteon scenes don't send status updates back so tht may be a large chunk of the HA. How would we pronounce it? AIHA, AI/HA, HAAI, HA/AI, AHA!

I don't have a MSII but I see a few possible problems. First you are not querying the MSII. Insteon doesn't usually work like that. Is the battery level an analogue parameter? If so you didn't post a value. If not having two event based triggers ANDed should never run Then. Sent using Tapatalk

Expanding that somewhat... 'Control switched on' and, 'Control switched off' are two different devices, each with two states. Status is one device with two states. Sent using Tapatalk

To further Paul's explanation... ISY is an event/trigger based engine. It does not loop process as some object oriented engines do. With your time bracketed conditional/trigger/If section: If From Sunset to 10:25:00 PM (same day) Then wait 10 minutes (random) ...this will run at sunset (every day) Else ...this will run at 10:25 PM (every day) If Enable is unchecked the triggers will not initiate processing and it only becomes a permissive window. Calling it from another program it can act as a permissive filter only, without any self triggers.