... | ... | @@ -26,7 +26,10 @@ Not all devices send data. Some are only receiving commands for details of the d |
|
|
|
|
|
|
|
|
### 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 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)). There are 2 possible ways to send controls to a device via the EnOcean Service:
|
|
|
* [CommunicationService](https://ressel.fh-salzburg.ac.at/ENOSAR/Framework/wikis/tutorial-core-service-communication) with the PID **org.enosar.service.io.enocean**.
|
|
|
* [MessagingService](https://ressel.fh-salzburg.ac.at/ENOSAR/Framework/wikis/tutorial-core-service-messaging) with the topic **out.homeautomation.enocean**
|
|
|
If the device supports receiving 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>
|
... | ... | |