-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Register IoT Agent #22
Comments
Let me read up a bit on AWS and Azure so we can define a common vocabulary of terms and I'll try to get back to you in a bit. Meanwhile you could open a duplicate question on FIWARE Ask where there should be more community and eyeballs on the question. |
Thank you for taking the time! The image comes from MS but the structure is identical to AWS. My question relates to what in the picture refers to "IoT device library" or "IoT Edge". For the purpose of this discussion they are the same thing in that they are responsible for the connection to the IoT Hub. The IoT hub has four main functions:
The device state, is one of the places where I'd expect the context broker to be superior. Device state is essentially just a json document shared between the IoT device and IoT Hub. It's powerful in that you can use it pretty much how ever you want such as for sensor- and meter configuration or firmware state etc. However there is no built-in modeling of entities such as with Context Broker. Questions:
Again, thank you for sharing and I hope to return the favor ;) |
Hi,
I have a customer who'd like to make use of the FIWARE platform.
I personally come from a background of AWS and Azure and (perhaps wrongly) assumed an IoT Agent is equivalent of a "Thing" (AWS) or "Device"(Azure). In other words, this would represent the device connecting to the Context Broker.
-If this is the case, how do I provision new IoT Agents, accepting and providing keys and tokens for agents?
The text was updated successfully, but these errors were encountered: