Revision history [back]

click to hide/show revision 1
initial version

onboarding service daemon

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?

onboarding service daemonappearing as a second device?

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?