RE: [misterhouse-users] progress update: 21 untested items

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi,

I use the Dallas 1wire equipment on my MH system. It uses the DS2406
devices for Input & Output.
Here is a sample of the MHT files -

	IBUTTON, 1200000024200e, Deck_Light,
All_Lights|Outside|Deck_Light, undef, 'A'
	IBUTTON, 12000000248824, Bathroom_Light,
All_Lights|Outside|Bathroom_Light, undef, 'A'

In my code I use the following I/O as well
	#$Deck_Light     =3D new iButton '1200000024200e', undef,'A';=20
	$Deck_PIR       =3D new iButton '1200000024200e', undef,'B';=20

	#$Pool_Light     =3D new iButton '1200000024ea33', undef,'A';=20
	$Pool_PIR       =3D new iButton '1200000024ea33', undef,'B';

	#$Bathroom_Light =3D new iButton '12000000248824', undef,'A';
	$Bathroom_PIR   =3D new iButton '12000000248824', undef,'B';=20

It would be nice to be able to see the inputs (PIR Movement Devices) on
the WEB pages,
but I have not figured out how to change the icons based on the input
state yet.
When I do I will move these into the MHT files.

Note the MHT files need to be able to understand the port reference i.e.
the 'A' or 'B' areas
	IBUTTON, 1200000024200e, Pool_Pump,
All_Lights|Outside|Pool, undef, 'A' #Output to turn on the pool pump
	IBUTTON, 1200000024200e, Pool_ON_OFF_Switch,
All_Lights|Outside|Pool, undef, 'B' #Manual override switch
Both of these use the same device address but specify different ports on
the device.

Regards,

Neil Wrightson.

> -----Original Message-----
> From: Chris Witte [mailto:cwi...@wi...]
> Sent: Wednesday, 12 November 2003 3:33 AM
> To: mis...@li...
> Subject: [misterhouse-users] progress update: 21 untested items
>=20
>=20
> The table A conversion to XML is complete, and I have cleanly tested=20
> exactly half of the 42 different items that can be defined in mht=20
> files.    I have automated the testing process, and it is very simple=20
> for me to test your mht files now, so that any necessary corrections=20
> can be incorporated into the released code.  If you wait, and=20
> complain=20
> that your mht files are broken after an upgrade, it will just=20
> slow down=20
> the migration...and irritate me that we didn't get the fixes=20
> in before=20
> the release.
>=20
> additional contributions are still welcome--especially if=20
> they contain=20
> any of the untested items listed below...   send them to=20
> cwi...@wi...
>=20
> The following items have NOT been verified, b/c I didn't receive any=20
> mht files that use them, and there are no sample .mht files in the=20
> distribution that use them:
>=20
> usage: [AUDIOTRON] ::
> usage: [CAMERA] ::
> usage: [COMPOOL] ::
> usage: [GENERIC] ::
> usage: [MP3PLAYER] ::
> usage: [PA] ::
> usage: [SG485LCD] ::
> usage: [SG485RCSTHRM] ::
> usage: [STARGATEASCII] ::
> usage: [STARGATEIR] ::
> usage: [STARGATEPHONE] ::
> usage: [STARGATETHERM] ::
> usage: [TEMP] ::
> usage: [WAKEONLAN] ::
> usage: [WEATHER] ::
> usage: [X10G] ::
> usage: [X10O] ::
> usage: [X10S] ::
> usage: [X10TR] ::
> usage: [XANTECH] ::
> usage: [YACCLIENT] ::
>=20
>=20
> Thanks to Jason Sharpee,  Bill Young and Bruce, the following items=20
> have all been tested to generate the same code from the xml files as=20
> they did from the table A files:
>=20
> usage: [DOOR] :: 5
> usage: [IBUTTON] :: 9
> usage: [GROUP]
> usage: [LIGHT] :: 35
> usage: [MOTION] :: 21
> usage: [OCCUPANCY] :: 1
> usage: [PHOTOCELL] :: 19
> usage: [PRESENCE] :: 16
> usage: [RF] :: 5
> usage: [SERIAL] :: 55
> usage: [STARGATEDIN] :: 7
> usage: [STARGATEFLAG] :: 18
> usage: [STARGATERELAY] :: 3
> usage: [STARGATEVAR] :: 1
> usage: [VOICE]
> usage: [X10A] :: 35
> usage: [X10I] :: 164
> usage: [X10MS] :: 4
> usage: [X10SL] :: 8
> usage: [X10T] :: 1
> usage: [ZONE] :: 15
>=20
>=20
>=20
>=20
> On Saturday, Nov 8, 2003, at 22:06 America/Chicago, Bruce=20
> Winter wrote:
>=20
> >> Since i didn't receive any objections to the table_a=20
> proposal that I
> >> posted earlier ([misterhouse-users] table_A vs xml_table_A), I
> >> proceeded to make the changes.
> >>
> >> Before integrating the changes into the mainstream mh=20
> code, I'd like=20
> >> to
> >> verify that all  of the different types and syntaxes of=20
> *.mht files=20
> >> are
> >> supported--if possible.  The prior distribution of the=20
> xml_A code has
> >> grown rather incomplete.
> >
> > Sorry I didn't resond to your proposal.  Sounds good to me!
> >
> > My only mht entries are in code/bruce/items.mht.   Nothing fancy in=20
> > there,
> > mostly standard entries.
> >
> > Bruce
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: ApacheCon 2003,
> > 16-19 November in Las Vegas. Learn firsthand the latest
> > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > WebDAV, and more! http://www.apachecon.com/
> > ________________________________________________________
> > To unsubscribe from this list, go to:=20
> > http://sourceforge.net/mail/?group_id=3D1365
> >
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> ________________________________________________________
> To unsubscribe from this list, go to:=20
> http://sourceforge.net/mail/?group_id=3D1365
>=20
>=20