larryllix

Double tap on top = Fast On = no ramp Single tap on top = On with local ramping speed Hold top for longer than a tap = Brighten Hold botton for longer than a tap = Dim Single tap on bottom = Off with local ramping speed Double tap on bottom = Fast Off = no ramp Of course the local connected light on the unit being operated goes to the setting without program intervention but... if you set the local ramp to a few seconds (ie. 2.0s ) the program can usually beat it with it's new level and ramp speed and you will never notice the starting ramp from the light switch before the program scene takes over. The Fast On and Fast Off being the exceptions as they defeat any ramping delays.

Users tell me Google recently released the Nest SDK and interface to the public.

In my gathering room I have six dimmable sets of lights each with their own SwitchLinc and one LampLinc module. I have set up Scenes that I control from one switch closest to the entrance / exit spot for the room. I make use of the six available commands from the one SwitchLinc. - On = turns on my GathRm.Reading scene and then toggles between that and GathRm.TV scene each additional tap - Fast On = turns on my GathRm.AllOn scene - Brighten = turns on my GathRm.Bright scene - Dim = turns on my GathRm.Movie scene - Off = turns on my GathRm.Off scene - Fast Off = not used - only affects the lights connected directly to the SwitchLinc I found it much easier to have six preset levels for the room mood than to attempt variable dimming crosslinking. Attempting to synchronise the dimming of two devices may be hard and they may not level-sync well using programs. I control most of my lighting needs from one SwitchLinc and an Insteon KeyPad, that duplicates all commands with the same style of taps, but can control individual areas with it's own switch temporarily overriding any scene preset. This should be easier to write the SwitchLinc status checking into each command handling program for your desired logic. The scene levels are easy to modify from the Admin Console for tweaking your mood levels. Do you know how to send each of the six commands from a SwitchLinc dimmer? Here is an example of a scene based on another condition. $cREADING_MODE can be changed to "Status is On" of your other switch in the code. GathRm Mode.TV If ( Control 'Gathering Room / PotLights over Chairs' is switched On Or Control 'Gathering Room / GathRm KeyPad.A' is switched On ) And $GathRm_Mode is $cREADING_MODE Then $GathRm_Mode = $cTV_MODE $GathRm_Mode Init To $GathRm_Mode Set Scene 'Gathering Room / TV Watching' On .... more code Else - No Actions - (To add one, press 'Action') Toggle Reading and TV Watching modes

One SynchroLinc was suggested but as Stusviews stated, you already have a battery backed up pump and this would allow you to play safely. Here is scheme I would use. - Get one SynchroLinc and one ApplianceLinc module - Plug one pump into each. - Set the pump with the SynchroLinc float to initiate at a higher water level so that it should never be activated unless the ApplianceLinc pump fails. - Write programs to detect if the SynchroLinc pump ever kicks in, then the ApplianceLinc pump has failed and notify help. - To exercise the SynchroLinc pump you could block the ApplianceLinc pump occasionally, (make it fail) via ISY schedules, and not only exercise the SynchroLinc pump but also verify, via ISY programs, that it still functions by detecting it's current levels. The ApplianceLinc modules have a fairly heavy contact rating on them. 1HP / 1800 Watts and should switch a sump pump quite easily. https://www.aartech.ca/2635-222-insteon-appliance-module.html

It is how you have the devices connected together that is important. There are several definitions and methods to create a scene. Insteon devices can talk directly to each other using a direct connect scene without any HA controller involved. This cuts ISY out of the picture somewhat but can be worked around with more advanced techniques. ISY has it's own scenes where devices are preset to various levels of brightness and/or ramping speed. The scene can then be treated like one Insteon device in the ISY, and when activated will control every device defined by their presets you have set up and can control in ISY.

I have been thinking of converting to all C temps as I have a mix now but for heating purposes don't you lose the temperature resolution using half degrees C instead of half degrees F? eg: My home thermostat system is using C and is settable to a half degree. At certain times of the day, I find 22.5° C too warm, but 22.0° C too cold. Using F scales I can get 9/5 of the settable C° resolution.

