OpenHAB – Working with the GUI

In the previous post [here] , I noted down on building OpenHAB and getting up and running with its distribution.

Here, I will briefly introduce you to the user interface. We will modify the OpenHAB demo setup, we installed earlier, by adding a new device to control. We will be able to toggle this device eventually.

Adding a new device in OpenHAB

This is quite easy. It is just incredible that anyone using OpenHAB doesn’t need to worry too much about it’s user interface. The files of interest here are,

$OPENHAB_HOME/configurations/sitemaps/demo.sitemap

$OPENHAB_HOME/configurations/items/demo.items

Please note that I use OPENHAB_HOME to refer to any location where you would have installed the OpenHAB distributions that we built here.

Sitemaps

If you look at the defOpenHAB-Demo Homeault demo page of OpenHAB, you will find that devices are segregated into groups. The groups here are given user readable names like “First Floor” or “Ground Floor”. This is hierarchical as you would have seen in the earlier post. We will define a new group as “Second Floor” and add a new Light control for its “Corridor”.

Each of the sections in the home page is a frame which provides a clear distinction between various functionality you might want to provide from your home page. You can define a new frame here just for devices that can be monitored (for example: Outside Temperature device here). This is just a high level logical separation that user might want to work with. No rocket science here.

In the file demo.sitemap, you will find the page layout definition. Here look at the first entry under unnamed frame type which includes groups for all the floors. Go ahead and add another entry for our “Second Floor”. It should now look something like this.

