Hello is the "old" API Version 2016-11-14 is still supported by IoT Hub ?
we are experiencing Timeout .
An IoT hub upgrade could impact the support of API version ?
you'll find the screenshot for the timout
https://i.stack.imgur.com/fmPe2.png
Related
Despite not tested or supported as mentioned here, can Azure IoT Python SDK be deployed on ESP32? Or I need to use MQTT Protocol directly to connect with Azure IoT Hub?
Currently we are evaluating Thingsboard CE. We have a requirement to connect a Teltonika device (GPS enabled devices) to connect to Thingsboard IoT platform and push the data to it.
Any ideas would be of great help.
We have installed Thingsboard CE on a server. We have created or added few devices and assigned them to few sample customers.
Basically we receive data from 'GPS' devices connected to waste collection vehicles like dumper/ tipper, with the help of a Java service which runs as a 'jar' file in the background.
Now we are stuck at a phase on how to use 'HTTP API' to push this data to Thingsboard platform.
Please Suggest us on how to proceed.
Thank you.
I am building an IoT solution based on devices that are not programmable (3rd party devices).
I can just configure the server they must connect to and I have the messaging (sending messages and receiving commands).
What is the best way to integrate them in an Azure IoT Solution (IoT Hub) ?
It looks like we can use Azure IoT Edge as Gateway (https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/iot-edge/iot-edge-as-gateway.md) in a "Identity translation" pattern, but I still not figure out how to do it.
I also find Azure IoT Protocol Gateway (https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-protocol-gateway) that seems to do the job but it is not sufficiently clear for me what to do.
Thanks in advance for your help.
The question is which protocols your devices support and how configurable your devices are. For instance you might be able to talk MQTT directly to the IoT Hub without using the SDK: https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support#using-the-mqtt-protocol-directly-as-a-device
Same is possible for HTTP using the REST API directly: https://learn.microsoft.com/en-us/rest/api/iothub/device
If neither is an option then yes, you need some kind of gateway - like in the examples which you linked.
I intend to use the IoT Hub to update firmware of my Edison device utilising its bi-directional capability although I am not sure of where to look for detailed instructions on how to do it. The only information I have found on the subject is HERE but doesn't go into detail on how exactly to do it, more a high level overview. Does anyone have any knowledge on how this is to be done or know any links that will help?
Thanks
The link you provided returns 404 for me right now; maybe that's temporary...
I work for Microsoft, on the Device Management SDK team for IoT Hub. The new Device Management capabilities we announced at Build last week should give you exactly what you need, but there isn't much info because the features aren't available to the public just yet.
For a preview, take a look at this video from Build where we demo'd firmware update on the Intel Edison. The device management segment starts at about 35 min, demo at 40 min.
To do firmware update using only what's available publicly today in IoT Hub, you'd probably start by sending a cloud-to-device message to your Edison. Of course, exactly how you go about downloading and updating the firmware after that is specific to your device and scenario.
Here is the link to the repo which allows you to update firmware remotely using the IoT Hub. Thanks MS!
https://github.com/Azure/azure-iot-sdks/tree/dmpreview
I have done this when running Debian using gpsd. But when running Windows IoT preview...what is a way to get the NMEA sentences off an attached GPS (on the USB port). Is that kind of support around yet?
Currently this support is not yet available but it is being actively developed. Furthermore the Geolocator API is broken. Unfortunately I don't have an ETA for this but its coming.
Mark Radbourne (MSFT)