LeeG

So long as the user has been warned and proceeds anyway, Buyer Beware. There may be times when it is useful to run a mismatch for test purposes. That is why I suggested a Continue button. Can you elaborate as to why you would want to continue running a session when the Admin Console it is not at the same level as the ISY?

"not sure if that would also send an Insteon "off" message to the ISY " Radio buttons (button groups, mutually exclusive buttons) do not send an OFF when turned Off by another button On press.

SteveSBE There is an insteondetails.pdf document on the SmartLabs web site. It is very old but the basic link record has not changed from 2005/2006. The first byte is a Flag byte which you have covered in your post. There is a 62 which you will see under ISY which is a Controller (E2) link record that has been deleted. Group number is Scene number is Group number. Hardware calls them Groups, user documents call them Scenes. Numbers range from 00-FF The last three bytes have no functional meaning in an E2 Controller link record. In an A2 Responder link record they are On Level 0=Off; FF=100% On - values in between are dim levels Ramp Rate 1F=fastest Ramp Rate; 00 slowest Ramp Rate for old devices, 0.2 seconds on new devices. Values in between are the various other Ramp Rates Unit Number was 00 for single output devices (SwitchLinc, ICON switch, ToggleLinc, etc); now 01 for single output devices - the newest InLineLinc is the first device requiring an 01 in this byte. For KeypadLincs the Unit number identifies the button number to respond 01-08 for 8 button KeypadLinc, 01-06 for 6 button KeypadLinc. I/O devices such as the I/O Linc have some different meanings for these bytes as do the list of SimpleHomeNet devices. Too many variations to cover here. Lee

Don't generate any Scene using a "new" InLineLinc running 3.1.15 Admin Console on ISY 3.1.16. They will not work. The problems running a mismatch are not always obvious.

As far as I know with my testing the MS does not have to be awake. Applying a voltage low enough to trigger the Group 03 On but high enough to allow the MS to function. When I originally tried my 3 battery test I did it with new AAA (not AA as I said before) batteries the MS did not send the Low Bat message. That is when I went to my recycle collection. Took a few tries but eventually found one when used with 2 new batteries generated the Group 03 On message. Happens within seconds of applying power. Voltage was near 4V when I got the message.

By terminal I mean there is no means of making the current Admin Console session compatible with the running ISY firmware. Some of the mismatch symptoms ... No Variables tab Unsupported device when adding device with Auto Discover Cannot find the device type in the Device Type pulldown InLineLinc does not work because the link records are wrong are just the ones that come to mind off the top. None of those symptoms should ever be seen by the user nor should he have to waste time finding the answers. They are all user errors resulting from running a mismatched Admin Console versus ISY and can be detected programmatically and prevented by some warning message when the Admin Console is invoked. When the levels do not match the Admin Console should not be used. Of course there will be times when a beta drop does not affect the Admin Console and running a mismatch will not result in problems. For many users who do not follow the forums day to day or work with the ISY nearly every day they will be helped by making them aware of a mismatched configuration. Trying to document what Admin Console levels are compatible with what ISY firmware is needless work.

The Motion Sensor does not send a message when a new battery is installed. You have to Query the motion sensor (maybe sync under HL) for it to pick up the battery level. Definitely do not have to remove the device and add it back to HL to get current conditions. I don't have a motion sensor under HL right now so I cannot test this but I did have MS's under HL before. There is a command/function (maybe sync) that directs HL to get the current MS information. It all comes back in the same Extended Set/Get 2E request. Once the function is queued HL waits for the next Motion On and performs the function.

sectechie The first four Opto-Isolated Inputs are wired the same way. Connect I1+ to 12v Connect I1- through door switch to GND When the contact is closed GND is applied to Input 1 which will turn it ON. Depending on whether using a NO or NC contact ON will indicate door open or door closed. The next three contacts will connect to I2,I3,I4 in the same way. The fifth is more complex. It will use !5/Anolog1. This input operates in digital mode by default (like I1,I2,I3,I4). However, it requires a 1/4 watt or 1/2 watt 10K resister from I5/AN1 to a +5V DC supply. Since the EZIO6I only has 12V DC a fixed 5V supply has to be constructed. Radio Shack has a simple 5V power supply chip for a few dollars. Connect door 5 contact between GND and I5/AN1. The resister used on I5/AN1 is known as a pull up resister. It applies +5V DC to I5/AN1 when the door contact is open turning the Input OFF. When the door contact is closed GND is applied and the input turns ON. THIS IS IMPORTANT. Until I5/AN1 is used and I6/AN2 always must be connected to GND to keep them from cycling. This should be done before plugging in the EZIO6I and adding it to the ISY. Otherwise these floating Inputs can cycle On and Off causing device add problems and flooding the powerline with unwanted On/Off messages. Lee

