LeeG

Need a few more Adjust Scene statements. Those that are setting Scene Responder On Level is for the Scene name which applies when the Scene name is used in a Program or the Scene controlled through the Admin Console. The ISY PLM is the Controller for these two situations. When the paddles are pressed the respective devices are the Controllers and those Responder On Levels have to also be set with Adjust Scene statements. The first two statements in the Then clause set the Local On Level for the respective devices. In addition, for those Controllers, the Responder On Level also has to be set. The two new statements in Red set the Responder On Levels. Then In Scene 'Hardware / Family Room Light' Set 'Hardware / Family Room Light' 30% (On Level) In Scene 'Hardware / Family Room Light Slave' Set 'Hardware / Family Room Light Slave' 30% (On Level) In Scene 'Hardware / Family Room Light' Set 'Hardware / Family Room Light Slave' 30% (On Level) In Scene 'Hardware / Family Room Light Slave' Set 'Hardware / Family Room Light' 30% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light' 30% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light Slave' 30% (On Level) Need two additional statements in the Else clause with 100% On Level

The file errors do not mean anything. Two of them are the result of not having any variables defined. Scenes do not have Status as far as Insteon is concerned. I don't use MobiLinc. Is it the devices in the Scene that do not show the correct status? The communication with some devices is poor (the Hops Left=0 previously mentioned) so Scene failures (not Scene Test) would be expected as Scene On/Off does not have the retry built into the Scene command other Insteon commands have.

Since the observed results do not match the other v.41 SwitchLinc let’s see if there is a difference between the commands being issued to establish the Local On Level. With the Event Viewer running at LEVEL 3, click Clear to clear any current trace activity. Select the SwitchLinc node, use the On Level (applied locally) slider to set a 45% On Level. When the Progress bar is complete do the On, Off, On paddle test and the Fast On, Off, On paddle test. Post the trace so that the command used to set the Local On Level can be identified and whether the paddle tests have any results different from when the Adjust Scene statements are used to set the Local On Level.

Thanks Mike. That is actually great news. Means the OP SwitchLinc is not working as yours is. Actually that raises another question. The Local On Level is being set with the Admin Console On Level (applied locally) slider? That is something else the OP can try. The scenario being used thus far is using Adjust Scene to set the Local On Level. Should be the same extended command but that is a variable to eliminate. Thanks again. scastano I believe Mike is using the Admin Console to set what amounts to a static Local On Level. Don't think that will make any difference but that is another test you can run. Click the SwitchLinc node and move the On Level (applied locally) slider to something different such as 55% percent and then do the Fast On, Off, On paddle test after the Progress Bar completes making the slider change.

RichTJ99 SmartLabs is estimating 10 year battery life. Not sure how useful a low batt indication after 10 years would be. Any bets on whether that Leak Sensor will be functional 10 years from now.

Then Repeat Every 2 minutes and 30 seconds Send Notification to 'Default' content 'Water Sensor wet' Actually with the Wait of 2 minutes the email would come every 4 minutes 30 seconds if the Wait is included.

MikeD Can you add a Fast On paddle press into the mix. After the Fast On followed by Off paddle press the next On paddle press goes to 100% rather than the expected 50% for the OP. scastano What Tom is suggesting is a test that will eliminate the ISY as a possible cause of this because the interface to an I2CS SwitchLinc Dimmer has changed. Disable the ISY Program that changes the Local On Levels. Use the SwitchLinc Dimmer User Guide, setting the Local On Level to 100% to confirm the manual change. Then set the Local On Level to 50% and verify that the simple On paddle press does now go to 50% On. Then add the Fast On paddle press into the mix. If the Fast On does not affect later On paddle press operations the I2CS SwitchLinc Dimmer has changed the commands needed to correctly set the Local On Level. I don't think this is the case but Tom raises a good point. Other I2CS devices (I/O Linc being the last one I remember) have required alternate approaches to setting options.

TheWabit Can you do a screen capture of the Scene definition and post to forum. The image should cover the left part of the Scene definition in the My Lighting tree showing all the nodes in the Scene. Are there any Green Icons to the left of any of the nodes?