Got more MSes from aartech.ca while they are on sale over the New Years time, so I am eliminating more X10 MS units from my system. I have been attempting to improve the plain battery low sensor for the Insteon MS units with this program for each unit to be monitored. The Wait time needs to tuned for each application keeping in mind if the units sees day/night reliably, and expected motion gaps considering away times. Since these "extra" methods of detecting a dead battery and/or lack of MS function are additional to the usual LowBatt signal they are not required but should act as a back up reminder to missed or forgotten notifications. MS.LowBatt.LLand If Control 'Lower Landing / Motion.LLanding / LowBatt.LLanding' is switched On And Control 'Lower Landing / Motion.LLanding / LowBatt.LLanding' is not switched Off And Control 'Lower Landing / Motion.LLanding' is not switched On And Control 'Lower Landing / Motion.LLanding / Dark.LLanding' is not switched On And Control 'Lower Landing / Motion.LLanding / Dark.LLanding' is not switched Off Then Wait 5 minutes $MS_Battery_Status = $cLOWER_LANDING Else Wait 150 hours Run Program 'MS.LowBatt.LLand' (Else Path) $cLower_Landing is one of many constant variables (Integer) used to identify each room in passed parameters $MS_Battery_Status is a state variable and triggers a program like this for notifications and reset. MS Battery Low If $MS_Battery_Status is not 0 Then Wait 5 seconds Send Notification to 'Text Larry' content 'MS Not Sending' Wait 5 minutes $MS_Battery_Status = 0 Run Program 'MS Battery Low' (Else Path) Else - No Actions - (To add one, press 'Action') The single notification message looks like this ALERT! - MS not sending. ${sys.date} @${sys.time24} In room ${var.2.14}. 10=RecRm 12=AftBr 13=EveBr 14=Libr 16=Util 19=LLand 20=GathRm 21=MBR 29=MudRm 30=Shop

Agreed! Just turn both pumps on and set one float switch level higher than the other so that one always gets used and the other only gets used if the first fails. Rotate them every few years for even wear and verification of life or just check them every few months and exercise the mechanism by hand. If Insteon fails you could have a problem you were trying to avoid. Adding technology always makes it less reliable. Adding to what Teken advised, get a plug-in SynchroLinc monitor for the higher level float unit and if it ever turns on your ISY will know the first pump failed. https://www.aartech.ca/2423a5-smarthome-insteon-synchro-linc.html Editted: for level logic.

If you have a milli-volt control from a thermocouple you will only have a few hundred milli-volts. These units do not recommend having more than one contact in series with the solenoid gas valve and the only switch. The voltage drop can damage your gas valve and you will usually have to replace your burner mechanism. My unit could have a switch and a thermostat in series if I cleaned the contacts once per year. When oxidised the valve would not turn on. If your PLM sends an all On command and you are not home you may cause some danger in your home. Since two series controllers are not recommended it rules out having a high-limit device to shut the fireplace down with overheating when you are not home. You may want to seek some professional advice from the manufacturer on this one. Get names and document for insurance purposes.

This is excellent! but... this would be much better in the Tasker Forum thread created for easier finding. http://forum.universal-devices.com/forum/100-tasker/

Always good to hear!

Currency? Shipping included?

If you have all Insteon devices you could create an ISY scene with all devices in it. HS could probably activate that scene directly.

