Alljoyn Binding for OH 2?

[ashish nagar]

Is there any AllJoyn Binding available for OH 2 ?

I like to use AllJoyn framework with Openhab 2.

Thanks

Ashish

[Kai Kreuzer]

Ashish,

Please note that openHAB 2 is not yet for users, but for developers - so if you want to implement an AllJoyn binding, please let me know, I am very interested in this as well!

To see what kind of bindings exist so far, please have a look at openHAB 1.x: http://www.openhab.org/features-tech.html

Regards,

Kai

--
You received this message because you are subscribed to the Google Groups "openhab2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab2+u...@googlegroups.com.
To post to this group, send email to open...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/bf403e38-2e28-41f0-bbeb-9c077e516e6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ashish nagar]

Yes I am interested in developing AllJoyn binding.  I have reviewed smarthome binding implementation hue, wemo, sono and yahoo weather.  

If somebody can guide me with some specs - how to approach AllJoyn binding like channel types, I can write the code.

Discovery should not be any issue.  Once the AllJoyn device is discovered, it may have custom interface, methods to interact. So one channel may be getting the interface details.

Once interface details are available, another channel can be used to call the methods with the parameter.

how to handle the return value?

[Kai Kreuzer]

Hi again,

Yes I am interested in developing AllJoyn binding.  I have reviewed smarthome binding implementation hue, wemo, sono and yahoo weather.  

That’s great to hear - so please give it a try and I will do my best to support you!

So one channel may be getting the interface details.

Once interface details are available, another channel can be used to call the methods with the parameter.

This sounds like a mapping on the wrong abstraction level to me. I am not in the details of the AllJoyn spec, but I would expect that after discovering a device and reading its interface, you would then construct a thing that has different channels for the different methods that the device offer.

Do you have a pointer to how such device interfaces can look like for AllJoyn?

Regards,

Kai

On Thursday, December 11, 2014 7:01:15 PM UTC+5:30, Kai Kreuzer wrote:

Ashish,

Please note that openHAB 2 is not yet for users, but for developers - so if you want to implement an AllJoyn binding, please let me know, I am very interested in this as well!

To see what kind of bindings exist so far, please have a look at openHAB 1.x: http://www.openhab.org/features-tech.html

Regards,

Kai

Am 11 Dec 2014 um 08:28 schrieb ashish nagar <nagar...@gmail.com>:

Is there any AllJoyn Binding available for OH 2 ?

I like to use AllJoyn framework with Openhab 2.

Thanks

Ashish

--
You received this message because you are subscribed to the Google Groups "openhab2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab2+u...@googlegroups.com.
To post to this group, send email to open...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/bf403e38-2e28-41f0-bbeb-9c077e516e6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "openhab2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab2+u...@googlegroups.com.
To post to this group, send email to open...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/a4593357-d44a-4247-986b-4a76c354ace9%40googlegroups.com.

[ashish nagar]

Hi,

I am getting familiar with AllJoyn Framework.

As per your suggestion, after discovery a device and reading its interface, is it possible to construct thing with channels dynamically.  All the OH2 bnding samples I have studied have channel information in thing-type.xml.

Assuming we can create channels dynamically, how would you suggest handling the return value from methods and passing parameters to methods.

Thanks

[Kai Kreuzer]

Hi,

As per your suggestion, after discovery a device and reading its interface, is it possible to construct thing with channels dynamically.  All the OH2 bnding samples I have studied have channel information in thing-type.xml.

You are right, so far all bindings define the supported devices statically. But our concept allows that you dynamically define the thing-type as well as the channels.

Assuming we can create channels dynamically, how would you suggest handling the return value from methods and passing parameters to methods.

Well, this depends on what the method and the return value is. Somehow the functionality of the device must be mapped onto items in openHAB. Can you give a concrete example of a method?

Regards,

Kai

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/29308701-b165-44b1-a7b8-bb855ade4f6f%40googlegroups.com.

[Kai Kreuzer]

Maybe a good device to start with would be LIFX - as this is the only device I have seen so far that claims that it is on the market and AllJoyn-compatible.

And we already have a static thing definition for LIFX within Eclipse SmartHome: https://github.com/dnobel/smarthome/blob/lifx/binding/org.eclipse.smarthome.binding.lifx/ESH-INF/thing/thing-types.xml

