Author |
|
cmhardwick Senior Member
Joined: July 08 2006 Location: United States
Online Status: Offline Posts: 290
|
Posted: October 09 2013 at 19:49 | IP Logged
|
|
|
I've got a new keypadlinc dualband, model 2334 and I
can't get it to program. All I get are NAKs when
attempting to program it.
Sample insteon RAW data
TX 02 62 25 08 22 05 29 03
RX SENTINSTEON-0F 43 16 25 08 22 05 29 03 06
RX RECEIVEINSTEONRAW=22 08 22 0F 43 16 A1 29 FF
RX INSTEON NAK-25 08 22
I've tried a factory reset, and made sure the I2CS patch is installed. I also had add a
device type entry, since it wasn't available.
This is the first of this model I've received, but it's
pretty much what's available out there now.
Edited by cmhardwick - October 09 2013 at 22:28
__________________ Cicero, Enjoying automation!
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: October 09 2013 at 22:30 | IP Logged
|
|
|
This appears to be a classic example of an I2CS device
returning a NAK with the last byte being FF.
Since you've verified that the I2CS patch is installed,
it must be a synchronization issue. In the Insteon
Explorer under the Devices tab, set the Insteon Type (for
this new KPL) to Auto Detect and Save. Watch the log and
see if the device properly detects the type. It may not
if you've already defined certain parameters with the
device.
You may need to delete the device (on the devices tab)
and then use the auto discovery on the setup tab to
recreate the device. This should get everything
synchronized I2CS wise.
Let me know how this goes.
Dave.
|
Back to Top |
|
|
cmhardwick Senior Member
Joined: July 08 2006 Location: United States
Online Status: Offline Posts: 290
|
Posted: October 10 2013 at 09:08 | IP Logged
|
|
|
TX 02 62 25 08 22 0F 10 00
RX SENTINSTEON=05 43 16 25 08 22 0f 10 00 06
RX RECEIVEINSTEONRAW=25 08 22 0F 43 16 2B 10 00
RX RECEIVEINSTEONRAW=25 08 22 01 42 43 8B 01 70
RX ENROLLMENTBROADCAST=01 70 25 08 22 01 42 43
After this, my device type shows 48. After a reinit, XXXX - New Insteon Device Type
Seems like I can control it now. There are a LOT of links for this device. I'll update after further testing.
Thanks Dave!!
__________________ Cicero, Enjoying automation!
|
Back to Top |
|
|
cmhardwick Senior Member
Joined: July 08 2006 Location: United States
Online Status: Offline Posts: 290
|
Posted: October 10 2013 at 13:25 | IP Logged
|
|
|
Looks like a rebuild of the device successfully created the links I had in previously. I also renamed the device type to properly reflect what it was and set the parameters.
Thanks again Dave!
__________________ Cicero, Enjoying automation!
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: October 10 2013 at 14:19 | IP Logged
|
|
|
Cicero,
Glad to hear everything is working now. I was going to suggest renaming the XXXX to the appropriate description but see you've already done that.
I prefer the Auto Detect to add new device types since it will query and create the new type with the proper Cat and Sub Cat fields which cannot be determined by just looking at the device. After the device is created, you can then adjust the parameters appropriately.
One other thing, when a new device type is detected, you should only need to close and reopen the Insteon Explorer in order for the type to properly show. A reinit shouldnt be necessary .
Dave.
|
Back to Top |
|
|