From: Gregg L. <gr...@li...> - 2008-04-11 07:49:41
|
Hi Andy, Quoting "M. Andrew Peter" <and...@an...>: > In the interest of brevity, I will respond to Gregg's and Chad's notes > together. > Gregg - I hope you had a good vacation in Germany. Still there; so, sill unable to give a proper response based upon looking at code and trying to reproduce your problem. > I did > not see this problem until I updated to the latest SVN. When I point > back to an "older" SVN, the problem does not occur. ... not sure which code base you might be pointing backward to. But, I can say that there were numerous changes to accommodate device-specific and linking changes. One thing that I didn't catch the first time is that you really should always define light *switches* as IPLL (whereas plugin lamp or appliance adapters can be IPLD). > I did try the following definition to link > the device to itself and then did a "sync links": > IPLL, 0B.75.80:01, Family_Rm_Lt, All_Lights|First_Floor, > Insteon_PLM That's much better since you're now using IPLL. > SCENE_MEMBER, Family_Rm_Lt, Family_Rm_Lt, 19%, 0.1s That is going to cause *lots* of problems as you're essentially doing a circular reference. Please get rid of it and restart. I'll try to remember to modify the code to catch the above condition and throw an error. > After the > "sync links" and a "scan link table" on the switch, here is what is > in log: Do remember to always "scan link table" *before* doing anything that would modify the link table such as sync links. Otherwise, it is possible that mh's understanding of the link table differs from reality. The nightly trigger should normally keep the table updated; but, you should do it manually if in doubt. > 04/08/08 10:10:04 PM menu_run: g=HM m=Insteon i=4 s=7 => action: > Family Rm Lt 'log links' > 04/08/08 10:10:04 PM Running: Family Rm Lt log links > 04/08/08 10:10:04 PM [Insteon_Device] link table for $Family_Rm_Lt > (devcat: 0101): Note the above reference to a proper devcat. I don't recall from your original email message whether mh knew the device type. If you don't see it; then devcat scanning has not yet occurred (it is metered out). Some devices like the RemoteLinc needs to have the devcat manually specified by appending it just after the reference to the PLM in your mht entry. > 04/08/08 10:10:04 PM [Insteon_Device] aldb [0x0FF0] rspndr(01) record > to 0ab011(05): onlevel=20% and ramp=0.1s (d3:00) > 04/08/08 10:10:04 PM [Insteon_Device] aldb [0x0FE0] rspndr(01) record > to $Family_Rm_Lt(01): onlevel=19% and ramp=0.1s (d3:00) The above is obviously a problem and you need to sync links after getting rid of the above SCENE_MEMBER as you've now messed up the link table in your device. > 04/08/08 10:10:04 PM [Insteon_Device] aldb [0x0FD8] contlr(01) record > to $Family_Rm_Lt(01), (d1:ff, d2:1f, d3:00) > 04/08/08 10:10:04 PM [Insteon_Device] aldb [0x0FE8] contlr(01) record > to $Insteon_PLM(01), (d1:32, d2:1f, d3:00) > 04/08/08 10:10:04 PM [Insteon_Device] adlb [0x0FD0] is empty > 04/08/08 10:10:04 PM [Insteon_Device] Checking $Family_Rm_Lt for > duplicate records > > Unfortunately, this did not work either. --Andy > -------- Original Message -------- > Subject: Re: [HM] Insteon: Remote on-level and ramp rate vs. scenes > From: Chadwick E. <dr...@ho...> > Date: Mon, April 07, 2008 9:29 am > To: The main list for the MisterHouse home automation program > <mis...@li...urceforge[1].net> > > Andy, > Check out this page: > http://misterhouse.wikispaces.com/Insteon+Linking+and+Scenes[2] > You may need to set the on-level and ramp speed when you define > your light, or define a SCENE. > Hope this helps, > -Chad > > ------------------------- > Date: Sun, 6 Apr 2008 14:31:40 -0700 > From: and...@an...[3] > To: mis...@li...[4] > Subject: Re: [HM] Insteon: Remote on-level and ramp rate vs. scenes > > Gregg, Here is another variation of this problem. I have the light > $Family_Rm_Lt that I have locally set to come on at 19% when it is > turned on at the switch. It is defined in MH as: IPLD, 0B.75.xx, > Family_Rm_Lt, All_Lights|First_Floor, Insteon_PLM When MH is shut > down and I turn the switch on (tap the top of the switch), the light > comes on at 19%. However, if MH is running and you turn the switch > on (again, tapping the top of the switch), it first goes to 19% and > then jumps to 100% a split second later. It is as if MH noticed the > light came on, yet did not like the fact it was only at 19% and > therefore sent its own command to set the light to 100%. > Here is the log: 04/06/08 04:25:19 PM [Insteon_PLM] Parsing serial > data: 02500b7580000001cb1100 > 04/06/08 04:25:19 PM [Insteon_Device] command:11; type:alllink; > group: 01 > 04/06/08 04:25:19 PM [Insteon_Device] found: on > 04/06/08 04:25:19 PM [Insteon_PLM] Processing message for > $Family_Rm_Lt > 04/06/08 04:25:19 PM [Insteon_Device] $Family_Rm_Lt::set(on, > Insteon_Device=HASH(0x272ac10)) > 04/06/08 04:25:19 PM [Insteon_PLM] Parsing serial data: > 02620b75800f11ff06 > 04/06/08 04:25:20 PM [Insteon_PLM] Parsing serial data: > 02500b75800ca6d82b11ff > 04/06/08 04:25:20 PM [Insteon_PLM] Processing message for > $Family_Rm_Lt > 04/06/08 04:25:20 PM [Insteon_Device] received command/state > acknowledge from $Family_Rm_Lt: on and data: ff > This is happening for other switchlincs that I have also locally > configured to come on to a preset dim. Any ideas on why MH insists > on firing a command to change the dim level of the light to what it > thinks it should be. Is there a way to tell MH how I have configured > the local light so that it does not attempt to override it? > Thanks --Andy > -------- Original Message -------- > Subject: Re: [HM] Insteon: Remote on-level and ramp rate vs. scenes > From: "John R." <jo...@wo...> > Date: Sun, February 03, 2008 12:51 pm > To: The main list for the MisterHouse home automation program > <mis...@li...urceforge[5].net> > > Brian Warren wrote: >> On Sunday 03 February 2008 12:19:12 pm Gregg Liming wrote: >>>> 02/03/08 11:08:53 AM [Insteon_Device] $test_scene::set(on, web) >>>> 02/03/08 11:08:53 AM [Insteon_PLM] Parsing serial data: > 02618011ff15 >>>> 02/03/08 11:08:53 AM [Insteon_PLM] Prior cmd failed >>> ... and, you ran sync-li nks to actually create the link entries > in the >>> plm and device? >>> >> >> I get the same thing and we've just determined that the plm co > ntroller records >> don't exist. >> > > I did not run sync-links...one I did the scene works as expected. > > Thanks to both you... > > John > > ------------------------------------------------------------------------- > This SF.net[6] email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/[7] > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365[8] > > ------------------------- > Going green? See the top 12 foods to eat organic.[9] > ------------------------- > ------------------------------------------------------------------------- > This SF.net[10] email is sponsored by the 2008 JavaOne(SM) Conference > > Register now and save $200. Hurry, offer ends at 11:59 p.m., > Monday, April 7! Use priority code J8TLD2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone[11] > > ------------------------- > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365[12] > > > > Links: > ------ > [1] mailto:mis...@li...urceforge > [2] http://misterhouse.wikispaces.com/Insteon+Linking+and+Scenes > [3] mailto:and...@an... > [4] mailto:mis...@li... > [5] mailto:mis...@li...urceforge > [6] http://sf.net/ > [7] http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > [8] http://sourceforge.net/mail/?group_id=1365 > [9] > http://green.msn.com/galleries/photos/photos.aspx?gid=164&ocid=T003MSN51N1653A > [10] http://SF.net > [11] > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > [12] http://sourceforge.net/mail/?group_id=1365 > |