LarryM

Thanks Jack. Yes, being from C & C++ this is a tad different

@jca001 Much appreciated, thank you for putting that together. ============================================================================================ Then $State_Check_MS_Low_Battery = 1 Wait 30 seconds $State_Check_MS_Low_Battery = 0 Side note: from my readings, you are using a 'State' variable above to take advantage of the fact that when it changes then FD MS Low Battery Check - [ID 0026][Parent 0060] will be run every time that variable changes. It takes a bit of time getting use to 'Event driven programming'.

Thanks @jca001 That’s what I thought.

Thanks Humm Well that’s quite like not seeing the forest for the trees.

Thanks Larry1. Any answers to the two comments in the post prior to your post.

So you get the message and put a new battery in the MS. - How does $Int_FD_MS_Battery_Low get set back to zero? =========================================================================== - Seems like something like the following might replace the last two programs, however, I probably am missing something. If ( Time is 7:15:00AM Or Time is 7:15:00PM ) And $Int_FD_MS_Battery_Low > 0 Then Send Notification to 'Home and Work' content 'FD MS Low Battery' Else - No Actions - (To add one, press 'Action')

@jca001, thank you. Since I started with this stuff 3 weeks ago still struggling with the acronyms/terminology/jargon. Or maybe it’s has to do with old age.

@jca001 In ‘FD MS Low Battery On - [ID 0024][Parent 0060]’ , what is the function of: $Int_FD_MS_Battery_Low Init To $Int_FD_MS_Battery_Low

Yes, Larry was a very popular name a few years ago ? . I worked with a Larry once, he called me Lawrence I called him Larry2. I think Larry means, very good looking and very smart . . . Well, at least I still can recognize my name.

Another example: When Status is used in the ‘If’, a button on a hand remote (linked to that device) can cause the Status of that device to change, this would ‘also’ be detected as would a press on that device’s paddle. You would therefore be able to detect a ‘hand remote’ button event and/or a ‘device paddle’ press event with one program.

Re: AtStartupTime - [ID 0004][Parent 0001][Not Enabled][Run At Startup] For those following, I just tested my program (green) in the last post, it 'does' work. Q.E.D.

Not after you mentioned the factory reset That's an ugly emoticon. AtStartupTime - [ID 0004][Parent 0001][Not Enabled][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Disable Program 'GarageEntryTrigger' Set 'Outlets / PatioOutlets / FountainOnOffTop' Off Disable Program 'AtStartupTime' Else - No Actions - (To add one, press 'Action') Anything that needs to be initialized at power-up can be placed in this program. Examples: Disable some programs, turn off the water fountain etc.

@larryllix thank you for this. Excellent idea. Now in the program I posted prior to your post, I am confused what this would do: If Program 'AtStartupTime' is True Then Disable Program 'GarageEntryTrigger' Set 'Outlets / PatioOutlets / FountainOnOffTop' Off etc. (2 more months ) But time is going by too fast ! !

Found something, I believe this would be a valid way to initialize things at Startup/Reboot time. AtStartupTime - [ID 0004][Parent 0001] If Program 'AtStartupTime' is True Then Disable Program 'GarageEntryTrigger' Set 'Outlets / PatioOutlets / FountainOnOffTop' Off Else - No Actions - (To add one, press 'Action') Anything that needs to be initialized at power-up can be placed in this program. Examples: Disable some programs, turn off the water fountain etc.

Thanks again @paulbates As a new user with this stuff, I have been having fun. I read something a while back about running a program at reboot time only, I cannot seem to find it again. Was thinking this would be a good feature to use so I can reboot to to a known state. Would you have a suggestion about the run at reboot time?

@paulbates Thank you for your response. One last question, if the ISY goes through a power fail recovery or a re-reboot, how can I make make sure the GarageEntryTrigger - [ID 0007][Parent 0008] program starts off in the disabled i.e. [Not Enabled] state? Seems to work: GarageEntryTrigger - [ID 0007][Parent 0008][Not Enabled] If From 9:00:00AM To 7:00:00PM (same day) Then Set Scene 'Scenes / GarageManDoorScenes / GarageManDoor100%' On Wait 6 minutes Set 'SwitchDimmers / GarageEntryLight' Off Disable Program 'GarageEntryTrigger' Else Set Scene 'Scenes / GarageManDoorScenes / GarageManDoor50%' On Wait 6 minutes Set 'SwitchDimmers / GarageEntryLight' Off Disable Program 'GarageEntryTrigger' This program is normally disabled. When the motion sensor detects motion, program 'GarageEnryMotion' enables then runs this program. After 6 minutes either the 'Then' or 'Else' section once again disables this program. GarageEntryMotion - [ID 0006][Parent 0008] If Control 'MS / GarageManDoor' is switched On Then Enable Program 'GarageEntryTrigger' Run Program 'GarageEntryTrigger' (If) Else - No Actions - (To add one, press 'Action') When the motion sensor detects motion it sends an ON to the ISY controller. After sending an ON, the motion sensor delays 30 seconds, then it sends an OFF. This sequence of: send ON, wait a timout period, send an OFF is to keep the battery from being discharged with constant transmissions. This timeout period can be adjusted from 30 seconds to 128 minutes, factory setting is 30 seconds (.5 minutes). Thank you.

