onboarding service appearing as a second device?

asked 2014-10-09 02:27:11 -0700

anszom gravatar image

updated 2014-10-16 01:49:01 -0700

I'm trying to implement onboarding for an embedded linux (non-openwrt) device. The device would also support other AllJoyn interfaces (control panel for now). I have built alljoyn services using the openwrt build config and I've ported most of the openwrt scripts to my embedded system. I'm using the provided onboarding-daemon which handles the onboarding process, but I also have another application running which handles the control panel interface. I've made sure that both processes use the same alljoyn-deviceId.txt file.

Currently I'm testing my device with the android "AllJoyn On" application, and it shows me two "Nearby Devices". One represents the onboarding service, the other is my own app. Can I somehow make it show up as one device only?

Do I need to integrate the onboarding functionality into my control application? Or can the About service be somehow instructed that both of the interfaces come from one device?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-11-03 16:44:06 -0700

bspencer gravatar image

Each AllJoyn BusAttachment is going to be seen as a separate application. One thing that "AJ On" application is not doing at this time is filtering/combining applications that come from the same DeviceID field in the About signal. If you would like the application to appear as the same tile then at this time you can either:

a) Merge all your AllJoyn code into a single application.

b) Write a new AllJoyn Application for a mobile that combines applications with the same DeviceID field.

c) Leave it as is, its just an extra piece of UI that doesn't hurt anything.

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

1 follower


Asked: 2014-10-09 02:27:11 -0700

Seen: 126 times

Last updated: Nov 03 '14