All Posts

One of the most uncomfortable moments in building real-world IoT systems is the moment you realize that the sensor is not wrong. It’s just no longer telling the truth you expected. At first, everything looks fine. The numbers line up with the datasheet. Lab tests pass. Early deployments look stable. Dashboards feel reassuring. Stakeholders gain confidence. The product moves forward. And then, slowly, something begins to shift. The values don’t jump. They drift. They don’t fai

There is a number that appears in almost every IoT conversation sooner or later. “Two years on a coin cell.” “Five years on AA batteries.” “Ten years with one battery replacement.” The number is usually spoken with confidence. It looks clean in a presentation. It feels reassuring. And in many cases, it is quietly wrong. At EurthTech, we’ve learned to be cautious whenever battery life is expressed as a single number. Not because engineers are careless, but because battery life

Gateways rarely get much attention when an IoT system is first imagined. They appear in architecture diagrams as simple boxes in the middle. They are described as bridges, pipes, pass-throughs. Something that connects devices to the cloud and then politely steps out of the way. At EurthTech, we’ve learned that this mental model works only until the first real deployment begins. After that, gateways stop being infrastructure and start behaving like characters in the story. In

There is a noticeable shift in tone when an IoT product moves from general experimentation into a regulated or high-trust environment, and it is rarely announced explicitly, but you can feel it in the questions that start getting asked. Until that point, conversations revolve around functionality, performance, cost, and timelines, with an implicit assumption that anything can be fixed later as long as the core idea works. Once regulation enters the picture, that assumption qu

Developing embedded systems requires a structured approach to transform complex ideas into reliable, secure, and future-ready products. Each phase in the development lifecycle plays a critical role in ensuring the final system meets stringent performance and security standards. I will walk you through the essential phases of embedded systems development, highlighting practical steps and technical considerations that drive success in this demanding field. Understanding the Pha

There is a moment in most IoT projects when a decision feels small enough to be harmless. Which MCU to use! Which sensor variant to pick! Which regulator looks “good enough.” Which module is easily available right now! These choices are often made early, when timelines are tight, suppliers are pushing availability, and the pressure is to get something working. At that stage, hardware decisions feel reversible. After all, it’s just a component. You can always change it later.

The first time an IoT proof-of-concept works, it creates a very specific kind of confidence. It’s not excitement, exactly. It’s quieter and more dangerous than that. It’s the confidence that comes from watching data appear on a dashboard and thinking, without quite saying it out loud, that the hard part is over. At EurthTech, we’ve learned to treat that moment carefully. Not because proof-of-concepts are meaningless — they aren’t — but because they answer a much smaller quest

Published By Srihari M, Director Product Development at EurthTech For a long time, cloud-first thinking felt like progress. Centralize logic, centralize data, centralize control. Push everything upward, analyze everything later, and let elastic infrastructure handle complexity. In software-only systems, this worldview worked remarkably well, and it shaped an entire generation of engineering decisions that assumed connectivity was stable, latency was acceptable, and failure wa

Published By Srihari M, Director Product Development at EurthTech There is a particular kind of fatigue that appears in engineering teams long after a product has shipped, long after the excitement of early deployments has faded, and long after the original architects have moved on to new problems. It is not the fatigue of overwork or technical difficulty, but the fatigue of dealing with systems that resist understanding. At EurthTech, we’ve come to recognize this fatigue as

A EurthTech Deep Technical Narrative Every IoT engineer eventually faces a strange moment — one that is never mentioned in textbooks, rarely discussed in architecture diagrams, and almost never spoken about in marketing material. It happens when a device and the cloud both believe they are right…and they disagree. At first, this feels absurd.How can a tiny device mounted on a pipe or ceiling disagree with a cloud running Kubernetes clusters, Postgres, EMQX brokers, and Lambd

A EurthTech Deep Technical Narrative Every IoT device lies eventually. Not intentionally. Not maliciously. But slowly, quietly, subtly — often without realising it. A temperature sensor drifts by half a degree after a year of heat cycles. A battery voltage reading becomes erratic as internal resistance increases with age. A vibration sensor starts coupling to the enclosure, distorting its frequency content. A radio module begins retrying transmissions, burning more power than

In the evolving landscape of IoT and embedded systems, data collection has become a cornerstone for innovation and operational efficiency. However, the methods used to gather this data must be both effective and ethical. As companies develop complex IoT solutions, understanding ethical data collection methods is crucial to ensure compliance, build trust, and deliver secure, future-ready products. This article explores the principles, techniques, and best practices for ethical

In the evolving landscape of technology, companies developing complex IoT and embedded systems must prioritize data privacy. Indian firms face unique regulatory requirements and operational challenges when drafting privacy policies. These documents are not mere formalities; they are critical legal instruments that protect user data, ensure compliance, and build trust. I will guide you through the essential steps and considerations for crafting a privacy policy tailored to Ind

A EurthTech Deep Technical Narrative There comes a point in every IoT project when you realise something quietly profound:your system is no longer just sending data. It is thinking . Not thinking the way humans do, but thinking in the way ecosystems do — through patterns, corrections, repetitions, rewards, failures, and tiny adjustments spread across thousands of devices. This is the moment when your IoT system stops behaving like a pipelineand starts behaving like a feedback

A EurthTech Deep Technical Narrative There’s a moment in every serious  IoT product engineering  journey when you finally understand the difference between  “works”  and  “survives.” A prototype works.A lab test works.A demo works.A pilot works. But a real deployment — one that lives on rooftops, inside factories, in basements, in remote villages, in sub-zero chillers, and in hot, dust-filled enclosures — doesn’t simply need to work. It needs to  survive . Survival is an enti

In today’s fast-paced technological landscape, businesses are constantly seeking innovative solutions to enhance their products and services. One key area that significantly impacts success is  custom electronics manufacturing , especially for companies building  smart infrastructure solutions ,  Industrial IoT and automation platforms , and connected products. By investing in tailored electronics manufacturing, organizations can deliver scalable, reliable, and high-quality

A EurthTech Deep Technical Narrative There is a strange silence that falls over IoT systems after the first year. The excitement of deployment fades. The dashboards that once fascinated everyone become routine. The firmware that seemed groundbreaking becomes “the old build.” The cloud pipeline that once felt modern is now just another service. The devices that engineers watched like newborn infants now sit quietly in their installations — ceilings, rooftops, factory walls, pu

A EurthTech Deep Technical Narrative There’s a dramatic shift that happens in IoT when you cross a certain threshold.At 10 devices, everything feels easy.At 100 devices, you feel confident. At 500 devices, you feel in control. But at 5,000 devices… you begin feeling nervous. And at 50,000 devices? The system stops feeling like “your system.” It starts feeling like a city  you accidentally built. Nothing — truly nothing — will expose the character of your architecture more b

A EurthTech Deep Technical Perspective If you’ve ever tried running AI on a microcontroller, you probably remember two contrasting moments. The first moment is magical — the instant you see your tiny model running on a bare-metal MCU, making sense of a sensor stream. It feels like science fiction. A kilobyte-sized network doing real work, right at the edge. And the second moment happens soon after — when the magic suddenly collapses under noise, jitter, power fluctuations, ra

When you first encounter LoRaWAN, it feels almost magical. You place a tiny device in your hand, powered maybe by a coin cell, and it whispers a few bytes across a vast distance — sometimes kilometres — landing neatly in a gateway as if by telepathy. For someone who grew up in the world of Wi-Fi and 4G, the idea that a packet can travel so far with so little energy almost feels wrong. But the magic ends very quickly when you connect a real sensor to that device. Because senso