Xathros

Luckily, the ramp rate and On level are in the responder link records - not the controller link record. No changes necessary to the MS only the target responder. If I get some free time this evening, I'm going to build a test setup of this scenario to document and screenshot. I don't have the necessary parts at the office to test with. -Xathros

Then try this, adjust the settings on your computer's network connection to have the same netmask and then try to access the ISY and fix the netmask. Then set your computer's netmask back to 255.255.255.0 -Xathros

Larry- Responses in BLUE above. -Xathros

Do you know what you changed the netmask to? -Xathros Sent from my iPhone using Tapatalk

I suspect what Larry is getting at here is that using a scene with the MS as a controller is faster than triggering with a program. If that is the case then I 100% agree. I'm just unsure of what exactly he means by "Direct Link". -Xathros

Larry- If the scene was defined outside if the ISY this is quite true as the ISY has no idea of the link records. If however, you were to reset the devices and re-add them to the ISY and define your scene using the ISY, then you DO have the ability to do this. In general it is recommended that you don't do "Set Button Linking" outside of the ISY. What we are trying to do here is update a responder link record to set an on level of 0 at certain times. The MS still fires and activates the scene. Only the scene OnLevel is 0 so in effect the lights stay off. Downside - if the lights are turned on manually, motion will turn them off. Kind of a narrow use case but it fit the OP's need. -Xathros

Larry- As the OP did, you need to select the scene controller in the adjust scene statement (the motion sensor) and set the responder on levels to 0% -Xathros

How about when the switch is turned off, have a program issue an adjust scene statement that sets the on level for the scene to 0%. You will need a second program to modify the on level for when you want the light to come on with motion. -Xathros Sent from my iPhone using Tapatalk

Antonio- I am unable to duplicate that behavior here. I highly suspect program involvement. On the Programs Summary tab, sort by last run time. Query your KPL and then look to see if any programs were triggered as a result. Analyze any programs that react to the query to see if they may be turning off the KPL button(s) -Xathros

Anytime. Happy to help. -Xathros

Unless a program Then or Else ends with a Run Program .... statement, execution simply ends at the last statement. Event driven programming in the ISY is not necessarily a linear program flow like a BASIC program. Many things (threads) can run in parallel. Take for example: Program: TestProgram If Then Run Program1 (If Path) Run Program2 (If Path) Run Program3 (If Path) Run Program4 (If Path) Run TestProgram (Else Path) Else Run Program5 (If Path) Run Program6 (If Path Selecting Run Then on TestProgram will result in programs 1 through 6 all running simultaneously. -Xathros

bbconvert- What are you querying? The Primary node (ON/Off for a KPL6 or A for a KPL8) or one of the secondary nodes? I believe when querying a multi-node device, you should always query the primary node and the ISY will update the status for all of the device's nodes at once. -Xathros

John- You need a scene containing only the KPL button as a responder. Then just turn off the scene. Adjusting the backlight levels affects the backlight brightness globally for all of the KPL's buttons and does NOT change the state of the button. -Xathros

naPS- Assuming you are running the current firmware 4.2.18, then the place to report suspected bugs would be in the 4.2.18 Firmware thread at: http://forum.universal-devices.com/topic/14420-release-4218-is-now-official/ Otherwise, look for the announcement thread for the version you are running. If you are more than a few versions behind, I recommend you update to the current version and recheck to see if your problem still exists first. -Xathros

Yep. Didn't scroll far enough up for the name. Sorry. -Xathros

Anytime. Always happy to help. -Xathros

For what it's worth, the only manual I remember seeing the full description in was the manuals for my access points. -Xathros

Hi bh56- Its not the ISY. More than likely, its the 2441TH not being able to handle a spike coming from your HVAC equipment. Assuming its your furnace based on the time of year. Some with gas fired furnaces have reported this as a result of a spike sent when the furnace either fires or shuts down. There are a number of threads on here about this very issue and some of the steps that have been taken to try and remedy the situation. I don't recall if there was ever a final accepted solution however. Personally, I think some form of OptoIsolator between the stat and the HVAC equipment is the way to go. Here is a link to one of the threads on this: http://forum.universal-devices.com/topic/9105-a-new-2441th-issue/?do=findComment&comment=72648 Hope this helps. -Xathros

Hi Jimbo- I have a few programs in my set up that do this sort of thing. Let me give you a few ideas. First, Program: Back Deck Timer Daytime If From Sunrise + 1 second To Sunset - 1 second (same day) And Status 'Back Porch / Back Porch Flood Light' is On Then Set Scene 'Back Porch / Back Porch' Off Else - No Actions - (To add one, press 'Action') No reason for the floodlight to be on during daylight hours. If a someone turns it on accidentally, turn it back off. If it was left on before sunrise, turn it off at sunrise. Second, Back Deck Timer Nighttime If From Sunset To Sunrise (next day) And Status 'Back Porch / Back Porch Flood Light' is On Then Wait 15 minutes Set Scene 'Back Porch / Back Porch' Off Else - No Actions - (To add one, press 'Action') 15 minute timer. Adjust delay as necessary to suit your needs. Next, Program: Back Deck Timer Disable If Control 'Back Porch / Back Porch Flood Light' is switched Fast On Then Disable Program 'Back Porch Timer Daytime' Disable Program 'Back Porch Timer Nighttime' Resource 'TIMER: Back Deck Timer Disabled' (Notify me if timer is disabled) Else - No Actions - (To add one, press 'Action') Disable the timer for those times when we are working out there and need the lights to stay on beyond the normal timeout. And finally, Program: Back Deck Timer Enable If Status 'Back Porch / Back Porch Flood Light' is Off Then Enable Program 'Back Porch Timer Nighttime' Enable Program 'Back Porch Timer Daytime' Else - No Actions - (To add one, press 'Action') Re-enable timer when light is turned off for any reason. (Self correcting system) I have a set of these for each of my outside lights. Works like a champ. I also have a midnight cleanup routine that will turn most things off at midnight if left on. I have one KPL button in my master bedroom that will override this and a number of other automations in the rare event we have a party or something running that late into the evening (NewYear's eve etc.) Hope this helps. -Xathros

We will likely need to stop referring to the beacon test as the 4 tap test as Insteon progresses into the new flow chart (I forget their name for it) method of configuring devices. Also, do you have the full manual for your dual band devices or the "Quick Start Guide" as the beacon test is usually not covered in the abbreviated quick start guides. -Xathros

Sounds like some missing link records or comm errors to me. Start the event viewer at level 3 and select restore device on the KPL from the ISY and see where that takes you. Post the event trace if the restore does not solve the problem. -Xathros

On the remote/client end, port forward port 443 through the router and point it at the ISY. Set up a DynDNS service to track the external IP of the router/modem. Then in your ISY Finder simply add the url pointing to https://DynDNSname:443 -Xathros

The beacon (4 tap test) only applies to dual band devices / access points / range extenders. Single band (power line only or RF only) are incapable of bridging the power line legs via RF. You will find no mention of the beacon test in any single band device manual. -Xathros

Blame it on the solar flares! -Xathros Sent from my iPhone using Tapatalk

Just put a wait 3 before the scene off command. -Xathros Sent from my iPhone using Tapatalk