Author |
|
judetf Senior Member
Joined: January 23 2008
Online Status: Offline Posts: 234
|
Posted: September 21 2008 at 07:01 | IP Logged
|
|
|
Two of my four KPLs are returning "Error reading data from KeyPadLinc. Please try again."
Trying again doesn't work (I've restarted PH and it didn't help).
This started happening after moving to the Alpha.
The two that are not coming up are the only two where I ever changed how a particular KPL button functions, having set a couple of buttons on each to be On/Off buttons rather than toggles.
I found two other threads on the forum that mention this problem but saw no solutions, so I'm reposting. Anyone know how I can get back at configuring those KPLs?
Thanks
jtf
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: September 24 2008 at 20:29 | IP Logged
|
|
|
jtf,
Send me an email. I would like to setup a VNC session so I can try some remote troubleshooting.
Thanks,
Dave.
|
Back to Top |
|
|
judetf Senior Member
Joined: January 23 2008
Online Status: Offline Posts: 234
|
Posted: September 25 2008 at 08:39 | IP Logged
|
|
|
Done!
|
Back to Top |
|
|
judetf Senior Member
Joined: January 23 2008
Online Status: Offline Posts: 234
|
Posted: October 05 2008 at 06:58 | IP Logged
|
|
|
Since the other threads that mention this error had no conclusion, I'll post a quick recap of what Dave discovered after taking a look at my system.
While he's not 100% certain, he believes that it is some combination of either the firmware of the two KPLs that are having this problem and/or the PLM I have (which is a brand new one and one that he hasn't had a chance to play with yet), and that the two are failing to communicate correctly (the KPLs are not responding to enrollmentbroadcasts).
The KPLs are both firmware version 43, and the PLM is firmware version 114 (although I think there was something else significant in the specs on the PLM that Dave noted out loud, but which I didn't catch).
Regardless, while most of the communications b/t the two work, not all do. This was most quickly and obviously evident when upgrading to PH 2.0, when PH didn't pick up the devicetype for the KPLs and instead returned -1.
In any event, Dave thought that there was something he could change and would include the change in the next patch to PH, so I'm biding my time and will post hopefully a successful follow-up once that comes out.
Thanks, Dave!!
jtf
|
Back to Top |
|
|
judetf Senior Member
Joined: January 23 2008
Online Status: Offline Posts: 234
|
Posted: February 21 2009 at 08:22 | IP Logged
|
|
|
I'm bumping this back up since the same issue appears to have cropped up with my newly purchased KPL. The device is functioning correctly for the most part, but there is something going on whereby PH isn't fully communicating with it.
When I try to load the KPL config I get an "error reading data from the keypadlinc" and the raw log errors are the same as they were the last time this happened: the NAKs are always an RX Insteon timeout.
If I recall, Dave, when you VNC'd into my machine the last time, you were seeing PH not properly reading the way in which the KPL was sending its firmware information, which was why it wasn't properly detected in the first place and why it was failing to communicate in some specific instances.
While you managed to get the KPLs properly recognized the last time, you also informed me that it wouldn't be until the next PH release that I'd actually be able to load the KPL configs for those new KPLs. That turned out to be true, and as soon as you came out with 2.1 I could read those other KPLs. But now it has happened again with the newest KPL.
Anything to do?
Thanks,
jtf
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: February 21 2009 at 18:06 | IP Logged
|
|
|
JTF,
If PH is having trouble reading the firmware on the new KPL, try manually typing the value in in the "Devices" tab of the Insteon Explorer. Scroll almost all the way to the right and type an appropriate value. It should be something like 38 or 40 (this is what I have in my system). Im not sure what the latest firmware version is for new switches. Save and then try to re-read the KPL configuration.
Dave.
|
Back to Top |
|
|
syonker Senior Member
Joined: March 06 2009 Location: United States
Online Status: Offline Posts: 212
|
Posted: October 03 2010 at 09:32 | IP Logged
|
|
|
FYI - I had this same problem, looked at the device, found it was set to Firmware v41 (which is surprising since I bought this particular KeyPadLinc when they first came out on the market), changed it to 40, and PRESTO, it worked.
Thanks Dave!
__________________ "I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
Back to Top |
|
|