I. What are BLE, LoRa Private Protocols, and the LoRaWAN Standard Protocol?

Bluetooth Low Energy (BLE)

Bluetooth Low Energy (BLE) is a mainstream short-range communication solution in the consumer electronics and smart hardware sectors, ideal for indoor, short-range human-machine interaction. Since smartphones come with native Bluetooth support, devices can connect directly to mobile apps without the need for intermediate equipment like gateways or servers. The physical layer supports a maximum transmission rate of 2 Mbps, OTA firmware upgrades, and high-frequency waveform acquisition; customizable connection intervals allow for millisecond-level real-time response.

Bluetooth operates in the 2.4 GHz frequency band; signals suffer significant attenuation when passing through walls or the human body, limiting reliable communication range to just 10–30 meters (or a maximum of 100 meters in open environments). Bluetooth Mesh networking has limitations: as the number of nodes increases, channel congestion and latency rise, making it unsuitable for high-density, large-scale sensor networks. Ebyte’s E104 series Bluetooth modules are optimized for low power consumption, achieving microampere-level standby current, making them ideal for small, battery-powered smart terminals.

LoRa Private Protocols

LoRa private protocols are custom transparent transmission solutions based on the LoRa physical layer. Unconstrained by standardized protocol stacks, they offer flexible deployment and simple development. They are frequently used in lightweight IoT scenarios such as industrial monitoring, enclosed factory sites, and long-range data transmission in the field.

Leveraging LoRa spread-spectrum technology, these protocols achieve receiver sensitivity of up to -148 dBm. Combined with Sub-GHz low-frequency bands, they offer strong obstacle penetration and diffraction capabilities, mitigating signal issues caused by architectural obstructions or “dead zones” in factory areas. They utilize serial transparent transmission, eliminating the need to port complex protocol stacks; simple configuration enables wireless transparent transmission over several kilometers, thereby shortening project development cycles.

This solution cannot communicate directly with mobile devices like smartphones and requires a gateway for protocol conversion. Lacking a standardized MAC layer scheduling mechanism, simultaneous communication by a large number of nodes can easily lead to channel conflicts; developers must design their own anti-collision mechanisms, making this approach unsuitable for ultra-large-scale scenarios involving simultaneous multi-node communication. Ebyte’s E22 series represents the corresponding hardware products. LoRaWAN Standard Protocol

LoRaWAN is a standardized MAC-layer networking architecture built upon the LoRa physical layer. It features unified communication rules, encryption mechanisms, and device management logic, making it suitable for large-scale, wide-coverage, and standardized IoT networking scenarios.

The protocol supports ADR (Adaptive Data Rate) and multi-channel parallel transmission, allowing a single gateway to support thousands of simultaneously connected end-devices. It mandates AES-128 encryption, complies with international standards, and integrates with various third-party IoT cloud platforms. Ebyte’s E77 series features a built-in, full protocol stack; when paired with E8xx series gateways, it enables the rapid deployment of large-scale monitoring networks for campuses or cities.

Its drawbacks include a high development barrier, strict requirements for protocol stack logic and timing, and lengthy deployment and debugging cycles. In the mainstream Class-A mode, gateways cannot actively issue commands; instead, they rely on the end-device’s uplink window to complete downlink communication, resulting in latency on the order of seconds—making it unsuitable for real-time device control.

II. Core Characteristics of the Three Communication Solutions

1. Communication Range: BLE effective range is within 100 meters; LoRa private transparent transmission can reach 3–10 km; LoRaWAN standard protocol can reach 3–5 km.

2. Operating Frequency Band: BLE uses 2.4 GHz; both LoRa private transparent transmission and LoRaWAN use Sub-GHz bands.

3. Real-time Performance: BLE operates at the millisecond level with excellent real-time performance; LoRa private transparent transmission operates at the second level with good real-time performance; LoRaWAN has average real-time performance, as it is influenced by heartbeat cycles.

4. Connectivity: BLE supports direct connection to smartphones without a gateway; neither LoRa private protocols nor LoRaWAN support direct smartphone connections, requiring a gateway for relay.

