error on ICONTROLLER devices from Insteon sync all links

[Sleepyhat]

I loaded the Master code on the evening of 12/26 and since then, my scheduled Insteon "Sync All Links" scans produce the errors listed below. For a little background, my Insteon devices are all lights and sensors. I have some X10 lights and sensors mixed in, but my Insteon does not have X10 functionality turned on. I run everything out of one MHT file. PLM is a physical USB PLM. $lightALL, $Exterior and $Interior are INSTEON ICONTROLLER devices. The den and mst_br lamps are INSTEON APPLIANCELINC devices. The Front, Back and Side lights are either TOGGLE or SWITCHLINCs (defined as SWITCHLINCs in the MHT).

---

12/29/2013 07:41:00 AM: Saving object states ... done
12/29/2013 07:41:06 AM Running: PLM sync all links
12/29/2013 07:41:06 AM [Sync all links] Starting now!
12/29/2013 07:41:06 AM [Sync all links] Adding $lightALL to sync queue
12/29/2013 07:41:06 AM [Sync all links] Adding $Exterior to sync queue
12/29/2013 07:41:06 AM [Sync all links] Adding $Interior to sync queue
12/29/2013 07:41:06 AM [Sync all links] Adding $den_lamp to sync queue
12/29/2013 07:41:06 AM [Sync all links] Adding $mst_br_lamp to sync queue
12/29/2013 07:41:06 AM [Sync all links] Adding $mudroom_door to sync queue
12/29/2013 07:41:06 AM [Sync all links] Adding $front_lights to sync queue
12/29/2013 07:41:06 AM [Sync all links] Adding $back_lights to sync queue
12/29/2013 07:41:06 AM [Sync all links] Adding $side_lights to sync queue
12/29/2013 07:41:06 AM [Sync all links] Now syncing: $lightALL (1 of 9)
tie_events eval error: Can't locate object method "link_data3" via package "Insteon::ApplianceLinc" at /stor/misterhouse/bin/../lib/Insteon/AllLinkDatabase.pm line 1179, line 10.
at mh line 31, line 10.
main::ANON("Can't locate object method "link_data3" via package "Insteon:"...) called at /stor/misterhouse/bin/../lib/Insteon/AllLinkDatabase.pm line 1179
Insteon::AllLinkDatabase::has_link(Insteon::ALDB_i2=HASH(0xac106b8), Insteon_PLM=HASH(0xac35e30), 10, 0, 01) called at /stor/misterhouse/bin/../lib/Insteon/BaseInsteon.pm line 1748
Insteon::BaseDevice::has_link(Insteon::ApplianceLinc=HASH(0xac61af4), Insteon_PLM=HASH(0xac35e30), 10, 0, 01) called at /stor/misterhouse/bin/../lib/Insteon/BaseInsteon.pm line 3082
Insteon::BaseController::sync_links(Insteon::InterfaceController=HASH(0xae63d44), 0, "&Insteon::_get_next_linksync()", "&Insteon::_get_next_linksync_failure()", 1) called at /stor/misterhouse/bin/../lib/Insteon.pm line 555
Insteon::_get_next_linksync() called at /stor/misterhouse/bin/../lib/Insteon.pm line 520
Insteon::sync_all_links(0) called at (eval 3910417) line 1
eval 'Insteon::sync_all_links(0)
;' called at mh line 2482
main::check_for_tied_events(Voice_Cmd=HASH(0xaf03804)) called at /stor/misterhouse/bin/../lib/Generic_Item.pm line 1098
Generic_Item::reset_states2(Voice_Cmd=HASH(0xaf03804), "sync all links", "web [10.0.0.5]", "") called at /stor/misterhouse/bin/../lib/Generic_Item.pm line 1414
Generic_Item::reset_states called at mh line 1505
main::check_for_action called at mh line 3302
main::monitor_commands called at mh line 6723

---

To pre-answer the most common question that I get about my devices, I use the applicancelincs for lamps because I am controlling compact fluorescent lights and they handle that nicely. I use non-dimmable togglelincs for my light switches for the same reason. Most of my lighting is CFL and the togglelincs handle those nicely. They also match every other switch in my house.

Relevant parts of my MHT file contents are listed below (just in case you think that may be a source of the issue):

INSTEON_ICONTROLLER, 10, lightALL, All_Lighting,
INSTEON_ICONTROLLER, 11, Exterior, Ext_Lighting,
INSTEON_ICONTROLLER, 12, Interior, Int_Lighting,

Insteon Devices and Switches

ApplianceLinc Indoor non-dimming Power Module

INSTEON_APPLIANCELINC, 25.B8.D7, den_lamp, Den_Lighting|LightALL|Int_Lighting
INSTEON_APPLIANCELINC, 25.C2.DD, mst_br_lamp, BR_Lights|LightALL|Int_Lighting

TriggerLinc Door Sensor

INSTEON_TRIGGERLINC, 22.AA.0C, mudroom_door, SensorSwitch

SwitchLinc Paddle - front lights

INSTEON_SWITCHLINC, 27.86.EF, front_lights, Ext_Lighting|LightALL|Front

ToggleLinc Switch - Side and Back lights # MH Doesn't have TOGGLE defined - using SWITCH instead

INSTEON_SWITCHLINC, 27.99.8B, back_lights, Ext_Lighting|LightALL|Back
INSTEON_SWITCHLINC, 27.99.A6, side_lights, Ext_Lighting|LightALL|Side

Scene Definition

Scene Link Responder Controller Options

SCENE_MEMBER, den_lamp, lightALL,
SCENE_MEMBER, mst_br_lamp, lightALL,
SCENE_MEMBER, front_lights, lightALL,
SCENE_MEMBER, back_lights, lightALL,
SCENE_MEMBER, side_lights, lightALL,

Scene Link Responder Controller Options

SCENE_MEMBER, den_lamp, Interior,
SCENE_MEMBER, mst_br_lamp, Interior,
SCENE_MEMBER, front_lights, Exterior,
SCENE_MEMBER, back_lights, Exterior,
SCENE_MEMBER, side_lights, Exterior,

Please let me know if you need additional information or if you see something in my setup that may be contributing to this issue.

[mstovenour]

Thanks Robert. I apologize for the hoop jumping request to open the new ticket. It helps me keep all this strait. I assume you must be running on the master branch because of the reference to link_data3(). On the Web UI can you look at the "MrHouse Home" screen and tell me the version you are running? It should look something like this: develop-ref Build 139 (1174d3a)

[Sleepyhat]

Not a problem at all.  Now this may look wonky, because for Insteon, I have been piecemilling my upgrades - I need to get my webdir and codedir completely moved out of my main MH tree to make upgrades easier.  I did a full blown upgrade to 104 on the 15th of Dec.  On the 26th, I upgraded the /lib tree only because I didn't see any changes in any other directories I was using that had also changed since the previous upgrade on Dec 15. 

The /lib branch was pulled from a full Misterhouse-master.tar taken on the 26th.

The Web interface shows:

Version develop-ref Build 104 (b1f8f5d)

Robert
i386@yahoo.com

 

On Sunday, December 29, 2013 10:06 AM, Michael Stovenour notifications@github.com wrote:

Thanks Robert. I apologize for the hoop jumping request to open the new ticket. It helps me keep all this strait. I assume you must be running on the master branch because of the reference to link_data3(). On the Web UI can you look at the "MrHouse Home" screen and tell me the version you are running? It should look something like this: develop-ref Build 139 (1174d3a)
—
Reply to this email directly or view it on GitHub.

[john-]

I am thinking that the approach you took to update mh would be considered "advanced" and difficult for others to support. It may be worth the team to start clean using (in general) instructions on wiki. From there, layer in just your configuration as needed. This would include separating things out as needed to facilitate easier upgrades.

From that points upgrades are as you expect: Pull down new version of mh without stepping on your environment specific installs.

I will defer to whoever is willing to work on this if another approach should be taken but that is my recommendation as it will create a known good base to work from.

[mstovenour]

This is very interesting but I'm 100% sure that this issue only exists because of the way you've tried to manually sync your installation. If your files were based only on (b1f8f5d) then you would not have any references to link_data3(). The branch where I introduced all of the link_data3() changes was after (b1f8f5d).

To be 100% certain I reconfigured one of my LampLinc devices to be an ApplianceLinc and tested quite a few variations of adding, deleting, syncing, pruning, scanning, etc. I am unable to reproduce the error and in fact I cannot imagine how you even got that error. I can only assume that your lib/Insteon/BaseInsteon.pm file is somehow behind lib/Insteon/AllLinkDatabase.pm. There may be (many?) other issues in your installation files but the error above is caused by those to files being out of sync.

Manually updating a running directory by copying files around is very tricky because you can't go by file dates. You must literally "diff" the files between your installation and a git clone. There is a way to do a file system diff between two subdirectories but it is complicated. I sympathize because when Lieven switched the repository over to GitHub, I had several local customizations. I had to clone the latest GitHub master and do a file-by-file diff to my old installation to find all my customizations.

I'm going to close this issue for now. If you still have a problem after running from the latest master zip file or cloning and updating master, then please do reopen this issue and I'll take another look.

[Sleepyhat]

I will work on getting my codedir and webdir moved and see if I can move out to a clean misterhouse-master this week.  I have a duplicate system (hardware wise) that I can prop up to make the move easier.

Thanks for looking into it and I will report back in the problem persists after a clean load.

 

Robert
i386@yahoo.com

On Sunday, December 29, 2013 11:56 AM, Michael Stovenour notifications@github.com wrote:

Closed #343.
—
Reply to this email directly or view it on GitHub.