Re: [LHA-misc] Line parsing routine

[<HGu...@ao...>]

Ok,

This helps a little, Jay have you documented the commands and the correct 
syntax?

I have added networking support to the HEYU program. Currently you can telnet 
in via a socket interface to the heyu program to status and issue basic 
commands (ie, on/off/dim).

The new HEYU actually supports and handles two types of services: the 
origional X10D (on the hamx10 service port) and a new format on the heyu 
service port. so you can telnet into either port and get the correct 
communicatios format.

I need some feedback from the list, first is this a useful  program (the idea 
is to use HEYU to handle CM11A stuff instead on X10D). 

Second, is there a need for the X10D emulation, do many programs use it? And 
if so is the interface documented (i've been reading the source, but I'm 
missing a lot of information about the interface).

Then lastly, the heyu service (if  you telnet or connect to the heyu port)  
I'm planning on making this new format Jay and Neil are talking about, but I 
need more  information on the proposed syntax to finish up .

If anyone is interested in trying out this new version of heyu, let me know 
an I will post it, but it's still pretty preliminary (needs a little more 
work) and a lot of documentation.

Thanks everyone,

H. Gunner




In a message dated 11/26/00 7:39:23 PM Eastern Standard Time, jh...@fa... 
writes:

> At 04:37 PM 11/26/00 -0500, you wrote:
>  >Quoting Neil Cherry <nc...@ho...>:
>  >
>  > >
>  > > This was taken from Jay Hogg's recommendation, I hate it because
>  > > it's
>  > > hard to remember (and !12000200 is?) but it is simple and I
>  > > think it
>  > > covers all types of commands that can be sent. Maybe instead of
>  > > value
>  > > we can change that to num= , str=, hex=, oct=, etc?
>  > >
>  > > Hey this is becoming more object oriented!
>  > >
>  >
>  >TO save bandwidth, but make it somewhat readable for debugging, perhaps
>  >you should use single or double char commands.
>  >
>  >Stuff like N=, etc.  But that kinda limits you.  But keeping things 3
>  >chars or less would do fine.
>  
>  Hey Neil, If you don't like it I'm game for changes...
>  
>  What I've got implemented as far as commands are:
>  USER <user id>
>  PASS <password>
>  QUIT
>  HELP  (displays allowed commands)
>  LANG  (tells language variants - AGENT-1.0 MCUSTOM)
>  SET <>
>  GET <>
>  NOTIFY <>  (Sets notification events to be received)
>  Mxxx <>    (Module specific for "playing", dlding code/IR on ocelot
>  
>  General format of addresses is:
>  [device name:]device.domain.point
>  [device name:]device.domain.group.point
>  
>  Where:
>  [device name:] is used from the server side to identify an agent
>  device is the particular address within an agent
>      Ocelots: 0=Ocelot, 1..N=Adicon Bus
>      ADICON:  0..N=Bus
>      RCS Themostats 0..N = Controller # (rs485) or 0 for Serial
>      Napco P9600 0=Main Unit (no others)
>  domain is the area within the device:
>      Ocelot & ADICON:
>        0=X10, 1=IR, 2=Inputs, 3=Outputs, 100=Parms, 101=Timers, 102=Vars
>      RCS Themostats
>        Domain = Zone
>      Napco
>        0=Areas, 1=Keypads, 2=Sensors, 3=Relays
>  item is the particular variable within the domain
>  
>  group was in because some devices have more nesting layers and I
>  needed it when I first layed out the RCS Thems but can't remember
>  why at the moment.
>  
>  Regarding the 1/2/3 character variable names - it doesn't make any
>  difference on the packets if it is <42 bytes because it will be
>  padded. I'd rather use descriptive names plus it make the
>  transition to XML and no-brainer because we just change the format
>  and not the content.
>  
>  Jay
>  
>  _______________________________________________
>  http://lists.sourceforge.net/mailman/listinfo/linuxha-misc
>  To unsubscribe, send "unsubscribe Linuxha-misc"
>  in the body of a message to  Lin...@li...
>  
>  
>  ----------------------- Headers --------------------------------
>  Return-Path: <lin...@li...>
>  Received: from  rly-yd05.mx.aol.com (rly-yd05.mail.aol.com [172.18.150.5]) 
> by air-yd05.mail.aol.com (v77.14) with ESMTP; Sun, 26 Nov 2000 19:39:23 
-0500
>  Received: from  lists.sourceforge.net (mail1.sourceforge.net 
[198.186.203.35]
> ) by rly-yd05.mx.aol.com (v76_r1.19) with ESMTP; Sun, 26 Nov 2000 19:39:03 -
> 0500
>  Received: from mail1.sourceforge.net (localhost [127.0.0.1])
>   by lists.sourceforge.net (8.11.1/8.11.1) with ESMTP id eAR0c2u26703;
>   Sun, 26 Nov 2000 16:38:02 -0800
>  Received: from fastlane.net (fastlane.net [209.197.224.10])
>   by lists.sourceforge.net (8.11.1/8.11.1) with ESMTP id eAR0bSu26681
>   for <lin...@li...>; Sun, 26 Nov 2000 16:37:28 -0800
>  Received: from j_hogg1.fastlane.net (jh.fastlane.net [209.197.226.71])
>   (authenticated)
>   by fastlane.net (8.10.2/8.10.2) with ESMTP id eAR0bQ215022
>   for <lin...@li...>; Sun, 26 Nov 2000 18:37:26 -0600 
(
> CST)
>  Message-Id: <4.3...@ma...>
>  X-Sender: jh...@ma...
>  X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
>  Date: Sun, 26 Nov 2000 18:57:12 -0600
>  To: lin...@li...
>  From: Jay Hogg <jh...@fa...>
>  Subject: Re: [LHA-misc] Line parsing routine
>  In-Reply-To: <975...@ww...>
>  References: <3A2...@ho...>
>   <3A1...@ho...>
>   <3A2...@ks...>
>   <3A2...@ho...>
>  Mime-Version: 1.0
>  Content-Type: text/plain; charset="us-ascii"; format=flowed
>  Sender: lin...@li...
>  Errors-To: lin...@li...
>  X-BeenThere: lin...@li...
>  X-Mailman-Version: 2.0beta5
>  Precedence: bulk
>  Reply-To: lin...@li...
>  List-Id: Linux Home Automation - Misc. Discussions <linuxha-misc.lists.
> sourceforge.net>
>  
>