LeeG

Usually restarting the Admin Console will establish a session where the ISY is able to push data to the Admin Console. It seems to happen here when the Admin Console is slow to start because of other system activity although that is only speculation at this point. If you have the Pro version the last two Icons on the right associated with holding updates and RF device updates do not display when this happens. Try just ending and invoking the Admin Console again without doing anything else.

The link records in the Motion Sensor were created successfully. How many times does the Motion Sensor Red LED blink when motion is sensed?

No. The HouseLinc enabled PLM is a USB interface PLM. The ISY requires a Serial interface PLM. The only Serial PLM now being marketed is the 2413S Dual Band PLM. Also note that it is very difficult to manage a given inventory of Insteon devices with two different Automation applications (HouseLinc and ISY). Both establish links in all the devices pointing back to their respective PLMs to facilitate event based activity. There will be continual conflicts with device link records both are trying to manage. You must be an Insteon expert, have extensive knowledge of how the ISY and HouseLinc work internally and will still have problems. Definitely not recommended.

These nodes can be Controllers in an ISY Scene to turn On/Off other Insteon devices. The conditions which the node represent have not occurred for the two that are blank. Like a TriggerLinc that has not been opened/closed yet or a Motion Sensor Dusk/Dawn node that has not yet seen a Dusk/Dawn transition.

RichTJ99 Thanks, 992 is the key number. The PLM link database is full. Run File | Restore Modem (PLM) which should compress out duplicate and no longer used links. When the Restore Modem (PLM) is done run another Show PLM Links Table with Count to verify that the PLM now has substantially less than 992 links. If the number remains at 992 then the number of Scenes has to be reduced to make room for additional device links. EDIT: 992 is the maximum number of links the 2413 will store despite what the sales page spec indicates. I've tested this on a number of different 2413 PLMs. The very lowest storage area is reserved for PLM firmware use so it is not available to store link records. .

dec3169 Delete the Motion Sensor. Use New INSTEON Device, enter Insteon Address, Name of choice, leave Device Type Set to Auto Discover. Be sure Motion Sensor is in linking mode (Red LED blinking) before clicking Ok. When add completes are there three nodes listed for the Motion Sensor.

When the Show PLM Links Table has read all the PLM link records the Count button at the bottom of the window is active. Click the Count button for a count of records read for this Show PLM Links Table run. The Show PLM Links Table has to be done 3-4 times to see if it produces the same Count each time. Unless the Count is the same on several runs the count is not accurate.

A static variable value combination does not trigger a Program. A State variable has to change value while the Folder the Program is under is True. If the Variable values are established while the Folder is False, changing the Folder to True does not trigger the program until the variable value changes.

Starting in March 2012 SmartLabs started manufacturing and Smarthome started shipping devices that contain the newest evolution of the Insteon protocol, I2CS. The I2CS firmware was rolled out incrementally across the various Insteon device types such that now almost every device has the I2CS firmware. A positive test for I2CS is run Tools | Diagnostics | Event Viewer with LEVEL 3. Right click on the device node , select Diagnostics | Query Insteon Engine. Trace entries similar to the following are produced Mon 12/03/2012 03:33:23 PM : [iNST-TX-I1 ] 02 62 20 29 E8 0F 0D 00 Mon 12/03/2012 03:33:23 PM : [iNST-ACK ] 02 62 20.29.E8 0F 0D 00 06 (00) Mon 12/03/2012 03:33:23 PM : [iNST-SRX ] 02 50 20.29.E8 19.70.06 AB 0D FF (FF) A FF or 02 indicates an I2CS device. The I/O Linc was one of the first devices to be shipped with I2CS firmware.

That is the only realistic approach. If you spend enough time analyzing the Export file, developing an application that would take the Copy to Clipboard format and convert to the Export format so that it could be imported. The ISY is not expecting the Import file to be anything but perfect since it was created with Export so any mistake could produce some very unfortunate results. Stick with the Admin Console GUI.

