LeeG

Hopefully someone familiar with a large commercial environment will jump in. I doubt 500 devices per PLM would work as many Insteon devices use 2 link records in the PLM just to add them to the ISY. That would exceed the PLM capacity. When Scenes are added to the equation the number of devices per PLM is even smaller. Really need to do advance planning regarding what device types and how many Scenes are anticipated. Eight button KeypadLincs take 9 links per device to add to the ISY so you can see the type of device is most important. A commercial environment may use metal boxes. Many houses use metal boxes but the distance is not what a commercial environment would be. I think there are too many questions to expect an absolute Yes. Again, someone who has installed large commercial environments will have many of those answers.

In a commercial environment it may be 3 phase power which Smarthome now says is supported with all the Dual Band devices. A PLM holds a maximum of 992 links so multiple PLMs and multiple ISYs would be required for that many Insteon devices. No experience with the other protocols.

Xathros - did not mean to jump into your conversation. Thought you were away from the forum until tomorrow.

Any program that is coded this way needs parens as indicated. The final AND is anding only the last OR in the list without the parens. If ( On Mon, Tue, Wed, Thu, Fri From 6:00:00AM To 8:00:00AM (same day) Or On Sat From 7:45:00AM To 9:29:59PM (same day) Or On Sun From 7:45:00AM To 9:15:00AM (same day) ) And $S.vacation is 0 If ( On Mon, Tue, Wed, Thu, Fri From 3:45:00PM To 9:29:59PM (same day) Or On Sun From 11:00:00AM To 9:29:59PM (same day) ) And $S.vacation is 0 This change is required for all programs with this sequence

There are many posts about Java 51 update. This level of Java requires something additional in the Java image that was not needed back when 3.3.10 was released. Go to Java Security tab and add the ISY IP to the Exception Site List. If/when you move to a 994i 4.1.2 has the additional information. This topic has great post by Xathros with step by step instructions viewtopic.php?f=25&t=13545&p=107380

Variables and Status are fine as Folder conditions. If Status xxxx On If $xxxx = 4 The If Control is checking the command that has just flowed from a device. It would be True only for the instant that the command reaches the ISY. Otherwise the If Control result would be False, not what is needed for a Folder condition. Use If Control as a condition in a Program rather than a condition in a Folder.

Using If Control as a Folder condition does not work. If Control is looking at the command flowing from the device. That would be True only for the small time the command is actually received. That would be used in a Program rather than a Folder. The second Off command appears to be a duplicate message to the ISY and is ignored. The third message (second that is marked ignored) is an I2CS message reflecting the state of the Group message sequence when the button/paddle is pressed. It is not a functional message. On insteon.com there is an insteondetails.pdf document that describes many of the internals of Insteon messages.

Do not know if that is a defective KPL or a change in how non-toggle works. The User Guide does not indicate a change in the way non-toggle ON works but that does not necessarily mean the button LED turning Off is not a new function. The fact that it blinks twice and stays On after the button is turned On with a Scene suggests it is a bug in the KPL but that is also not an absolute. I suggest a call to the Smarthome tech support line and see if they have information that did not reach the User Guide. Most of the time a button LED is Off when the button mode is changed and it has always turned On after the two blinks in non-toggle On mode.

There are reports on the Smarthome forum that the 6V power supply can result in the thermostat generating a flood of humidity messages. One user changed to a 5V supply, one user added a diode in the + leg going to the thermostat to lower the 6V power closer to 5V.

The device is not sending a Fast On or Fast Off in the posted trace. An Off command is sent twice. Looks like the device was not pressed twice fast enough to generate a Fast Off command

Creating Set button links is not good with the ISY. The ISY is not aware of these links and will eventually overlay or delete them. That is why the links do not show under the ISY. The ISY does not support the Humidity Scenes.

