LeeG

johnmsch The ToggleLinc is sending On commands, not Fast On commands. The 11 in the follow excerpt is the ON command. The LTONRR is the ISY interpretation of the command. It will reflect FastOn and where there is now an 11, it will be a 12 (Fast On command) when you are successful in double tapping the toggle. 11 00 LTONRR Tap the toggle twice FASTER to create a Fast On. Lee

johnmsch Run Tools | Diagnostics | Event Viewer with Level 3 or Device Communications Event. Look at the command being sent by the Togglelinc. The timing of a double tap on a ToggleLinc has been a problem. The device may be sending one or two On commands rather than a Fast On. Lee

oskrypuch Tim is exactly right. Inputs 3 & 4 can operate in Digital On/Off mode (default) or Analog mode where an analog voltage is applied to Inputs 3 & 4. Because these Inputs can operate in Analog mode it is not possible to build in a pullup resister. As Tim said either connect Input 3 & 4 to GND to lock both Inputs On or connect a 10K 1/4 or 1/2 watt resister (2 required) between Inputs 3 & 4 to the provided +5V. This will lock the Inputs Off. To use Inputs 3 and/or 4 connect a dry contact switch between the Input and GND leaving the 10K pullup resister connected to +5V. When the dry contact is closed the Input will be connected to GND and be On. When GND is removed when the switch opens the pullup resister will take the respective Input to +5V turning it Off. Lee

reakhavok I did a Factory Reset of my EZIO2X4 and then a Restore Device which returned it to full operation. I think there two possible solutions. Either Delete the EZIO2X4 from the ISY and add it back so that all the links are reestablished for that specific device OR do a File | Restore Modem {PLM} to restore the entire PLM. That is over kill since is looks like all you other devices are working. The problem with Deleting a device from the ISY is that it will be removed from any Scenes and Programs that reference the EZIO2X4. The Restore Modem (PLM) can take a long time if the Insteon installation is large. The Delete and add back will be faster but all the Scene and Program references have to be put back manually. Just depends on which option you prefer. Do an ISY Backup before using either option. Lee

reakhavok Sorry for the delay, I was out of town. It sounds like the links in the PLM have been erased during the process of moving back and forth between images. There are a few things to check first but likely the File | Restore Modem (PLM) will be required. First though... Does the Admin Console show status for all your devices (or is status blank) Does the Admin Console device status change as you press a paddle or KPL button. Does the EZIO2X4 Node associated with where the magnetic switch is connected show a change in status as the door is opened and closed. Lee

Perhaps visually but the motion sensor will not get an ACK from the device(s) for which the link has been removed. This will cause the motion sensor to retry the Group Cleanup message multiple times for each responder that is missing the link. Unneeded Insteon traffic and a battery drain on the motion sensor.

The status of the inlinelinc can be used in a program. If the sense line is controlling the inlinelinc the inlinelinc status reflects the sense line. If the sense line has been overridden by a Fast On or Fast Off command the sense line can change state that is not reflected in the inlinelinc status.

Yes. Simplehomenet provides a service that will refresh the device firmware to the latest level as well as updating the internal PLM to the latest firmware. This service can be ordered online from the SHN web site under Products | Services. Sorry it took so much to get to this point. I don't like to suggest having a device updated unless absolutely certain and necessary. Most of the time the problem is not having added it under a 2.8.x image.

The EZIO4O is currently defined in the ISY with no links (scenes). The Show Device Links Table shows the one end of list entry posted above. The Set button link is done outside of the ISY. Do not change anything in the ISY. The EZIO4O remains defined in the ISY with no Scenes. Put a Controller into linking mode. A SwitchLinc would be fine. A button on the RemoteLinc would be fine. Most controllers will entry linking mode by pressing the On button for approx 10 seconds. Then press and hold the Set button on the EZIO4O until the controller recognizes the EZIO4O. This will take 3-4 seconds to link to most controllers. Tap the EZIO4O Set button once to have the link control relay 1. Press the EZIO4O Set button for 3-4 seconds to complete the Set button link. Press the controller On and Off buttons to confirm the relay turns On and Off (should hear the relay click). This manual linking process is described in the EZIO4O Quick Start guide. Now run a Show Device Links Table in the ISY. I am expecting the link just established with the Set button will not be displayed.