OK Got it! I can't believe I have read this over so many times and attempted to apply it without success. I think the problem was the "Adjust Scene" pulldown scene list was too long and I never scrolled it up that far to even see these devices at the top. The syntax of the whole thing really is NOT very intuitive, either. I suppose the way to think of this is you are adjusting the levels in the SLD link from the MS. UDI couldn't name it after the SLD because it could contain links from many devices and be ambiguous. The list would have to contain all the combinations (see LeeG's post above) such as "MD-SLD","KPL-SLD", "ISY-SLD", etc..... I hate to say it but I have been messing around with this method for almost a year on and off. I have read some posts attempting to explain this before but it just never clicked. Even tonight I read your post over and over for many hours and began wondering if this was some kind of joke. Either you were or I had to be crazy or maybe both of us. Thank you so much (also LeeG) for your time and persistent efforts. Tis was an extremely bumpy road for me. I owe you a few beers for this one!!!

Here is my test program. It is verified to affect the ISY Scene setup brightness each way but does not affect the SLD or any of my plug-in modules when attempting this. If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then In Scene 'Mudroom / MudRm Walkthrough' Set 'Mudroom / Mudroom Potlights' 0% (On Level) Else In Scene 'Mudroom / MudRm Walkthrough' Set 'Mudroom / Mudroom Potlights' 100% (On Level) Do you see any difference? There is nothing else in this scene to adjust. The MS is not available to adjust in the scene and not in linking mode to take an adjustment. With ISY installing direct connected reciprocal links between the MS and SLD I doubt it that link can be affected by ISY as I stated above. Maybe there is a clue there. Note the direct link was installed by the ISY scene and not "on the side". I have repeatedly tried this technique in five or six locations, in about five or six sessions, every few months, when I become enthused again, unsuccessfully each time and gave up. I have also tried this with direct X10 links in LampLincs and abandoned that idea due to lack of ISY control (in the X10 case ISY doesn't even know the LampLinc is activated). Back to the default method with X10 through the ISY to an Insteon LampLincyou can expect 2-10 seconds of delay sometimes. It would be real nice to make this work. What am I missing?

Using ISY scenes I installed a new SwitchLinc last night to do more testing. I used an existing MS for this. Here is what I found with this SW and MS combination. Before any ISY scene was created = SW contained two links to the PLM Create an ISY scene with just the SW = SW contains three links to PLM Add the MS to the ISY scene = SW contains three links to PLM and one direct link to MS Note: MS has to be put into linking mode at which time ISY writes the direct link to the SW into it. Until then the MS is marked as bad-comm. - In effect ISY has created a direct link between the two devices and now has no ISY control over any part of that scene now existing outside of ISY. - ISY can now control parameters of it's own scene and when the scene is activated the brightness levels and ramp speeds will be effective but only when initiated by the ISY programs or manual operation. - The MS and SW now have their own link and that operation cannot be affected by the ISY scene settings. - This does not seem to be the intended purpose for an ISY scene to have a controller device included in ISY scenes. They appear to serve no purpose, and may be a detriment to intended operations, cutting the ISY control out of the picture. BTW: Removing a device from an ISY scene and/or deleting the whole scene does not remove the direct links from the devices (despite writing to device indications in the Admin Console) . A restore must be done on each device to remove the scene links to ISY or the direct links between devices after deleting/removing the devices from the ISY scene.

Several reasons I use it - The folder colours indicate the program "Then" or "Else" last ran for debugging - I can see the status of things in MobiLinc on my cell phone since it cannot display variables - Other programs can see the status of the program in question although I don't think I ever use that feature.

LeeG Myself and many others report that "then" code will execute when the "If" is called with no condition lines inside it. Are you saying the program can be left, or become, false without any "If" section code and stay that way to cause "Else" to execute each time the "if" section was called?

To help facilitate this process I will rename the old model with a few "X"s at the end lie this "LightSwitchXX" The new one will get the original name used in the programs "LightSwitch" Then with the copy/replace option mentioned by Xathros above the two names are found very close to each other in the list and easy to implement Replace "LightSwitchXX" with "LightSwitch" in all programs. Of course delete the "LightSwitchXX" from the device tree when you are done.

A "direct link" is a link created directly between the MS and the SwitchLinc. This can be done directly between the devices or using an ISY scene and writing the links into the devices. The devices then talk "directly" between themselves without any ISY intervention. ISY can not adjust any settings in this "direct link", from my testing experiences. This "direct link" between a MS and a SwitchLinc or other device reacts almost instantaneously. The eye has a hard time discerning any delay, unlike communicating the MS signal to the ISY and then ISY triggering a scene to be communicated out to the SwitchLinc. Insteon links were designed to work without any controller and be very fast, after the slow X10 protocol it was built on. This "Direct link" is what the OP appears to want but to control the parameters with the ISY. You can't, from my experiences.

I have tried that and you cannot affect a scene directly linked outside of ISY. When you turn the scene on from inside ISY the scene brightness works but when the MS activates the direct scene link the ISY settings have no effect. I use the scene adjust technique for non-direct linked scenes (ISY control) and they work somewhat but not for directly linked scenes.

Here is how I control my directly linked setup. I used a long "just in case" timer for the manual control lest people forget they turned it on at the switch. This happens frequently with automagically controlled lights.

Directly linked scenes are much faster but mostly out of ISY control, unfortunately.

I have tried this in every way I can think of in my setup. I can't make it work. When you adjust the local control brightness of a dimmer with daily programs you are turning the light on to that level at that time. Not acceptable usually. When you set up a direct linked scene between two devices and adjust the brightness of a device in the ISY scene other devices directly linked do not trigger that scene in ISY. With direct linked scenes ISY cannot intervene in brightness or ramp speed. ISY can only monitor. I use a direct linked scene with one dimmer in my mudroom and the speed of response embarrasses the ISY program response speed. I can use this in this location only, as I do not have any need to control brightness, time of day, or ramp speed. I just let it activate during the day. Only time off delay can be adjusted by ISY but for 60 seconds of CFL on energy, a few times during the daylight hours, there is no point. The ballast triggering is the wear out issue on CFLs and the damage is already done. If this can be done some other way I would surely be interested.

You could combine the last two if you don't need to differentiate between the states 1 and 2. Remember the slave subroutine programs should be disabled or they can self trigger. //Generac.SendMessage1 (disabled) If $GeneracIsOn is 1 OR $GeneracIsOn is 2 Then Send Notification to 'steve.sms' content 'Generac.On' Else ---- Another way to skin this cat. //Generac.SendMessage1 (disabled) If $GeneracIsOn > 0 Then Send Notification to 'steve.sms' content 'Generac.On' Else ----