"Where do I get the WSDK?" Use this link to see the 3.1.16 announce. There is a link to the WSDK toward the bottom of the post. viewtopic.php?f=25&t=6015

I can create the Low Bat message. I have a 3 AA cell battery holder that I attached a 9 volt snap connector. By using some old AA batteries that I accumulate waiting to take a pile to the recycle center, I can find some with voltage low enough to trigger the Group 3 message.

Thanks Michel for considering the function. Since a mismatch between ISY Firmware and UI level is normally terminal (perhaps with a Continue button that allows for some exception testing) the user should never see the popup unless the Admin Console is incompatible with the ISY and should not proceed anyway.

Unfortunately they do odd things when the battery is low. False motion messages, missed motion messages are two I have seen with a low battery.

I propsed that check in the past. There was an issue with implementing such a check across all the Admin Console variations and UDI declined the idea. At least now the UI line in later Admin Console versions provides a positive indication. Before that one had to search through the New INSTEON Device Device Type pulldown list looking for particular device types knowing what image added particular devices. My hope is that at some point in the future when the UI information is available in all the Admin Console variations a programmatic check can be implemented. That would sure save users from the symptoms of running a mismatch because the Help | About was not checked. There have been 2 topics just this year alone where the UI line provided definitive information regarding running mismatches. If a programmatic check had provided a warning popup the problems would never have lasted long enough to require forum assistance. In case it is not obvious, this is a sales pitch for a programmatic check.

The ISY firmware level is 2.8.16 in both cases. That cannot change without loading a new ISY image. What is changing is the Admin Console code that is being invoked. "In this version it is firmware 2.8.16 and UI 3.1.13." The UI 3.1.13 line in the Help | About display is identifying an Admin Console for one of the later 3.1.x Beta images. That version of the Admin Console should never be run with an ISY Firmware of 2.8.16.

Set On Level to 0% and Ramp Rate to 9 minutes. These values result in 00 00 in the first two data bytes in the Responder link record which is what the EZFlora is expecting for Zone control.

1. Fast On/Fast Off have the same effect as On/Off when controlling a Zone directly 2. Do not change On Level or Ramp Rate values. The corresponding bytes in EZFlora link records have different functions. EDIT: Fast On/Fast Off have no effect on EZFlora Zones when used in a Scene command. The EZFlora is expecting On/Off commands only in Scenes.

A Low Bat is a Group 03 On. It will look similar to the following trace entries Thu 01/05/2012 08:57:26 PM : [iNST-SRX ] 02 50 14.69.A7 00.00.03 CB 11 03 LTONRR (03) Thu 01/05/2012 08:57:26 PM : [standard-Group][14.69.A7-->Group=3] Max Hops=3, Hops Left=2 Thu 01/05/2012 08:57:26 PM : [ 14 69 A7 3] DON 3 Thu 01/05/2012 08:57:26 PM : [ 14 69 A7 3] ST 255 Thu 01/05/2012 08:57:26 PM : [iNST-SRX ] 02 50 14.69.A7 00.00.03 CB 11 03 LTONRR (03) Thu 01/05/2012 08:57:26 PM : [standard-Group][14.69.A7-->Group=3] Max Hops=3, Hops Left=2 Thu 01/05/2012 08:57:26 PM : [iNST-SRX ] 02 50 14.69.A7 00.00.03 CB 11 03 LTONRR (03): Process Message: Ignored Thu 01/05/2012 08:57:26 PM : [standard-Group][14.69.A7-->Group=3] Max Hops=3, Hops Left=2 Thu 01/05/2012 08:57:27 PM : [iNST-SRX ] 02 50 14.69.A7 19.70.06 41 11 03 LTONRR (03) Thu 01/05/2012 08:57:27 PM : [standard-Cleanup][14.69.A7-->ISY/PLM Group=3] Max Hops=1, Hops Left=0 This message does not repeat. Only 1 Low Bat message is sent.