porscheguy The ISY device add for an EZIO4O does not create link records in the EZIO4O because it has no Inputs. The single end of list entry is normal. Lee

The link record is the end of list marker, a 00 in the first byte. The other bytes have no meaning in the end of list record. A factory reset would normally clear all the link database area. This is another indication the PLM memory is large but the PLM firmware is treating it as small. The PLM only cleared the memory it thought it had rather than the memory it really has. The end of active list indicator was set by the ISY during the device add. I will delete my EZIO4O to confirm this but I don't think the ISY establishes any links during the device add process. Since the device has no Inputs there is nothing to establish so the ISY would be aware of Input changes. The ISY does not establish links to the Output Relays until a Scene is defined with a relay as a responder. I’m 95% sure this is a memory size PLM firmware mismatch. Defining a link between a Controller (like the RemoteLinc since you have deleted it from the ISY) with an EZIO4O relay using the Set button on the EZIO4O will confirm this. I expect the Set button link will work but the link record will not display. This will be the result of the PLM writing the Set button link at 0FF8 while the ISY is looking at 3FF8 because of the larger memory being physically present. There will be an audible click when the EZIO4O relay turns On. The relays can be turned On and Off with the Admin Console because Insteon Direct commands are used which do not use link records. I’ll post again after I have deleted and added the EZIO4O to my system and verified that no link records would be expected.

Sorry, I meant to move where the EZIO4O is plugged into to the same location as the ISY PLM to eliminate any question about powerline communication. I don't think it is a communication problem but it is easy to eliminate the question by moving where it is plugged in. The content of the link records should be correct under 1.8.14. It is where they are written in memory. Specifically I am assuming the internal PLM memory is large so the ISY is writing link records at 3FF8 which is where is should for a large memory PLM. I'm concerned the EZIO4O was built around the time that Smartlabs was shipping PLMs which had the large memory anticipating the move to supporting 2000+ links. We have found two PLMs (this would make three if my memory is correct) where the firmware in the PLM was at the old level where the link database memory was small and had the link records starting at 0FF8. If this is the case for your EZIO4O PLM, the PLM is looking for link records at 0FF8 with the ISY writing link records at 3FF8. Again, the physical link record has the correct information, just not written where the PLM firmware is looking. There are some Zebras that I have not covered. There could be an old link record in the EZIO4O that came from 2.7.15 which the PLM is finding. I doubt that since adding the EZIO4O under 2.8.14 would normally erase all the old link records (assuming the default delete exising link records option was used during add). Oh good grief. That could be a problem. The 2.7.15 image would write link records at 0FF8 but the link record content is wrong at 2.7.15. The LD1/2/3 data is not correct for controlling relays. When the EZIO4O was added using 2.8.14 it would not have cleared the links at 0FF8. Sorry. I should have thought about that sooner. I hate to ask this but I would suggest doing a factory reset of the EZIO4O after deleting the EZIO4O from the ISY. Then add it back. The factory reset will clear the entire link database. This will not fix a conflict between the memory size and PLM firmware but will fix the problem if it is related to the links records 2.7.15 wrote that 2.8.14 will not clear.

porscheguy Sorry you are having this difficulty. You have done everything correctly. There was a small window of time when Smartlabs was moving the PLM to the large memory model (supports 2000+ links) where PLMs had the large memory but the PLM firmware used it as though it had small memory. The result of this combination is that the ISY writes the link records where they should be for a large memory PLM but the PLM firmware ignores these link records. The only solution to this is to return the EZIO4O to SHN and have them update the device to the latest PLM and firmware levels. There is a method to determine this condition. It is somewhat involved. Factory reset the EZIO4O, do a Set button link with another Insteon Controller device. The internal PLM firmware in the EZIO4O writes the link record in this case. Use the Show Device Links Table to display the EZIO4O link database. If the Set button link does not display then there is a memory/firmware mismatch. If the link record does display then see if the other Controller device will actually turn the linked relay On and Off. The relay can be heard (click) when it turns On. I ran my initial test here to be sure nothing had regressed at 2.8.14. With it working here either the problem is specific to your EZIO4O or a communication problem where the EZIO4O is plugged. The EZIO4O can be moved to the ISY PLM plug point to see if the ISY Scene will turn the relay On/Off. Lee