"The question is, is there a way to reset it? So when I turn the lights off again... the next time a single paddle press ON is executed, the lights come on to the local on level, instead of full on?" Unfortunately I do not have a v.41 to test against so see if the Fast On change is on all the V.41 SwitchLinc or just yours. Nor do I have a vehicle to test against to find some way to bypass the Fast On results. Perhaps someone with a v.41 can add additional information.

"Even if I wait a few seconds between then.... I tap the ON paddle, lights come on to %50.... then I wait 10 seconds and tap the ON paddle again, lights go up to 100%...." All the SwitchLincs I have tested over the years behave this way. Repetitive On paddle presses (not Fast On) cycle the SwitchLinc from the Local On Level to Full On to Local On Level. All the SwitchLincs I have tested operate this way. The difference with the v.41 firmware is that Fast On causes the repetitive On paddle presses to go to full On. That I have not seen before and is not the way my v.38 and v.40 operate. SmartLabs does not publish changes so whether this is by design or an oops or something limited to your SwitchLinc only testing with other v.41 devices will answer.

The ISY is not sending a command to turn the SwitchLinc On. The trace entries show an On paddle press which the ISY marks the device at 50% because that is what the Local On Level is set to. The ISY is expecting the device to react to the Local On Level value. When the SwitchLinc paddle is pressed On or Off it initiates an Insteon Group protocol sequence. The messages sent to the PLM indicate which paddle/button is pressed (On or Off) but carries no information about the actual On level the device went to. This is why the ISY relies on Local On Level information to mark the device On Level. Nothing in these Insteon Group protocol messages contain actual On level. Tue 01/29/2013 06:20:51 AM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 C7 11 00 LTONRR (00) Tue 01/29/2013 06:20:51 AM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=1 Tue 01/29/2013 06:20:51 AM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 06:20:51 AM : [ 20 AD 6D 1] ST 127 Tue 01/29/2013 06:20:51 AM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 06:20:51 AM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 I have no next. The trace shows the Local On Level being set to 0x7F which is nominally 50% Local On Level. Your relating of the actual device reaction is that this is ignored after a Fast On. Testing on a V.38 and V.40 shows these devices honor the Local On Level after a Fast On. Conclusion, v.41 operates differently. Would have to see this from more than one v.41 to know this is not a specific device issue rather than a v.41 firmware design change.

Sorry, my latest Dual Band SwitchLinc is v.40 which works as the v.38 does. The Fast On does not affect the next On paddle press. It comes back to 50% On with a Fast On, Off, On. 20.AD.6D is the SwitchLinc in question?

It should but what KPL button is involved?

RichTJ99 The Repeat goes before the statements to be repeated rather than after. The Repeat is a no-op since there is nothing following it.

I am concerned the SwitchLinc v.41 firmware has changed the way the SwitchLinc is responding. I am testing on a v.38 which does not go back to 100% after a Fast On. I'll see if I have v.41 available for test.

The Hops Left=0 indicates the comm between the PLM and the SwitchLinc is working at the very extreme of reliability. May be producing consistent command response but any additional interference and the setup has nowhere to go except fail. Something to look at after the On Level is resolved. When testing new Program variations keep in mind the ISY does not write the Local On Level information when the ISY thinks the device already has that information. Changing the Program If section and running the Program again is not actually sending the Local On Level information again. To insure the SwitchLinc is receiving the Local On Level change it is necessary to change the Local On Level percentage in the Program, Save change then run the Program. Also a good idea to run the actual section being tested rather than running the If. Run Then or Run Else. Seeing pseudo code rather than the actual Program code leaves open questions. Right click the Program name, select Copy to Clipboard. Then Paste into posts. What is the SwitchLinc firmware level? Right pane, line 2. below device name. I have not been able to recreate the described behavior here. The SwitchLinc goes to the lower On Level with a single paddle press even after a Fast On so long as there is an Off paddle press in between. Thus the question of SwitchLinc firmware level.

