Fleshing out more messages

Getting a feel for how the development experience is with this setup. With the previous idea of abstracting the request into a getSystemInfo() function on the Unit itself, the documentation for what to expect from GetSystemInfo either had to live in two places or be presented as a link to the canonical location. Neither felt great, so I think the caller can just call send(GetRequest()) themselves.

Also added the first "set" message which is capable of toggling a body or circuit.
This commit is contained in:
2025-01-03 16:01:58 -06:00
parent ceb9299d03
commit 7daf47ac18
32 changed files with 634 additions and 391 deletions

View File

@ -1,127 +1,3 @@
export class ICResponseParam {
// "": "PROGRESS";
ABSMAX;
ABSMIN;
ACT;
ACT1;
ACT2;
ACT3;
ACT4;
ADDRESS;
ALK;
AVAIL;
BADGE;
BODY;
BOOST;
CALC;
CALIB;
CHILD;
CIRCUIT;
CITY;
CLK24A;
COMUART;
COOL;
COUNT;
COUNTRY;
CYACID;
DAY;
DLSTIM;
DLY;
DNTSTP;
EMAIL;
EMAIL2;
ENABLE;
FEATR;
FILTER;
FREEZE;
GPM;
HEATER;
HEATING;
HITMP;
HNAME;
HTMODE;
HTSRC;
IN;
LIMIT;
LISTORD;
LOCX;
LOCY;
LOTMP;
LSTTMP;
MANHT;
MANOVR;
MANUAL;
MAX;
MAXF;
MIN;
MINF;
MODE;
NAME;
OBJLIST;
OBJNAM;
OBJTYP;
OFFSET;
ORPSET;
ORPTNK;
ORPVAL;
PARENT;
PARTY;
PASSWRD;
PERMIT;
PHONE;
PHONE2;
PHSET;
PHTNK;
PHVAL;
PRIM;
PRIMFLO;
PRIMTIM;
PRIOR;
PROBE;
PROPNAME;
PWR;
QUALTY;
READY;
RLY;
RPM;
SALT;
SEC;
SELECT;
SERVICE;
SETTMP;
SETTMPNC;
SHARE;
SHOMNU;
SINDEX;
SNAME;
SOURCE;
SPEED;
SRIS;
SSET;
START;
STATE;
STATIC;
STATUS;
STOP;
SUBTYP;
SUPER;
SWIM;
SYNC;
SYSTIM;
TEMP;
TIME;
TIMOUT;
TIMZON;
UPDATE;
USAGE;
USE;
VACFLO;
VACTIM;
VALVE;
VER;
VOL;
ZIP;
}
export class ICResponseObj {
objnam = "";
params;