porscheguy Thanks for your last post. I was writing mine before seeing the newest post. How old is the EZIO4O? The Scene On/Off from the ISY is only one command. It was necessary to add the device under a 2.8.x image as they are the only images which have the code to determine the size of the internal PLM memory in the EZIO4O. The symptoms appear as though the link records in the EZIO4O are not working. In the past (before 2.8.x) this was the result of the link records being written at the wrong location because of a larger memory in the EZIOxx devices. When you added the EZIO4O did you use the New INSTEON Device AND specify the Device Type as EZIO4O? This is the only technique which has the code to determine the PLM memory size. Lee

porscheguy Which device has the bunch of FF's in the link record? Can you post the link record display. If you can post the Event Viewer (be sure Device communications events set) when the RemoteLinc button is pressed I can be sure but it is normal for several messages to flow from a RemoteLinc (and other RF devices such as Motion Sensors and TriggerLincs). This is the Event Log from my test with RL button 1 controlling EZIO4O relay 4. This is the RL On button press Wed 02/09/2011 12:36:06 PM : [iNST-SRX ] 02 50 11.AD.CF 00.00.01 C7 11 00 LTONRR (00) Wed 02/09/2011 12:36:06 PM : [standard-Group][11.AD.CF-->Group=1] Max Hops=3, Hops Left=1 Wed 02/09/2011 12:36:06 PM : [ 11 AD CF 1] DON 0 Wed 02/09/2011 12:36:06 PM : [ 1 DC 76 4] ST 255 Wed 02/09/2011 12:36:06 PM : [ 11 AD CF 1] ST 255 Wed 02/09/2011 12:36:06 PM : [iNST-SRX ] 02 50 11.AD.CF 00.00.01 C3 11 00 LTONRR (00) Wed 02/09/2011 12:36:06 PM : [standard-Group][11.AD.CF-->Group=1] Max Hops=3, Hops Left=0 Wed 02/09/2011 12:36:06 PM : Duplicate: ignored Wed 02/09/2011 12:36:06 PM : [iNST-SRX ] 02 50 11.AD.CF 00.00.01 C3 11 00 LTONRR (00): Process Message: failed Wed 02/09/2011 12:36:06 PM : [standard-Group][11.AD.CF-->Group=1] Max Hops=3, Hops Left=0 Wed 02/09/2011 12:36:06 PM : [iNST-SRX ] 02 50 11.AD.CF 12.9F.E4 41 11 01 LTONRR (01) Wed 02/09/2011 12:36:06 PM : [standard-Cleanup][11.AD.CF-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 This is the Event Viewer of the Admin Console Scene On button click. There is no status line display as the relay was already On Wed 02/09/2011 12:36:49 PM : [iNST-ACK ] 02 62 00.00.3C CF 11 00 06 LTONRR (00) This is the Event Viewer of the Admin Console Scene Off button click. Wed 02/09/2011 12:37:04 PM : [iNST-ACK ] 02 62 00.00.3C CF 13 00 06 LTOFFRR(00) Wed 02/09/2011 12:37:04 PM : [ 1 DC 76 4] ST 0 This is the Event Viewer of the Admin Console Scene On button click. Wed 02/09/2011 12:37:12 PM : [iNST-ACK ] 02 62 00.00.3C CF 11 00 06 LTONRR (00) Wed 02/09/2011 12:37:12 PM : [ 1 DC 76 4] ST 255 This is the Event Viewer of the Admin Console Scene Off button click. Wed 02/09/2011 12:37:17 PM : [iNST-ACK ] 02 62 00.00.3C CF 13 00 06 LTOFFRR(00) Wed 02/09/2011 12:37:17 PM : [ 1 DC 76 4] ST 0 Lee

What firmware were you running when the EZIO4O was added to ISY? EDIT: I created a Scene with RemoteLinc button 1 as Controller and EZIO4O relay 4 as Responder. RL button controls EZIO4O relay and Admin Console reflects state change and a Query reflects the state of the relay. Note that the EZIO4O has to be added to the EZIO4O under one of the 2.8.x images. If the EZIO4O was added to the ISY under 2.7.15 and then the ISY image updated to 2.8.14 the Scene will not work. If the EZIO4O was added to the ISY under a 2.8.x image what EZIO4O relay is used in the Scene? Lee