5. Network Scale: BLE has limited networking capacity, and Mesh networks are prone to congestion with many nodes; LoRa private protocols lack MAC scheduling, making them prone to collisions when many nodes transmit concurrently; LoRaWAN supports thousands of end-devices per gateway, making it suitable for massive device connectivity.

6. Development Difficulty: BLE is easy to deploy; LoRa private protocols offer simple and flexible development; LoRaWAN protocols are complex, presenting a high barrier to entry for development and debugging. 7. Security Capabilities: The LoRaWAN protocol mandates AES-128 encryption; in contrast, BLE and proprietary LoRa protocols do not define a unified, mandatory encryption standard.

III. Application Scenarios for the Three Communication Solutions

Bluetooth Low Energy (BLE) Application Scenarios

Suitable for projects requiring short-range human-machine interaction, direct smartphone control, low latency, and medium-to-high speed data transmission.

Typical applications: Smart locks, portable testing instruments, indoor lighting control, and other short-range devices.

Proprietary LoRa Protocol Application Scenarios

Suitable for projects involving a limited number of nodes that prioritize long-range transmission and rapid development/deployment, such as data transparent transmission within enclosed industrial sites or in the field.

Typical applications: Field monitoring and remote sensor data backhaul from industrial sites.

LoRaWAN Standard Protocol Application Scenarios

Suitable for large-scale IoT projects requiring massive concurrent device access, wide-area coverage, unified cloud-based management, and standardized communication security.

Typical applications: Smart city monitoring, comprehensive smart meter reading, and asset tracking.

Note: Selecting a wireless IoT solution essentially involves balancing transmission bandwidth, device power consumption, and communication range; the choice must account for both physical performance limits and architectural constraints.

IV. Ebyte Product Recommendations

Based on the technical characteristics of BLE, proprietary LoRa transparent transmission, and LoRaWAN standard protocols, as well as specific application requirements and Ebyte product compatibility, we offer modules tailored for short-range interaction, long-range transparent transmission, and large-scale wide-area networking. Specific product recommendations are as follows:

E104 Series: Features a high-performance BLE chip operating in the 2.4GHz band with an effective communication range of 10–30 meters. It supports 2Mbps high-speed transmission, millisecond-level low latency, firmware OTA upgrades, and ultra-low power consumption (microampere level), enabling direct smartphone connectivity without a gateway. Suitable for short-range human-machine interaction scenarios such as smart locks, portable testing instruments, and indoor lighting control. E22‑170M22S: Utilizes mature LoRa spread-spectrum technology and operates in the Sub‑GHz band. It offers a transmit power of 22–30 dBm and a maximum communication range of 3–10 km. Featuring transparent serial data transmission, it eliminates the need for complex protocol stacks, ensuring simple development and flexible deployment. It supports point-to-point and point-to-multipoint long-range transparent transmission without requiring a gateway, making it ideal for low-cost, long-range applications with limited nodes, such as field monitoring and remote sensor data backhaul in industrial facilities.

E77 Series: Powered by the STM32WLE5 RF SoC, this series natively supports the LoRaWAN standard protocol and covers mainstream IoT frequency bands (400 MHz/433 MHz/915 MHz) with a communication range of 3–6.5 km. It supports ADR (Adaptive Data Rate) and AES‑128 encryption, allows for massive concurrent terminal access via a single gateway, and integrates seamlessly with cloud-based management and data analytics. It is the preferred choice for large-scale wide-area networking projects, such as smart city monitoring, comprehensive smart metering, and equipment/asset tracking.

Nine o’clock on a Monday in the back office of an independent shop, and three windows are open on the laptop. One is the till system’s weekly sales export. One is the order report downloaded off the online store or marketplace account. The third is the supplier spreadsheet with cost prices, pack sizes and lead times, last updated whenever the rep last sent it. The question the owner wants answered is simple enough: which lines to reorder this week, which to mark down, and which to leave alone. Getting that answer out of the three windows is where the morning goes.

Each system was bought for a specific job and does it well. None was designed to agree with the others.

Three numbers that only make sense together

