LeeG

Per a post by SLee (Smarthome/Smartlabs rep) on the Smarthome forum the 2413 Dual Band PLM supports substantially more than the 1000+ links indicated in the sales page. The 2413 Dual Band PLM has a faster processor so it may run faster than a 2412. There have been some anecdotal posts on the forums about seeing faster powerline communication with the 2413 when heavy device query activity is done such as querying the entire installed inventory. Smarthome/Smartlabs has discontinued the 2412S PLM so it has a limited existence. Only 2412SR refurbished PLMs are now available. I had not seen any the statement about the 2412 PLM only supporting 800 devices for status. Not even sure what that means. Can you indicate where you saw that. In general it is a good idea to eliminate unnecessary links. The fewer that have to be managed the better but I would not eliminate desired function simply to reduce the number of links.

Mike, I am having Internet problem but it is a local issue. The phone company replaced my DSL modem recently when the old one died. They do not have the new modem user guide online yet (different manufacturer) so I have not been able to login and set up port forwarding for the ISY. Lee

That actually makes sense. The Start Linking option worked well enough to get the device added to the ISY but did not get the Controller link records written. That is only a guess but would be consistent with not seeing anything when the toggle is pressed. Michel does not work Saturdays (he actually gets a day off, go figure ). I'm sure UDI will chime in.

The attempt to display theToggleLinc link database failed because of what I think is a bug in the ISY at 2.7.15. Newer devices indicate and do support the ALDB Extended command for accessing the link database. I think the ISY is using an invalid value in the cmd2 field when issuing this command. Something to do with what the ISY does when working with the IRLinc and somehow has carried over to devices other than the IRLinc. I ran into this testing the EZFlora on the 2.8.0 Alpha which was fixed for the EZFlora in the 2.8.1 Beta. I don’t know if 2.8.1 would work any better with the ToggleLinc. There was a post a few days ago where a user was having trouble adding a ToggleLinc. The suggested work around was to use the Start Linking option for adding devices. That is not an option when attempting to display the device link database. Bottom line is I don’t know what is actually in the device link database but highly suspect the link records are missing. Otherwise you would see Group message activity when pressing the toggle. I’m afraid this one will have to wait for UDI folks to respond unless you want to load the 2.8.1 Beta and try it.

Define a new Scene. Right click on the SLD and select Add to Scene. Set it as a Controller. Right click on the KPL button and select Add to Scene. Set it as a Controller. Click on OK. This definition will cross-link the SLD and the KPL button. When complete the SLD will be a Controller with the KPL button a Responder. The KPL button will be a Controller with the SLD as a Responder. The ISY has a pretty good User Guide that you can download. It provides more detail than I have posted. Also describes how to set the responder information such as bright level and ramp rate if appropriate to the responder.

You are correct about expecting to see messages in the Event log when pressing the ToggleLinc toggle. Try pressing the togglelinc toggle a little longer in the On position. A few users have complained that togglelincs do not respond to On/Off presses as fast as paddles do. You can even hold it On for a few seconds. The worst that will happen is it sends a start dim sequence rather than a simple On. If nothing is sent after holding for a few seconds then the analysis is why the device is not sending anything, or the messages are not reaching the ISY PLM. Did you physically move the togglelinc since the last time it worked correctly. Runs Tools | Diagnostics | Show Device Links Table to display the link records in the togglelinc. This will establish that the ISY PLM can communicate with the togglelinc and that the required link records are still present in the togglelinc. Have the Event Viewer level 3 active when you do this in case the ISY PLM cannot communicate with the togglelinc. Cannot trigger a Program until messages show in the Event Viewer when the toggle is pressed.

How are you factory resetting the ISY?

The following is the link to the error message information .... http://www.universal-devices.com/mwiki/ ... tem_Errors

Simply Remove each device one at a time. Does not take long. Then add each device back with the default option that ignores (and removes) all active links when the device is added to the ISY. You can Factory reset each device to clear all the links and restore the device to all the Factory defaults if concerned over more than active links. You would do this after Removing the device and before adding it back to the ISY.