Put the RemoteLinc into linking mode by pressing the Dim/Bright buttons together until the LED starts flashing. Right Click on the RemoteLinc node and select Write Updates to Device. Be sure RemoteLinc is within range of a Dual Band device and the batteries are good. Weak batteries and linking mode can be an issue. Tap the All Off button to end linking when update complete. EDIT: if there are no pending updates click on Query after doing the right click, being sure the RemoteLinc is still in linking mode.

Besides the fact that such a function does not exist, it would not work for a Motion Sensor because they are asleep most of the time. It is not possible to remove a link in the motion sensor programattically without waking it up.

The 2.8.14 image just released today fixes a problem with the 2477D/DH. To add a device to a Scene, right click on the device node (under My Lighting tree) and select something like Add Device to Scene ... (something like that, running to a Super Bowl party).

Define an ISY Scene. Add both switches as Controllers of the Scene. Once the Scene information has been written to both switches the devices will be cross-linked. Not a good idea to link outside of ISY or factory reset the devices before adding to the ISY.

clockwrkz The Smarthome forum is a better place for information on this matter. The wires from the top location where there is a neutral (white) and line (black), where the 3 wires to the lower switch originate, two of those wires have to be retasked. The white wire of the 3-wire cable is connected to neutral in the top box. The black wire of the 3 wire cable is connected to the line in the top box. The red wire of the 3 wire cable is capped at both ends. This provides unswitched 120V to the lower switch. The red load control wire of the lower Insteon switch is capped. Once installed and powered the two switches are cross-linked with an ISY Scene where both switches are Controllers of the Scene. EDIT: answered without looking at the diagram. In addition to the change described above the wiring in the fixture has to be changed as well. Either an additional wire must be run from the fixture to the top switch box or you need an InlineLinc installed in the fixture. If using the InLineLinc approach then the fixture wiring is changed to pass through the neutral and line to the top switch box and as described above, on to the lower box. With the InLincLinc neither of the switches in the top nor bottom box physically control a load. They are cross-linked to the InlineLinc as well as themselves. Wired Insteon devices require unswitched neutral and line connections. Again, I suggest using the Smarthome forum for this topic. There are some Insteon users that are past and present electricians which provide great wiring information. Lee

Some of my KeypadLincs do that very rarely when power drops for very short periods of time, .5 seconds to 1 second. Or cycles through several power cycles as the utility equipment automatically resets the feed that has tripped due to a temporary short (such as when a squirrel decides to touch the top of a transformer) and immediately trips again. This is definitely not an ISY issue as this has occurred before I started using an ISY. Normally pulling the air-gap switch for 30 seconds or so will restore KeypadLinc operation.

If it is a 2413 Dual Band PLM then one Access Point should be enough. Some folks install the ISY and PLM in a service closet in the basement which may not provide good RF to another location. Start with one Access Point. The procedure described in the Quick Start guide describes the Set button procedure to verify the PLM and Access Point are in communication and are on opposite 120V legs. If there is a problem then another Access Point or other Dual Band device can be obtained to create the coupling from a location other than the PLM.

Jellis Having a breaker box outside does not prevent the Insteon signals from reach an Insteon device powered from that breaker panel. If the ISY PLM is on one 120V leg and the SwitchLinc is on the other 120V leg then coupling with a pair of Access Points or other Dual Band devices is required. Some folks prefer coupling with a hardwired coupler at the primary electrical panel. This approach works fine but does not provide support for wireless devices such as the Motion Sensor, TriggerLinc, Venstar Thermostat adaptor. There is no one size fits all solutions. I run with a pair of Access Points and no hardwired coupler. I have 2 secondary power panels, with Insteon devices on circuits powered from these secondary panels. One panel is in a detached garage some 300’ wire feet from the house. Depends on how large an electrical installation rather than the number power panels (assuming they are all supplied from the one electric meter). Lee

ELA The Insteon Direct commands the Admin Console and Programs use for direct device control are automatically retried by the PLM should a device fail to ACK the command. If a Direct command fails to cause the device to respond there is definitely a problem as the PLM has tried multiple times. The ACK from the device will show the Hop count on the command that caused the device to respond. That could show how many devices have to repeat the Direct message for it to reach the device. A Direct command to a device that works reliably compared to a device that is intermittent provides a method for seeing the difference between good communication and bad. The Event Viewer does have to be at Level 3 or Device Communications Events. Lee