Community

Loading...

Azure Sphere

83 Ideas

Allow for transfering device ownership

As an OEM or someone creating an IoT solution that includes the device as a component of the product, I will need to setup up the device in order to test it and make sure that the overall product is working and performs to specifications prior to shipping it to distributor, SI, VAR, etc. These in turn will require the ability to themselves work with the device while integrating or configuring into a an aggregated product prior to being sold to another third party or end customer. A chain of custody is required so that each of these can work with the device in a secure way while the device is under their control, and then be able to transfer device ownership when sold.Please check what Intel is doing with Secure Device Onboarding (Intel SDO).

Support C#

Add support for connection over cellular network

Provide option to make network connection over cellular with external cellular modem chipset such as uBlox, Quectel, etc.,..

Add Mac Support

Support C++

Setup WiFi in field using WiFi access point instead of BLE

When we want to connect the sphere to a WiFi at customer location, have the sphere be put into a mode that it is an access point so that a phone can connect to it and then have the WiFi connection settings on the phone be sent to sphere. Much like the WEMO setup

Sphere must support GPIO driven interrupts

Polling for GPIO state is hugely power hungry. Interrupt support for GPIOs must be supported.

OpenSource the OS so we can help fix the API and build a community

There is currently no way to use this technology for anything professional / commercial, as we can not fix the multitude of missing things in the API by ourselves and the risk of this technology failing is huge.Even if you were to fix some of the shortcomings of the API, your team obviously is too small to add features in a timely manner to satisfy the needs of the community. Cause, basicly everyone of us has totally different needs.And then, if my team decides to use this tech as the base for our next IOT product, the product will instantly die if you ever pull support for the Azure Sphere tech. And for me, this is where things are currently headed.Reason being, there is no community around Azure Sphere, and it being closed source, there is a huge risk none will ever form.I understand you put 5 billion dollars into IOT, but how is it, that after a full year of Azure Sphere being out, we still dont have a complete GPIO API, can't read a DeviceID, can't get a Mac address of the device, the sample code is still in C, we don't have a proper filesystem access (no, MutableStorage dont cut it) and the rest of the things we see below.And then, what I really don't get:You are Microsoft, have with C# a programming language that pretty much tops all others in efficiency, and you decide to let us program in C for your new MCU? Why on earth?Give us choices. Give us a complete API with full access.Let us program apps for the MCU in C# or C++ and be able to fix the bugs in your OS in C and add the features we need.There is no way I can hang the fate of my new IOT product and maybe the whole company on the chance that you will not ***** up Azure Sphere and the remote chance that you implement all the API features I need (which I dont even know about yet myself).So please, go full OpenSource, and this thing will skyrocket.

api to call reset (from iothub directmethod)

Device update check happens every 24 hours or device reset. If we need to push hotfix, we can't wait for 24 hours and need a way to call reset from iothub (directmethod) to update devices as needed

API to get memory/CPU usage

We'd like to have some approach to get process memory usage and CPU usage. So we can measure app works correctly which include:1. No memory leak2. No exceed memory budget3. When something bad happens, we can detect it and either log a error event or try to recover.We tried traditional Linux ways like check /proc/self/status, or getrusage() or run ps, but none of them been supported with Azure Sphere.