Could you tell, how the interfaces/methods for LIFX look like in AllJoyn?

Regards,
Kai

Hi,

To unsubscribe from this group and stop receiving emails from it, send an email to openhab2+unsubscribe@googlegroups.com.

[ashish nagar]

Hi Kai,

LIFX binding is not directly using alljoyn sdk.  It is using android sdk(https://github.com/LIFX/lifx-sdk-android).   I have spent sometime reviewing lifx android sdk but don't see any reference to alljoyn libraries.  May be instead of using alljoyn sdk, they have implemented alljoyn messaging protocol internally.  I have to study the implementation and verify with alljoyn spec.

I will create demo alljoyn server and client and share the code.  You will get better idea regarding alljoyn and suggest the approach.

Any suggestion or pointers regarding following:

1.  What are the different ways to pass parameters to binding ? Is configuration only way?  

2.  What is the way to handle return value?  Is string or number item type only option?

3.  Any example to learn how to create channel on run time?

4.  Is it possible to use multiple persistence i.e specify persistence service at item level?

Thanks

Hi,

[Kai Kreuzer]

Hi  Ashish,

Yes, I am aware that the LIFX SDK is not using AllJoyn. But you might notice that LIFX has stopped any further development on this SDK, so I would expect that they now concentrate on being AllJoyn compatible. And if they are compatible, they would not need to offer any LIFX SDK anymore, right?

Unfortunately, there isn’t much information on whether LIFX already speaks AlLJoyn - questions about this stay unanswered: http://support.lifx.co/hc/communities/public/questions/200667144-LIFX-running-AllJoyN-

On the other hand, LIFX is one of the only products that is usually meantioned as an example of an AllJoyn device.

So I was thinking that it should be a good example device for testing an AllJoyn binding. Or do you have any other product available for testing?

1.  What are the different ways to pass parameters to binding ? Is configuration only way?  

Yes, but configuration for bindings should be minimal and static. Usually, you should rather configure the Things that are managed through the binding.

2.  What is the way to handle return value?  Is string or number item type only option?

No, all item types are possible: https://github.com/eclipse/smarthome/blob/master/docs/sources/architecture/index.md#items-and-events

3.  Any example to learn how to create channel on run time?

Not yet really. The important line is https://github.com/eclipse/smarthome/blob/master/bundles/core/org.eclipse.smarthome.core.thing/src/main/java/org/eclipse/smarthome/core/thing/binding/ThingHandlerFactory.java#L65

In your ThingHandlerFactory, you have to dynamically construct your things in the createThing() method.

To do so, you can use the utility class https://github.com/eclipse/smarthome/blob/master/bundles/core/org.eclipse.smarthome.core.thing/src/main/java/org/eclipse/smarthome/core/thing/binding/builder/ThingBuilder.java

4.  Is it possible to use multiple persistence i.e specify persistence service at item level?

Not sure if I understand your question. Bindings should know nothing about persistence services.

So if your question is in some other context: Yes, you can have as many persistence services as you like for the same item.

Best regards,

Kai

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/6410b5c2-b09c-4ffe-8d21-0c090f8cdb3e%40googlegroups.com.

[ashish nagar]

Hi Kai,

I have posted similar question on LIFX forum, lets see if they reply.  I am working on creating alljoyn server component which will have one method GetTemperature(location) and it will return current temperature of the given location.  This is similar code as yahoo weather binding sample.

Once I have sample code running, I will send you the code.  Then you will be able to suggest best way to proceed for AllJoyn binding.

You said in reply that "Yes, you can have as many persistence services as you like for the same item." - where do I specify multiple persistence service configuration? 

thanks

[Kai Kreuzer]

You said in reply that "Yes, you can have as many persistence services as you like for the same item." - where do I specify multiple persistence service configuration? 

There is currently no change from openHAB 1.x so far, so please see https://github.com/openhab/openhab/wiki/Persistence

Regards,

Kai

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/0e7e4bfa-d2e5-4841-b0f0-51fe41f859dc%40googlegroups.com.

[ashish nagar]

Hi Kai,

Pls download alljoyn sample - client and server.  

https://drive.google.com/file/d/0B6mEQTpeF5q1SVFDck83SjhRbDg/view?usp=sharing

zip file contains two (java console apps) projects:

1. AlljoynService

2. AlljoynClient

You can directly import these projects in Eclipse using import -> General -> Existing Projects into Workspace -> Select archive file

1. AlljoynService:

====================

This is a service component with one interface SampleInterface.  Sample Interface has one method GetTemperature(String location). It returns current temperature of the location. Location is WOEID code.

WOEID code lookup (http://woeid.rosselliot.co.nz/)

This is to simulate alljoyn based end node (sensor).

2. AlljoynClient:

=================

This is a client component.  It supports discovery and calls GetTemperature(location) method on the Service component.  

Client app is a java console app. It has 4 options in menu -  Always run Discovery (option 1) before running other options.

Option 2 gets the published interface from service and prints the detail.

Notice SampleInterface is also included in the client component. 

This sample will give you some idea of how alljoyn works.  

Thanks

Ashish 

...

[Kai Kreuzer]

I have requested access to download the file, you didn't grant it yet...

[ashish nagar]

I have not received any request.

I have turned on the sharing with public ..so try to download again.

https://drive.google.com/file/d/0B6mEQTpeF5q1SVFDck83SjhRbDg/view?usp=sharing

[Kai Kreuzer]

Hi Ashish,

Thanks, now I was able to download it.

It seems to me as if this level of AllJoyn API is a bit too generic for a useful integration. It more or less resembles an RPC.

I guess there should be something like an ontology in AllJoyn that defines and describes certain kinds of devices. Do you know anything like this?

LIFX is probably still the best way to move forward with some real example.

Note that there is a sample app which simulates a device that implements the lighting service: https://play.google.com/store/apps/details?id=com.qualcomm.luminaire

Documentation and sample code for the lighting service can be found at https://wiki.allseenalliance.org/tsc/connected_lighting.

Could this be a good approach for a first integration?

Best regards,

Kai

--
You received this message because you are subscribed to the Google Groups "openhab2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab2+u...@googlegroups.com.
To post to this group, send email to open...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/6b060f45-c7d0-4d20-b6c3-836e00644b33%40googlegroups.com.

[ashish nagar]

I am not aware of ontology in AllJoyn.

I will look at lighting service documentation and sample code.

Thanks

[ashish nagar]

Hi Kai,

I have reviewed Lighting Service Framework (LSF).  I think this can be a good starting SDK for AllJoyn binding

There are 3 major components:

1. Lamp Service - very small footprint library for End Node...implemented by Lamp(Light bulb) manufacturer

2.  Lighting Controller Service 

   - Dependent on AllJoyn Core 

   - runs outside of the Lamp - on Hub, Router, Switch, Gateway, or any other Linux-based device on the same network as the Lamps

   - Discovers & connects with devices running Lamp Service

   - stores group, scene, and present info

   - Controller service client provides a set of C/C++ APIs to application developers to access Controller service

   Features

   ----------

   - Lamp Details - Lamp Details are lamp-specific metadata that can be queried. Extends metadata in About.

   - Control - Power On/Standby, Brightness, Hue, Saturation, Color Temperature 

   - Presets - Any combination of Hue, Saturation, Color Temperature, and Brightness properties can be saved as a “Preset”

   - Groups - Lamps can be grouped and controlled together

   - Scenes - Scenes are preferences that can be saved to set a particular mood or automate a lighting configuration.

   - Effects - 2 Effects are defined in the LSF, Transition and Pulse. Effects must be implemented in the lamp OEM firmware. 

   - Events - All Scenes created in the LSF generate AllJoyn Events when the Scene is applied, Events allow the LSF to notify other devices and applications when a Scene is applied, allowing them to react when they receive the Event.  

   - Actions - Actions allow Scenes in the LSF to be discovered, introspected, and easily invoked by other devices and applications. This makes it very easy for other devices to trigger a scene

   OPENHAB Binding

   ===============

   1. Control

   Out of all the features, Control feature can be implemented without any problem.

   LSF SDK Control                         OH Item Type

   --------------------                                  ------------

   PowerOn/StandBy                             Switch

   Brightness (0-100%)                          Dimmer

   Hue   (0 - 360 deg)                            Dimmer

   Saturation (0 - 100%)                        Dimmer

   Color Temperature  (2700K - 5000K)  Dimmer

   Input value of control parameters are from sample android app.  Still need to verify from api/documentation for correct value ranges.

   2. Groups

   OH has similar functionality.  May be there is a way to create and manage LSF group with OH Group.  Need to keep OH Group and LSF Group in sync.

   3. Scenes, Actions, Events

   Not sure if there is any way to manage this using OH.  Scenes like Groups can be managed through LSF.  Each Scene can be discovred as Actions and can generate Events when executed.

   4. Presets, Effects 

   This is very specific to LSF.

   OH is mostly use for controlling devices and getting status.  If that's the case, is binding going to allow only Control feature? or Is binding going to manage all other features?

   I am going to install Lighting Controller Service on linux box and write sample app to learn SDK.  Luminaire Android APP from google play store can help simulate the end node lamp.

Thanks

Ashish

[Kai Kreuzer]

Hi Ashish,

Cool, thanks for the analysis!

Yes, I think the "control" functionality should be rather straight forward and the main feature to implement.

Please note that the different functions should actually be bundled into only two channels:

- One for "color", combining Power/Brightness/Hue/Saturation into one HSBType for a ColorItem

- One for "colorTemperature", being linked to a DimmerItem for 0-100% "heat".

See the Philips Hue bulbs as an example, where it is exactly this way: https://github.com/openhab/smarthome/blob/master/binding/org.eclipse.smarthome.binding.hue/ESH-INF/thing/LCT001.xml

Another important feature is the discovery support (and with it the "lamp details" feature), which should be implemented in openHAB. Probably even better to start with this step instead of the control features.

Best regards,
Kai

[ashish nagar]

Hi Kai,

Lighting Service Framework (LSF) SDK is only released for Android and iOS.  I tried to use SDK jars in java but there is android dependency.  

I will research more and try to make it work in java.  There no forum to get help. 

Thanks

[Jayaraj Esvar]

Hi,

     Are you guys still working on Alljoyn Binding. I am new to openhab.

    i have implemented my devices with alljoyn frame work using control panel interface. Can you guys help me in binding alljoyn with openHab.

    

You can create Java based control panel by just adding  fully built android.jar

 

thanks and regards,

   jayaraj 

[Kai Kreuzer]

Hi Jayaraj,

I am currently looking into building a binding using the AllJoyn LSF (which provides a higher level of abstraction for lights). What kind of devices have you build? How would you want to see them mapped within openHAB?

Regards,
Kai

[Jayaraj Esvar]

Hi,

      I am build devices on top of alljoyn frame work , Currently working on connecting all switch boards ( Multiple switches with fan controller) and sensors.

      In Alljoyn we add the meta data of devices with their interfaces(Properties, signals and methods) on the device. Which is called the control panel. As all the definitions are part of device, once after auto discovery we create the widgets for the control panel based on the meta data.

     

     I am now looking for Automation feature and cloud connectivity for my gateway controller. So thought of creating binding with Eclipse SmartHome/ openHab2.

     As Alljoyn Java implementation was tightly coupled with Android code I had to hack them to fit to run on ubuntu. Now I get thing's definitions &  Event Listeners out of  Control panels definitions for each device. 

   My queries are 

     1. Will I be able add things to OpenHab2 dynamically from my binding code?

              My Binding code will have auto discovery of devices. Just need to map them with Things

     2. Does OpenHab2 Cloud connectivity? 

     3.How do you connect to cloud from openHab2. Do you provide the Cloud router/connectivity.

For eg  ControlPanel meta data:

<controlPanelDevice xmlns="http://www.alljoyn.org/controlpanel/gen">

  <name>Device</name>

  <headerCode>#include "ControlPanelProvided.h"</headerCode>

  <url>http://www.ABCD.com</url>

  <languageSet name="supportedLanguages">

    <language>en</language>

  </languageSet>

  <controlPanels>

    <controlPanel languageSet="supportedLanguages">

      <rootContainer>

        <name>ElnettySwitchboard</name>

        <secured>false</secured>

        <enabled>true</enabled>

        <hints>

          <hint>vertical_linear</hint>

        </hints>

        <elements>

          <stringProperty>

            <name>switch1Property</name>

            <getCode>getswitch1</getCode>

            <setCode>setswitch1(%s)</setCode>

            <secured>false</secured>

            <enabled>true</enabled>

            <writable>true</writable> 

            <hints>

              <hint>switch</hint>

            </hints>

            <constraintVals>

              <constraint>

                <display>

                  <value type="literal" language="en">off</value>

                </display>

                <value>off</value>

              </constraint>

              <constraint>

                <display>

                  <value type="literal" language="en">on</value>

                </display>

                <value>on</value>

              </constraint>

            </constraintVals>

          </stringProperty>  

        </elements>

      </rootContainer>

    </controlPanel>

  </controlPanels>

</controlPanelDevice>

Thanks & regards,

    jayaraj esvar

--
You received this message because you are subscribed to a topic in the Google Groups "openhab2" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab2/WVZrawtO2_Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab2+u...@googlegroups.com.

To post to this group, send email to open...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/22e3e97c-8da4-4e02-8220-fa548bfeeeb6%40googlegroups.com.

[Kai Kreuzer]

Hi Jayaraj,

I am also working on a prototype on an AllJoyn binding for Eclipse SmartHome - we should hence try to synchronize our efforts!

     As Alljoyn Java implementation was tightly coupled with Android code I had to hack them to fit to run on ubuntu. Now I get thing's definitions &  Event Listeners out of  Control panels definitions for each device. 

This sounds great! Can you share the code changes that you did in order to get a „pure“ Java version?

     1. Will I be able add things to OpenHab2 dynamically from my binding code?

              My Binding code will have auto discovery of devices. Just need to map them with Things

Implementing a DiscoveryService will allow you to add new „things“ to the Inbox. The user can then approve them, so that they are available in openHAB.

     2. Does OpenHab2 Cloud connectivity? 

Not yet, but we will be working on this soon, see https://groups.google.com/d/msg/myopenhab/I98CNQQaayE/G90ynSYDNK4J

     3.How do you connect to cloud from openHab2. Do you provide the Cloud router/connectivity.

There is a specific OSGi bundle to add to the openHAB runtime, which then uses SocketIO to establish a permanent connection to https://my.openhab.org/.

Best regards,

Kai

You received this message because you are subscribed to the Google Groups "openhab2" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openhab2+u...@googlegroups.com.

To post to this group, send email to open...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/CAJ6Mnc746ikQ3Zt1DWviHLyE9O3rnMf6_hXwhOeB9Puoe7kVfg%40mail.gmail.com.

[Jayaraj Esvar]

Hi,

       Right now I am working on a binding  for customized interfaces for my devices. As Alljoyn has generic control panel interface which defines widget, I am trying to figure out how to map it to a thing_type which has fixed channels on Openhab2. (On Alljoyn, Widget is created dynamically).

       So for openHab2 People should create few generic controlPanel definition and corresponding thing definition for openHab2 for each device type. Then we can suggest them to use our binding.

     I have just started working on it, once finished will update you.

thanks & regards,

   jayaraj

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/867A42E4-F2FE-482D-BBF6-747313A8CE65%40openhab.org.

[Kai Kreuzer]

       So for openHab2 People should create few generic controlPanel definition and corresponding thing definition for openHab2 for each device type. Then we can suggest them to use our binding.

I am not sure if I understand what you mean. In openHAB, you have to define ThingTypes that represent the structure of your device. It sounds as if this corresponds to your controlPanel definitions. So if these definitions are somewhere accessible, you could go and construct ThingTypes dynamically based on this information.

Regards,

Kai

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/CAJ6Mnc4LXJS4zd4abjA7Xe2nSz5ZFdDu_j7RzYQZOwj_mHcRNw%40mail.gmail.com.

[Jayaraj Esvar]

Hi,

       Yes you are right on what I meant. If we are going to create a generic Binding for Allyon devices then how do we map them.

  In Alljoyn Clients, they have the capability create Widgets or things without the knowledge of the device. But here in OpenHab2 we need to know the definitions of the device.

 So If you have some plan to create a generic widgets for few devices types. OR some standard definitions to mention what type of thing  that device is. Then we can Map them.

  For my devices I am planning to create multiple things based on the my customized Control panel definitions.

thanks & regards,

  jayaraj

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/26498550-A313-4F75-80F9-B42F4EFC3761%40openhab.org.

[Kai Kreuzer]

  In Alljoyn Clients, they have the capability create Widgets or things without the knowledge of the device. 

Well, this is exactly what openHAB does as well. It simply renders widgets for the different channels (which can be a switch, a slider, a number etc.).

If you do not have any structural information at hand, you can also dynamically create the Thing within ThingHandlerFactory.create, without having to define a ThingType at all.

Regards,

Kai

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/CAJ6Mnc7GTnYWpYbQC9p4iMndRoi6bYFcVjAcbxK%3DHN%3DQFh6YVw%40mail.gmail.com.

[Jayaraj Esvar]

Hi,

      So Do you mean that I can create a Thing type without, defining the channel types in openHab2? . Because they have property types which can map to any control.

     what i meant was without  BindingConstants and thing definitions in xml, Is it possible to create things.

Thanks & regards,

   jayaraj

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/0117016E-A188-49B6-9C06-5B00F44E939E%40openhab.org.

[Kai Kreuzer]

So Do you mean that I can create a Thing type without, defining the channel types in openHab2?

Correct. All you need to do is to construct a valid thing (including channels, which do not have any reference to a channel type) when https://github.com/eclipse/smarthome/blob/master/bundles/core/org.eclipse.smarthome.core.thing/src/main/java/org/eclipse/smarthome/core/thing/binding/ThingHandlerFactory.java#L67 is called. The ThingTypeUID that you use for discovery and the ThingUID can be fully made up - there does not have to be a ThingType registered at all for it.

Regards,

Kai

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/CAJ6Mnc5HySppg38eSq%2Brdz%2BUc%2BiqtUt%3DcxqWaKLduHswqok4Cw%40mail.gmail.com.

[Jayaraj Esvar]

Hi,

       Ok then we can create a generic binding for alljoyn before that we need to finalized on how alljoyn controlPanel xml definition is written for the openHab2 binding.

      Users can write controlPanel xml based on the guidelines and generate code for there devices.

     One query on channel Labels, can user change the label name on Openhab2. I see that you pick label names from devices.

thanks & regards,

   jayaraj

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/E3D86456-F3CD-4BCD-8CC4-606DFF7AAC6A%40openhab.org.

[Kai Kreuzer]

Another question for you: How do you solve the problem with the required native C libraries for AllJoyn?

Do you use JNI and compile the libs for your platform?

I tried using the liballjoyn_java.so from the Android SDK for running on a RaspPi, but somehow my runtime is not able to load the library.

Regards,

Kai

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/CAJ6Mnc4tpBdKomYQi53D_VHZ7v3QNYaT9iR0hZEATUwMNwvzUg%40mail.gmail.com.

[Jayaraj Esvar]

Hi,

       Yes I use JNI Libs. For now I am running x86_64, so I picked x86_64/debug/dist/java/lib/liballjoyn_java.so. You will take liballjoyn_java.so from the android distribution. which are compiled for armeabi.

I just added these on the manifestfile

Bundle-ClassPath: .,

 lib/alljoyn_about.jar,

 lib/android.jar,

 lib/alljoyn.jar,

 lib/alljoyn_config.jar,

 lib/alljoyn_apps_android_utils.jar,

 lib/ControlPanelService.jar,

 lib/ControlPanelAdapter.jar

Bundle-NativeCode: lib/x86_64/liballjoyn_java.so;

 osname=Linux;

 processor=x86_64

thanks & regards,

  jayaraj

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/5BCB4209-3F1C-4598-98DB-2278C79ABCF9%40openhab.org.

[Kai Kreuzer]

Hi Jayaraj,

Did you make any progress on your binding? Is it working?

I by now gave up on path going for LSF (see https://lists.allseenalliance.org/pipermail/allseen-lighting/2015-July/000073.html) and need to look into the same way that you chose. Do you have any code to share? Would be great to have a jump start on building a rather generic AllJoyn binding!

Best regards,
Kai

[Jayaraj Esvar]

Hi,

       I have done that binding for alljoyn with Control Panel Interface based devices with some hints for binding with openhab2(My devices will be based out of alljoyn control panel interface). This may not be a generic library.

Also ported openhab2 with alljoyn on RasberryPI, It works fine.

I have not done any thing for Light Frame Work.

thanks & regards,

  Jayaraj Esvar

--

You received this message because you are subscribed to a topic in the Google Groups "openhab2" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab2/WVZrawtO2_Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab2+u...@googlegroups.com.
To post to this group, send email to open...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab2/67e784aa-b7a0-4178-be4d-a0ec5bde3739%40googlegroups.com.