doc_tap_Knx_Gatew;

Label in BAOS	Data point type	Used by TapHome virtual devices	Used by TapHome virtual variable	Comment
doc_tap_Lab_baos;	doc_tap_data_point;	doc_tap_virt_dev;	doc_tap_virt_var;	doc_tap_Cmt;
DPT 1	1 Bit, Boolean
	doc_tap_1bb;
DPT 2	2 Bit, Control
	doc_tap_2bc;
DPT 3	4 Bit, Dimming, Blinds
	doc_tap_4bdb;
DPT 4	8 Bit, Character Set
	doc_tap_8bchs;
DPT 5	8 Bit, Unsigned Value
	doc_tap_8buv;
DPT 6	8 Bit, Signed Value
	doc_tap_8bsignedv;
DPT 7	2 Byte, Unsigned Value
	doc_tap_2bunsigv;
DPT 8	2 Byte, Signed Value
	doc_tap_2bsignedv;
DPT 9	2 Byte, Float Value
	doc_tap_2floatv;
DPT 10	3 Byte, Time			Implementing date and time from KNX into TapHome does not make sense. TapHome has its own internal date and time engine. doc_tap_fromKNX_toTH;
	doc_tap_3bt;
DPT 11	3 Byte, Date
	doc_tap_3bd;
DPT 12	4 Byte, Unsigned Value
	doc_tap_4bunsigv;
DPT 13	4 Byte, Signed Value
	doc_tap_4bsignedv;
DPT 14	4 Byte, Float Value
	doc_tap_4floatv;
DPT 15	4 Byte, Access
	doc_tap_4baxx;
DPT 16	14 Byte, String			Planned feature, coming soon
	doc_tap_14bstr;			doc_tap_plan_coming;
DPT 17	1 Byte, Scene Number
	doc_tap_1bsNo;
DPT 18	1 Byte, Scene Control
	doc_tap_1bSxCo;