| Author |
|
patrickm
Senior Member
Joined: February 22 2007
Location: United States
Online Status: Offline
Posts: 188
|
| Posted: November 03 2013 at 21:08 | IP Logged
|
|
|
Has anyone been able to setup links in PH for the 2334-222 dual band keypad?
I was trying to replace a 2486DW with a new 2334-222 dual band keypad. I replaced the keypad and put in the new address in the Replace Address field and hit save. PH appeared to writing the links into the new keypad with no NACKs. When it was complete the Disabled field was checked. I unchecked the field and hit save again. PH immediately started trying to write the links again into the keypad but the keypad started NACKing anything sent to it.
I did a factory reset but the device continues to NACK any attempt to identify it or write links to it.
Any help would be greatly appreciated.
Patrick
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: November 04 2013 at 15:23 | IP Logged
|
|
|
That KPL is an I2CS device. Are all the I2CS updates in
place? Not sure the Replace function will handle an I2CS
device from scratch. Post a dozen or so entries from the
Insteon Raw Log so we can see what commands are being
issued.
Factory resetting an I2CS device is the worst thing that
can be done. That wipes out the authorization link record
that must exist for PH (or any app) to control and
read/write link records in an I2CS device.
Edited by grif091 - November 04 2013 at 15:25
__________________
Lee G
|
| Back to Top |
|
| |
traviskleckner
Senior Member
Joined: February 26 2007
Location: United States
Online Status: Offline
Posts: 118
|
| Posted: November 05 2013 at 12:39 | IP Logged
|
|
|
For what it's worth, I've gotten one to write links
(although not a replace, it was a new device.) with all the
I2CS patches in.
As I am sure you now (and has been extensively covered) it
*does not* work in KPL config although it does appear that
it can load data from the KPL but it is clearly bogus.
I can also 100% confirm that writing links with PowerHome
and HomeLinc will cause random breakage of yours links, in
particular when linking with non-I2CS devices.
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: November 05 2013 at 13:31 | IP Logged
|
|
|
Sorry if my post was misleading. PH certainly supports
adding an I2CS device. The way I2CS is currently
implemented PH has to go through a Status Scan to complete
the I2CS evaluation and definition process. This works for
multiple users and I tested it myself with a few I2CS
devices before Dave released the I2CS patch.
The question is whether the Replace function can process an
I2CS device from scratch. I doubt it but Dave will have
to comment on that question.
__________________
Lee G
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: November 05 2013 at 13:51 | IP Logged
|
|
|
Patrick,
Not sure what the state your database is currently in so not sure of the best way to fix but I'll give it a go.
Probably the best way to add new I2CS devices is to either auto-discover them or manually add them with the "Auto Detect" device type enabled. With auto discover, it creates the device and auto-detects the type (creating a new type if necessary) and then configures the I2CS links as necessary. Once that is done and the initial device scan is complete, if you are wanting to replace a device, then I would navigate to the device being replaced and use the "Replace ID" column (vs the replace address) to find the newly added I2CS device. Select and save changes and it should go smoothly.
Since you're beyond that, Im thinking you initially just did a replace address. This will most likely have a bunch of links waiting to be created. If so, I would go to the Devices tab and replace the first character of the address with a V. If your new device has an address of 12.AB.23 then change it V2.AB.23. Save/refresh. Now auto discover the new device as explained above. When that is all complete, delete this newly discovered device and change the address back to what it originally was. Scroll to the right and set IEngine to I2CS and check Use Ext for ALDB. Save changes and re-enable if device is disabled.
Lets see where this gets us.
Dave.
|
| Back to Top |
|
| |
patrickm
Senior Member
Joined: February 22 2007
Location: United States
Online Status: Offline
Posts: 188
|
| Posted: November 12 2013 at 14:56 | IP Logged
|
|
|
Thanks for the replies.
I will try using the auto detect followed by the replace device on my next Insteon replacements.
Is there any difference between the PLM and the Insteon hub in regard to I2CS and Powerhome?
Thanks
Patrick
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: November 13 2013 at 14:45 | IP Logged
|
|
|
Patrick,
The Insteon hub requires the Virtual Serial port plugin. Basically you need to configure the plugin to connect to the IP and port of the hub (check for SmartLinc/Netlinc posts...if you cant find it, let me know and I'll look it up) and create a virtual serial port number. Then you declare a controller of Insteon PLM and point it to the virtual serial port.
Once you've got this connected, then there is no difference in I2CS between a PLM and hub. The only problem is that sometimes the virtual serial port plugin can be wonky and I don't believe anyone has gotten it to work yet in Windows 8. The next version has a direct socket controller for the Hub/SmartLinc/Netlinc devices so won't require the use of the VSP plugin.
Dave.
|
| Back to Top |
|
| |
patrickm
Senior Member
Joined: February 22 2007
Location: United States
Online Status: Offline
Posts: 188
|
| Posted: November 13 2013 at 15:26 | IP Logged
|
|
|
Dave,
I will wait for the next PH version before I get a hub. Do you have any updates on the new version?
Thanks
Patrick
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Dual Band Keypad Issues
