larryllix

Awesome! I agree about the HA not just being remote control. See my post above. This is what I want to accomplish as well. Occupancy detection comes into play as a factor also. Not just your dumb switch anymore.

This seems confusing. Doesn't the pullchain switch get removed from the box, not only to replace with the fanlinc control unit, but also to make enough room in these cramped wiring boxes? I am thinking of installing a fanlinc in my Honeywell ceiling fan but it currently has some fancy two wire (hot and neutral only) method of controlling the lights, with dimming, and the fan speed. Would be nice to know what protocol this things uses. It comes with a thermostat inside the wallswitch control unit but inside a wall box, but with dimming electronics heat, is not a good place for a temperature sensor. I have a 2441ZTH just waiting to be enslaved for graduated smart fan speed control.

I would be afraid that somebody would pull too hard out of frustration maybe and fracture the glass. Can they not be just stored above the glass globe and not dropped through at all or the pullchain switch bypassed?

I am not sure how the Elk event triggers work in ISY but give this a try. If From 10:30:00PM To 5:00:00AM (next day) AND { Elk Zone 'Family-Motion' is Violated OR other zone is Violated } AND { <----Elk triggers may not require this section. Elk Zone 'Family-Motion' is not Violated <----disables 'reminder' if motion starts again. AND other zone is not Violated } Then Wait 30 minutes Enable program 'reminder' Else Disable program 'reminder' Program 'Reminder' (disabled) If Elk Area '1' 'Armed State' is Disarmed Then Repeat Every 30 minutes Set Elk Speak Word 'Alarm' Set Elk Speak Word 'Is_disarmed' Else --

Is the ++ significant on the Notepad name? When I open the logs in Notepad I get no newline and everything is run-on smashed together. If I use Wordpad it seems to handle it better but with two newline chars for each line.

Your reference to post #6 states "Switch box #1 (slave): ..... Switch box #2 (master):" as the only form of identification. There is no switchbox #1 established that is consistent. Now you are changing the master and slave. It would seem this has already confused the OP and wiring changes were not as you instructed. Again. The diagram should be labelled with references. Best of luck.

Once he changes his wiring the master and slave are switched. We have to assume the switch reference number are not.. The diagram should be labelled so both talk the same language. I can already see some confusion following your instructions.

Label the switches as it seems your Switch#1 may be Stu's Switch #2 in the discussion.

Switches #1 and 32 were never identified in text or on the drawing. Perhaps that caused some confusion of wiring changes?

The humidity should not be fluctuating that fast with bobble. Humidity sensors never seem to respond that fast, especially up and down repeatedly. This sounds like a problem with the thermostats. What is your power supply to it?

If I allow my Admin Console to slip into background processing I cannot trust the Admin Console anymore to show updated variable and/or program statuses. I can usually change program code and write it to ISY no problem but updates usually suffer and foils my debugging sleuthing. There is no indication of this except things do not seam to function properly inside the Admin Console. Exiting and rebooting the Admin Console always fixes the problem until I run another task without closing the Admin Console again.

I can act as a heartbeat for "alive" detections but in my mind it should be quite regular, not erratic timing.

The only way I can see this happening is if you stop the program from running. Then you already know it is NOT active. Perhaps you are trying to establish intent of the program before disabling it and halting it. Then you can resume the same process. . Is this correct? As Lee suggested this would require a variable flag... an "I was going to" flag. You had stated you set a variable upon completion of a possibly halted program. Can you not just use that variable to see if the program finished before rendering it inactive?

I still use some x10 devices also but can't wait to get rid of them finally. In applications where they operate dynamically with motion or other fast action sequences they can tie my ISY/PLM up for up to 60 seconds. For low action background devices they work just fine. eg. China cabinet light, Christmas tree lights. Now if Insteon would just produce a decent beeper or doorbell chime for dryer done and/or garage door open indicators I wouldn't have these X10 problems.

Well I did mean just devices but since you raised it....

Some Leak sensors send On and then Off alternatively for a heartbeat while apparently some newer units only repeatedly send On. If you check the status of an older unit it could be in any state and quite normal.

This seems rather odd that want to disable a folder containing a program and yet have the program continue to run. You program snapshot is rather small text and low res, to be readable, for me so I don't understand why you are trying to do this. Maybe a clearer explanation of what you are trying to do. We got some sharp ones here. On the surface it would seem if you want the timer to finish you must not disable it's folder, or take the program out of the folder., or create another program, out of the folder, to do the job. When you re-enable the folder the timers inside the programs are not relevant anyway. You probably need to rethink your logic somewhat and find another way to accomplish your mission (should you choose it.) If what I think you want to accomplish is have any timers in the folder complete before disabling further triggers in the programs. This could be done with folder logic looking at all the programs statuses inside. So that my program statuses look nice for Mobilinc and Admin Console I often use an Else call at the end of each Then section. If whatever Then do something Wait 1 second Run 'This program' (else) Else ----- You could also have each program disable itself as a last line in each. You can detect a program is true and also detect how long since the program was last run but IIRC not if it is running currently.

