Tag: dailyprompt-1838

Why Universities Need a Real IoT Lab, Not Just Another Embedded Lab

I still remember a meeting with a group of lecturers, where I asked a simple question.

“Why do we really need an IoT Lab in universities?”

I paused for a moment.
Because deep down, I already knew the answer.

Most universities already have something they proudly call an IoT lab. Rows of ESP32 boards. Arduino kits. LEDs are blinking happily. LCD screens displaying temperature values. Students smile because something lights up.

And yet, something feels incomplete.

This is not IoT. This is just the beginning.

This blog is not meant to criticise universities. I have spent years inside them. I was once a lecturer designing syllabuses, labs, and assessments. This comes from care. From concern. From watching students graduate with confidence in embedded programming but struggle the moment systems become real, connected, and dependent upon.

This reflection is based on a recent lecture I delivered on the need to establish a proper IoT Lab in universities, one that reflects how systems are actually built, deployed, and trusted today.

Embedded Systems Taught Us How to Build Devices

Let me be very clear.

Embedded systems are important. They are foundational.

Students need to learn how to program microcontrollers. They need to understand sensors, actuators, interrupts, memory, and power consumption. All of that matters.

An embedded system is usually a standalone device. It senses something. It controls something. It logs data into local storage.

There is nothing wrong with that.

In fact, embedded systems are still used today in places with no connectivity. Remote areas. Harsh environments. Offline conditions.

But here is the problem.

Once the data is captured, someone has to physically go to the site, connect a laptop, download the data, return with it, and process it manually.

I have seen this happen too many times.

Two technicians. One vehicle. Hours of work. Just to retrieve data that could have been transmitted automatically.

I always ask myself… why are we still doing this in 2026?

Connectivity Changes Everything

The moment a device is connected to the internet, everything changes.

Data no longer waits for humans to come and collect it.
It flows.
It moves.
It becomes alive.

This is the moment embedded systems evolve into the Internet of Things.

Now we can monitor systems remotely.
Now we can detect failures early.
Now we can see battery levels dropping before devices die silently.
Now we can act before complaints arrive.

And yet, most university labs stop just before this moment.

Students are taught how to blink LEDs, but not how to send data reliably.
They learn how to display values, but not how to secure data in transit.
They build devices, but not systems.

And systems are what the real world depends on.

A Real IoT Lab Must Teach Technology Layers

IoT is not a single skill. It is a stack.

In my lecture, I stressed that a proper IoT Lab must expose students to multiple technology layers, not in theory, but through hands-on work.

Layer 1: Hardware and Firmware

This is where universities are already strong.

Sensors. Controllers. Actuators. Firmware logic. Power management.

Students should continue learning this well.

But they must also understand that this is just one layer.

Layer 2: Connectivity and Protocols

This is where gaps start to appear.

Students must learn how data travels.

Wi-Fi. Cellular. LPWAN.
Bluetooth. ZigBee. RFID.
MQTT. CoAP. REST. HTTP.
LoRa. NB-IoT. Sigfox.

Not as a list to memorise.
But as choices with consequences.

Which protocol suits low power?
Which network works for long range?
What happens when connectivity drops?

Without this understanding, troubleshooting becomes guesswork.

Layer 3: Platform and Middleware

This is the heart of IoT.

Devices do not talk directly to dashboards. They talk to platforms.

An IoT platform manages devices.
Authenticates them.
Stores data.
Provides APIs.
Handles scale.

This is where students should learn about device identities, data ingestion, databases, and analytics pipelines.

This is also where they start to understand why platforms like FAVORIOT exist in the first place.

Not to replace learning.
But to enable it.

Layer 4: Analytics and Visualisation

Dashboards are not the end goal.

They are the beginning of understanding.

Students should learn how data evolves from descriptive charts to deeper insights.
They should see patterns.
Spot anomalies.
Ask better questions.

This prepares them for real projects, not demos.

Security Must Exist Across All Layers

Security cannot be an afterthought.

Devices must be authenticated.
Data must be encrypted.
Platforms must be protected.
Applications must be hardened.

