|
|
# Tutorials
|
|
# Tutorial: Getting started with EnOcean
|
|
|
|
|
|
|
|
[Getting started with EnOcean](tutorials/getting-started-with-enocean) |
|
In this tutorial we will setup an FREDOSAR Pi and configure it to retrieve EnOcean Messages sent from a button.
|
|
\ No newline at end of file |
|
|
|
|
|
# Content
|
|
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
## Prerequisits
|
|
|
|
- Java Knowledge
|
|
|
|
- OSGi Knowledge
|
|
|
|
- Maven Knowledge
|
|
|
|
- Git Knowledge
|
|
|
|
|
|
|
|
## Components
|
|
|
|
|
|
|
|
You need:
|
|
|
|
- Raspberry PI 2 or 3 with sd card and powersupply
|
|
|
|
- EnOcean Pi with TCM310
|
|
|
|
- Peha Swtich wall transmitter
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Preparation
|
|
|
|
First mount the EnOcean Pi on the raspberry in the first pin
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Next download the [FREDOSAR PI image from here](http://repo.fredosar.org/fredosarpi-images/fredosarpi-v0.1.2-beta.1.img.gz) and write it to the sd card with you favourite tool, e.g. Win32 Disk Image
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Insert the sd card an boot your pi.
|
|
|
|
|
|
|
|
### Connect to the FREDOSAR Pi
|
|
|
|
|
|
|
|
Fire up a shell an login to your FREDOSARPI with ssh (Username: pi, password: raspberry). The FREDOSARPI is configured for DHCP, in this turtorial it got the IP 192.168.1.12.
|
|
|
|
|
|
|
|
FREDOSAR uses OSGi an therefore you find the Apache Felix Framework on the pi. Already preinstalled.
|
|
|
|
|
|
|
|
Let us explore what is in the image. Change directory into the FREDOSAR dir `/home/pi/FREDOSAR/felix-framework-5.4.0` . Here you find the following structure
|
|
|
|
```sh
|
|
|
|
pi@fredosarpi:~/FREDOSAR/felix-framework-5.4.0 $ ls -la
|
|
|
|
total 68
|
|
|
|
drwxr-xr-x 10 pi pi 4096 Jan 17 09:29 .
|
|
|
|
drwxr-xr-x 4 pi pi 4096 Sep 13 14:20 ..
|
|
|
|
drwxr-xr-x 3 pi pi 4096 Sep 13 14:20 bin
|
|
|
|
drwxr-xr-x 2 pi pi 4096 Jan 17 09:47 bundle
|
|
|
|
drwxr-xr-x 2 pi pi 4096 Sep 13 14:20 conf
|
|
|
|
-rw-r--r-- 1 pi pi 987 Sep 13 14:20 DEPENDENCIES
|
|
|
|
drwxr-xr-x 7 pi pi 4096 Sep 13 14:20 doc
|
|
|
|
drwxr-xr-x 2 pi pi 4096 Sep 13 14:20 enocean_config
|
|
|
|
drwxr-xr-x 37 pi pi 4096 Feb 28 09:37 felix-cache
|
|
|
|
-rw-r--r-- 1 pi pi 11358 Sep 13 14:20 LICENSE
|
|
|
|
-rw-r--r-- 1 pi pi 1095 Sep 13 14:20 LICENSE.kxml2
|
|
|
|
drwxr-xr-x 2 pi pi 4096 Feb 28 09:37 load
|
|
|
|
-rw-r--r-- 1 pi pi 550 Sep 13 14:20 NOTICE
|
|
|
|
-rw-r--r-- 1 pi pi 1322 Feb 28 09:14 permissions.txt
|
|
|
|
drwxr-xr-x 2 pi pi 4096 Feb 28 09:38 store
|
|
|
|
```
|
|
|
|
In this tutorial, we will focos on the `load/` directorys. The load directory contains all our bundles. Later we will upload our application bundle to this file. Every bundle in this folder is autloaded by the framework.
|
|
|
|
|
|
|
|
Let us now start the framework. The output should look like this:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
pi@fredosarpi:~/FREDOSAR/felix-framework-5.4.0 $ java -jar bin/felix.jar
|
|
|
|
____________________________
|
|
|
|
Welcome to Apache Felix Gogo
|
|
|
|
|
|
|
|
g! 2017-02-28 11:43:00.351:INFO::FelixStartLevel: Logging initialized @5208ms
|
|
|
|
2017-02-28 11:43:00.635:INFO:oejs.Server:FelixStartLevel: jetty-9.2.14.v20151106
|
|
|
|
2017-02-28 11:43:00.991:INFO:oejsh.ContextHandler:FelixStartLevel: Started o.e.j.s.ServletContextHandler@32e158{/,null,AVAILABLE}
|
|
|
|
2017-02-28 11:43:00.993:INFO:oejs.Server:FelixStartLevel: Started @5851ms
|
|
|
|
2017-02-28 11:43:01.151:INFO:oejs.ServerConnector:FelixStartLevel: Started ServerConnector@150155c{HTTP/1.1}{0.0.0.0:8080}
|
|
|
|
[INFO] Started Jetty 9.2.14.v20151106 at port(s) HTTP:8080 on context path / [minThreads=8,maxThreads=200,acceptors=1,selectors=2]
|
|
|
|
2017-02-28T11:43:01.683 [INFO--org.fredosar.service.io.enocean.basedriver.impl.EnOceanBaseDriverFREDOSAR] initial host path : /dev/ttyAMA0
|
|
|
|
2017-02-28T11:43:02.574 [ERROR-org.fredosar.service.io.enocean.impl.DeviceHandler] Error AddressService is null
|
|
|
|
DEBUG:org.fredosar.core.communication 30> new addresserviceaware object
|
|
|
|
INFO:org.fredosar.core.auth 23> granting communication access for bundle org.fredosar.mgmt.modules to service org.fredosar.service.io.http
|
|
|
|
INFO:org.fredosar.core.messaging 29> adding subscriber - now containing 6
|
|
|
|
INFO:org.fredosar.core.webserver 34> HTTPServiceTracker started
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via /fredosar/user Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via /fredosar/permission Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via /fredosar/update Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register static resource /fredosar/ui - bundle20 Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via /fredosar/access Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via /fredosar/module Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via /fredosar/config Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via /fredosar/address Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via /fredosar/message Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 34> register servlet via / Auth: false
|
|
|
|
INFO:org.fredosar.service.datastore.jsonfile 22> mapping service injected
|
|
|
|
DEBUG:org.fredosar.core.datastore 26> injecting org.fredosar.service.datastore.jsonfile with type persistent
|
|
|
|
INFO:org.fredosar.core.communication 30> injected DSS JSONFileDataStoreServiceImpl
|
|
|
|
INFO:org.fredosar.service.io.rabbitmq 27> trying to (re)connect to RabbitMQ server...
|
|
|
|
INFO:org.fredosar.service.io.rabbitmq 27> ... RabbitMQ connected
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
The next step is to find out the EnOcean ID of our PEHA switch. Press it and have a look at the console ouput. The EnOcean Bundel writes every unknown device to stdou, like here:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
2017-02-28T12:26:12.072 [INFO--org.fredosar.service.io.enocean.basedriver.impl.EnOceanBaseDriverFREDOSAR] Device 0x01846b3d not found.
|
|
|
|
```
|
|
|
|
|
|
|
|
Remember the EnOcean ID *01846b3d*, we will now configure the device through the webinterface. Fire up a browser an goto: http://192.168.1.12:8080. Login with user: admin and password admin. You should now see the webinterface of the FREDOSAR Dashboard.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Goto Address Management and enter `pehaswitch` the name into the `Add new address object`
|
|
|
|
|
|
|
|
|
|
|
|
Press add.
|
|
|
|
|
|
|
|
Technology is `org.fredosar.service.io.enocean` and receiver data must be `0x01846b3d.F60201.button`
|
|
|
|
|
|
|
|
|
|
|
|
Receiver data contains the ID of our EnOcean Device followed by a dot and the the RORG function code followed by the fredosardevice button.
|
|
|
|
|
|
|
|
Press update and now our FREDOSAR PI knows ho to handle the telegrams comming from our PEHA switch device.
|
|
|
|
|
|
|
|
### Code a EnOcean listener
|
|
|
|
|
|
|
|
We provide the template project, which will helps you to speedup your project setup. Goto https://ressel.fh-salzburg.ac.at/Applications/templates . download the code and follow the steps from the readme:
|
|
|
|
- Rename the directory to your new package name (e.g. org.fredosar.application.tutorialenoceanswitch)
|
|
|
|
- Import the project into eclipse (Import -> Existing Projects...)
|
|
|
|
- Rename the project
|
|
|
|
- Rename the java package name to your new package name. Also rename the package name in the Activator.java
|
|
|
|
- Rename the module settings in the pom.xml (artifactId, groupId, Activator qualified name and private packages).
|
|
|
|
Our project now looks like this
|
|
|
|
|
|
|
|
|
|
|
|
- Build the project with mvn clean install. Right click on pom.xml -> Run as -> Maven build ... Add goals `clean install` and then run it.
|
|
|
|
|
|
|
|
|
|
|
|
If successfully build you should get the output *BUILD SUCCESS*
|
|
|
|
|
|
|
|
|
|
|
|
To get rid of the wrong eclipse warning, press F5 and also ALT + F5 to update project deps in eclipse. Your setup should now look like this:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#### Add the listener code
|
|
|
|
|
|
|
|
Add a new Java File: `EnoceanRequestHandler.java` with the content
|
|
|
|
|
|
|
|
```java
|
|
|
|
package org.fredosar.application.tutorialenoceanswitch;
|
|
|
|
|
|
|
|
import java.util.Map;
|
|
|
|
|
|
|
|
import org.fredosar.core.communication.api.CommunicationService;
|
|
|
|
import org.fredosar.core.messaging.api.MessageConsumer;
|
|
|
|
import org.fredosar.core.messaging.dto.EventDTO;
|
|
|
|
import org.osgi.service.log.LogService;
|
|
|
|
|
|
|
|
public class EnoceanRequestHandler
|
|
|
|
implements MessageConsumer{
|
|
|
|
|
|
|
|
private static final String STORE_PREFIX = "org.fredosar.application.smartthings";
|
|
|
|
private Map<String, CommunicationService> serviceArray;
|
|
|
|
|
|
|
|
@Override
|
|
|
|
public synchronized void push(EventDTO event, String topic) {
|
|
|
|
Activator.getLog().log(LogService.LOG_INFO, "pushed topic: `" + topic + "` EventDTO: from:`"
|
|
|
|
+ event.getFrom() + "`,to:`" + event.getTo() + "`,body:`" + event.getBody() + "`");
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
The EnoceanRequestHandler implements the MessageConsumer interface. It implements the push method, which is called by the FREDOSAR Messaging framework when an EnOcean message comes in. Within the push we log what happend.
|
|
|
|
|
|
|
|
Now wire everything together in your `Activator.java`. Edit the start method:
|
|
|
|
|
|
|
|
```java
|
|
|
|
public void start(BundleContext bundleContext) throws Exception {
|
|
|
|
context = bundleContext;
|
|
|
|
logServiceTracker = new LogServiceTracker(context);
|
|
|
|
logServiceTracker.open();
|
|
|
|
|
|
|
|
// register request handler to listen to communication services for EnOcean
|
|
|
|
Dictionary<String, Object> propertiesEnOcean = new Hashtable<>();
|
|
|
|
//listen to all in.homeautomation.enocean.* topics
|
|
|
|
propertiesEnOcean.put(Constants.MSG_TOPIC, new String[] {"in.homeautomation.enocean.*"});
|
|
|
|
//register the new service
|
|
|
|
context.registerService(
|
|
|
|
new String[] {MessageConsumer.class.getName()},
|
|
|
|
new EnoceanRequestHandler(), propertiesEnOcean);
|
|
|
|
|
|
|
|
Activator.getLog().log(LogService.LOG_INFO, "org.fredosar.application.tutorialenoceanswitch started.");
|
|
|
|
}
|
|
|
|
```
|
|
|
|
It defineds, that our EnoceanRequestHandler listens to all in.homeautomation.enocean. topics and registers that service.
|
|
|
|
|
|
|
|
|
|
|
|
The full tutorial code can be found here: https://ressel.fh-salzburg.ac.at/Applications/tutorialenoceanswitch
|
|
|
|
|
|
|
|
Next step ist to build our bundle and upload it to our FREDOSARPI. Richt click the pom.xml Run as -> Maven build. If everything works you should see
|
|
|
|
|
|
|
|
|
|
|
|
Go into the `target/` directory where you find your new bundle
|
|
|
|
|
|
|
|
|
|
|
|
Upload this bundle to the Pi `~/FREDOSAR/felix-framework-5.4.0/load/` folder. For ssh Filetransfer i use FileZille
|
|
|
|
|
|
|
|
|
|
|
|
Login to the pi and start FREDOSAR
|
|
|
|
```shell
|
|
|
|
pi@fredosarpi:~/FREDOSAR/felix-framework-5.4.0 $ java -jar bin/felix.jar
|
|
|
|
____________________________
|
|
|
|
Welcome to Apache Felix Gogo
|
|
|
|
|
|
|
|
g! 2017-02-28 13:17:31.066:INFO::FelixStartLevel: Logging initialized @3899ms
|
|
|
|
2017-02-28 13:17:31.316:INFO:oejs.Server:FelixStartLevel: jetty-9.2.14.v20151106
|
|
|
|
2017-02-28 13:17:31.665:INFO:oejsh.ContextHandler:FelixStartLevel: Started o.e.j.s.ServletContextHandler@1068806{/,null,AVAILABLE}
|
|
|
|
2017-02-28 13:17:31.668:INFO:oejs.Server:FelixStartLevel: Started @4502ms
|
|
|
|
2017-02-28 13:17:31.793:INFO:oejs.ServerConnector:FelixStartLevel: Started ServerConnector@1353e01{HTTP/1.1}{0.0.0.0:8080}
|
|
|
|
[INFO] Started Jetty 9.2.14.v20151106 at port(s) HTTP:8080 on context path / [minThreads=8,maxThreads=200,acceptors=1,selectors=2]
|
|
|
|
DEBUG:org.fredosar.core.communication 29> new addresserviceaware object
|
|
|
|
INFO:org.fredosar.core.auth 21> granting communication access for bundle org.fredosar.application.smartthings to service org.fredosar.service.io.rabbitmq
|
|
|
|
INFO:org.fredosar.core.auth 21> granting communication access for bundle org.fredosar.application.smartthings to service org.fredosar.service.io.rabbitmq
|
|
|
|
INFO:org.fredosar.application.smartthings 22> serviceArray registered
|
|
|
|
INFO:org.fredosar.core.auth 21> granting communication access for bundle org.fredosar.mgmt.modules to service org.fredosar.service.io.http
|
|
|
|
INFO:org.fredosar.core.messaging 28> adding subscriber - now containing 7
|
|
|
|
INFO:org.fredosar.core.webserver 33> HTTPServiceTracker started
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/message Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/module Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/update Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register static resource /fredosar/ui - bundle18 Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/access Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/config Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/user Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/permission Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/address Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via / Auth: false
|
|
|
|
2017-02-28T13:17:33.361 [INFO--org.fredosar.service.io.enocean.basedriver.impl.EnOceanBaseDriverFREDOSAR] initial host path : /dev/ttyAMA0
|
|
|
|
DEBUG:org.fredosar.core.communication 29> new addresserviceaware object
|
|
|
|
2017-02-28T13:17:33.507 [ERROR-org.fredosar.service.io.enocean.impl.DeviceHandler] Error AddressService is null
|
|
|
|
INFO:org.fredosar.core.auth 21> granting communication access for bundle org.fredosar.application.smartthings to service org.fredosar.service.io.rabbitmq
|
|
|
|
INFO:org.fredosar.core.auth 21> granting communication access for bundle org.fredosar.application.smartthings to service org.fredosar.service.io.rabbitmq
|
|
|
|
INFO:org.fredosar.application.smartthings 22> serviceArray registered
|
|
|
|
INFO:org.fredosar.core.auth 21> granting communication access for bundle org.fredosar.mgmt.modules to service org.fredosar.service.io.http
|
|
|
|
INFO:org.fredosar.core.messaging 28> adding subscriber - now containing 8
|
|
|
|
INFO:org.fredosar.service.datastore.jsonfile 20> mapping service injected
|
|
|
|
INFO:org.fredosar.application.smartthings 22> DataStoreService injected
|
|
|
|
DEBUG:org.fredosar.core.datastore 24> injecting org.fredosar.service.datastore.jsonfile with type persistent
|
|
|
|
INFO:org.fredosar.core.communication 29> injected DSS JSONFileDataStoreServiceImpl
|
|
|
|
INFO:org.fredosar.service.io.rabbitmq 25> trying to (re)connect to RabbitMQ server...
|
|
|
|
INFO:org.fredosar.application.smartthings 22> MappingService injected
|
|
|
|
INFO:org.fredosar.core.auth 21> could not grant messaging access for bundle org.fredosar.application.tutorialenoceanswitch to topic in.homeautomation.enocean.*, bundle undefined
|
|
|
|
INFO:org.fredosar.core.messaging 28> adding subscriber - now containing 8
|
|
|
|
INFO:org.fredosar.application.tutorialenoceanswitch 36> org.fredosar.application.tutorialenoceanswitch started.
|
|
|
|
INFO:org.fredosar.service.io.rabbitmq 25> ... RabbitMQ connected
|
|
|
|
```
|
|
|
|
|
|
|
|
Currently our tutorialenoceanswith is not allowed to access the messaging framework `INFO:org.fredosar.core.auth 21> could not grant messaging access for bundle org.fredosar.application.tutorialenoceanswitch to topic in.homeautomation.enocean.*, bundle undefined` so we have to grant the access to it. In the Webinterface goto Access Violations review the violation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Permissions are managed within the permissions.txt file under FREDOSAR/felix-framework-5.4.0/
|
|
|
|
|
|
|
|
Add the line to permissions.txt
|
|
|
|
```
|
|
|
|
M|org.fredosar.application.tutorialenoceanswitch|in.homeautomation.enocean.*|1
|
|
|
|
```
|
|
|
|
so that the full file looks like this:
|
|
|
|
```
|
|
|
|
U|admin|admin
|
|
|
|
M|org.fredosar.service.io.rabbitmq|in.rabbitmq.*|3
|
|
|
|
M|org.fredosar.service.io.rabbitmq|out.rabbitmq.*|3
|
|
|
|
M|org.fredosar.application.tools.mytest|io.*|1
|
|
|
|
M|org.fredosar.service.io.enocean|in.*.out.homeautomation.enocean|3
|
|
|
|
M|org.fredosar.service.io.enocean|in.homeautomation.enocean.*|3
|
|
|
|
M|org.fredosar.mgmt.modules|custom.repository.*|3
|
|
|
|
M|org.fredosar.mgmt.modules|in.http.*|1
|
|
|
|
M|org.fredosar.mgmt.modules|timer.*|1
|
|
|
|
M|org.fredosar.mgmt.timer|timer.*|2
|
|
|
|
M|org.fredosar.application.smartthings|in.rabbitmq.out.org.fredosar.application.smartthings.*|1
|
|
|
|
M|org.fredosar.application.smartthings|in.homeautomation.enocean.*|1
|
|
|
|
M|org.fredosar.application.tools.enocean.tester|io.enocean.*|1
|
|
|
|
M|org.fredosar.application.tools.timer|timer.*|2
|
|
|
|
M|org.fredosar.service.io.http|in.http.*|2
|
|
|
|
M|org.fredosar.service.io.http|out.http|3
|
|
|
|
M|org.fredosar.application.tutorialenoceanswitch|in.homeautomation.enocean.*|1
|
|
|
|
C|org.fredosar.application.rassa.enocean|org.fredosar.service.io.enocean.client
|
|
|
|
C|org.fredosar.service.io.enocean|org.fredosar.service.io.enocean
|
|
|
|
C|org.fredosar.mgmt.modules|org.fredosar.service.io.http
|
|
|
|
C|org.fredosar.application.smartthings|org.fredosar.service.io.http
|
|
|
|
C|org.fredosar.application.smartthings|org.fredosar.service.io.rabbitmq
|
|
|
|
C|org.fredosar.application.smartthings|org.fredosar.service.io.enocean
|
|
|
|
C|org.fredosar.service.io.rabbitmq|org.fredosar.service.rabbitmq
|
|
|
|
C|org.fredosar.application.tools.enocean.test|org.fredosar.service.io.enocean.client
|
|
|
|
```
|
|
|
|
|
|
|
|
Restart FREDOSAR, press the swith and you should see our log output:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
pi@fredosarpi:~/FREDOSAR/felix-framework-5.4.0 $ java -jar bin/felix.jar
|
|
|
|
____________________________
|
|
|
|
Welcome to Apache Felix Gogo
|
|
|
|
|
|
|
|
g! 2017-02-28 13:25:27.045:INFO::FelixStartLevel: Logging initialized @3933ms
|
|
|
|
2017-02-28 13:25:27.296:INFO:oejs.Server:FelixStartLevel: jetty-9.2.14.v20151106
|
|
|
|
2017-02-28 13:25:27.652:INFO:oejsh.ContextHandler:FelixStartLevel: Started o.e.j.s.ServletContextHandler@1068806{/,null,AVAILABLE}
|
|
|
|
2017-02-28 13:25:27.654:INFO:oejs.Server:FelixStartLevel: Started @4543ms
|
|
|
|
2017-02-28 13:25:27.781:INFO:oejs.ServerConnector:FelixStartLevel: Started ServerConnector@ae7040{HTTP/1.1}{0.0.0.0:8080}
|
|
|
|
[INFO] Started Jetty 9.2.14.v20151106 at port(s) HTTP:8080 on context path / [minThreads=8,maxThreads=200,acceptors=1,selectors=2]
|
|
|
|
DEBUG:org.fredosar.core.communication 29> new addresserviceaware object
|
|
|
|
INFO:org.fredosar.core.auth 21> granting communication access for bundle org.fredosar.mgmt.modules to service org.fredosar.service.io.http
|
|
|
|
INFO:org.fredosar.core.messaging 28> adding subscriber - now containing 6
|
|
|
|
INFO:org.fredosar.core.webserver 33> HTTPServiceTracker started
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/message Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register static resource /fredosar/ui - bundle18 Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/access Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/config Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/user Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/permission Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/module Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/address Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via /fredosar/update Auth: true
|
|
|
|
INFO:org.fredosar.core.webserver 33> register servlet via / Auth: false
|
|
|
|
2017-02-28T13:25:29.312 [INFO--org.fredosar.service.io.enocean.basedriver.impl.EnOceanBaseDriverFREDOSAR] initial host path : /dev/ttyAMA0
|
|
|
|
DEBUG:org.fredosar.core.communication 29> new addresserviceaware object
|
|
|
|
2017-02-28T13:25:29.459 [ERROR-org.fredosar.service.io.enocean.impl.DeviceHandler] Error AddressService is null
|
|
|
|
INFO:org.fredosar.core.auth 21> granting communication access for bundle org.fredosar.mgmt.modules to service org.fredosar.service.io.http
|
|
|
|
INFO:org.fredosar.core.messaging 28> adding subscriber - now containing 7
|
|
|
|
INFO:org.fredosar.service.datastore.jsonfile 20> mapping service injected
|
|
|
|
DEBUG:org.fredosar.core.datastore 24> injecting org.fredosar.service.datastore.jsonfile with type persistent
|
|
|
|
INFO:org.fredosar.core.communication 29> injected DSS JSONFileDataStoreServiceImpl
|
|
|
|
INFO:org.fredosar.service.io.rabbitmq 25> trying to (re)connect to RabbitMQ server...
|
|
|
|
INFO:org.fredosar.service.io.rabbitmq 25> ... RabbitMQ connected
|
|
|
|
INFO:org.fredosar.application.tutorialenoceanswitch 23> pushed topic: `in.homeautomation.enocean.button.assistbutton` EventDTO: from:`in.homeautomation.enocean.button.assistbutton`,to:``,body:`[{"type":"homeautomation.ButtonDTO","fredosarId":"assistbutton","state":"RELEASED"},{"type":"homeautomation.ButtonDTO","fredosarId":"assistbutton","state":"RELEASED"},{"type":"homeautomation.ButtonDTO","fredosarId":"assistbutton","state":"RELEASED"},{"type":"homeautomation.ButtonDTO","fredosarId":"assistbutton","state":"PRESSED"}]`
|
|
|
|
INFO:org.fredosar.application.tutorialenoceanswitch 23> pushed topic: `in.homeautomation.enocean.button.assistbutton` EventDTO: from:`in.homeautomation.enocean.button.assistbutton`,to:``,body:`[{"type":"homeautomation.ButtonDTO","fredosarId":"assistbutton","state":"RELEASED"},{"type":"homeautomation.ButtonDTO","fredosarId":"assistbutton","state":"RELEASED"},{"type":"homeautomation.ButtonDTO","fredosarId":"assistbutton","state":"RELEASED"},{"type":"homeautomation.ButtonDTO","fredosarId":"assistbutton","state":"RELEASED"}]`
|
|
|
|
``` |
|
|
|
\ No newline at end of file |