Insteon. I have read other forums and listened to the complaints and used X10 since the 70s and Insteon has them all beat except for the lack of device variety.

Do you have other Insteon devices that were not on? Also, view your event logs in level 3 after operating these in question several times and compare the "hops left" count. Try the same after operating at the midnight usual time and see if you get variances. This usually indicates comm problems.

The program is halted and disabled.

Backup old ISY data Need to get copy of old ISY variables and create in new ISY. There may be a better way to do this one. Maybe restore will create them??? Pull in the backup file into your new ISY with Restore. Rename all your devices by adding XX to the end of each name. -Install new Insteon device with same names (no XX) -Use find/replace to replace all occurrences of that device name using XX with device name not using XX -Delete device with XX Repeat above three steps until all XX's are gone. Save frequently in case of mistakes This is a PITA but the only way I know to preserve your code and swap in new Insteon addresses.

Usually with notifications you need to use two programs. The first program has the trigger and calls the second program (disabled) as a subroutine. The second program disables the first program, sends out notifications, waits awhile until ready for another notification, and then enables the first program again. Hysteresis is the deadband between on and off levels.

I have to disagree somewhat. If I send an X10 On to an Insteon LampLinc module ISY has no idea the lamp has turned on unless I detect the X10 command or manually query the LampLinc module. Also, ISY does not keep track of scene statuses and presents no status on the scene's setup page. This was discussed elsewhere that ISY can send scene commands but not (or won't) receive them. ISY only keeps track of commands from itself or initiating devices and doesn't really know the true status of any device. This is why there are so many ISY status blanks on power up. Most of the time this is transparent.

I use one Switchlinc Dimmer for seven different scenes. Double tap up -- all lights in room on full Single tap up - Lights in TV watching mode, toggles between reading mode scene Long press up - brighter scene for room Long press down - Movie watching mode and trn on coloured lights around perimeter Single tap down - All lights off scene - bedtime Double tap down. - Turn on coloured lights only - turn on Off scene for white lights I use these programs to set one variable to a value (non zero except Off scene). I built many programs that turn on scenes based on that variable value. If I change an involved light say... brighter over a desk, when I turn off that switch over the desk I can resume the scene by setting the variable to -1 (no scene) and then back to it's value again. ISY is automagic! Here is a sample of both ends of this code using the double tap up command on any of 4 SwitchLinc Dimmers ora 4 button RemoteLinc that clones the tapping styles of the main SwitchLinc. Note $cMODE.FULLON is an integer variable only used for a constant and predefined in the variables for easy reading and programming. Also note the use of a second variable, $sGathRm.Colours, to duplicate this process with coloured light scenarios. GathRm Mode.FullOn.select - [ID 005F][Parent 0004] If Control 'Gathering Room / PotLights over Chairs' is switched Fast On Or Control 'Gathering Room / GathRm KeyPad.A' is switched Fast On Or Control 'Gathering Room / PotLight over Desk' is switched Fast On Or Control 'Gathering Room / PotLight over Table' is switched Fast On Or Control 'PotLights over TV' is switched Fast On Then $sGathRm.Mode = -1 $sGathRm.Mode = $cMODE.FULLON $sGathRm.Mode Init To $sGathRm.Mode $sGathRm.Colours = $cCOLOUR.FULLON Wait 1 second Run Program 'GathRm Mode.FullOn.select' (Else Path) Else - No Actions - (To add one, press 'Action') Here is one program that actually operates the white light scene GathRm Mode.FullOn - [ID 00AF][Parent 00C8] If $sGathRm.Mode is $cMODE.FULLON Then Set Scene 'Gathering Room / FullOn' On Else - No Actions - (To add one, press 'Action')

Sorry for the sideline but.... For both our educations. DR Front On Program If Status 'CR / Devices / CR FanLinc-Light 80' is not Off { Or Status 'KT / Devices / KT Ceiling 50' is not Off { Status is used instead of Control, so it doesn't matter how the light was turned on Or Status 'LR / Devices / LR Ceiling Light KPL 20' is not Off { Then.... How does ISY know if a device was operated via some scene or - do you never operate devices involved via scene control, or - do you detect the scene operation via the initiating device command sent, or - will status always know a devices status? I didn't think this was true and hardly ever use it anyway - other