EnOcean Gateway

EnOcean Gateway
Version 1	Version 2

Developer	Matthias F.
Status	Version 0.9 beta
Microcontroller/Board	Cortex M0+ SAMD (Arduino Zero)
KNX connectivity	KNX Transceiver on Board
EnOcean Module	EnOceanPI
Needed libraries	KONNEKTING Lib [1] Wire (part of Standard Arduino)

Description

Hardware

Software

GiitHub Source Code

Software Components

KonnektingEnocean_V1.0.ino: "Operating System", maps together all components, here the set of devices is configured.
kdevice_KNX_EnOcean_Gateway.h: Derived from the Konnekting configuration XML this header-file defines the available-configuration elements
EEPROM.h: Basic input/output, to access the EEPROM storage that stores the configuration.
EnOcean.h / EnOcean.cpp: Core components, that are shared among the device-modules.

EnOceanDevice_EMPTY.h: Empty EnOcean device template, can be used as a source for copying, to create new Device modules for this Gateway. Feel free to join the development!
EnOceanDevice_NodOn_2Ch.h: Device Module to forward the actuators states from EnOcean to KNX. To allow switching of the actuator from KNX it is neccessary to use a sender module.
EnOceanDevice_RPS_sender.h: Device Module that simulates a simple single EnOcean push-button. Can be used to switch EnOcean actuators. This module can be used independently from any actuator, it is working fire and forget.
EnOceanDevice_RPS_simple.h: Device Module that receives commands from EnOcean push-button devices with up to four rockers.

Software structure

Each Device Module defines the Konnekting representation of a specific device-type. E.g. EnOceanDevice_RPS_simple.h is a module that reflects a standard push-button switches such as Eltako FT-55. If you have two switches, so two FT-55, you need two instances of that Device Module loaded in your Sketch.

Within the "operating system" the devices are registered as objects and within the setup-routine configured. The order of appearance within the setup-routine matters.

How to build the software

Use Arduino with the libraries Wire and KonnektingDevice.

Supported EEP Profiles

ETS* = Sonderversion die direkt in der ETS genutzt werden kann

