Re: [mh] Insteon problems with new PLM

Factory reset didn't fix anything on the keypad, and I tried it a few 
times.

I reset the PLM to factory, re-ran all the scans, and syncs, with the 
exception of the three "problem children" in the group, and everything 
worked as I expected, including my other keypad's and outletlinks.
I then tried to re-link the three, and scan them, with the result of the 
error itself going away, and the read of the first address in the link 
table just hanging. I still can't find anything outside of being cites 
as a reserved code, as to what the "pre_nak_long_db_search" actually 
means, and what should be done to address it, beyond what I have already 
done.

My network isn't that big right now, about 9 hardwired devices, 4 
plug-in devices and about 10 RF only devices (triggerlinc's, hidden 
doorframe (2845-222) and reed switch styles(2843-222), motion sensors 
and remotelinks).
At this point I am thinking that, for whatever reason, the signal isn't 
getting to that part of the house, as I remember having issues when I 
first installed those devices. The crazy thing is I have a dimmer switch 
up there that works fine. I have enough dualband devices that range 
shouldn't be an issue, but I notice other issues on the network that 
make me think it is more to the house wiring, and RF band, than it is 
with the new PLM.

I swapped the old PLM back in, and it read everything fine, but it isn't 
dual-band, which might be part of the issue with my specific setup that 
I need to work out.


Regards,
Seann Clark

On 10/16/2019 4:31 PM, Spencer Ryan wrote:
> Yeah, factory reset it again, and assuming your devices are i2cs all 
> you should have to do is "link to interface"
>
> On Wed, Oct 16, 2019, 5:30 PM Carl McGrath <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     I have experienced what sounds similar with KeyPadLink units, found I
>     had to factory reset to get them to behave and respond properly.
>
>     On 10/16/19 4:03 PM, Seann via misterhouse-users wrote:
>     > All,
>     > I recently replaced my old, and issue prone PLM (2412S V3.1) with a
>     > new model, a 2413s. While running into issues that I have seen
>     on the
>     > mailing list and forums before, mainly with having to manually
>     re-link
>     > devices with the PLM, I came across an error that I can't find any
>     > data on.
>     > Two of my lamplinc devices refused to sync or link (manual linking
>     > doesn't seem to take either, have tried it two times each way, via
>     > link as controller in MH, and by manually on the PLM via the set
>     > button), and return the error "pre_nak_long_db_search" as part
>     of the
>     > NACK sent back.  I can't find anything at all on google for this
>     > specific message, so I am stumped and wondering if anyone else has
>     > seen this?
>     > The other issue I have run into is I have a Keypadlinc that is
>     > refusing to sync/link, but unlike the lamplinc's it doesn't
>     return an
>     > actual NAK message, it just blankly NACK's anything from the new
>     PLM,
>     > even after a factory reset.
>     >
>     > I am running the latest master branch code, and aside from dropped
>     > messages and table errors on the old PLM, things were working very
>     > well on my issue devices mentioned above.
>     >
>     >
>     > The logs for this, on debug are:
>     > 10/16/19 14:38:50  [Scan all link tables] Now scanning:
>     > $Ceiling_fan_light (3 of 15)
>     > 10/16/19 14:38:50  [Insteon::AllLinkDatabase] WARN The link
>     table for
>     > $Ceiling_fan_light has changed.
>     > 10/16/19 14:38:50  [Insteon::ALDB_i2] $Ceiling_fan_light reading
>     ALDB
>     > at location: 0x0000
>     > 10/16/19 14:38:50  [Insteon::BaseObject] WARN!! encountered a nack
>     > message () for $Ceiling_fan_light.  It may be unplugged, have a
>     burned
>     > out bulb, or this may be a new I2CS type device that must first be
>     > manually linked to the PLM using the set button.
>     > 10/16/19 14:38:50  [Insteon::BaseObject] WARN: Now calling message
>     > failure callback: &Insteon::_get_next_linkscan_failure(1)
>     > 10/16/19 14:38:50  [Scan all link tables] WARN: failure occurred
>     when
>     > scanning $Ceiling_fan_light.  Moving on...
>     > 10/16/19 14:38:50  [Scan all link tables] Now scanning:
>     > $Left_Nightstand (4 of 15)
>     > 10/16/19 14:38:50  [Insteon::AllLinkDatabase] WARN The link
>     table for
>     > $Left_Nightstand has changed.
>     > 10/16/19 14:38:50  [Insteon::ALDB_i2] $Left_Nightstand reading
>     ALDB at
>     > location: 0x0000
>     > 10/16/19 14:38:51  [Insteon::BaseInterface] DEBUG: PLM
>     > command:insteon_ext_received; Device command:read_write_aldb;
>     > type:direct; group:
>     > 10/16/19 14:38:52  [Insteon::BaseObject] WARN!! encountered a nack
>     > message (pre_nak_long_db_search) for $Left_Nightstand. It may be
>     > unplugged, have a burned out bulb, or this may be a new I2CS type
>     > device that must first be manually linked to the PLM using the set
>     > button.
>     > 10/16/19 14:38:52  [Insteon::BaseObject] WARN: Now calling message
>     > failure callback: &Insteon::_get_next_linkscan_failure(1)
>     > 10/16/19 14:38:52  [Scan all link tables] WARN: failure occurred
>     when
>     > scanning $Left_Nightstand.  Moving on...
>     > 10/16/19 14:38:52  [Scan all link tables] Now scanning:
>     > $Right_Nightstand (5 of 15)
>     > 10/16/19 14:38:52  [Insteon::AllLinkDatabase] WARN The link
>     table for
>     > $Right_Nightstand has changed.
>     > 10/16/19 14:38:52  [Insteon::ALDB_i2] $Right_Nightstand reading
>     ALDB
>     > at location: 0x0000
>     > 10/16/19 14:38:52  [Insteon::BaseInterface] DEBUG: PLM
>     > command:insteon_ext_received; Device command:read_write_aldb;
>     > type:direct; group:
>     > 10/16/19 14:38:53  [Insteon::BaseObject] WARN!! encountered a nack
>     > message (pre_nak_long_db_search) for $Right_Nightstand. It may be
>     > unplugged, have a burned out bulb, or this may be a new I2CS type
>     > device that must first be manually linked to the PLM using the set
>     > button.
>     > 10/16/19 14:38:53  [Insteon::BaseObject] WARN: Now calling message
>     > failure callback: &Insteon::_get_next_linkscan_failure(1)
>     > 10/16/19 14:38:53  [Scan all link tables] WARN: failure occurred
>     when
>     > scanning $Right_Nightstand.  Moving on...
>     >
>     > Has anyone seen, and come up with a resolution on this?
>     >
>     > Regards,
>     > Seann
>     >
>     >
>     >
>     >
>     >
>     >
>     > ________________________________________________________
>     > To unsubscribe from this list, go to:
>     > https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>     >
>
>
>
>     ________________________________________________________
>     To unsubscribe from this list, go to:
>     https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>




________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users