I have the below 'GarageEntryTrigger' and 'GarageEntryMotion' programs. I run 'GarageEntryTrigger' (blue) when my motion sensor detects movement 'GarageEntryMotion (red). Most of the time, the desired 100% and 50% scenes run as I want. Unwanted programming triggering: However, without motion being detected, at 9AM the (Then) GarageManDoor100% runs and at 7PM the (Else) GarageManDoor50% runs. This is not a major problem, but I was wondering what I can change so the non motion triggering events do not run? I was thinking maybe the program Enable/Disable feature on the 'GarageEntryTrigger' could do this. GarageEntryTrigger - [ID 0007][Parent 0008] If From 9:00:00AM To 7:00:00PM (same day) Then Set Scene 'Scenes / GarageManDoorScenes / GarageManDoor100%' On Wait 6 minutes Set 'SwitchDimmers / GarageEntryLight' Off Else Set Scene 'Scenes / GarageManDoorScenes / GarageManDoor50%' On Wait 6 minutes Set 'SwitchDimmers / GarageEntryLight' Off GarageEntryMotion - [ID 0006][Parent 0008] If Control 'MS / GarageManDoor' is switched On Then Run Program 'GarageEntryTrigger' (If) Else - No Actions - (To add one, press 'Action') When the motion sensor detects motion it sends an ON to the ISY controller. After sending an ON, the motion sensor delays 30 seconds, then it sends an OFF. This sequence of: send ON, wait a timeout period, send an OFF is to keep the battery from being discharged with constant transmissions. This timeout period can be adjusted from 30 seconds to 128 minutes, factory setting is 30 seconds (.5 minutes).

And, do a factory reset on your devices before proceeding to use them with the ISY.

For example with a 2477D added to a Scene as a Controller only: When you click on the Scene ‘itself’ you should see, on the lower right hand side of the screen, the device and it’s settings as as a Responder. When you make changes to these settings, then when the device is toggled ON these settings become active.

Work with power disconnected. Using a DVM or AC tester, confirm no voltage is present in box before proceeding. White of 2477 goes to white bundle (neutrals), may have to use a Red wire nut for the whites. Black of 2477 goes to the existing two wires (hots) of the old switch, use a Yellow wire nut for the three blacks. Red of the 2477 goes to Black load wire, use Yellow wire nut. Copper wire on 2477 to solid copper wire with Orange wire nut, other end of solid copper wire to box ground. After all connections are made, I use a 1/2” by 1/2” by 8” piece of wood to position wires in the box and neatly compress the wires to the back of the box. Note: Prior to adding a tinned wire from the Insteon switch, it is important that solid wires in a bundle be neatly twisted together with pliers so these wires self support each other without the need of a wire nut. Always confirm a wire nut is sized to the number of conductors in a bundle. Always check the final wire nut installation for all wires properly terminated with no copper exposed at the mouth of the wire nut (except ground of course).

Why didn’t you get the new Plus?

I thought others might like this template for labeling the buttons on the Insteon 8-button remote 2342-222. This label was done in MS Word, see attached file, change as needed. See attached file: Insteon Remote X8 Labels.docx After printing, fold the paper in half so you have the label on top of the fold, then laminate. If you do not have access to a laminator, you can use wide clear packing tape. Cut out the complete grid with a small border. You will be left with the front laminated with the back exposed paper. Apply clear, good quality double sided tape to the back. Commercial gummed labels do not have enough adhesion for this application. Using a sharp utility knife and a metal ruler, cut the blue lines then the red as mentioned in the image below. Clean button surface with Isopropyl Alcohol (IPA), let dry, apply label to button. Note: the label was designed to be a bit smaller than the actual button dimensions. Insteon Remote X8 Labels.docx

I made this Insteon test jig to set up my new devices on the ISY. New users like me, may find it useful to build one, especially if you have a lot of newly purchased devices to install. Thanks @larryllix re: doing a factory reset on new devices. Actually, this is the bottom of the PCB. R1 and D2 mounted on the bottom of the board.

@larryllix Thanks again for your input. Doing the factory reset and a restore indeed fixed the problem. "Every Insteon device should be factory reset before installing into ISY. The factory leaves these things with unbelievable qualities that you may never see again. I had one MS send the opposite status." I will remember remember this. The factory reset page:

After installing 20 or more 2477D dimmer/switches, one of them works a bit different form the rest. All dimmers have their 'On Level [Applied Locally]' settings set to 60%. When you single tap the 'ON' paddle, they go to the 60% level, as I wanted. However, one of these dimmers returns to the last locally dimmer setting made on it, the other dimmers do not act this way, they go to the 60% as I wanted. i.e. If on the dimmer that's different, you set the light level locally to 20%, then the single click becomes 20%. Examining the 'On Level [Applied Locally]' for this different dimmer, it is still set to the 60% mentioned above. Any suggestion how to get the dimmer to act the same as all the rest of the dimmers?