I followed the Azure IoT tutorial at:
https://azure.microsoft.com/en-us/documentation/articles/iot-hub-csharp-csharp-getstarted/
and everything works great.
I now have a new requirement, which is to connect to the IoT hub from an iPhone. In the C# example, I had to download the appropriate NuGet package (Microsoft.Azure.Devices.Client) and use the DeviceClient class.
Is there a similar "package" available for iPhone development? How can an iOS device connect to the Azure IoT hub?
There's a REST API for devices to exchange messages with an Azure IOT Hub.
The Azure IoT Hub C# Device SDK is now cross-platform (with Xamarin), and supports iOS devices.
It's published as a nuget package:
https://www.nuget.org/packages/Microsoft.Azure.Devices.Client.PCL/
Related
I have a service that's already Dockerized. The service listens on some ports and makes some outbound network calls. At the moment, updating the service requires someone to access the console remotely and manually replace the old container with the latest version.
After reading through the Azure IoT Edge documentation and the SDKs, it's not clear to me if an Azure IoT module MUST include an Azure IoT SDK. I know the Azure IoT SDK is necessary for passing messages, accessing the module twin, and probably more, but I don't need any of that at the moment for this specific use-case.
Can I reuse my existing Docker containers with Azure IoT Edge or would I need to add the Azure IoT SDK (because there's a health check or other internal requirement for the SDK)?
As you mentioned, Azure IoT SDK is the recommended way to do messaging, access twin etc. But it is optional.
If you just want the IoT Edge runtime to launch a Docker container that listens on local ports and performs outbound network calls, you can certainly do that. Nothing will get in your way.
building a product utilizing EWM3166 module used in Azure IoT devkit and would like to customize the bootloader.
where can I find the source code for Azure IoT devkit AZ3166 bootloader?
I am new to azure iot and I am trying to connect a 3g obd 2 tracker to my account azure iot hub. I found an example to connect the obd to local gateway (phone) via bluetooth or wifi but I want the tracker to be completely independant from any local gateway.
Is there a tutorial or documentation to help me getting starting with connecting 3g teacker to azure iot
There is no tutorial specifically on 3G trackers. What is the OS running on the device? You can always use the device SDK to connect to IoT Hub directly if your device is IP capable.
Our Current Deployment:
1) several back-end devices running an MQTT client connect to an opensource MQTT broker (Mosquitto)
2) Mosquitto is running on a Linux VM and acts as a broker and a communication point between back-end & front-end devices.
3) Several front-end devices (Mobile App / browser based GUI) connect to the broker. some of the front-end devices read & write to the broker (Sub & Pub) while some front-end only read (Sub)
4) Some front-end devices connect for a few minutes & some front ends are always connected.
5) Although the amount of data being transferred is a few kb, it is sometimes fast changing.
6) No TLS is used for the MQTT traffic & it cannot be enabled on the back-end devices.
This setup works for us, but I am looking for a way to scale up and was considering the azure IoT hub, but I am confused if the IoT hub can be used as a broker or I would need additional components to be deployed for acting as a MQTT broker ?
Azure IoT Hub is not a generic MQTT Broker. There is a built-in the device communications for MQTT protocol. More details can be found in the Using the MQTT protocol directly
For exploring the MQTT Devices (virtual devices) with the Azure IoT Hub (without the coding) can be used a small tool Azure IoT Hub Tester
I am using the Offline Sync feature of Azure Mobile Apps and it is working as expected.
I am also running a Service Fabric cluster on Azure for other services.
Is there anything that would prevent me technically or legally from running the Azure Mobile App on Service Fabric? (As opposed to running Azure Moble App on Azure Mobile App host on Azure).
Azure Mobile Apps uses three things:
Offline sync with a SQL Azure instance backend - fully supported on whatever container you choose
Push Registrations connected via App Service Push - will not be supported outside of Azure App Service
Authentication via server-flow or client-flow - will not be supported outside of Azure App Service
You don't have a problem legally - Azure Mobile Apps is an open-source project licensed under a OSS friendly license. However, Auth and Push are going to be issues if you use them.