"The button itself was setup so that the light was off when I set it up." I have not heard of a button in non-toggle On mode do anything but blink twice and stay On after being pressed. That is how a non-toggle On button is identified versus the button blinking twice and turning Off in non-toggle Off mode. "it stays on unless I go back to the ISY to initiate the scene manually. " What is being done here that is different from "if I initiate this scene from the ISY or Mobilinc, the button toggles to 'on' (lights up)" What is the KPL firmware? Are there any Programs that might turn the KPL button Off?

The upgrade on the UDI web site is for a 994i only, no PLM. It may be less expensive to purchase the ISY update from UDI and a new PLM from Smarthome.

The ISY/PLM functions as both a Controller, turning On and Off devices, as well as a Responder when a device signals a local state change for example. I am guessing the older firmware ApplianceLinc was treated differently. None of the old ApplianceLincs had Controller capability (ability to turn another device on/off) so the Responder (A2) link in the PLM serves no purpose. The link record has more capability than is used in a PLM. There is an insteondetails.pdf document on insteon.com that may provide more information. It was updated a few months ago and I have not looked at the new version. Folks have said it contains the old information and some new information as well.

The number and type of link record varies by device type. A2 EF 1E.0C.0D 05 0B 0B A2 = this is a Responder link record; E2 is a Controller link record EF = Group/Scene number defined by the Controller specs 1E.0C.0D = Insteon address of the Controller that would use this Responder link record The next three bytes have no functional capability when PLM link record 05 0B = cat/subcat of the device (device type) 0B = firmware of Controller E2 00 20.B9.9D 02 09 42 E2 = Controller link record 00 = Group/Scene number controlled by this link record 20.B9.9D = Insteon address of device being controlled by this Controller link The next three bytes have no functional capability when PLM link record 02 09 = cat/subcat of the device (device type) 42 = firmware of Responder

The PLM this device is aware of is 2A.1F.B3 Insteon address. If this is the current PLM the device link table is okay.

The Mini Remote alternates between Bright and Dim. First press and hold issued a Fade Down/Fade Stop second press and hold issued a Fade Up/Fade Stop Wed 02/19/2014 09:51:47 AM : [iNST-SRX ] 02 50 1C.27.E3 00.00.01 CB 17 00 LTMCON (DOWN) Wed 02/19/2014 09:51:47 AM : [std-Group ] 1C.27.E3-->Group=1, Max Hops=3, Hops Left=2 Wed 02/19/2014 09:51:47 AM : [ 1C 27 E3 1] BMAN 0 Wed 02/19/2014 09:51:47 AM : [iNST-SRX ] 02 50 1C.27.E3 00.00.01 CB 17 00 LTMCON (DOWN) Wed 02/19/2014 09:51:47 AM : [std-Group ] 1C.27.E3-->Group=1, Max Hops=3, Hops Left=2 Wed 02/19/2014 09:51:47 AM : [iNST-DUP ] Previous message ignored. Wed 02/19/2014 09:51:52 AM : [iNST-SRX ] 02 50 1C.27.E3 00.00.01 CB 18 00 LTMCOFF(00) Wed 02/19/2014 09:51:52 AM : [std-Group ] 1C.27.E3-->Group=1, Max Hops=3, Hops Left=2 Wed 02/19/2014 09:51:52 AM : [ 1C 27 E3 1] SMAN 0 Wed 02/19/2014 09:51:52 AM : [ 1C 27 E3 1] ST 0 Wed 02/19/2014 09:51:52 AM : [iNST-SRX ] 02 50 1C.27.E3 00.00.01 CB 18 00 LTMCOFF(00) Wed 02/19/2014 09:51:52 AM : [std-Group ] 1C.27.E3-->Group=1, Max Hops=3, Hops Left=2 Wed 02/19/2014 09:51:52 AM : [iNST-DUP ] Previous message ignored. Wed 02/19/2014 09:51:55 AM : [iNST-SRX ] 02 50 1C.27.E3 00.00.01 CB 17 01 LTMCON (UP) Wed 02/19/2014 09:51:55 AM : [std-Group ] 1C.27.E3-->Group=1, Max Hops=3, Hops Left=2 Wed 02/19/2014 09:51:55 AM : [ 1C 27 E3 1] BMAN 1 Wed 02/19/2014 09:51:56 AM : [iNST-SRX ] 02 50 1C.27.E3 00.00.01 CB 17 01 LTMCON (UP) Wed 02/19/2014 09:51:56 AM : [std-Group ] 1C.27.E3-->Group=1, Max Hops=3, Hops Left=2 Wed 02/19/2014 09:51:56 AM : [iNST-DUP ] Previous message ignored. Wed 02/19/2014 09:52:01 AM : [iNST-SRX ] 02 50 1C.27.E3 00.00.01 CB 18 00 LTMCOFF(00) Wed 02/19/2014 09:52:01 AM : [std-Group ] 1C.27.E3-->Group=1, Max Hops=3, Hops Left=2 Wed 02/19/2014 09:52:01 AM : [ 1C 27 E3 1] SMAN 0 Wed 02/19/2014 09:52:01 AM : [ 1C 27 E3 1] ST 255 Wed 02/19/2014 09:52:01 AM : [iNST-SRX ] 02 50 1C.27.E3 00.00.01 CB 18 00 LTMCOFF(00) Wed 02/19/2014 09:52:01 AM : [std-Group ] 1C.27.E3-->Group=1, Max Hops=3, Hops Left=2 Wed 02/19/2014 09:52:01 AM : [iNST-DUP ] Previous message ignored. I confirmed the Mini Remote was is non-toggle mode as it only issued On commands from single tap.