Sell-through is the share of the stock you brought in that has sold over a given period. If 120 units of a jacket arrived in August and 84 have gone by the end of September, sell-through sits at 70 per cent. On its own that looks healthy. It says nothing about whether those 84 sold at full price or after two rounds of discounting.

Margin after returns and discounts fills that in. Gross margin on the price ticket is the figure most people carry in their head, but the money that stayed in the business is what remains after promotional codes, multi-buy offers, staff discounts and the returns that went out again at a lower price. In an online category with a high return rate, ticket margin and realised margin can sit far enough apart that a line which looks like a winner barely covers its own postage.

Weeks of cover is the third. Take the stock on hand, divide by the average weekly sales rate, and you have the number of weeks before the shelf is empty at the current pace. Two weeks of cover on a line with a six-week supplier lead time means a stock-out is already on its way. Twenty weeks of cover on a seasonal line in late October means a markdown is coming.

Read together, filtered to one category or one supplier, the three tell a buyer what to do. Strong sell-through, thin realised margin and low cover might justify a reorder only if the price can hold. Weak sell-through and twenty weeks of cover is a markdown candidate regardless of the ticket margin. Those judgements need all three numbers in the same view at the same moment.

Why they live in three different systems

The till knows what sold in store and, often, what stock it believes is on the shop floor. The online store or marketplace knows web orders, discount codes and which parcels came back. The supplier sheet knows cost prices and lead times. Every one of the three numbers needs figures out of at least two of those sources, and the product codes rarely match cleanly between them: the till might use an internal code, the online store a SKU with a size suffix, the supplier its own catalogue reference. Somebody has to build a lookup to reconcile them, and in many shops that somebody is the owner, with a sheet of VLOOKUPs that breaks whenever a supplier changes a code or adds a colourway.

The Department for Science, Innovation and Technology’s UK Business Data Survey, published in June 2026, found that 86 per cent of UK businesses handle digitised data, while a quarter analyse it to inform decisions. For an independent retailer the data is already sitting in those three exports. The work is in joining it.

Spreadsheets handle the first version of this well. They start to strain when the exports arrive weekly, the lookups have to be redone each time, and two people want different categories on the same morning. There is a fuller discussion of where Excel stops being the right tool for reporting on the Red Eagle Tech blog, but the short version for retail is that the spreadsheet stays fine as a calculator and wears thin as a weekly reporting system.

What joining them in Power BI looks like

Power BI is Microsoft’s reporting tool, and the free Desktop version covers most of what a small retailer needs. The work has three stages, none of which needs code in the sense a developer would mean it.

The first stage is bringing the files in. Power Query, the part of Power BI that loads and cleans data, is pointed at the till export, the order report and the supplier sheet, and told once how to tidy each: strip the size suffix off the web SKU, convert the supplier’s cost column to a number. Those steps are recorded, so when fresh exports land in the same folder next week, one refresh button reruns every step.

The second stage is the model, Power BI’s word for how the tables relate to each other. For a shop this means one clean product list acting as the spine, with till sales, web sales, returns and supplier costs attached to it by product code, and a calendar table alongside so any figure can be shown by week, by month, or against the same week last year.

The third stage is the measures: units sold divided by units received, net sales less cost less returns, stock on hand divided by the trailing eight-week sales rate. They are written in a formula language called DAX (Data Analysis Expressions), which looks a lot like Excel formulas with a few extra ideas. Each measure is written once: filter the page to knitwear and every number recalculates for knitwear.

The result is a single page: a table of product lines with sell-through, realised margin and weeks of cover beside each other, and a slicer at the top for category, supplier and channel. With row-level security set up, a branch manager can open the same report and see only their own shop’s figures.

Why learning it in-house pays back for a small retailer

The case for the owner or buyer learning the tool themselves, rather than having the page built and handed over, rests on something specific to retail: the questions change every week. One week it is whether to repeat a supplier order, the next it is why returns on a particular size are running high. Someone who built the model can add it in an afternoon. Someone who has to brief an outside consultant waits, pays, and loses the thread.

