Re: insteon corrupt link table(s)?

> Greetings all,
>
> I am trying to get MH and insteon to work and am having some problems. I
> am using
> MH 2.105 R2020. I will go newer but would like confirmation that
> newer(est) will
> be better.
>
> At the moment, I am trying to get most basic understanding and functions
> working.
> For me, this means ooze - not even crawl.
> I have several X-10 devices in service and I can control them from MH
> with PLM when I have
> necessary info in insteon.mht file.
> I have (of course) a 2413UH PLM and ONE 2486D KeypadLinc.
>
> My test scenarios are:
>
>  From Home -> Browse Items -> [Appropriate Section]
> Turn on, off, and dim load of KeypadLinc. - Formerly successful.
> Create scene that works. Not.
> Make led on KeypadLinc follow state of another button / scene and vs/vs.
> Not not.
>
> I used to be able to control load of keypadlinc but at this point I
> can't be confident
> of what I did to succeed and what was wrong effort in ignorance.
>
> Now, I am getting link table corrupt messages from the KeypadLinc and
> another error (below).
>
> 06/07/12 03:38:41 PM Running: PLM AUDIT - delete orphan links
> 06/07/12 03:38:41 PM [Insteon::ALDB_PLM] #### NOW BEGINNING DELETE
> ORPHAN LINKS ####
> 06/07/12 03:38:41 PM [Insteon::ALDB_i1] Delete orphan links: skipping
> $Test_light because health: corrupt. Please rescan this device!!
> 06/07/12 03:38:41 PM [Insteon::ALDB_i1] Nothing else to do for
> $Test_light after deleting 0 links
> tie_events eval error: Can't use an undefined value as an ARRAY
> reference at /home/misterhouse/mh/bin/../lib/Insteon/AllLinkDatabase.pm
> line 1996, <GEN1151> line
> 11.
>
> And this also:
>
> 06/07/12 03:42:17 PM Running: Test light status
> 06/07/12 03:42:27 PM Running: Test light link to interface
> 06/07/12 03:42:43 PM Running: Test light scan link table
> 06/07/12 03:42:43 PM [Insteon::ALDB_i1] $Test_light accessing memory at
> location: 0x0FF8
> 06/07/12 03:42:53 PM Running: Test light log links
> 06/07/12 03:42:53 PM [Insteon::ALDB_i1] Link table for $Test_light
> health: corrupt
> 06/07/12 03:43:03 PM Running: Test light sync links
> 06/07/12 03:43:03 PM [Insteon::BaseController] DEBUG: flagging
> $Test_light for update because existing on level (0) != target (100)
> 06/07/12 03:43:03 PM [Insteon::ALDB_i1] updating $Test_light light level
> controlled by $Test_light and group: 01 with on level: 100 and ramp
> rate: 0.1
> 06/07/12 03:43:03 PM [Insteon::ALDB_i1] WARN: $Test_light write_link
> failure: no address available for record to device: 1C8B49 and group: 01
> and is_controller: 0
> 06/07/12 03:43:03 PM [Insteon::ALDB_i1] DEBUG2: adding link record
> $Test_light light level controlled by $Test_light and group: 01 with on
> level: 100 and ramp rate: 0.1
> 06/07/12 03:43:03 PM [Insteon::ALDB_i1] $Test_light address: FFFFFFF8
> found for device: 1c8b49 and group: 01
> 06/07/12 03:43:03 PM [Insteon::ALDB_i1] $Test_light accessing memory at
> location: 0xFFFFFFF8
> 06/07/12 03:44:00 PM Running: Test light log links
> 06/07/12 03:44:00 PM [Insteon::ALDB_i1] Link table for $Test_light
> health: corrupt
>
> Can anyone tell me if my test case should work? Having the KeypadLinc
> address be
>  the same for both source and destination (button C turn on button
> A(and thus the load)
>  or button C turn on button D)wouldn't happen that often in the real
> world I guess.
>  This would normally not be desired but I am not familiar enough with
> insteon
>  or mh to judge. I am trying to keep my test rig as basic as possible.
>
>
> I have the following in my insteon.mht file :
>
> Format = A
> # -*- mode: perl-mode; -*-
> #
> # See mh/lib/read_table_A.pl  for definition of Format=A items
> #
>
> # My Insteon PLM Interface
> INSTEON_PLM,   PLM,
> #
> # Snip - my X10 entries were here.
> #
> # INSTEON devices
>
> INSTEON_KEYPADLINC, 1C.8B.49:01,        Test_light,         All_Lights
> INSTEON_KEYPADLINC, 1C.8B.49:02,        Test_KP_B2,
> buttons|All_Buttons
> INSTEON_KEYPADLINC, 1C.8B.49:03,        Test_KP_B3,
> buttons|All_Buttons
> INSTEON_KEYPADLINC, 1C.8B.49:04,        Test_KP_B4,
> buttons|All_Buttons
> INSTEON_KEYPADLINC, 1C.8B.49:05,        Test_KP_B5,
> buttons|All_Buttons
> INSTEON_KEYPADLINC, 1C.8B.49:06,        Test_KP_B6,
> buttons|All_Buttons
> INSTEON_KEYPADLINC, 1C.8B.49:07,        Test_KP_B7,
> buttons|All_Buttons
> INSTEON_KEYPADLINC, 1C.8B.49:08,        Test_KP_B8,
> buttons|All_Buttons
>
> # INSTEON_ICONTROLLER, 10, test_scene, all_scenes
>
> # INSTEON_ICONTROLLER, F0, surrogate_scene, hidden
>
> # SCENE_MEMBER, Test_KP_B6, surrogate_scene, surrogate
> # SCENE_MEMBER, Test_KP_B8, surrogate_scene, surrogate
>
>
> # SCENE_MEMBER, Test_light, test_scene, 100%, 0.1s
> # SCENE_MEMBER, Test_KP_B6, test_scene,
> # SCENE_MEMBER, Test_KP_B8, test_scene,
>
> # SCENE_MEMBER, Test_light, Test_KP_B8, 100%, 0.1s
>
> # SCENE_MEMBER, Test_KP_B8, Test_light
>
> I have some errors related to scenes and surrogates.  I am still trying
> to make sense of them. Corrections welcome.
>
> In order to rule out effects from incorrect code for scenes and
> surrogates, I have commented out that code and re-loaded.  I still am
> having problems restoring control of Test_light. What follows is log
> after commenting out scene and surrogate info, stopping mh, upload
> insteon.mht, deleting the the necessary files in data and code and
> re-starting.
>
> 06/07/12 08:15:33 PM Running: PLM show link table to log
> 06/07/12 08:15:33 PM [Insteon::ALDB_PLM] Link table health: unknown
>
> 06/07/12 08:23:50 PM Running: Test light sync links
> 06/07/12 08:23:50 PM [Insteon_PLM] DEBUG2: Sending obj=$PLM;
> interface_data=41A2011c8b49000000 incurred delay of 0.00 seconds;
> starting hop-count: ?
> 06/07/12 08:23:50 PM [Insteon_PLM] DEBUG3: Received raw PLM data:
> 026f41a2011c8b4900000015
> 06/07/12 08:23:50 PM [Insteon_PLM] WARN: PLM unable to complete
> requested PLM link table update (update/add responder record) for group:
> 01 and deviceid: 1c8b49
> 06/07/12 08:24:33 PM Running: PLM AUDIT - delete orphan links
> 06/07/12 08:24:33 PM [Insteon::ALDB_PLM] #### NOW BEGINNING DELETE
> ORPHAN LINKS ####
> 06/07/12 08:24:33 PM [Insteon::ALDB_i1] (AUDIT) Delete orphan because no
> reverse link could be found $Test_light details: responder,
> deviceid=1c8b49, group=08, data=01
> 06/07/12 08:24:33 PM [Insteon::ALDB_i1] (AUDIT) Delete orphan because no
> reverse link could be found $Test_light details: controller,
> deviceid=1c8b49, group=08, data=00
> 06/07/12 08:24:33 PM [Insteon::ALDB_i1] (AUDIT) Delete orphan because no
> reverse link could be found $Test_light details: responder,
> deviceid=1c8b49, group=01, data=08
> 06/07/12 08:24:33 PM [Insteon::ALDB_i1] (AUDIT) Delete orphan because no
> reverse link could be found $Test_light details: controller,
> deviceid=1c8b49, group=01, data=08
> 06/07/12 08:24:33 PM [Insteon::ALDB_i1] Nothing else to do for
> $Test_light after deleting 0 links
> tie_events eval error: Can't use an undefined value as an ARRAY
> reference at /home/misterhouse/mh/bin/../lib/Insteon /AllLinkDatabase.pm
> line 1996, <GEN1291> line 11.
> 06/07/12 08:26:24 PM Running: Test light unlink with interface
>
> Regards,
>
> Peter
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
>