oberkc is very correct, Scenes do not have status. Insteon has no concept of Scene Status. MobiLinc may be generating something to represent the state of the Scene but it did not come from Insteon. I suggest getting the I/O Linc Sensor and Relay working through the Admin Console first. That eliminates one complete variable. I am sure MobiLinc works, just adds to the questions at this point. A Scene can be used to control the I/O Linc Relay as those results will match what Smarthome has published for the I/O Linc. Smarthome does not describe how the I/O Linc Relay reacts to Insteon Direct commands (which is very different from a Scene) because Insteon devices (except for automation applications using a PLM) cannot issue Insteon Direct commands. Some of the confusion when using MobiLinc stems from the fact that MobiLinc will automatically control a Scene instead of a Device when it sees the Device is in a Scene. That is why I suggest doing all the initial testing using the Admin Console. Once that is working with Direct commands or Scenes (as you chose) then introduce MobiLinc into the mix. geogecko If moving from 3.2.6 to 3.3.4 or 3.3.5, 3.2.6 had a bug associated with the Set Options function and the new I2CS I/O Linc. 3.3.4 and 3.3.5 have the fix so there will be differences in what Set Options shows once on 3.3.4/3.3.5.

Does it specifically indicate it is for a Smoke detector circuit. The CO relay also carries the 120X designation.

Terminology seems to be getting us in trouble. There is a reference to a Folder with Action statements but Folders do not have Action statements. There is a reference to doing something at Sunset but nothing posted uses Sunset. Seems like the actual Folder is missing and perhaps the Programs that are controlling the Variables used in the posted objects. As noted before the Programs | Summary page provides information about if a Folder is True or False, if and when a Program is triggered (Last Run Time) and what clause was run (Status True or False).

Click Help | About 3.3.4 is RC1 3.3.5 is RC2

“Does this device work well with ISY?†Yes “ What is the best way to link this device to ISY?†Use New INSTEON Device, enter Insteon Address, Name of choice, leave Device Type set to default Auto Discover. The ISY should be at 3.3.5 (RC2) or later “Once the device is linked, do the 4 different contollers appear in ISY†There will be 4 responder nodes, one for each Relay. A simple ISY Program can be used to turn each Relay On and Off for the desired times. “does the EZIO40 have a programable fail safe off time.†Yes. However the ISY does not support setting the timers. It is necessary to use the SHN Utility Suite (free download from SHN Web site) and a PLM to set the timer values. The EZFlora is a simpler device to use with the ISY. The EZFlora timers are supported by the ISY.

The Fast On response by the SwitchLinc is changed in later versions. I have a v.36 SwitchLinc Dimmer. When a Fast On double tap is done the SwitchLinc goes to 100% On as expected. The next single tap takes it to 25% On. Next single tap goes to 100% On. Next single tap goes to 25% On. The old v.27 SwitchLinc will have to be updated to avoid the 100% On from a single tap following a double tap Fast On.

The connections for I3 and I4 are correct as described. Each 10K resister applies +5V to the respective Input. This puts each Input in the Off state. These resisters are referred to as pullup resisters in the EZIO2X4 documentation. They are necessary on Inputs 3 and 4 because these Inputs can optionally work in Analog mode which makes it impossible to have a pullup resister built into the Input itself. Appling EZIO2X4 GND to either Input turns the Input On. No additional configuration is needed. These Inputs are configured to work when the EZIO2X4 is added to the ISY. That is why these Inputs should be tied to GND if not used so they do not cycle On/Off due to stray electrical noise.