There is also the matter of knowing the data. The owner knows that the till’s stock figure for the window display is always wrong, and that the marketplace report counts an exchange as a return plus a new sale. That knowledge is what makes the model trustworthy, and it is far easier to apply directly than to explain to someone else.

Training is the piece that makes this possible. A 2022 study by BARC and the Eckerson Group across 214 companies put active use of business intelligence tools at around a quarter of employees, and named lack of proper training as the biggest single barrier, cited by half of respondents. The tool sits on the laptop; the skill to use it is what has to be acquired.

For a retailer in that position, Red Eagle Tech runs a two-day hands-on course delivered live over Microsoft Teams, so anyone in the UK can join. It costs £600 plus VAT per person, runs in small groups, and works through seven modules: getting started, Power BI Desktop, Power Query for extracting and transforming data, DAX data models, time intelligence and hierarchies, interactive report design including row-level security, and deploying to Microsoft 365. The trainer has led Power BI training across a FTSE 100 company. Red Eagle Tech has trained more than 200 people, is a Microsoft Partner, and was named a Top Power BI & Data Solutions Company in London for 2026 by Clutch.

Where to start this week

Pick one category, ideally one with a reorder decision due. Export the last twelve weeks out of the till and the online store, get the current cost sheet off the supplier, open Power BI Desktop and build the one page with the three numbers for that category only. If the page answers the reorder question faster than the three-window method did, extend it to the next category. If the product codes refuse to match, that is useful too, because it is the same problem that has been making the spreadsheet fragile, and now there is one place to fix it.

The kitchen floor is still dusty when the robot returns to its base. Yesterday it seemed to manage the usual clean; today you are wondering whether a Roomba battery replacement will put things right. Before ordering, separate the interrupted cleaning job from its possible causes. A robot vacuum battery is a component to identify, not a diagnosis you can make from unfinished work alone.

Begin with what changed. A useful purchase decision connects the robot’s identity, the charging behaviour and the proposed replacement part, while keeping any unresolved fault visible rather than expecting a new battery to cure it. You do not need to become a repair technician. You do need a clear answer about what you are buying.

Describe the cleaning problem before naming a faulty part

Write down the symptom in ordinary language. Did the robot stop during cleaning, fail to begin, report a charging problem or return to its base earlier than you expected? Those are different observations. Keep the exact wording of any message rather than translating it immediately into “dead battery”.

Compare familiar work. If the room, schedule or cleaning assignment has changed, describe that change alongside the symptom so that a support adviser can distinguish a new demand from a change in the robot’s behaviour under its previous routine. Avoid inventing a demanding endurance test. The everyday task is the useful reference.

A hypothetical robot that repeatedly leaves the same job unfinished deserves investigation, but that observation does not establish which part to replace. Save the history. It will be more useful to the repairer than a guess repeated with increasing confidence.

Find the exact robot model before searching for batteries

iRobot’s official battery catalogue separates batteries for e, i and selected j families from a product for Combo j9+/j7+ and selected j9 robots, and from a separate s9 product. The catalogue does not present a universal Roomba battery. Its compatibility descriptions make the exact robot identifier part of the purchase decision.

Start with the device information available through the manufacturer’s normal identification instructions. Record the full identifier, including its suffix, and compare it with the proposed product’s supported-model list. Do not shorten the name because the first part looks familiar. Differences that seem minor in a search result can be the very details the listing uses to distinguish products.

Where it stops: the official catalogue tells you about the official products it describes. It does not automatically validate a similarly named third-party replacement.

Keep charging dock symptoms separate from battery wear

What happens at the charging dock? Record the indication shown when the robot is normally positioned there and whether the device reports a charging error. Use the model’s support instructions for any routine check. Do not improvise contact adjustments, electrical tests or charging arrangements.

A useful service enquiry describes the sequence: the robot approached the dock, displayed a particular message and then did or did not begin its usual charging behaviour. That gives support something to investigate without claiming that the dock, battery or another component has already been ruled out.

Stay within the boundary of the evidence. A charging complaint that has not been resolved is a poor foundation for a speculative battery purchase, even when a replacement is readily available and the computer-generated product suggestions look convincing. Ask for the next model-specific check instead of buying both components on a hunch.

