Kaa Scenario

[Fábio Lima]

Good morning all,

I'm looking a platform for an Industrial IoT implementation and at the moment I'm testing some platforms, in which kaa platform is included.

In the POC i designed the following scenarios:

- Indoor Localization in a couple of spaces defined and something more simple like an temperature and noise sensor.

The hardware and protocols chosen for this scenarios it's essentially arduino, raspberry pi, BLE, Zigbee, MQTT.. 

For the indoor localization the sensor endpoint will be composed by an module BLE + Arduino that captures the Bluetooth signal and send the information "by zigbee" for an "intelligent gateway" that will be in this case an Raspberry pi. This raspberry Pi should be capable to management the devices, management the information, rules engine, sent information for cloud or local data-store, and others. The messaging for the the applications will be trough  the MQTT protocol. Basically that's it.

In the way to understand better how the best way to integrate the platform kaa in this scenario, I need your advices, if it's possible.

What is the best option for my scenario? I need to have in each sensor endpoint (module BLE + Arduino) an Kaa SDK or it's possible just have a Kaa SDK for gateway (Raspberry PI)? Because in the industrial implementation will have a huge number of endpoint sensors, and so much  as possible i wanna be clear of the best option for the future implementation.

From what i read and saw in the forum, the typically option it's connect directly the SDK into the sensor endpoint (module BLE + arduino). What i want figured out is if the implementation of KAA SDK is made in the the gateway(Raspberry PI) i will have some disadvantages or loosing some functionality/potential of Kaa platform.

Many thanks in advance

FL   

 

[Dmitry Sergeev]

Hello!

It's possible to embed Kaa SDK only in gateway (Raspberry PI in your case). The main disadvantage is need for additional implementation of some segregation logic:

1) Which logs comes from what Arduino device.

2) Implemenation of communication layer between gateway and sensors. (Forwarding notifications, events, configuration etc.)

So the most suitable and easy way to develop is to place Kaa SDK directly on a sensors. But in some cases (eg. sensors are too weak no handle SDK) your solution is good enough.

Thanks, Dmitry

четверг, 10 марта 2016 г., 14:22:04 UTC+2 пользователь Fábio Lima написал:

[Fábio Lima]

Thank you so much by the explanation Dmitry.

It's exactly this "segregation logic" that I'm trying to escape, at least in this phase. 

I can't  running away too much of this kind of solution, because the majority of sensors can't handle with sdk, and for the POC arduino it's one of the requirements and i thought at the moment the Kaa isn't compatible with arduino (correct if I'm wrong) .

I thought that installing the Kaa SDK in the gateway and with the endpoint profiles mechanisms existent, i would "easily" get a way to integrate the gateway (raspberry pi) to the endpoint sensors (module ble + arduino).

Creating first the profiles in the gateway, the sdk doesn't generate some kind of identifier that i could implement in the api arduino, so when the arduino connect for the first time with the gateway, the gateway knows "who is"? After this first paring and the ontologies created it's more easy to handle with the information received, device management, notification and others.

Many thanks in advance.

FL

[Dmitry Sergeev]

Hello again!

Here's extended solution for your case. You can spawn multiple SDK instances on gateway side and link them with corresponding sensor. We call this "actor gateway".

Please, look at schema that demonstrate this approach:

Thanks,

Dmitry

четверг, 10 марта 2016 г., 19:04:52 UTC+2 пользователь Fábio Lima написал:

[Ali Jawad]

Hello Baronsky ,

Can you please provide detail information how to make actor gateway?

Thanks

[Taher Kawantwala]

Hello Dmitry,
Can you explain how to create Actor Gateway? How to register Multiple Endpoint to Kaa IoT Server from Gateway?