To change the SwitchLinc Dimmer Local On Level the Adjust Scene 'In Scene' parameter must specify the node name of the Switchlinc Dimmer, not the Scene name. Also, the only way to know for sure the speed of the paddle double tap On press is generating a Fast On is run Tools | Diagnostics | Event Viewer at LEVEL 3. The annotation of the command name will indicate a Fast On plus the command for a Fast On is 0x12. The Standard On command is 0x11. The double tap On paddle press might be generating two On commands. Regardless of the double tap results the Adjust Scene must specify the SwitchLinc node in both the 'In Scene' and 'Set' parameters. That is the combination the ISY uses to indicate the Local On Level is to be changed.

A backlight level of 0/7 makes an On condition as low as an On LED gets. If you have some visual indication the outside lights are On so the button LED is not required or a short confirmation is okay a Program could be triggered with the button B On and turn the KPL button LED Off 10-20 seconds later. That would provide some initial visual indication at the KPL but only for a short time. Adding button B to an ISY Scene as a Responder with the Program triggered with the On button press turning the Scene Off in 10-20 seconds, the button LED will turn Off without affecting the lights the button turned On.

bh56 I would repeat the test with a small amount of water in a plate rather than using a wet towel. My Leak Sensor works as you describe when using a damp paper towel but I think that is only because there is not enough water for the Leak Sensor to function correctly. Once I started using water the Dry node is On when the Leak Sensor is dry and the Wet node is On when the Leak Sensor is sitting in actual water. I used only enough water to submerge the two metal sensors. Not enough for water to enter the device.

Insteon does not cascade/propagate Scenes. If a device should respond to the All Interior Off Scene it must be a Responder in that Scene. The ISY assumes a Controller is also a Responder so if the All Interior Scene has multiple Controllers assigned those devices do not have to be assigned as Responders.

Assign office KPL button B as a Responder to the All Interior Off Scene.

Post the Program. The Repeat goes before the statement(s) to be repeated.

The first statement in the Program Then sets the Local On Level of ‘SwitchLinc Dimmer DB’ to 50% which affects what happens when the paddle is pressed On. The second statement in the Then clause sets the Scene Responder On Level to 50% which affects what happens when the Scene is invoked from MobiLinc The Else clause sets the Local On Level and Responder On Level to 100%. Scene ‘SceneCrossLink’ has ‘SwitchLinc Dimmer DB’ as a Controller. If From Sunset To Sunrise (next day) Then In Scene 'SwitchLinc Dimmer DB' Set 'SwitchLinc Dimmer DB' 50% (On Level) In Scene 'SceneCrossLink' Set 'SwitchLinc Dimmer DB' 50% (On Level) Else In Scene 'SwitchLinc Dimmer DB' Set 'SwitchLinc Dimmer DB' 100% (On Level) In Scene 'SceneCrossLink' Set 'SwitchLinc Dimmer DB' 100% (On Level)

rsansev Click on the event viewer trace entry (turns pink ?), Ctl - C will copy it to clipboard, then paste to post.

Adding the devices that participate in the same n-way configuration to an ISY Scene as Controllers is the correct definition. The ISY will cross-link all the devices such that they stay in sync. However, proper linking does not compensate for comm issues between the devices. It does sound like there are comm issues. Whether they are all related to CFLs, related to RF limitations when installed in j-boxes with lots of wiring and potential other factors such as metal boxes and/or covers, other sources of noise or signal attenuation, cannot be determined simply by some work and some don't. When a device works when the load is Off but not when the load is On is a good indication the load is contributing to the problem. May not be the only problem. This is about the most frustrating part of Insteon. No good independent tools that plug in to monitor powerline signal levels, noise levels, RF levels, etc. X-10 has lots of them because X-10 has been around for decades and it is open. SmartLabs is a single source that has not seen fit to provide what a DIYer really needs. Off my soap box, evaluate what works, what does not. What is common if anything about what does not work. Time of day make a difference, verify that phase coupling is working well with the 4 tap test. It may be necessary to unplug (just powering Off is not enough) appliances to eliminate as potential sources of interference, either noise or signal absorption. The CFLs concern me particularly since moving to something else has resolved the bedroom problem.