Use the battery label as a matching reference

The part reference matters. Ask the manufacturer or a qualified repairer how to identify the fitted battery through the service information appropriate to your robot. This article is not a removal guide. If identification requires work you are not equipped or instructed to perform, hand that step to qualified service.

Keep the robot identifier and the battery part reference together. Then ask whether the proposed pack matches the required dimensions, electrical specification and battery connector, rather than relying on a photograph that shows only the outer casing. A matching silhouette leaves those questions unanswered.

Do not accept modification as the missing link. A suggestion to alter a connector, adapt the voltage or make the pack fit changes the job from selecting a supported replacement into an unverified repair. Stop the purchase and seek proper guidance if that is the proposed solution.

What a seller’s capacity figure can and cannot tell you

As a seller catalogue example, Replacement Battery Mall lists a Roomba ABL-D2 battery at 14.4V and 32Wh. Those are details of that listing. They do not establish compatibility with every Roomba, independent safety certification or approval from iRobot.

Read the figures alongside the exact supported part and device information. A capacity label does not answer whether this robot vacuum battery belongs in your machine, and it does not promise that the robot will complete a particular room or cleaning schedule. Ask the fit question first.

Compare like with like. When the seller proposes an alternative part, request an explanation tied to your exact robot rather than treating a larger capacity claim as an automatic improvement; if that explanation is missing, the apparent upgrade is still an unresolved compatibility question. Keep the response with the proposed listing.

Ask for confirmation that survives the checkout page

Write a short enquiry containing the full robot identifier, the confirmed battery reference and the symptom being addressed. Ask the seller to confirm the proposed part and to identify any detail still needed. A vague answer that repeats the product category is not a completed match.

When comparing Replacement Battery Mall Roomba battery options, save the listing and the written compatibility response before ordering. Product descriptions are seller claims. They do not become manufacturer authorisation simply because the listing contains a familiar brand or model name.

The order must stay specific. If a substitute is offered later, review that product against the same device and part information rather than assuming the previous answer carries over to a different battery. A household needs a working robot, not a parcel that merely resembles the item in the original search.

Decide whether the whole repair still makes sense

Consider a hypothetical robot that otherwise meets the household’s needs and has a service assessment pointing to its battery. A compatible replacement with a suitable installation route is a reasonable repair to price. Compare the complete job, including any required fitting and diagnosis, with the available alternatives.

Now change the situation. If the charging dock fault remains unresolved or the robot has other problems that already prevent useful cleaning, a battery-only quote does not describe the cost of restoring the machine to service. Keep those problems on the estimate. Do not hide them behind the cheapest visible part.

Ask what result the repairer expects. “Replace battery” describes work; “restore the normal cleaning assignment without the reported interruption” describes the purpose. The distinction helps you decide whether the proposal actually addresses the household’s complaint.

Keep a damaged pack out of the troubleshooting routine

Stop if the battery or device appears damaged, swollen or otherwise suspicious. Contact the manufacturer or qualified service rather than continuing to charge it to see whether the cleaning time improves. An unresolved safety concern ends the shopping comparison.

Do not squeeze a swollen casing, force a battery into position or experiment with a different charging arrangement. A seller’s compatibility answer is not a clearance to use a damaged pack, and a successful power-on does not establish that the device is safe.

Give service staff the observations already collected. They can then advise on assessment and handling without asking you to recreate the symptom through more charging or use. Follow their model-specific instructions. Battery modification and cell repair are outside an ordinary replacement purchase.

Keep a simple record of the decision and result

A short purchase note makes the next conversation easier. It also helps another person in the household understand why this part was selected rather than a visually similar alternative.

• Robot identity: the full model label or manufacturer-confirmed identifier.
• Battery identity: the confirmed part reference and proposed replacement.
• Docking symptom: the message or behaviour that support investigated.
• Confirmation needed: any unresolved fit or diagnosis question before ordering.
• Result: whether the normal cleaning task works after approved service.

Keep the repair outcome tied to the original complaint. If the interruption remains, return to support with this record instead of ordering another battery on the same uncertain assumption.