Yes, run Show PLM Links Table with Count 3 to 4 times in a row. Only when the same number of links is obtained can that number be considered accurate. Inbound Insteon traffic processed by the PLM during the Show PLM Links Table process will cause the link records being displayed to be skipped or duplicated. The result is a false Count when the display completes. For a device to send a message and the ISY PLM process it there must be link records in the device pointing to the PLM and the PLM must have link records pointing to the device. The Restore Device trace shows there are link records in the device. That leaves either a communication problem or the possibility the PLM link database is full so it cannot accept the link records for the TriggerLincs. It would be a simple matter to check the PLM link record count except the process is unreliable when any Insteon traffic reaches the PLM. Thus it is necessary to run the Show PLM Links Table multiple times and believe the Count only when that count is the same on several Show runs. oberkc These are RF only TriggerLincs sitting side by side.

“Two things fail at this point. 1) I double click 'Hallway main' to 100% during the 25% timeframe, it won't return back to 25%. Turning it off then on again goes it goes back to 100%. That is NOT the case with 'hallway' switch. It always returns to 25% even after a 100% double click over ride.†The ‘Hallway’ switch always causing the ‘Hallway main’ switch and light to go to 25% with a single paddle tap is because ‘Hallway main’ is being told to turn On as a Responder device of Controller ‘Hallway’. As a Responder ‘Hallway main’ is obligated to react to the Responder link record information which is currently set to 25%. This is correct/expected behavior for an Insteon Responder. The first part, the Fast On double tap going to 100% is correct. Will have to look into the ‘Hallway main’ SwitchLinc reaction to additional single taps after the Fast On double tap. Normally to cycle between 25% and 100% by the load control device the SwitchLinc paddle is tapped once each time. Because this reaction is of the load control device using the paddle on the load control device (rather than a Responder device reaction initiated by ‘Hallway’), all reaction is controlled by the SwitchLinc firmware and Local On Level information in the device. Will have to do some research into a SwitchLinc response after a local Fast On when the initial Local On Level is not set to 100%. †Second item is controlling 'hallway' from the ISY node. ON and OFF change the switches leds up and down but it never impacts the lights.†This is the correct/expected behavior for Insteon. Controlling a specific node On/Off does not cause linked devices to react. Since no load is connected to ‘Hallway’ no light actually turns On/Off. If ‘Hallway main’ node is turned On/Off the ‘Hallway’ status LEDs will not change. Again because controlling an individual device does not cause linked devices to react. To control both devices from the Admin Console or an ISY Program turn the Scene On/Off. What is the firmware level of the ‘Hallway main’ SwitchLinc? This is displayed on the second line in the right pane when ‘Hallway main’ node is clicked in the My Lighting tree.

okay, thanks. Lets verify some of the previous information. You did Set button linking with all the links and local on levels set to 25%. When done manually all things worked turning On to 25% from either paddle, both Status LEDs and actual light level went to the desired 25% On Level with either paddle. What ISY firmware is being used.

The Primary/Secondary designations have no meaning beyond allowing the Smarthome doc to have a positive way to reference each SwitchLinc. They do come prelinked from Smarthome. When each SwitchLinc was added to the ISY was the 'remove existing links' option used?

Ask a real estate agent if Insteon devices would be a plus or minus in a future sale. If the wiring is done such that only Insteon or some other remote control lighting devices can be used there is no fall back plan. There are many electricians who cannot spell Insteon let alone maintain an Insteon installation for a future buyer. Sorry, I did not answer the last question. I would NEVER wire a house that required DIY devices to control it.

A count of 200 seems low. How many nodes are in the My Lighting tree? How many ISY Scenes have been defined? Was the same exact count received for each of 3-4 Show PLM LInks Table runs. You could add the closet SwitchLinc to the ISY and verify the Admin Console will see state changes. That will verify the PLM has room for new links.

Something to think about. If the primary house wiring is done as you suggest it does not allow installing normal mechanical switches in the future if that would be advantageous when selling the house. Not everyone considers automation a plus. I would insure that all switch locations have unswitched power (line and neutral). No running power to a fixture with a simple pair running to the switch.

Not the question asked but be careful about what is sitting in front of the EZFlora devices. These devices produce some heat which can be blocked with that transformer blocking air flow.