The If Control "ToggleLinc name" is On should work. Make sure the Program is Enabled and run Tools | Diagnostics | Event Viewer and set Change level: to 3. Press the toggle On and see what event viewer messages are generated.

The Set button procedure described in the Access Point Quick Start Guide is mandatory to insure that the Access Points are being powered from opposite 120V legs. The process does NOT actually link the Access Points to each other as when you link one Insteon device to another. When device to device communication is reliable but PLM to device communication is not, a suspect is the power supply of the PC/UPS that is often powered from the same circuit as the PLM plug point. A simple test to determine if this is a problem is to plug the PLM into a good 3 wire extension cord and plug the extension cord into circuit away from the PC/UPS. If this improves PLM to device communication, installing a Smarthome FilterLinc between the PC/UPS and outlet usually resolves the problem. Power supplies in PCs and particularly UPS devices are so good at removing noise on the powerline that they tend to attenuate (reduce) the level of the Insteon powerline signal to the point of being unreliable.

Suggest you install 2.8.1 Beta. The Event Trace shows the form of the ALDB command used to access the link database (because the device reports I2) has a value of 02 in the cmd2 value. That value is used with an IRLinc to access IR code information but should be 00 when accessing the actual link database in non IRLinc. Thu 08/26/2010 03:54:27 PM : [iNST-ACK ] 02 62 15.2B.DB 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (02)

When you start the Event Viewer click on Change level and set to level 3. The posted trace says a problem exists but no detail. Level 3 will show the actual commands issued and what failed. On the surface it looks like a powerline communication problem. Assuming the ISY is not having trouble communicating with the existing devices such as being able to manually control existing devices the PLM should be okay. Do you have a pair of Dual Band devices such as Access Points coupling the 120V legs.

The I/O Linc relay can be opened or closed with an On command. The Off command will have the opposite effect. I don't have an I/O Linc so I don't know if this is an option that can be set through the ISY. When doing the links with the Set button the I/O Linc relay is set to the state you want it to respond to an On command, then the link is done. I suspect the relay was in the opposite state you want it to be in when the link was established. The I/O Linc user guide (which can be accessed online from the I/O Linc sales page) describes the process of establishing the relay state first. Look under the topic "Linking an INSTEON Controller to Control the I/O Linc Output Relay".

You did fine so far. A Scene can have multiple Controllers with each Controller being able to establish different responder settings. Left click on the Scene name and that will show each responder with their respective settings. Based on the link records I think you will find the I/O Linc set to 0%. Left click on the RemoteLinc button 4 Controller entry under the Scene name. It should be in red. You should see each responder with potentially different settings then were presented when you clicked on the Scene name. The ISY allows you to define different responder settings for each Controller. Clicking on the Scene name shows the responder settings for when the Scene is controlled from the Admin Console or with a Program. Clicking on the RemoteLinc button 4 Controller entry shows the Responder settings for when the RemoteLinc button is the Controller.

The responder link record for the ISY Scene has byte 6 set to 00 which would turn the device Off with a Scene On command (assuming the I/O Linc supports it). 0FD8 : A2 13 0F.9F.2E 00 1F 00 The responder link record for the RemoteLinc button 4 has byte 6 set to FF which is Full On. 0FC0 : A2 04 12.EB.FF FF 1F 00 How did you establish the Scene with RemoteLinc button 4 as the Controller and the I/O Linc as the Responder. It appears the settings for the RemoteLinc Controller are set to 100% for the I/O Linc Responder.

mdyod Actually the link record you displayed may be the responder link record for the ISY itself, not a representation of the link record in the I/O Linc. If the Scene display shows the I/O Linc at 0% then use Tools | Diagnostics | Show Device Links Table to display the link record in the I/O Linc. With two I/O Lincs behaving the same way I am inclined to believe the I/O Linc does not have the function to turn Off in response to an On command. The link record in the I/O Linc itself is the definitive piece of information. If the byte 6 is 00 then the I/O Linc does not have the function to turn Off in response to an On command. Lee