sitemap demo label=”Main Menu”
{
Frame {
Group item=gFF label=”First Floor” icon=”firstfloor”
Group item=gGF label=”Ground Floor” icon=”groundfloor”
Group item=gC label=”Cellar” icon=”cellar”
Group item=Outdoor icon=”garden”
      Group item=gSF label=”Second Floor” icon=”firstfloor” 
}

……….

…..

The highlighted entry defines a new group type (no devices yet) with user label of “Second Floor” and an user defined icon.

Items

Now, under the demo.items declare that “Second Floor” group gSF will be used. Your entry should look like this,

Group All
Group gGF (All)
Group gFF (All)
Group gC (All)
Group gSF (All)

Now under this new group we can add any number of devices or items to control. Since we want to control a light device on the second floor corridor, define a new corridor device like this,

Group SF_Corridor “Corridor” <corridor> (gSF)

Now under section commented as Lights, include the following line,

Switch Light_SF_Corridor_Ceiling “Corridor” (SF_Corridor, Lights)

Now this tells OpenHAB system that SF_Corridor is a switch device type and that it can be controlled in ON or OFF manner like Lights. This is rather an incomplete definition since there is no physical access defined for controlled this device. But OpenHAB is happy to oblige and doesn’t care if there is no physical device present.

Device Control Simulation

Now refresh your browser (preferably by clearing the cache) and you should be able to see the new device additions to OpenHAB GUI.

OpenHAB New Second Floor Group
New Second Floor Group
Second Floor Location List
Second Floor Location List
Second Floor Corridor Device List
Second Floor Corridor Device List

Everytime you toggle the Corridor Light, you will be able to see INFO logs on the OpenHAB console. These message are helpful when debugging,

11:53:39.388 INFO runtime.busevents[:22] – Light_SF_Corridor_Ceiling received command OFF

11:54:00.186 INFO runtime.busevents[:22] – Light_SF_Corridor_Ceiling received command ON

The OpenHAB console also provides for command line access to the devices. You can quickly test your device access instead of using the GUI. You can list out all the devices under Second Floor using pattern matching,

osgi> openhab items *SF*
gSF (Type=GroupItem, Members=1, State=ON)
SF_Corridor (Type=GroupItem, Members=1, State=ON)
Light_SF_Corridor_Ceiling (Type=SwitchItem, State=ON)

This lists all the SF group devices and their state information.

To specifically check status of an item, you can use the status option,

osgi> openhab status Light_SF_Corridor_Ceiling
ON

Control of the item can be done using the update command,

osgi> openhab update Light_SF_Corridor_Ceiling OFF
Update has been sent successfully.

This has been an easy change. But to physically cause state of a device (LED for now) to change using this GUI, we will use a RaspberryPI with OpenHAB running on it. We will also introduce another OpenHAB concept of bindings in the next post.

Advertisements

6 thoughts on “OpenHAB – Working with the GUI

  1. Hello. Thank you for this tutorial. Everything went fine up until I tried to add the “Second floor” … its showing up as GSW on the homepage and when clicked there’s no item in the list at all. I am using the latest version which may be different from yours. Please let me know if/what I need to do different because I copied exactly what you stated here and no dice. Also do you mind replying back with an email or some other form of contact? Im trying to setup a way to control a few lights and was hoping you could give me a few more ponters. Thanks again!

    Like

      • Sachin

        Thanks. I also posted on your youtube account. I decided to leave all default configurations and simply add the command at the end just for testing purposes. I have the LED working through command line but cannot get it to turn on/off through OpenHab. I posted the following logs on your YT channel as well but will post here in case you missed it. I would REALLY appreciate it if you can help me get this solved asap.. I’m sure its something simple I am overlooking. I am using the latest version of Openhab from their site running on Raspberry Pi Model B:

        sgi> 19:51:54.109 INFO o.o.c.internal.CoreActivator[:61] – openHAB runtime has been started (v1.5.1).
        19:52:20.027 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘exec.persist’
        19:52:23.835 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘logging.persist’
        19:52:24.290 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘db4o.persist’
        19:52:24.426 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘rrd4j.persist’
        19:52:25.351 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘demo.items’
        19:52:40.597 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘demo.sitemap’
        19:52:43.680 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘demo.script’
        19:52:45.644 INFO o.o.i.s.i.DiscoveryServiceImpl[:72] – mDNS service has been started
        19:53:03.228 INFO o.o.io.rest.RESTApplication[:143] – Started REST API at /rest
        19:53:09.549 INFO o.o.u.w.i.s.WebAppServlet[:79] – Started Classic UI at /openhab.app
        19:53:26.826 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘demo.rules’
        19:53:49.496 ERROR o.o.m.r.i.engine.RuleEngine[:267] – Error during the execution of startup rule ‘Initialize light states’: Could not invoke method: org.openhab.model.script.actions.BusEvent.postUpdate(org.openhab.core.items.Item,java.lang.Number) on instance: null
        19:53:52.623 ERROR o.o.m.r.i.engine.RuleEngine[:267] – Error during the execution of startup rule ‘Initialize heating states’: Could not invoke method: org.openhab.model.script.actions.BusEvent.postUpdate(org.openhab.core.items.Item,java.lang.Number) on instance: null
        19:53:55.050 ERROR o.o.m.r.i.engine.RuleEngine[:267] – Error during the execution of startup rule ‘Initialize contact states’: Could not invoke method: org.openhab.model.script.actions.BusEvent.postUpdate(org.openhab.core.items.Item,java.lang.Number) on instance: null
        19:53:59.727 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:53:59.751 ERROR o.o.m.r.i.engine.RuleEngine[:267] – Error during the execution of startup rule ‘Update max and min temperatures’: cannot invoke method public abstract org.openhab.core.types.State org.openhab.core.persistence.HistoricItem.getState() on null
        19:53:59.889 INFO o.o.c.s.AbstractActiveService[:169] – Exec Refresh Service has been started
        19:53:59.996 INFO runtime.busevents[:26] – Temperature_GF_Corridor state updated to 19.60000000
        19:54:00.069 INFO runtime.busevents[:26] – Temperature_GF_Toilet state updated to 18.70000000
        19:54:00.104 INFO runtime.busevents[:26] – Temperature_GF_Living state updated to 21.50000000
        19:54:00.239 INFO runtime.busevents[:26] – Temperature_GF_Kitchen state updated to 18.40000000
        19:54:00.293 INFO runtime.busevents[:26] – Temperature_FF_Bath state updated to 19.70000000
        19:54:00.340 INFO runtime.busevents[:26] – Temperature_FF_Office state updated to 19.60000000
        19:54:00.377 INFO runtime.busevents[:26] – Temperature_FF_Child state updated to 19.90000000
        19:54:00.405 INFO runtime.busevents[:26] – Temperature_FF_Bed state updated to 20.50000000
        19:54:01.625 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:54:01.634 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:55:00.250 INFO runtime.busevents[:26] – Temperature_GF_Corridor state updated to 19.00000000
        19:55:00.219 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:55:00.318 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:55:00.372 INFO runtime.busevents[:26] – Temperature_GF_Toilet state updated to 18.70000000
        19:55:00.451 INFO runtime.busevents[:26] – Temperature_GF_Living state updated to 17.70000000
        19:55:02.424 INFO runtime.busevents[:26] – Temperature_GF_Kitchen state updated to 19.40000000
        19:55:02.705 INFO runtime.busevents[:26] – Temperature_FF_Bath state updated to 18.80000000
        19:55:02.799 INFO runtime.busevents[:26] – Temperature_FF_Office state updated to 18.00000000
        19:55:02.911 INFO runtime.busevents[:26] – Temperature_FF_Child state updated to 20.10000000
        19:55:02.988 INFO runtime.busevents[:26] – Temperature_FF_Bed state updated to 20.30000000
        19:56:00.145 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:56:00.161 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:56:32.581 WARN o.o.c.t.i.s.MapTransformationService[:70] – Could not find a mapping for ‘-‘ in the file ‘en.map’.
        19:56:34.970 INFO runtime.busevents[:22] – Light_GF_Kitchen_Ceiling received command ON
        19:56:35.847 WARN o.o.c.t.i.s.MapTransformationService[:70] – Could not find a mapping for ‘-‘ in the file ‘en.map’.
        19:56:48.818 INFO runtime.busevents[:22] – Light_GF_Kitchen_Table received command ON
        19:56:49.359 WARN o.o.c.t.i.s.MapTransformationService[:70] – Could not find a mapping for ‘-‘ in the file ‘en.map’.
        19:57:00.121 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:57:00.137 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:58:00.042 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:58:00.051 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:59:00.104 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        19:59:00.114 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:00:00.237 INFO runtime.busevents[:26] – Temperature_GF_Corridor state updated to 17.60000000
        20:00:00.275 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:00:00.288 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:00:00.368 INFO runtime.busevents[:26] – Temperature_GF_Toilet state updated to 22.50000000
        20:00:00.460 INFO runtime.busevents[:26] – Temperature_GF_Living state updated to 18.30000000
        20:00:00.524 INFO runtime.busevents[:26] – Temperature_GF_Kitchen state updated to 18.60000000
        20:00:00.595 INFO runtime.busevents[:26] – Temperature_FF_Bath state updated to 21.60000000
        20:00:00.645 INFO runtime.busevents[:26] – Temperature_FF_Office state updated to 19.10000000
        20:00:00.734 INFO runtime.busevents[:26] – Temperature_FF_Child state updated to 22.40000000
        20:00:00.835 INFO runtime.busevents[:26] – Temperature_FF_Bed state updated to 21.20000000
        20:00:01.114 WARN o.o.c.t.i.s.MapTransformationService[:70] – Could not find a mapping for ‘-‘ in the file ‘en.map’.
        20:01:00.076 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:01:00.093 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:02:00.087 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:02:00.102 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:03:00.093 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:03:00.109 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:04:00.070 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:04:00.099 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:05:00.144 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:05:00.169 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:05:00.190 INFO runtime.busevents[:26] – Temperature_GF_Corridor state updated to 20.80000000
        20:05:00.263 INFO runtime.busevents[:26] – Temperature_GF_Toilet state updated to 18.70000000
        20:05:00.335 INFO runtime.busevents[:26] – Temperature_GF_Living state updated to 17.70000000
        20:05:00.462 INFO runtime.busevents[:26] – Temperature_GF_Kitchen state updated to 22.10000000
        20:05:00.520 INFO runtime.busevents[:26] – Temperature_FF_Bath state updated to 20.20000000
        20:05:00.593 INFO runtime.busevents[:26] – Temperature_FF_Office state updated to 21.70000000
        20:05:00.639 INFO runtime.busevents[:26] – Temperature_FF_Child state updated to 18.80000000
        20:05:00.725 INFO runtime.busevents[:26] – Temperature_FF_Bed state updated to 20.90000000
        20:05:00.801 WARN o.o.c.t.i.s.MapTransformationService[:70] – Could not find a mapping for ‘-‘ in the file ‘en.map’.
        20:06:00.079 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:06:00.107 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:06:52.277 WARN javax.jmdns.impl.DNSIncoming[:415] – There was an OPT answer. Not currently handled. Option code: 65002 data: C57605E3713A5E9D
        20:07:00.090 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:07:00.099 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:08:00.093 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:08:00.104 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:08:01.165 INFO o.o.m.c.i.ModelRepositoryImpl[:97] – Refreshing model ‘demo.items’
        20:08:01.736 INFO runtime.busevents[:26] – Light_GF_Corridor_Ceiling state updated to Undefined
        20:08:01.929 ERROR o.o.m.c.i.f.FolderObserver[:105] – An unexpected exception has occured
        java.lang.NullPointerException: null
        at org.openhab.binding.gpio.internal.GPIOGenericBindingProvider.processBindingConfiguration(GPIOGenericBindingProvider.java:89)
        20:08:12.054 INFO o.o.m.c.i.ModelRepositoryImpl[:97] – Refreshing model ‘demo.items’
        20:08:12.550 INFO runtime.busevents[:26] – Light_GF_Living_Table state updated to Undefined
        20:08:12.612 ERROR o.o.m.c.i.f.FolderObserver[:105] – An unexpected exception has occured
        java.lang.NullPointerException: null
        at org.openhab.binding.gpio.internal.GPIOGenericBindingProvider.processBindingConfiguration(GPIOGenericBindingProvider.java:89)
        20:08:22.726 INFO o.o.m.c.i.ModelRepositoryImpl[:97] – Refreshing model ‘demo.items’
        20:08:23.182 INFO runtime.busevents[:26] – Light_GF_Living_Table state updated to Undefined
        20:08:23.247 ERROR o.o.m.c.i.f.FolderObserver[:105] – An unexpected exception has occured
        java.lang.NullPointerException: null
        at org.openhab.binding.gpio.internal.GPIOGenericBindingProvider.processBindingConfiguration(GPIOGenericBindingProvider.java:89)
        20:08:33.375 INFO o.o.m.c.i.ModelRepositoryImpl[:97] – Refreshing model ‘demo.items’
        20:08:33.731 INFO runtime.busevents[:26] – Light_GF_Living_Table state updated to Undefined
        20:08:33.798 ERROR o.o.m.c.i.f.FolderObserver[:105] – An unexpected exception has occured
        java.lang.NullPointerException: null
        at org.openhab.binding.gpio.internal.GPIOGenericBindingProvider.processBindingConfiguration(GPIOGenericBindingProvider.java:89)
        20:08:43.939 INFO o.o.m.c.i.ModelRepositoryImpl[:97] – Refreshing model ‘demo.items’
        20:08:44.214 INFO runtime.busevents[:26] – Light_GF_Living_Table state updated to Undefined
        20:08:44.252 ERROR o.o.m.c.i.f.FolderObserver[:105] – An unexpected exception has occured
        java.lang.NullPointerException: null
        at org.openhab.binding.gpio.internal.GPIOGenericBindingProvider.processBindingConfiguration(GPIOGenericBindingProvider.java:89)
        20:08:54.392 INFO o.o.m.c.i.ModelRepositoryImpl[:97] – Refreshing model ‘demo.items’
        20:08:54.838 INFO runtime.busevents[:26] – Light_GF_Living_Table state updated to Undefined
        20:08:54.905 ERROR o.o.m.c.i.f.FolderObserver[:105] – An unexpected exception has occured
        java.lang.NullPointerException: null
        at org.openhab.binding.gpio.internal.GPIOGenericBindingProvider.processBindingConfiguration(GPIOGenericBindingProvider.java:89)
        20:09:00.088 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:09:00.102 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
        20:09:05.047 INFO o.o.m.c.i.ModelRepositoryImpl[:97] – Refreshing model ‘demo.items’
        20:09:05.373 INFO runtime.busevents[:26] – Light_GF_Living_Table state updated to Undefined
        20:09:05.435 ERROR o.o.m.c.i.f.FolderObserver[:105] – An unexpected exception has occured
        java.lang.NullPointerException: null

        Like

  2. Launching the openHAB runtime…
    osgi> 23:11:46.622 INFO o.o.c.internal.CoreActivator[:61] – openHAB runtime has been started (v1.5.1).
    23:12:13.797 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘exec.persist’
    23:12:16.891 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘logging.persist’
    23:12:17.461 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘db4o.persist’
    23:12:17.694 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘rrd4j.persist’
    23:12:18.447 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘demo.items’
    23:12:34.979 INFO o.o.i.s.i.DiscoveryServiceImpl[:72] – mDNS service has been started
    23:12:43.086 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘demo.sitemap’
    23:12:48.242 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘demo.script’
    23:12:57.230 INFO o.o.io.rest.RESTApplication[:143] – Started REST API at /rest
    23:13:05.102 INFO o.o.u.w.i.s.WebAppServlet[:79] – Started Classic UI at /openhab.app
    23:13:22.034 INFO o.o.m.c.i.ModelRepositoryImpl[:79] – Loading model ‘demo.rules’
    23:13:46.920 ERROR o.o.m.r.i.engine.RuleEngine[:267] – Error during the execution of startup rule ‘Initialize light states’: Could not invoke method: org.openhab.model.script.actions.BusEvent.postUpdate(org.openhab.core.items.Item,java.lang.Number) on instance: null
    23:13:50.053 ERROR o.o.m.r.i.engine.RuleEngine[:267] – Error during the execution of startup rule ‘Initialize heating states’: Could not invoke method: org.openhab.model.script.actions.BusEvent.postUpdate(org.openhab.core.items.Item,java.lang.Number) on instance: null
    23:13:52.690 ERROR o.o.m.r.i.engine.RuleEngine[:267] – Error during the execution of startup rule ‘Initialize contact states’: Could not invoke method: org.openhab.model.script.actions.BusEvent.postUpdate(org.openhab.core.items.Item,java.lang.Number) on instance: null
    23:13:59.812 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
    23:13:59.846 ERROR o.o.m.r.i.engine.RuleEngine[:267] – Error during the execution of startup rule ‘Update max and min temperatures’: cannot invoke method public abstract org.openhab.core.types.State org.openhab.core.persistence.HistoricItem.getState() on null
    23:13:59.984 INFO runtime.busevents[:26] – Temperature_GF_Corridor state updated to 18.00000000
    23:14:00.027 INFO runtime.busevents[:26] – Temperature_GF_Toilet state updated to 18.00000000
    23:14:00.100 INFO runtime.busevents[:26] – Temperature_GF_Living state updated to 21.10000000
    23:14:00.132 INFO runtime.busevents[:26] – Temperature_GF_Kitchen state updated to 21.10000000
    23:14:00.182 INFO runtime.busevents[:26] – Temperature_FF_Bath state updated to 20.20000000
    23:14:00.232 INFO runtime.busevents[:26] – Temperature_FF_Office state updated to 18.80000000
    23:14:00.276 INFO runtime.busevents[:26] – Temperature_FF_Child state updated to 18.50000000
    23:14:00.325 INFO runtime.busevents[:26] – Temperature_FF_Bed state updated to 22.10000000
    23:14:01.283 WARN o.o.m.i.i.GenericItemProvider[:108] – Attempted to register a second BindingConfigReader of type ‘gpio’. The primaraly reader will remain active!
    23:14:01.575 INFO o.o.c.s.AbstractActiveService[:169] – Exec Refresh Service has been started
    23:14:01.689 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
    23:14:01.695 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’
    23:15:00.152 WARN o.o.c.p.e.PersistenceExtensions[:404] – There is no queryable persistence service registered with the name ‘rrd4j’
    23:15:00.178 WARN o.o.c.p.e.PersistenceExtensions[:130] – There is no queryable persistence service registered with the name ‘rrd4j’

    Sorry about the long posts

    Like

    • Hi Nono,

      It appears that the distribution you have picked up has an issue. Raspberry Pi would be the last thing to suspect so, can you give me your distribution. I can try it on my Pi. I have the same model B.

      /Sachin

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s