RichTJ99 Every KeypadLinc button has its own set of link records both in the KeypadLinc itself and the ISY PLM. It sounds like the button D link record in the KeypadLinc or the PLM has been lost or is corrupted. Do a Tools | Diagnostics | Show Device Links Table for the KeypadLinc and click Compare button when all the link records have been displayed. There should be a link record for button D that looks like the following ... E2 xx aa.bb.cc zz zz zz xx is an 04 if an 8 button KPL, 06 if a 6 button KPL aa.bb.cc is the Insteon address of the ISY PLM zz zz zz is not important - not related to the functioning of the link record What level ISY firmware is running? Do Programs issue any Adjust Scene statements for the KeypadLinc? Is this a 6 or 8 button KPL? Lee

Sorry, no. Insteon devices do not remember where they were before the last On command. If all the devices should be restored to some Scene level the On/Off commands from the KeypadLinc button can trigger a Program that issues different Scene commands for the On and Off commands. The On command could run a Program Then clause which turns all the devices On and the Off command could run the Program Else clause and issue a Scene On for a different Scene that set the devices to some predetermined state. This would not take into account any devices that had been turned On/Off or dimmed/brighten manually.

It is a firmware update on the ISY and a software update to the Java Admin Console.

If the Current State column normally has status but is empty some times when the Admin Console is started, exit the Admin Console and invoke it again. I have seen this from time to time. Have not seen it at 3.1.16.

RLIKWARTZ Yes. Disabling a device stops the ISY from communicating directly with the device but it cannot stop Insteon Scene processing. A Scene On/Off command identifies the Scene number only. Any device that has a valid Responder link record will react to the Scene command. Disable does not do anything with the actual device. There is no Insteon Disable command. Lee

When the PLM is in linking mode resulting from clicking Start Linking and SwitchLinc sends a message at the 3-5 second mark (mine also beeps) it does not go into linking mode itself (LED blinking) as it is aware the PLM is looking for Responders. Holding the SwitchLinc Set button for 10 seconds did not put the SwitchLinc into Controller linking mode (SwitchLinc LED blinking) in this scenario. Pressing the SwitchLinc Set button for 10 seconds when the PLM is not in linking mode (not looking for Responders) does put the SwitchLinc into linking mode (SwitchLinc LED blinking). It may be that older devices operate differently. In the following Event Viewer trace entries the first line in blue is the PLM being put into linking mode. The message in red is from the device where the Set button was pressed for 3-5 seconds. If the KeypadLinc does not send this message while holding the KeypadLinc Set button it is not operating as newer devices do. It might take more than 3-5 second Set button press but it should not itself enter linking mode (its LED blinking). Thu 01/05/2012 12:25:44 PM : [LNK-BGN ] 02 64 01 00 06 Thu 01/05/2012 12:25:51 PM : [LNK-STAT ] 02 53 M(01) gid=00 16.3F.93 0119 38

The TriggerLinc has an optional operating mode where two nodes are used. The Open node gets On indications, the Closed node gets Off indications. There is a single jumper on the TriggerLinc printed circuit board that controls the option. The TriggerLinc User Guide covers this alternate method. Yes, using the Open node only is the normal approach. Don't know of anyone who uses a TriggerLinc in the alternate operating mode. May be useful where there is no intelligent controller but the second node is of no use when using an ISY.

I'm assuming Start Linking was used. If the KPL went into linking mode the Set button was held too long. It should have sent a message identifying itself as a Responder in 3-5 seconds. For the KPL to go into Controller linking mode it requires 10 seconds of Set button. An old device may operate differently but that is what the ISY is expecting. Once it goes into linking mode the KPL is looking for messages from other Responders rather than identifying itself as a Responder. You might be able to use New INSTEON Device, enter the Insteon address and a device name, leaving the device type set to Auto Discover. This procedure does not use a Set button press to identify the device type. The ISY asks the device what type it is. If it works (device reports a device type known to the ISY) the device firmware level will also be known.