Thanks. The following is the only Group 4 (button 4) link in the display. You should verify that 13.EB.FF is the Remotelinc Insteon address to insure we are looking at the right entry. A2 04 13.EB.FF FF 1F 00 The red FF is byte 6, FULL bright level (On), the responder will go to when the On command is received from the RemoteLinc. This value must be 00 for the I/O Linc to turn Off in response to the On command from the RemoteLinc. Recheck the Scene responder settings. This indicates the I/O Linc is set to 100% On rather than Off. Also the display is of the ISY Link Table, not the Device Link table. They should be the same and since this entry shows Ff rather than the required 00 it is safe to assume for now that the device contains the same link record. However, in the future display the Device Link records.

This is an example of a working responder link record that turns the device Off when an On command is issued. The byte 6 value is 00 which is the key to an On command turning a device Off. 0FE8 : A2 14 12.9F.E4 00 1F 00

A link record is 8 bytes long. There are only 7 bytes posted. Sorry but I think you will have to do the display again and post the full 8 bytes. Is 13.EB.FF the RemoteLinc Insteon address.

Display the link records in the I/O Linc (this is an I/O Linc and not an in-line Linc). You are looking for a record that starts with an A2 in byte 1, has an 04 in byte 2 (for button 4 on RL), has the Insteon address of the RemoteLinc in bytes 3,4,5, and has either a FF or 00 in byte 6. If there is a 00 then the link record is correct and the I/O Linc does not support being turned Off by an On command. If there is something other than a 00 in byte 6 the link record does not have the correct value. EIDT: example of responder link record 0FB8 : A2 04 12.9F.E4 FF 1F 00 A2 : responder link record 04 : Group/Button number of Controller button 12.9F.E4 : Insteon address of Controller FF : bright level responder should go to; FF full bright; 00 Off 1F : ramp rate 00 : output unit number The FF or 00 In byte 6 is the key to what the responder is told to do.

Multiple controllers must be defined as controllers of the scene. Defining one as a Controller and the other as a Responder insures the devices will get out of sync. The ISY will automatically generate all the cross-links necessary to keep the devices in sync when the controllers are defined as controllers. No need to add them as responders. ISY does this automatically.

I had the same question when I moved to the ISY. The ISY makes the actual Scene definition easier. Simple add both devices as Controllers. The ISY assumes the two devices are also Responders and writes the necessary link records to cross-link the devices. If the ISY will allow the LampLinc to be defined as a Controller (open question) then operating the SwitchLinc On/Off will turn On/Off the LampLinc and manually operating the LampLinc On/Off will turn the SwitchLinc On/Off. Just as if you had defined 4 link records as the ISY writes them automatically. If the ISY will not allow the LampLinc to be added to the Scene as a Controller they only way I know to make it work is to Remove the Lamplinc device definition from the ISY and add it back as a SwitchLinc. A SwitchLinc functions as a Controller and a Responder. The newer LampLincs function as a Controller and a Reponder.

When defining the Scene simply make the SwitchLinc a Controller and the LampLinc a Controller. The cross-linking happens automatically without adding either device as a Responder. The ISY may not allow the LampLinc to be specified as a Controller. Please post back whether you are able to define the LampLinc a Controller in the Scene. With this being the second time this question has come up it will likely come up again. Thanks

To keep two Insteon devices in sync they need to be Controllers of the Scene. They are cross linked as responders so no Responder definition is required. Not sure the ISY will allow that with a LampLinc as that device is normally considered a Responder only. LampLincs that were produced in the last few years do function as a Controller as well as a Responder. When this question came up a few weeks ago I don't the results were posted back. If ISY will not allow the LampLinc to be a controller I think you can Remove the LampLinc device definition and add it back specifying it as a SwitchLinc Dimmer. If a newer LampLinc they function the same and use the same command codes. It is not a perfect solution to incorrectly define a device as something it is not but I believe it will work in this case . I don't think you can edit/change the Controller/Responder definition. The type of link record is different between a Controller and Responder. Likely have to remove the device from the scene and then add it back.