| ... | ... | @@ -16,39 +16,28 @@ If a device has a entry in the Address Management the Service mapps the data to |
|
|
|
* EnosarDevice: is the type of the device and is a consant from org.enosar.core.types
|
|
|
|
* EnosarID: is the ID of the device as it is in the Address Management
|
|
|
|
|
|
|
|
The Message is a `List<EnosarType>` that is mapped to a JSON String.
|
|
|
|
|
|
|
|
For more information see [Device and Address Management](#device).
|
|
|
|
Not all devices send data. Some are only receiving commands for details of the devices see [Implemented Devices/Packets](#implDev).
|
|
|
|
|
|
|
|
|
|
|
|
### Outgoing EnOcean Messages (from a EnOcean device) and commands for the service
|
|
|
|
To send commands to EnOcean devices the Service receives EventDTO's from Applications over the CommunicationService.
|
|
|
|
The technology for the CommunicationService is `org.enosar.service.io.enocean`.
|
|
|
|
Because of the AddressDTO from the message the Client maps the ID to the device. There are 2 types of incoming messages:
|
|
|
|
|
|
|
|
* if the EventDTO data is not empty the device handles the DTO's, generates and sends the EnOceanMessages to the EnOcean device. Actual implemented commands:
|
|
|
|
|
|
|
|
* for D2 01 08 Devices:
|
|
|
|
* SwitchDTO: Turns on or off
|
|
|
|
* PowerDTO: Returns the actual measured power value
|
|
|
|
* EnergyDTO: Returns the actual measured energy value
|
|
|
|
|
|
|
|
*for RCM250 Devices:
|
|
|
|
* SwitchDTO: Turns on or off
|
|
|
|
|
|
|
|
### Outgoing EnOcean Messages (to a EnOcean device)
|
|
|
|
The EnOcean Service can send messages/controls to EnOcean devices (only if the device supports). The device must be registered in the Address Management (see [Device and Address Management](#device)). The Service gets controls via the [CommunicatioService](https://ressel.fh-salzburg.ac.at/ENOSAR/Framework/wikis/tutorial-core-service-communication) with the PID **org.enosar.service.io.enocean**. If the device supports getting commands the EnOcean Service will send the command to the device (see [Implemented Devices/Packets](#implDev) for supported devices).
|
|
|
|
The EnOcean service can receive `List<EnosarType>` or `EnosarType` to control devices. If a list of EnosarType is sent the Service will send the commands in the order they are in the list.
|
|
|
|
|
|
|
|
<a name="device"></a>
|
|
|
|
## Device and Address Management
|
|
|
|
Every device must have an entry in the Address Management of ENOSAR. For this it is necessary to add every device in the Address Management in ENOSAR.
|
|
|
|
You can find this on `http://[IP ENOSAR]:8080` under Address Management.
|
|
|
|
Every EnOcean device has to have an entry in the Address Management of ENOSAR. Access the Address Management via the Web App of ENOSAR.
|
|
|
|
|
|
|
|
There every Entry must contain:
|
|
|
|
A entry for a device has:
|
|
|
|
* Identifier: An unique ID in ENOSAR to identify the device (ENOSAR ID)(e.g.: switch1, socket1)
|
|
|
|
* Technology: For the EnOcean service `org.enosar.service.io.enocean`
|
|
|
|
* Technology: For the EnOcean Service `org.enosar.service.io.enocean`
|
|
|
|
* Receiver Information: Consists out of 2 information's. The EnOcean device ID and the packet description. The syntax is `0x[EnOcean ID in hex].[EEP]`:
|
|
|
|
* EnOcean ID: Is the unique ID of the EnOcean device. The EnOcean ID is displayed in the terminal when the device sends a message and is not in the Address Management.
|
|
|
|
* EEP: Describes the data packet that is sent of the device. This information can be found in the manual of the device (EnOcean Equipment Profile (EEP)). All implemented data packets are listed in [Implemented Devices/Packets](#implDev)
|
|
|
|
|
|
|
|
* EnOcean ID: Is the unique ID of the device. The ID is displayed in the terminal when the device sends a message and is not in the Address Management
|
|
|
|
* EEP: Describes the data sent of the device and can be found in the manual of the device (EnOcean Equipment Profile (EEP)).
|
|
|
|
If the device has a teach in function this entry is not necessary. The teach in entries then the Packed description automatically when a teach in is done.
|
|
|
|
If the device has a teach in function the EEP entry is not necessary. The teach in adds the Packed description automatically when a teach in is done.
|
|
|
|
|
|
|
|
<a name="implDev"></a>
|
|
|
|
## Implemented Devices/Packets
|
| ... | ... | @@ -94,6 +83,11 @@ Here is a List of implemented EEP packets and devices |
|
|
|
Implementation of EnOcean D2 01 08 Radio EEP telegram (See EnOcean_Equipment_Profiles_EEP_V2.63_public.pdf page 115 ff).
|
|
|
|
It is used for Electronic Switches and Dimmers with Energy Measurement and Local control (e.g.: Telefunken Funktionssteckdose FS2)
|
|
|
|
|
|
|
|
* for D2 01 08 Devices:
|
|
|
|
* SwitchDTO: Turns on or off
|
|
|
|
* PowerDTO: Returns the actual measured power value
|
|
|
|
* EnergyDTO: Returns the actual measured energy value
|
|
|
|
|
|
|
|
* <a name="d50001"></a>D5 00 01
|
|
|
|
|
|
|
|
Implementation of EnOcean D5 00 01 Radio EEP telegram (See EnOcean_Equipment_Profiles_EEP_V2.63_public.pdf page 25).
|
| ... | ... | |