ID	Profil	Konnekting	ETS*	Beschreibung
0	F6-02-01	x	x	Rocker Switch 2
1	F6-02-02	x	x	Rocker Switch 2
2	F6-02-03		x
3	F6-02-04		x
4	F6-03-01		x
5	F6-03-02		x
6	F6-04-01
7	F6-04-02
8	F6-05-01
9	F6-10-00	x	x	Fenstergriff
10	F6-10-01	x	x	Fenstergriff (ERP2)
11	D5-00-01	x	x	Fensterkontakt
12	A5-02-01		x
13	A5-02-02		x
14	A5-02-03		x
15	A5-02-04		x
16	A5-02-05		x
17	A5-02-06		x
18	A5-02-07		x
19	A5-02-08		x
20	A5-02-09		x
21	A5-02-0A		x
22	A5-02-0B		x
23	A5-02-10		x
24	A5-02-11		x
25	A5-02-12		x
26	A5-02-13		x
27	A5-02-14		x
28	A5-02-15		x
29	A5-02-16		x
30	A5-02-17		x
31	A5-02-18		x
32	A5-02-19		x
33	A5-02-1A		x
34	A5-02-1B		x
35	A5-02-20		x
36	A5-02-30		x
37	A5-04-01		x
38	A5-04-02		x
39	A5-04-03		x
40	A5-05-01
41	A5-06-01		x
42	A5-06-02		x
43	A5-06-03		x
44	A5-07-01	x	x	PIR
45	A5-07-02	x	x	PIR
46	A5-07-03	x	x	PIR
47	A5-08-01
48	A5-08-02
49	A5-08-03
50	A5-09-02
51	A5-09-03
52	A5-09-04
53	A5-09-05
54	A5-09-06
55	A5-09-07
56	A5-09-08
57	A5-09-09
58	A5-09-0A
59	A5-09-0B
60	A5-10-01
61	A5-10-02
62	A5-10-03
63	A5-10-04
64	A5-10-05
65	A5-10-06
66	A5-10-07
67	A5-10-08
68	A5-10-09
69	A5-10-0A
70	A5-10-0B
71	A5-10-0C
72	A5-10-0D
73	A5-10-10
74	A5-10-11
75	A5-10-12
76	A5-10-13
77	A5-10-14
78	A5-10-15
79	A5-10-16
80	A5-10-17
81	A5-10-18
82	A5-10-19
83	A5-10-1A
84	A5-10-1B
85	A5-10-1C
86	A5-10-1D
87	A5-10-1E
88	A5-10-1F
89	A5-10-20
90	A5-10-21
91	A5-11-01
92	A5-11-02
93	A5-11-03
94	A5-11-04
95	A5-12-00
96	A5-12-01
97	A5-12-02
98	A5-12-03
99	A5-12-04
100	A5-12-05
101	A5-12-10
102	A5-13-01
103	A5-13-02
104	A5-13-03
105	A5-13-04
106	A5-13-05
107	A5-13-06
108	A5-13-10
109	A5-14-01
110	A5-14-02
111	A5-14-03
112	A5-14-04
113	A5-14-05
114	A5-14-06
115	A5-20-01
116	A5-20-02
117	A5-20-03
118	A5-20-04
119	A5-20-10
120	A5-20-11
121	A5-20-12
122	A5-30-01
123	A5-30-02
124	A5-30-03
125	A5-30-04
126	A5-30-05
127	A5-37-01
128	A5-38-08
129	A5-38-09
130	A5-3F-00
131	A5-3F-7F
132	D2-00-01
133	D2-01-00
134	D2-01-01
135	D2-01-02
136	D2-01-03
137	D2-01-04
138	D2-01-05
139	D2-01-06
140	D2-01-07
141	D2-01-08
142	D2-01-09
143	D2-01-0A
144	D2-01-0B
145	D2-01-0C
146	D2-01-0D
147	D2-01-0E
148	D2-01-0F
149	D2-01-10
150	D2-01-11
151	D2-01-12	x	x	NodOn 2CH Aktor
152	D2-01-13
153	D2-01-14
154	D2-02-00
155	D2-02-01
156	D2-02-02
157	D2-03-00
158	D2-03-01
159	D2-03-02
160	D2-04-00	x	x	CO2, Hum, Temp
161	D2-04-01		x
162	D2-04-02		x
163	D2-04-03		x
164	D2-04-04		x
165	D2-04-05		x
166	D2-04-06		x
167	D2-04-07		x
168	D2-04-08		x
169	D2-04-09		x
170	D2-04-10		x
171	D2-04-1A		x
172	D2-04-1B		x
173	D2-04-1C		x
174	D2-04-1D		x
175	D2-04-1E		x
176	D2-05-00
177	D2-05-01
178	D2-05-02
179	D2-06-01
180	D2-10-00
181	D2-10-01
182	D2-10-02
183	D2-11-01
184	D2-11-02
185	D2-11-03
186	D2-11-04
187	D2-11-05
188	D2-11-06
189	D2-11-07
190	D2-11-08
191	D2-20-00
192	D2-20-01
193	D2-20-02
194	D2-30-00
195	D2-30-01
196	D2-30-02
197	D2-30-03
198	D2-30-04
199	D2-30-05
200	D2-30-06
201	D2-31-00
202	D2-31-01
203	D2-32-00
204	D2-32-01
205	D2-32-02
206	D2-33-00
207	D2-34-00
208	D2-34-01
209	D2-34-02
210	D2-40-00
211	D2-40-01
212	D2-50-00
213	D2-50-01
214	D2-50-10
215	D2-50-11
216	D2-A0-01
217	D2-B0-51

User Documentation

Get the sketch from the GitHub Source. It comes with an example setup, that allows you to
- Receive telegrams from up to 10 EnOcean button-units ( EnOceanDevice_RPS_simple.h)
- Send telegrams as up to 10 Buttons would do, so you can teach your KNX group address (type DPT 1) to any EnOcean Device ( EnOceanDevice_RPS_sender.h)
- Update the Status of up to 10 2Ch Nodon Actuators ( EnOceanDevice_NodOn_2Ch.h)
If needed change the device-configuration, e.g. if you need more or different Device Modules.
- Build the XML File with an XML-Editor of your choice
  - Add the Device Module XML snippets of your choice
  - Take good care of the order of the Device Modules within your XML-File
- Use the KONNEKTING-CodeCreator to create your h-File, matching the XML-File
- Alter the KonnektingEnocean_V1.0.ino file to match the XML-File.
Upload the code to your Hardware. Refer HowToUploadArduinoCode if you are struggling with Uploading. Here the device only needs to be connected to your PC via USB, no KNX connection is needed.
- You need the Wire lib and this one: KONNEKTING Lib
Configure the Gateway, using the Konnekting Suite and the XML-File, refer each Device Modules documentation on how to set the configuration. Some EnOcean device-ids might be needed here, so hold them ready.
Upload the configuration to the device using the Suite. Now no USB connection is needed but your Hardware needs to be connected KNX instead.
Now you don't need your PC anymore. Teach in all relevant EnOcean devices. Follow the instructions on each Device Modules page to understand the way each device-type is configured.

Developer Documentation

Refer this on how to build your own EnOcean Device Module

Build It

Links

KNX User Forum Thread

EnOcean Equipment Profiles