Dear flespi users, We've integrated the wirepas protocol. It connects Wirepas mesh network gateways to our platform over MQTT using the standard protobuf-encoded gateway-to-backend API published by Wirepas. https://flespi.com/protocols/wirepas
👍4

Channel
@flespi_news
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
194subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001101376777 |
|---|---|
| Type | Channel |
| Username | @flespi_news |
| Created | Between 1 February 2017 and 28 February 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/flespi_news |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 03:55 | 194 | -1 |
| 29 Aug 2026, 06:12 | 195 | +1 |
| 22 Aug 2026, 11:34 | 194 | +2 |
| 16 Aug 2026, 02:55 | 192 | +2 |
| 8 Aug 2026, 12:02 | 190 | no change |
| 7 Aug 2026, 21:09 | 190 | first reading |
20 posts held, back to 4 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
55 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 56.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 31 | 56.4% | |
| 👍 | 14 | 25.5% | |
| ❤ | 6 | 10.9% | |
| 🍾 | 3 | 5.45% | |
| 👏 | 1 | 1.82% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 18 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 55 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 May 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Dear flespi users, We've integrated the wirepas protocol. It connects Wirepas mesh network gateways to our platform over MQTT using the standard protobuf-encoded gateway-to-backend API published by Wirepas. https://flespi.com/protocols/wirepas
👍4
Every device starts long before it connects In our new article, we show how hardware manufacturers work with flespi engineers to launch products faster, validate firmware, and make sure new devices are ready from day one. https://flespi.com/blog/every-device-starts-long-before-it-connects
🔥1
⛈ July 2026 Changelog • 99.3847% monthly uptime • DDoS incident report and infrastructure hardening • Video telematics improvements • TrackBox: GPS tracking device emulator released • Multiple tachograph support updates • TachoBox is now open source • Changelogs now available via MQTT and REST API …new protocols and device types, and much more! Full recap: https://flespi.com/blog/july-2026-change-log
❤4
Dear flespi users, Now you can pull the synchronized telemetry vehicle data from Geotab platform using MyGeotab Data Feed API. Implementation updates will be posted here: https://forum.flespi.com/d/2124-changelog-geotab-feed-protocol
TachoBox is now open source 😎 A web viewer for tachograph files: driver card and vehicle unit, Gen1/Gen2, daily activity, violations, GNSS route, 14 languages. Built on the tacho-file-parse plugin (it reads the parsed JSON straight from the device media API). Forks and PRs welcome 😜 Demo: https://tachobox.flespi.io/#/?demo=1 Code: https://github.com/flespi-software/TachoBox
🔥7👏1
From BLE data to indoor positioning demo Mondays always need a little engineering inspiration. Looking for an idea? See how the Meitrack team put our AI Assistant to work to accelerate BLE implementation and build an indoor positioning demo for their customers. Read the full story: https://flespi.com/blog/from-ble-data-to-indoor-positioning-demo
👍1🔥1
How we took ourselves down We've just published the technical postmortem of the biggest outage in flespi history... It wasn't an easy story to tell, but we're sharing it because every hard lesson makes the platform stronger. Full recap: https://flespi.com/blog/how-we-took-ourselves-down
👍4
How to automatically create Teltonika devices with the correct device type One of the most common automation requests sounds simple until you try to implement it. Here's how we solved it. Step-by-step guide: https://flespi.com/blog/how-to-automatically-create-teltonika-devices-with-the-correct-device-type
👍2🔥1
Dear flespi users, Recently we’ve also integrated the a-telematics protocol which is designed to consume data from GPS tracking devices manufactured by A-Telematics headquartered in China. https://flespi.com/protocols/a-telematics
TrackBox: GPS tracking device emulator No GPS tracker on your desk? No problem. Our open-source GPS tracking device emulator lets you test the platform over Device REST, HTTP, and MQTT, with a step-by-step guide to get you started in minutes. https://flespi.com/blog/trackbox-gps-tracking-device-emulator
🔥3🍾1
☀️ June 2026 Changelog • Perfect 100% uptime • Tachograph functionality support in Assistant Telematics devices • Downloadable device-specific debug logs • Protocol development throughput doubled • New articles: AI in modern GPS hardware and the story behind flespi Full recap: https://flespi.com/blog/june-2026-change-log
🍾2🔥2
Dear flespi users, We’ve integrated the jmak protocol which is designed to consume data from GPS tracking devices manufactured by Jmak - a Brazilian company focused on developing high-quality IoT devices. https://flespi.com/protocols/jmak
❤2
Showing the 12 most recent of 20 posts we hold for @flespi_news. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 7 September 2026 — this entry's latest reading, not the date you are reading this.
“flespi news” (@flespi_news), 194 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/flespi_news.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.