Re: [mh] Insteon problems with new PLM

Carl McGrath <[email protected]>
Newsgroups gmane.comp.misc.misterhouse.user
Message-ID <[email protected]>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.