An investigation into the technical limitations, deployment challenges, and missing solutions holding back the next generation of intelligent connected devices.
Artificial intelligence is moving beyond computers, smartphones and cloud platforms. It is increasingly becoming part of machines, vehicles, industrial equipment, sensors, robots and everyday connected devices.
This transformation is often described through two closely related technologies: Artificial Intelligence of Things (AIoT) and Edge AI.
The idea is straightforward: connect intelligent algorithms to physical devices, process information closer to where it is generated, and enable systems to make decisions without depending entirely on remote cloud infrastructure.
But there is a considerable difference between demonstrating an AI model in a laboratory and making it work reliably in the real world.
Behind the impressive demonstrations, companies and engineers are still dealing with problems that are expensive, complicated and, in some cases, far from being adequately solved.
Some devices cannot run models efficiently. Some AI systems become unreliable after deployment. Industrial machines cannot communicate with modern platforms. Sensors gradually lose accuracy, while companies struggle to determine whether an unexpected measurement represents a genuine problem or simply a defective sensor.
These are not minor technical inconveniences. They are obstacles preventing businesses from adopting AIoT at scale.
After examining technical publications, academic research, industry reports and discussions from engineering communities, several recurring problems stand out.
The interesting part is that many of these challenges are not caused by a lack of artificial intelligence. They are caused by everything surrounding it.
1. The hardware fragmentation problem: Why can’t an AI model run everywhere?
One of the biggest obstacles in Edge AI is hardware fragmentation.
An AI model developed on a powerful computer does not automatically work efficiently on an embedded device.
A model might run perfectly on an NVIDIA GPU but perform poorly on an ARM processor, an ESP32, a dedicated NPU or another embedded platform.
The problem becomes more complicated when developers start adapting models to different hardware architectures.
Each platform has its own limitations, supported operators, memory architecture, acceleration libraries, compilers and deployment requirements.
Even when a model can technically be converted, its performance may change considerably.
Developers frequently have to deal with:
Model conversion between TensorFlow, PyTorch, ONNX and other formats.
Quantization and compression.
Unsupported operations.
RAM and Flash limitations.
Hardware-specific acceleration.
Different inference runtimes.
Performance and accuracy trade-offs.
A particularly revealing discussion appeared in the Google AI Edge developer community. A developer reported that a model worked correctly on a local machine but experienced performance problems when deployed to an Edge device. The discussion highlighted conversion formats, hardware compatibility, inference delegates and optimization parameters as potential sources of difficulty.
Google AI Edge developer discussion
A separate discussion in r/embedded described an engineer spending more time fighting the model conversion pipeline than actually developing the application. Quantization also reduced accuracy enough to make a simpler threshold-based algorithm more reliable.
Reddit: Did TinyML actually help your project?
What is still missing?
A genuinely reliable engineering environment that accepts an AI model, understands the target hardware, automatically evaluates compatibility, optimizes its architecture and produces a tested deployment package.
Existing frameworks address parts of this problem, but developers still need considerable technical knowledge to combine them successfully.
Who is affected?
Embedded engineers, semiconductor manufacturers, robotics companies, IoT developers and businesses building Edge AI products.
2. AI models that become unreliable after deployment
An AI model can achieve excellent accuracy during development and still become unreliable after being installed in a real environment.
Consider a machine-learning system designed to detect abnormal vibrations in industrial equipment.
During development, it is trained using data collected under specific conditions.
After deployment, the machine operates at different temperatures, processes different materials, experiences different loads and operates under different environmental conditions.
The incoming data gradually changes.
This phenomenon is commonly known as data drift or concept drift.
The difficulty is that many deployed systems continue making predictions without knowing whether their predictions are still trustworthy.
The consequences can include:
Missed equipment failures.
Incorrect maintenance recommendations.
Increasing false alarms.
Decreasing detection accuracy.
Unnecessary production interruptions.
An especially interesting research direction concerns the difference between detecting an anomaly and explaining its physical cause.
A system might report unusual vibration measurements, but the operator still needs to determine whether the cause is a bearing problem, misalignment, sensor degradation or a change in operating conditions.
A 2026 systematic review of 48 studies on industrial IoT anomaly detection highlights model degradation under changing conditions and the limitations of current explainability approaches. It argues for more useful diagnostic explanations that connect anomalies to operational causes.
2026 systematic review: Industrial IoT anomaly detection
What is still missing?
A complete monitoring system that continuously evaluates the reliability of deployed AI models, detects changing conditions, identifies potential causes and recommends appropriate corrective action.
Model monitoring exists, but dependable end-to-end monitoring across heterogeneous, resource-constrained devices remains challenging.
3. Predictive maintenance without sufficient historical data
Predictive maintenance is one of the most attractive applications of AIoT.
The objective is to identify potential equipment failures before they happen.
However, there is a fundamental problem: machine-learning systems generally need useful data to learn meaningful patterns.
What happens when a factory purchases a new machine?
There may be no historical failures, no labeled defect examples and no established baseline describing abnormal behavior.
The same issue affects smaller companies that have never implemented digital monitoring systems.
Their maintenance information may consist of handwritten records, occasional measurements and technicians’ personal experience.
Even when sensors are installed, collecting enough useful data to train a reliable model can take considerable time.
There are additional challenges:
Failures are relatively rare.
Different machines behave differently.
Operating conditions change.
Fault labels are expensive to obtain.
Models trained on one machine may not generalize to another.
This is particularly relevant in Morocco.
A study published in 2023, based on 115 Moroccan companies, found that only 33% of the surveyed companies had implemented predictive maintenance. The research identified organizational barriers, financial constraints and data protection concerns among the principal obstacles.
Research: Predictive maintenance in Moroccan SMEs
What is still missing?
An affordable predictive maintenance solution that can establish useful machine baselines with minimal historical data, adapt to different machines and improve its predictions as more information becomes available.
The opportunity is not simply to create another predictive maintenance dashboard. It is to make predictive maintenance practical for companies that cannot afford extensive data collection and specialized AI engineering.
4. Connecting old industrial machines to modern AI systems
Many factories operate equipment that was installed years or even decades ago.
These machines may still perform their functions perfectly well, but their communication capabilities are often incompatible with modern digital platforms.
Some use Modbus RTU over RS485. Others rely on proprietary communication protocols, older industrial networks or interfaces that were never designed for cloud connectivity.
Modern AI platforms, on the other hand, generally expect structured and accessible data through technologies such as MQTT, OPC UA and APIs.
Connecting these environments is rarely as simple as installing a gateway.
Engineers must understand the machine’s communication protocol, identify relevant registers, interpret the measurements, establish reliable connectivity and ensure that the resulting data makes sense.
For example, receiving the value 125 from a PLC is not particularly useful without knowing:
Which machine generated it?
What does the register represent?
Is the measurement expressed in degrees, amperes or another unit?
Is the value current?
Is the machine operating normally?
What does this measurement mean in the production process?
The problem becomes more complicated when a factory operates equipment from multiple manufacturers.
What is still missing?
An affordable universal industrial integration solution capable of discovering equipment, connecting different communication interfaces, interpreting machine data and producing standardized information ready for analytics and AI applications.
Existing industrial gateways and integration platforms address important parts of this problem. However, installation and configuration still frequently require specialized engineering work.
5. Sensors cannot always tell us when they are becoming unreliable
IoT systems depend on sensors to understand the physical world.
Temperature, pressure, vibration, humidity, current, voltage and other measurements are used to make decisions about equipment and processes.
But sensors are not perfect.
Over time, their measurements can become inaccurate because of aging, environmental exposure, mechanical stress, contamination or changes in calibration.
A particularly dangerous situation occurs when a sensor continues transmitting values that appear perfectly reasonable but are actually incorrect.
For example, an industrial temperature sensor might continuously report 65°C even though the actual temperature has increased considerably.
The monitoring system may interpret this as normal operation.
This creates a difficult distinction between two situations:
The machine is behaving abnormally.
The sensor measuring the machine is behaving abnormally.
Many monitoring systems are primarily designed around the first situation.
Research published in the IEEE Internet of Things Journal in January 2026 examined drift correction and uncertainty-driven calibration scheduling, demonstrating that sensor accuracy over long deployments remains an active engineering problem.
IEEE: Drift Correction and Calibration Scheduling for IoT
What is still missing?
An intelligent sensor-health monitoring layer that identifies gradual measurement drift, detects suspicious behavior, compares measurements across independent sensors and recommends recalibration or replacement.
The opportunity becomes particularly interesting in large installations where manually inspecting every sensor is expensive.
6. Too many false alarms are destroying confidence in industrial AI
Imagine an industrial monitoring system that generates 100 alerts every day.
The maintenance team investigates them, but most are harmless variations in machine behavior.
Eventually, operators begin ignoring notifications.
Unfortunately, important warnings can then be overlooked.
This is one of the practical problems associated with industrial anomaly detection.
Industrial environments are not static.
A machine might operate at different speeds, process different products or switch between production modes.
A measurement that is abnormal during one operating condition may be perfectly normal during another.
Traditional anomaly detection systems can struggle to distinguish these situations.
The problem is not simply detecting unusual measurements. It is understanding their context.
Recent research presented at the 2026 IEEE Smart Internet of Things conference specifically examines unstable alert volumes and inconsistent anomaly thresholds across different production stages.
IEEE: Segment-Aware Risk Calibration for Stable Alerting in Industrial IoT
What is still missing?
An intelligent alerting system that understands machine operating states, production stages and historical behavior, and can prioritize alerts according to their actual operational significance.
The ultimate goal should be fewer irrelevant notifications and more actionable information.
7. IoT devices are difficult to maintain after they leave the factory
Developing an IoT device is only the beginning.
Once thousands of devices are installed in different locations, manufacturers must maintain their firmware, security, connectivity and operational performance.
Consider a company selling connected monitoring devices.
Some devices may be installed in factories, others in warehouses and others in remote locations.
They may use different hardware revisions and firmware versions.
When a security vulnerability is discovered or a software improvement becomes available, the manufacturer needs to distribute an update safely.
But what happens if the device loses power during the update?
What happens if the new firmware is incompatible with a particular hardware revision?
What happens when the device cannot reconnect after restarting?
This is why secure over-the-air updates, staged deployment, rollback mechanisms and device monitoring are essential.
An important 2026 USENIX Security study, based on interviews with 30 IoT vendors and a survey of more than 100 practitioners, examined why companies struggle to maintain OTA updates.
Its findings are particularly revealing: the problem is not exclusively technical. Fragmented responsibilities across supply chains, economic constraints and mismatched hardware and software lifecycles also prevent long-term security maintenance.
Subscribe to the Medium newsletter
USENIX Security 2026: Security in the Air
What is still missing?
Affordable and sustainable device lifecycle management that combines firmware updates, compatibility checks, health monitoring, security maintenance and recovery across heterogeneous IoT products.
The industry already has OTA platforms. The remaining challenge is making long-term maintenance economically viable and dependable for manufacturers of different sizes.
8. Energy consumption: Running AI on small devices is not always practical
Edge AI promises faster processing, reduced cloud dependency and improved privacy.
However, local intelligence requires computational resources.
Running an AI model involves memory operations, processing and sometimes continuous sensor acquisition.
Wireless communication introduces another energy cost.
For battery-powered devices, these requirements can become a serious limitation.
Consider a remote agricultural monitoring device.
It needs to collect sensor measurements, process the data, determine whether an abnormal condition exists and communicate important information.
If it performs these operations too frequently, its battery may not last as long as expected.
If it spends too much time sleeping, it may miss important events.
If it transmits every measurement, it wastes energy and communication bandwidth.
There is no universally optimal configuration because the answer depends on the application, hardware, battery capacity, connectivity and environmental conditions.
What is still missing?
A unified energy-management solution that intelligently coordinates sensing, local AI inference, wireless communication and sleep scheduling.
Such a system should determine when processing is necessary, what information needs to be transmitted and when local computation is more efficient than communication.
9. Industrial wireless connectivity remains unpredictable
Industrial wireless communication is becoming increasingly important.
Wireless sensors, autonomous robots, connected equipment and mobile monitoring systems depend on reliable communication.
But industrial environments create difficult radio conditions.
Metal structures, moving equipment, electromagnetic interference and complex physical layouts can significantly affect signal propagation.
A wireless network that performs well during initial testing may behave differently once production begins.
The consequences depend on the application.
For a simple temperature-monitoring system, a delayed measurement may be acceptable.
For industrial control or coordinated robotics, unpredictable latency and packet loss may be much more serious.
Different applications also have different requirements for reliability, synchronization and response time.
What is still missing?
A practical industrial wireless intelligence system that continuously evaluates communication quality, detects interference, identifies weak coverage areas and recommends or implements appropriate network configurations.
This is an active area of research and industrial development rather than a problem without existing solutions. The remaining challenge is dependable operation across diverse environments and applications.
10. AIoT interoperability: Devices collect data, but systems still struggle to understand each other
This problem connects many of the previous challenges.
A modern industrial environment can contain PLCs, sensors, RFID readers, cameras, gateways, cloud platforms and AI applications.
Each component may work correctly on its own.
But connecting everything into one coherent system is considerably more difficult.
Different manufacturers use different data formats, naming conventions, communication protocols and information models.
Even when devices communicate successfully, the receiving platform may not understand the meaning of their measurements.
The problem is sometimes described as semantic interoperability.
For example, two systems may both report a value called temperature, but one represents the temperature of a motor winding while the other represents the surrounding environment.
Without the correct context, combining their information can produce misleading conclusions.
The International Telecommunication Union addressed this broader challenge in its June 2026 Recommendation ITU-T Y.4618, which defines an AIoT reference model spanning devices, edge infrastructure and cloud systems.
It specifically addresses interoperability, data management, security, model lifecycle management and operational requirements.
ITU-T Y.4618: AIoT Reference Model and Requirements
What is still missing?
A practical integration layer capable of discovering devices, interpreting their data, managing identities and creating a consistent representation of physical equipment across different platforms.
The challenge is not the absence of communication protocols. It is making different systems exchange information that has the same meaning.
11. Security: Protecting an intelligent device throughout its entire lifetime
Traditional IoT security already involves several difficult areas, including device authentication, encryption, secure boot, firmware integrity and network protection.
Adding artificial intelligence introduces additional concerns.
AIoT systems must protect not only the physical device and its communications but also the models and data used to make decisions.
Potential threats include:
Manipulation of sensor inputs.
Compromised firmware.
Model theft.
Model poisoning.
Unauthorized access to edge devices.
Insecure communication between devices, edge servers and cloud platforms.
Attacks against AI inference pipelines.
The International Telecommunication Union published a December 2025 technical report specifically examining security threats affecting AIoT devices.
ITU: Security Threat Analysis for AIoT on Devices
The bigger problem is that security is often treated as an installation requirement rather than a continuous responsibility.
A device can be secure when manufactured and become vulnerable several years later.
What is still missing?
An affordable end-to-end security lifecycle solution that combines device identity, secure provisioning, firmware verification, model integrity and continuous security monitoring.
12. A particularly important question: Why are these problems still difficult to solve?
After examining these challenges, an interesting pattern emerges.
Many of the problems are connected.
A predictive maintenance application may fail because the sensor measurements are unreliable.
The sensors may be reliable, but the industrial gateway may interpret their data incorrectly.
The gateway may work correctly, but the AI model may not generalize to the actual machine.
The model may be accurate, but the device may not have enough memory to execute it efficiently.
Even if everything works, maintaining the system across hundreds of installations may become too expensive.
This suggests that the AIoT industry does not simply need better algorithms.
It needs better engineering infrastructure.
The following areas deserve particular attention:
Engineering layerPersistent challengeHardwareResource limitations and platform fragmentationSensorsDrift, calibration and measurement reliabilityCommunicationConnectivity, latency and interoperabilityDataInconsistent formats and missing contextAI modelsGeneralization, drift and explainabilityDeploymentConversion, optimization and compatibilityOperationsMonitoring, maintenance and updatesSecurityLong-term device and model protection
The important point is that these layers cannot always be developed independently.
A failure at one level can compromise the entire application.
13. The situation in Morocco: An opportunity that deserves more attention
The challenges described above are global, but they have particular commercial importance in developing industrial markets.
Morocco has an expanding industrial ecosystem, including automotive manufacturing, aerospace, textiles, agriculture, logistics and energy.
However, adopting sophisticated digital technologies is not equally easy for every company.
Research published in 2026 on Morocco’s digital supply-chain transformation examined 300 sources, 903 Moroccan startups and an exploratory field investigation.
It identified several barriers affecting the adoption of integrated Industry 4.0 technologies, particularly among SMEs:
Limited financial resources.
Shortages of specialized technical skills.
Uneven digital readiness.
Fragmented data systems.
Security and connectivity challenges.
Difficulties scaling pilot projects.
Morocco’s Digital Supply-Chain Transformation, 2026
Another study examining 39 companies across 15 industrial zones in Casablanca found that 69.2% identified cost reduction as the strongest driver for energy-efficiency improvements. Financial constraints and competing investment priorities remained significant barriers.
Industrial Energy Efficiency in Morocco, 2025
This points toward a particularly interesting market opportunity.
Many businesses do not necessarily need sophisticated autonomous factories.
They need affordable systems that can monitor existing machines, reduce downtime, track production, improve energy efficiency and provide useful operational information.
Solutions that retrofit existing equipment rather than require expensive replacements may have a meaningful advantage.
14. Where are the real business opportunities?
The problems above suggest several product categories worth investigating.
Rather than developing another general-purpose AI chatbot or monitoring dashboard, the following areas address specific engineering difficulties.
1
. Universal Edge AI Deployment Platform
A development environment that automatically evaluates AI model compatibility, optimizes performance and generates deployment packages for different embedded hardware platforms.
- Intelligent Industrial Gateway
A modular hardware and software gateway that connects legacy PLCs, sensors and industrial equipment to modern AIoT platforms.
- Predictive Maintenance for Data-Scarce Environments
An affordable system that learns normal machine behavior without requiring years of historical failure data.
- Sensor Health Intelligence
A platform that identifies sensor drift, measurement errors and calibration problems before they compromise industrial decisions.
- Edge AI Monitoring and Diagnostics
A system that continuously evaluates deployed AI models, monitors performance and identifies changes in operating conditions.
- IoT Device Lifecycle Management
A platform that handles firmware updates, compatibility verification, device health, security and recovery across different hardware products.
- Industrial Data Normalization Platform
An integration layer that transforms heterogeneous machine and sensor measurements into structured, contextualized data that different AI applications can understand.
These are not completely unexplored markets. Existing companies already offer products in several of these categories.
The opportunity lies in addressing the limitations of existing products, reducing implementation complexity and serving customers who cannot justify expensive enterprise solutions.
15. Final thoughts: The next major AIoT opportunity may not be another AI model
There is enormous attention around increasingly powerful AI models, new processors and advanced hardware accelerators.
But the real-world adoption of AIoT depends on something less glamorous: making everything work together.
A company does not care how impressive a model looks in a demonstration if it cannot run reliably on its equipment.
An engineer does not want to spend weeks resolving conversion problems before testing an application.
A factory manager does not need hundreds of notifications that cannot be translated into useful decisions.
And a manufacturer cannot build a sustainable connected-device business if maintaining its installed products becomes more expensive than the products themselves.
These are the problems that deserve more attention.
The most interesting opportunities may emerge from combining embedded electronics, industrial automation, sensor intelligence, Edge AI and practical software engineering.
The next generation of AIoT products will not be defined only by how intelligent their algorithms are, but by how reliably they operate in the physical world.
That is where the industry still has considerable work to do.
Selected research and discussion sources
- ITU-T Y.4618 (2026) — AIoT Reference Model and Requirements
- USENIX Security 2026 — Security in the Air
- IEEE — Drift Correction and Calibration Scheduling for IoT (2026)
- IEEE — Systematic Review of TinyML Applications and Deployment Challenges (2025)
- Industrial IoT Anomaly Detection and Explainability Review (2026)
- Google AI Edge Developer Community — Deployment Discussion
- Reddit — Did TinyML Actually Help Your Project?
- ITU — AIoT Device Security Threat Analysis (2025)
Research note: This article synthesizes publicly accessible publications, research and selected developer discussions available as of November 3, 2026. It is not an exhaustive review of every internet source. The problems described are not necessarily without existing solutions; the focus is on areas where current solutions remain incomplete, difficult to deploy, insufficiently general or economically inaccessible.