Most labs barely touch this.

And yet, this is where real systems fail.

When Systems Break, Knowledge Is Tested

I often tell students this.

The real test of IoT knowledge is not when everything works.

It is when something breaks.

Data stops arriving.
Dashboards go blank.
Alerts do not trigger.

At that moment, students panic if they only know how to code LEDs.

But students who understand layers start asking better questions.

Is it the device?
Is it the network?
Is it the platform?
Is it the visualisation?

This is the mindset a real IoT Lab must build.

Research, AI, and the Future of IoT Labs

Universities are not just about projects. They are about research.

To do meaningful research, students need data. Lots of it. Clean data. Continuous data.

IoT Labs enable this.

Once data flows reliably, students can apply machine learning.
They can explore pattern recognition.
They can experiment with predictive models.

Today, this also means understanding edge AI.

Inference running on devices.
Decisions made locally.
Latency reduced.
Systems are becoming smarter as they operate.

This is where IoT Labs naturally evolve into AIoT Labs.

And this is where universities must go.

This Is a Call to Universities, Lecturers, and Policymakers

If we want graduates who can build real systems, not just academic projects, we must change how we teach IoT.

IoT Labs must move beyond embedded programming.
They must teach architecture, trade-offs, and responsibility.
They must reflect how systems are deployed outside campus walls.

I believe universities can do this.
I believe lecturers want this.
I believe students deserve this.

But it requires intention.

It requires investment.
It requires collaboration with the industry.
It requires courage to redesign labs that have been unchanged for years.

If you are a lecturer, start asking what your lab is missing.
If you are a dean, ask whether your graduates can troubleshoot real systems.
If you are a policymaker, ask whether our talent pipeline matches national ambitions.

And if you are a student reading this, ask yourself one question.

Am I learning how to build a device… or how to build a system people can trust?

I would love to hear your thoughts, experiences, and struggles in building or teaching IoT.
Drop a comment. Let’s talk.

The Story Behind Favoriot – Part 8: The Frustration of Unanswered Emails and Missed Opportunities

The Early Days: A Heart Full of Hope

I still remember waking up every morning during the early days of building FAVORIOT with an excitement that felt like an adrenaline rush. It wasn’t just the buzz of starting something new; it was the vision, the dream that IoT could change industries and improve lives.

The endless possibilities of the Internet of Things filled my mind, painting vivid pictures of smart cities, connected devices, and seamless automation. It felt like we were on the brink of something extraordinary.

Every meeting felt like a golden ticket, an opportunity to make a mark. I would walk into rooms filled with potential customers and partners, armed with passion and an unwavering belief in FAVORIOT’s mission. I put my heart into every presentation, explaining how IoT wasn’t just a trend but the future.

I could see the spark in their eyes—that moment when the idea clicked, and they nodded enthusiastically. I left those meetings feeling optimistic, convinced that a follow-up email would soon seal the deal.

The Deafening Silence

But days turned into weeks, and weeks into months. Once a symbol of hopeful anticipation, my inbox became a source of growing frustration. I refreshed my emails obsessively, waiting for responses that never came.

“Why can’t they just say no?” I often muttered, pacing the floor of my office.

It seemed simple—a clear rejection would be better than this soul-crushing silence. At least I could move on, refocus my efforts, and seek new opportunities. But the uncertainty? That was the worst. It felt like being stuck in limbo, caught between hope and resignation.

I wasn’t idle, though. I sent follow-up emails, made calls, and tried every approach I knew to reignite interest. But more often than not, my efforts were met with the same cold silence. It was like shouting into an empty room, hoping for an echo that never came.

The Sting of Missed Opportunities

The worst part wasn’t the silence. It was discovered that the same people who had shown so much enthusiasm for FAVORIOT had moved on and partnered with someone else.

“How could they?” I’d mutter, shaking my head in disbelief. “We had something here. Why didn’t they give us a chance?”

It wasn’t just a professional setback; it felt personal. I had invested time and effort and pieces of my dreams and aspirations into those meetings. Every missed opportunity felt like a small crack in my entrepreneurial spirit.

