EnOcean Gateway
| EnOcean Gateway | |
|---|---|
| Developer | Matthias F. |
| Status | Version 0.9 beta |
| Microcontroller/Board | Cortex M0+ SAMD (Arduino Zero) |
| KNX connectivity | KNX Transceiver on Board |
| EnOcean Module | EnOceanPI |
Description
Hardware
Software
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.