Re: [misterhouse-users] duplicate serial items

[Bill B. <bb...@ld...>]

Bruce,

Looks like my fumbled changing of state names (for consistency of course)
is what broke my code.  I have all of my item definitions in a separate
items.pl file.  Although I made no changes to the motion.pl file, I did
change my items.pl and failed to update motion.pl to match it.  I guess
it worked ok before because I only use the x10 item as an output, I set
it's state, but I never check it's state.

Thanks for the change to allow duplicate items.  I am already putting it
to use and it's working great.

Thanks,
Bill Bass

----- Original Message -----
From: Bruce Winter <br...@mi...>
To: <mis...@li...>
Sent: Thursday, May 04, 2000 9:19 AM
Subject: RE: [misterhouse-users] duplicate serial items


<snip>

> I'm not sure what recent changes might have changed how duplicate items
were
> handled.  I tried your code here and found that it doesn't work because
you
> need to test the state to 'computer room' rather than 'computer'.
>
> You do have a good point, though.  It would be nice to be able to define
an
> ID more than once and have all items get set when data is received.  With
> your version of mh, the last item defined wins, so $pir_motion gets set,
but
> not $computer_torch.
>
> I just updated mh so all items get updated.  I also took out the
'duplicate
> ID' message, as it that should no longer cause a problem.

<snip remainder>