Azure IoT Hub
Azure IoTHub MQTTs messaging
It supports HTTP, MQTT(over TLS or WebSocket), or AMQPS
MQTT over SAS_TOKEN or X509
1
2
3
4
5
6
7
8
9
10
11
Connection String:
HostName=AsavieIoT-20180403.azure-devices.net;DeviceId=myFirstJavaDevice;SharedAccessKey=BxFIalpPxn8FDaHCQ98MMQ==
SAS Request: (all generated from iot hub)
- Hostname
- DeviceId
- DeviceKey
X509 Request: (Harder to import into IoT Hub)
- Hostname
- Certificate
- PrivateKey
This one works!!!
Consuming the EventHub
The Event Hub-compatible endpoint for reading messages always uses the
AMQPprotocol.
1
2
3
4
- Event Hub name:
iothub-ehub-asavieiot-410371-ecd916cc4a
- Event Hub endpoint:
Endpoint=sb://ihsuprodamres070dednamespace.servicebus.windows.net/;SharedAccessKeyName=iothubowner;SharedAccessKey=e9k/U58zQ4sssu+btAxjvD1OEwhWKfqgrQ1VfOiPILY=
Azure IoTHub MQTT PUB/SUB End-to-End
- Azure IoTHub v.s. EventHub
- Azure IoTHub: ServiceBusQueue vs EventHub vs EventGrid
- Azure IoTHub MQTT communication way
### Azure SDK limitations
- Device-to-Cloud
- Cloud-to-Device ### How to make possible Device-to-Device?
- Solution 1: MQTT Broker in-between - Mosiquitto with Azure IoT
- Solution 2: Service with AMQP Device-to-Device
- Azure IoTHub Service SDK ### Direct mqtt connection
- Direct connection
- Some tips online
Azure Event Hub feature
Never miss a story from us, subscribe to our newsletter