Questioning Everything

There were days when self-doubt crept in like an unwelcome guest. I questioned everything:

  • Was it me?
  • Was it the product?
  • Did I say something wrong?

These thoughts gnawed at my confidence, making me second-guess every decision. It was tough, really tough. I felt like drowning in a sea of “what ifs” and “if only.”

A Turning Point: Seeking Advice

Amidst the frustration, I sought advice from other entrepreneurs who had faced similar situations. One conversation stands out. I was speaking with a seasoned business owner who had dealt with the same issues.

“Mazlan,” he said, looking me straight in the eye, “this is part of the process. Not everyone will have the courtesy to say no directly. It’s not about you or your product. Sometimes, they’re just not ready, or they’ve found something that fits their immediate needs better.”

His words were both comforting and sobering. It was a relief to know I wasn’t alone in this experience, but it also reinforced a harsh reality: the business world doesn’t owe you an explanation.

Lessons Learned: The Value of Rejection

Looking back, those early frustrations were necessary lessons in disguise. Each rejection, each unanswered email, taught me valuable lessons:

  1. Patience: Good things take time. Not every seed you plant will grow immediately.
  2. Perseverance: The road to success is paved with obstacles. What matters is how you manage them.
  3. Resilience: Don’t let rejection define you. Use it as motivation to improve and push forward.

Changing the Approach

Instead of waiting passively for responses, I became more proactive. During meetings, I started asking direct questions:

  • “What are your primary concerns?”
  • “How can we better meet your needs?”

This shift not only helped me gauge genuine interest but also provided valuable insights into potential customers’ minds.

I learned to read between the lines and to differentiate between polite nods and sincere enthusiasm.

Building Meaningful Relationships

With this new approach, I stopped chasing every opportunity and focused on building meaningful relationships with people who truly believed in our vision. These partnerships, though fewer, were far more impactful.

One particularly memorable project was with a city council on a smart city initiative. It was a long shot, but our persistence paid off. The project was a great success, serving as proof for many who had doubted us.

The Turning Point

That project was a turning point, not just for FAVORIOT but for me personally. It validated the sleepless nights, the endless follow-ups, and the resilience it took to get there.

It was a reminder that success isn’t always about winning every deal; sometimes, it’s about learning from the ones you lose.

Sharing the Lessons

Today, I often share these lessons with new entrepreneurs. I tell them:

  • “Don’t be afraid of rejection. Embrace it.”
  • “Don’t let silence discourage you. Use it as a time to reflect and improve.”
  • “Keep moving forward because the next opportunity is just around the corner.”

Gratitude for the Process

Reflecting on this experience, I realize that the early frustrations were not setbacks but stepping stones. They shaped me into the entrepreneur I am today. And for that, I am grateful.

The road ahead remains challenging, but with each step, I carry the lessons of the past. I approach new opportunities with careful optimism, knowing that even in silence, there’s growth.

This experience has made me stronger, more resilient, and more determined than ever to see FAVORIOT succeed.

In the end, every missed opportunity was just a lesson in disguise.

More Entrepreneurship Stories

  1. The Story Behind Favoriot – Part 8: The Frustration of Unanswered Emails and Missed Opportunities
  2. The Story Behind Favoriot – Part 7: The Task of Finding Favoriot’s First 10 Customers
  3. The Story Behind Favoriot – Part 6: Expanding The Business Models
  4. The Story Behind Favoriot – Part 5: Finding the Right Fit
  5. The Story Behind Favoriot – Part 4: How Favoriot Became More Than Just an IoT Platform
  6. The Story Behind Favoriot – Part 3: Why No One Wanted Our IoT Platform—And How We Turned It Around
  7. The Story Behind Favoriot – Part 2: Turning Failures into Milestones
  8. The Story Behind Favoriot – Part I: The Humble Beginnings of Favoriot
  9. Building My Personal Brand: The Stepping Stone to Favoriot’s Success
  10. From Research Lab Critiques to Startup Pitches: My Slide Story