| ... | ... | @@ -15,7 +15,7 @@ So this Service is fowarding incoming EnOcean messages to the MessagingService i |
|
|
|
### Incoming EnOcean Messages (from a EnOcean device)
|
|
|
|
The EnOcean Service receives messages from EnOcean devices. It accepts only devices that are registered in the Address Management (see [Device and Address Management](#device)). The Service also handles also Teach-In and Teach-Out messages.
|
|
|
|
If a device has a entry in the Address Management the Service mapps the data to Enosar DTO's(Data Transfer Objects) and publishes the messages to the [MessagingService](https://ressel.fh-salzburg.ac.at/ENOSAR/Framework/wikis/tutorial-core-service-messaging). The topic of the messages are:`in.homeatomation.enocean.[EnosarDevice].[EnosarID]`
|
|
|
|
* EnosarDevice: is the type of the device and is a consant from org.enosar.core.types
|
|
|
|
* EnosarDevice: is the type of the device and is a constant 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.
|
| ... | ... | |