The Program triggers (runs) every time there is motion sensed, at Sunset-30, and Sunrise. If not in the sunset/sunrise time bracket the Program evaluates False and runs the Else leg. If Sunrise happens while in the 2 minute Wait the Set Scene Off will not execute because the Program is triggered with a False evaluation and runs the Else leg. Put a Set Scene Off in the Else leg.

Age should make no difference. The ISY is asking what Insteon Engine the device supports. This command has been in every device I have worked with. At this point the ISY has not asked for the device type. Try factory reset of ApplianceLinc and make sure the Insteon address is correct.

All the traces show the same thing. The device is not responding to the command that is asking for the Insteon Engine supported by the device. There should be an 02 50 responce as in this trace in Red. Perhaps move the devices closer to the PLM. Tue 02/18/2014 10:01:27 PM : [13 8 1b ] Added to list of devices to link to ISY Tue 02/18/2014 10:01:27 PM : [iNST-TX-I1 ] 02 62 13 08 1B 0F 0D 00 Tue 02/18/2014 10:01:27 PM : [iNST-ACK ] 02 62 13.08.1B 0F 0D 00 06 (00) Tue 02/18/2014 10:01:27 PM : [iNST-SRX ] 02 50 13.08.1B 22.80.0B 2B 0D 01 (01) Tue 02/18/2014 10:01:27 PM : [std-Direct Ack] 13.08.1B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Here is an image of the Event Viewer set to LEVEL 3 that must be set BEFORE adding device.

Run Tools | Diagnostics | Event Viewer; at the bottom of the event viewer display is a Level field. Select the pulldown and select Level 3. After selecting LEVEL 3, attempt to add the device. Save the event file and post here. The posted trace file was taken while still in LEVEL 1.

Read the User Guide for the specific device in the area that discusses Local On Level. It describes the two modes the device can operate in. Assuming you have the device Local On Level defined correctly the device ignores that definition when operating in Resume Bright mode. This mode is described in the device User Guide under Local On Level.

Unfortunately it does not matter what the Local On Level is set to if running Resume Bright.

Was the Motion Sensor set up for Dusk/Dawn operation? Lighting outside will change the effect of the Dusk Level. Does the Red LED blink when someone walks past the Motion Sensor? Standing in front of the Motion Sensor does not trip motion. Hands moving may not trip motion if covered in a jacket. The Motion Sensor should be positioned where movement is across the face of the sensor.