An Edge Gateway lets you connect local IoT gateways to the Favoriot Platform Edge Gateway tutorial. It works as a bridge between on-site devices and Favoriot’s cloud services. Instead of every device speaking directly to Favoriot, the gateway collects and forwards data on their behalf. The platform then selects, stores and manages those data streams based on configured rules and mappings.
Why Use It
Most real-world IoT systems already have local gateways in place, such as LoRaWAN network servers, industrial PLC aggregators, or custom gateways handling many devices. Edge Gateway lets you bring those into Favoriot without rewriting firmware or replacing hardware.

How the Communication Flow Works
- Devices talk to the gateway
Local sensors and IoT nodes send data to a locally deployed gateway. - Gateway forwards to Favoriot
The gateway sends the data using either:- HTTP POST
- MQTT publish
These are standard internet protocols that Favoriot accepts.
- Favoriot receives and maps data
Within the platform, mapping rules determine which parts of the payload are stored or routed to device records, dashboards, or rules.
Steps to Create an Edge Gateway in Favoriot
1) Open the Edge Gateway Page
Inside the Favoriot dashboard, open the sidebar and click on Edge Gateway. This shows a list of any existing gateways you’ve registered.
2) Add a New Gateway
Tap the “plus” icon to start a new gateway entry.
A form appears where you give:
- Gateway name
- Description
- Location metadata (optional)
This identifies the gateway in your project.
Mapping Configuration — What It Is and Why It Matters

Once the gateway is created, you must add Mapping Settings.
This tells Favoriot how to interpret the incoming data. It allows you to:
Select Which Fields to Store
If the gateway sends a bulky JSON with many keys, you decide which data points matter for dashboards, rules, or analytics.
Rename Keys
If your gateway calls the temperature “temp_v1” but your platform device expects “temperature”, the mapping automatically translates it.
Link to Favoriot Devices
Instead of storing as generic data, you map incoming values to actual devices within Favoriot so they appear correctly in dashboards and analytics.
In short, you are shaping and normalising the raw payload from the gateway, so Favoriot knows:
- which device it belongs to
- What the values mean
- how they should be stored or used
Protocols for Sending Data
There are two main ways an edge gateway sends data to Favoriot:
HTTP
This uses RESTful web requests (POST) to send JSON to Favoriot’s cloud.
MQTT
The gateway publishes messages to a broker. Favoriot subscribes and receives them.
Both methods carry the same data; choosing one depends on your gateway’s capabilities.
Example Use Cases
Industrial Sites
Factories often have PLCs or protocol converters that collect machine status. Rather than rewrite firmware, the gateway forwards aggregated data cleanly to Favoriot for cloud analytics.
Smart Agriculture
Field sensors talk to a LoRaWAN gateway. The gateway batches and filters sensor data, then sends only meaningful values upstream.
Campus Environments
Sensors from multiple buildings connect to a central gateway. That gateway handles payload conversion and pushes to the platform.
Edge Gateway is especially valuable when:
- Devices cannot reach the internet directly
- Firewall or security rules block inbound cloud connections
- Large payloads must be filtered before cloud ingestion
- You want to maintain local control but still use cloud services for analysis and long-term storage
(No device firmware rewrite is needed)
Key Benefits of Using Edge Gateway
Modular Integration
You can integrate gateways that speak different protocols while still using a single centralised platform.
Payload Control
Not every value needs to go into the cloud. You decide what matters.
Clear Device Association
Mapping ensures data is stored under the right device identity.
Scales with Your Deployment
Whether you have a handful of field gateways or hundreds of sites, the system stays organised and manageable.

FAVORIOT Resources
- General
- Pricing
- How to Choose the Right Favoriot Plan for Your IoT Project
- Favoriot Ecosystem Plan
- Why Universities Need an IoT Ecosystem, Not Fragmented IoT Accounts
- When IoT Builders Outgrow Dashboards: Why the Favoriot Platform Developer Plan Exists
- Favoriot Launches Lite Plan to Support Students, Beginners, and Early IoT Builders
- Faybee AI – IoT Copilot
- Favoriot Intelligence
- Favoriot Insight Framework
- What is Favoriot Insight Framework (FIF)?
- Favoriot Machine Learning
- Why Favoriot’s ML Infrastructure Reduces Costs
- Why Favoriot’s Built-in Machine Learning Matters for AI Researchers and IoT Developers
- Favoriot’s Rule Engine 2.0: A Structured Approach to IoT Automation
- The Key Differences: Favoriot’s Rule Engine 2.0 and AI Agents
- IoT & AIoT Labs
- Trainings
- Favoriot Partner Network
- Videos (Playlist & Highlights)
- How-To Use Favoriot Platform Playlist
- Favoriot IoT World Playlist
- IoT Deep Dive Playlist
- Favoriot Sembang Santai Playlist
- IoT Deep Dive – Episode 7 (FAVORIOT Insight Framework)
- IoT Deep Dive – Episode 4 (Favoriot Partner Network Solves IoT Fragmentation)
- IoT Deep Dive – Episode 5 (Building IoT Solutions With Favoriot Middleware)
- Favoriot IoT World – Episode 3 (Unboxing the AIoT Lab)
- Favoriot IoT World – Episode 6 (Favoriot AIoT Architecture – Data to Decision)
- Favoriot IoT World – Episode 4 (Favoriot’s IoT Pricing)
- FULL FAVORIOT RESOURCES
- Others





![[Project Challenge #15] Smart Shopping Behaviour Analytics Using the Favoriot Insight Framework (FIF)](https://iotworld.co/wp-content/uploads/2026/03/Project-Challenge-15-Decoding-Precinct-Shopping-Movement-Patterns.png)
Leave a Reply