cause an electronic device to become unable to function, typically on a permanent basis.
“installing an unofficial OS voids the warranty and may brick the phone”
When we first set out to design the Helium IoT platform, we knew we had to make it easy to connect off-the-shelf hardware to a wireless layer and aggregate that data in an easy to access timeseries database. But our aspirations didn’t end there.
Over the course of building Helium, we’ve done a lot of investigation around how to structure our APIs and make them useful for developers in the context of the Internet of Things. In thinking through the various use cases of our platform (including hardware) and speaking to customers, it became apparent that tying location data back to sensors comes up often with a certain class of customers. So we made the Helium API extremely flexible such that it can accommodate location data like GPS coordinates. Not only is it built to store data from Helium-powered sensors, but it can ingest and expose virtually any JSON timeseries data. Recently, a customer of ours built an application that made great use of the the Helium API and location data so we wanted to share one aspect of their application design.
AstraZeneca is a global biopharmaceutical powerhouse. They invest early and often in technology and systems that help them bring better product to market faster. So it’s no surprise they are industry leaders when using IoT and sensing in their facilities. To that end, led by Marc Harrigan, the Office of the CTO has been building a proof of concept with Helium to deploy temperature and other sensing to critical production assets like lab refrigerators, freezers, and incubators. Using the entire Platform - Helium-powered sensors, Element Access Points, the Helium API, and the Helium Dashboard - AstraZeneca can retrofit existing infrastructure with lightweight sensing to get immediate visibility into asset status and health.
Whether building an IoT prototype or scaling out an entire commercial product, Helium provides the tools for you to to quickly develop and prove the value of your Internet of Things sensing applications.
Professional IoT developers as well as makers aspiring to release commercial product face a dilemma presented by the market today: the vast majority of development hardware is so far away from being put in users’ hands that it requires a full manufacturing turn before it is customer ready.
In today’s world of IoT buzzwords, hardware, software and Platform As A Service, it’s logical to assume that all of the pieces needed to create a connected device and use its data already exist in the wild. There are many individual components of IoT in existence, ranging from wireless parts, quick-turn hardware partners to cloud-hosted databases and data analytics systems.
Last Friday and Saturday (October 21st and 22nd, 2016), a massive Distributed Denial of Service (DDoS) attack was launched against large parts of the Internet’s Domain Name Service (DNS) infrastructure. The sheer scale of this attack led to widespread slowdowns and outages to large parts of the Internet until it was mitigated.
In a vast world of wireless technology, developers building connected products face a difficult choice when selecting a wireless layer for their applications. How do you choose which technology will highlight your product and give you robust connectivity in an unpredictable physical environment? And at what price point? This blog post highlights the Helium team’s thought process and criteria in selecting a wireless implementation with our primary user, the Internet of Things developer, in mind.
The Helium API offers a comprehensive set of options to fetch time-series data from your sensors.
Helium is a sensing platform that makes it simple to gather data and develop insights about your organization’s physical assets and environment. We offer a rich set of HTTP endpoints to make it easy for developers to manage and create solutions based on their installed Helium Smart Sensors.