Artwork for podcast The Business of LoRaWAN
Water Meter Monitoring & End To End Solutions - Michail Angelov
Episode 18 • 27th May 2025 • The Business of LoRaWAN • MeteoScientific
00:00:00 00:27:35

Share Episode

Shownotes

Michail Angelov, founder of IoTNet.eu and former Nokia IoT leader, talks about transforming water utilities through LoRaWAN-based remote water meter monitoring systems.

With over 20 years in telecom and IoT, Michail shares how he co-founded Nokia’s Worldwide IoT Network Grid before pivoting into one of the most pressing infrastructure challenges of our time: water loss. His company, IoTNet.eu, now oversees over 40,000 connected water meters across Bulgaria, gathering millions of data points each month to drive efficient water distribution.

He explains how low-power wide-area networks (LPWANs), and LoRaWAN in particular, disrupted the sector by enabling real-time, battery-efficient communication in locations without constant power—like underground water meters. By turning what used to be expensive, inflexible infrastructure into a scalable, data-driven system, Michail’s work is redefining the economics and capabilities of water meter monitoring.

Why water utilities lose up to 70% of water between source and tap—and how IoT helps measure and recover those losses

How LoRaWAN became the foundation for a scalable remote water meter monitoring system

Lessons from building a nationwide IoT network and pivoting from connectivity to full-stack solutions

The role of Helium in reducing infrastructure costs and expanding coverage

Using AI and structured data to predict pipe failures, detect theft (“non-technical losses”), and optimize performance

How local integrators anywhere in the world can partner to deploy IoTNet’s proven water meter monitoring system

This episode is packed with real-world insight into solving high-stakes utility problems with scalable IoT systems.

Links:

Michail Angelov - LinkedIn

  • Helium Global IoT Coverage - Want to know if Helium coverage exists where you need it? Check out this map!
  • Helium Foundation - The Helium Foundation's IoT Working Group (IOTWG) has generously provided support for the first 6 months of shows, please go check them out and consider using the Helium LoRaWAN as a primary or backup on your next deployment. With over a quarter million gateways deployed worldwide, it's likely that you have and can use Helium coverage.
  • Support The Show - If you'd like to support the MetSci Show financially, here's where you can donate on a one-time or an ongoing basis. Thank you!
  • MetSci Show - If you'd like to use our IoT or AI Data Value calculators, or you'd like to contact me, the MetSci Show site is the best way to do it.
  • MeteoScientific Console - Use LoRaWAN - The MeteoScientific Console allows you to use LoRaWAN today. As long as you have Helium coverage (and you probably do, about 90% of populated areas in the world have a gateway within 2 miles), you can onboard a sensor. You can always check coverage at https://explorer.helium.com and switch to the "IoT" tab in the top right.

Transcripts

Speaker:

Today's guest on

2

:

MeteoScientific's The Business of LoRaWAN

is Michail Angelov,

3

:

a seasoned telecom veteran

turned IoT entrepreneur who spent more

4

:

than two decades building networks, both

the technical kind and the business kind.

5

:

Michail began his career at Nokia,

where he spent 19 years helping shape

6

:

global telecom infrastructure

and co-founded the worldwide IoT

7

:

network Grid that many in the industry

8

:

recognize as one of Nokia's

boldest plays in IoT connectivity.

9

:

He holds multiple patents from his time

leading IoT

10

:

innovation and smart

lighting and connectivity platforms,

11

:

and has long been at the bleeding

edge of machine to machine communication.

12

:

What makes Michail especially relevant to

this audience

13

:

is his pivot from big telecom

to founding IoT network,

14

:

where he's solving very real,

very local problems, starting with water.

15

:

As he puts it after air water's

the next most essential thing.

16

:

And yet in many places, 40 to 70% of it

never makes it from the source to the tap.

17

:

That's a lot of loss.

18

:

Some from leaks,

some from theft, all from lack of data.

19

:

Michail's company now

manages over 40,000 connected water meters

20

:

across Bulgaria, using LoRaWAN to gather

millions of data points per month.

21

:

What began as a connectivity

play turned into a full stack

22

:

analytics business, driven by necessity

and the realization

23

:

that utilities didn't just want networks,

they wanted solutions.

24

:

In this episode, you'll hear

how IoT Net evolved, how they leveraged

25

:

the Helium network to scale

without overspending on infrastructure,

26

:

and how Michail sees the future of water

utilities not just as data

27

:

gatherers, but as AI powered systems

that can predict leaks,

28

:

prevent outages, and serve communities

more efficiently.

29

:

Let's dig in.

30

:

We are back with Michail from IoT network

31

:

EU and we've got a bunch of questions

for you about LoRaWAN, although it's

32

:

pretty interesting that you've been doing

this IoT thing for over 20 years.

33

:

So it's not like you just found this

and you're like, oh, I'll check this out.

34

:

Let's start with

when you're looking at IoT connectivity,

35

:

is there any kind of big problem

that you see out there that is unsolved,

36

:

or are all the problems

on the technical side for communications

37

:

more or less solved?

38

:

And now it's just implementation

and working the business side?

39

:

Yes. First,

thank you Nik for having me back

40

:

or let's say,

for having me in this context.

41

:

I do appreciate that

we're talking about tangible business

42

:

and things that everybody

can actually try and see with themselves.

43

:

And what brought me into the water

space is that water

44

:

is one of those funny things

that everybody needs to connect with.

45

:

I think without water,

you'd like quite soon, right after.

46

:

And I guess water is

the second most needed things.

47

:

Pretty important. Yeah.

48

:

Pretty important.

49

:

Also, water is nonrenewable.

50

:

This is funny, right?

51

:

So if you destroy a water supply

in an area, this is quite bad, right?

52

:

So what is actually quite an interesting

utility per se right.

53

:

You can probably generate

more electricity.

54

:

You know, you can probably add

you can clean it up a bit,

55

:

but the water disappears

from your environment.

56

:

It's difficult to bring it back.

57

:

And there have been some cases

in the world that even the rivers have.

58

:

The flow of the river has been turned

the other way around.

59

:

And this, of course, destroyed.

60

:

A lot of communities may be generated

in some other communities,

61

:

but in general, water is actually quite.

62

:

The interesting and exciting part

was that water

63

:

activities

were everything to do with flow.

64

:

It was the best use case

that they found for the low power.

65

:

Why that natural that I've been studying

probably for the last ten years now,

66

:

and why this was so?

67

:

Because this is actually one of the areas

which was probably most disrupted

68

:

by the proliferation

of the Internet of Things technologies,

69

:

because everything else

which has access to power,

70

:

all main type of power do you can

attach sensors and probably have access

71

:

to other type of connectivity technology

that uses the power.

72

:

And just to put it in context,

you could put the GSM model,

73

:

but just a model could use a lot of power.

74

:

So on the battery

it can survive limited time.

75

:

But the moment that you start to talk

about low power, wide area network,

76

:

then you can talk about use cases

that you don't have to visit

77

:

the device

to change the battery for five, ten years,

78

:

potentially even more

if you have photovoltaics.

79

:

And that's why the fluid management thing

to do with area

80

:

where you don't have electricity instance,

the power supply became possible.

81

:

And before that it was just not possible.

82

:

So that's why main water

meters, even water

83

:

meters, were never monitored centrally

because it was impossible to connect them.

84

:

You in a sustainable way,

meaning that you don't have to visit it

85

:

every year or every couple of months

because this is very expensive.

86

:

And the fact that you could connect

now, water meters and gas

87

:

and all kind of other central.

88

:

But let's stick to the water meter.

89

:

The fact you can connect

water meter with a sensor.

90

:

And this enables

stereotype collection of data from that.

91

:

The water meter in the sensors.

92

:

And then you can have

a sustainable use case

93

:

because it could always make

you have a service level agreement.

94

:

That means that this can last

for ten years on a traffic profile

95

:

that enables you to do audio use cases,

became a big enablement, and enabled means

96

:

that you could deliver a system,

you could actually maintain it,

97

:

and all the practice

would have that value.

98

:

So the utility would give you able access

the data.

99

:

The supplier or the system is regrettable.

100

:

However, actual business case

producers of devices could have a

101

:

reasonable profit margin.

102

:

So everybody along before the value chain

actually found the product market fit.

103

:

And this is what happened about ten

years ago with the mobile wider network.

104

:

So the first one that failed

miserably was Sigfox.

105

:

So it was not interested in that

because this was proprietary.

106

:

And then came LoRaWAN.

107

:

And the funny thing was that

108

:

it was even that open source

or basically open for everybody to use it.

109

:

Then regulators made the license available

and it just worked.

110

:

And that for me

was actually very exciting.

111

:

So that's why

112

:

I got started in the whole space and

how I started exploring all the options.

113

:

And ultimately that's

what the business is.

114

:

We can discuss in more detail

115

:

now, but I'll pause here because I was

just rambling from the first meeting.

116

:

Yeah. No, it's it's interesting.

117

:

And for folks that are listening,

you've got this background 19 years

118

:

at Nokia for Nokia, every reset Nokia.

119

:

And then you've invented a couple things

in the smart street lighting arena.

120

:

And then you running this business as IoT.

121

:

You all throughout Bulgaria,

not just Sofia

122

:

that is doing the smart water

metering piece.

123

:

So you've got this kind of business end,

you know, technician nerd background, so

124

:

you understand kind of how the things work

and then how the, the business works.

125

:

Yes. One of the big things with an IoT

businesses, it's a lot of us nerds

126

:

who are really excited

127

:

about getting something to work,

but not so good at getting the business.

128

:

Can you walk me through

how you get new business?

129

:

Do you?

130

:

I mean,

are you walking into City Hall and saying,

131

:

hey, I've got this cool water meter thing?

132

:

Is it all relationships with people

you already knew in Sofia

133

:

because you're Bulgarian?

134

:

Yeah.

One of the ways you get new business.

135

:

Yeah. Good point.

136

:

So actually, the journey of my journey

in the IoT in it,

137

:

of course, is a, it's a classical journey

of a startup, right.

138

:

You actually have an idea

139

:

and you start with something,

and then you get people to where you found

140

:

product market fit.

141

:

So the story of IoT, net was that

I knew that there is a market niche

142

:

that lies in the fact

that you can create a nationwide

143

:

communication network

dedicated to Internet of Things devices

144

:

without having the full cost burden

which traditional mobile networks get.

145

:

And that's the story of disruption,

because you could use unlicensed spectrum,

146

:

you could use very low cost equipment

147

:

because the equipment is small

and the spectrum is free.

148

:

You could use different type of permits

to be able to install the equipment,

149

:

and then you could have

150

:

a completely different cost base,

not like in telecom cost base,

151

:

but which is like enterprise

152

:

or almost like Wi-Fi type of cost base

to maintain the equipment.

153

:

And this got the stinking.

154

:

So together with the co-founder that

why don't we do this for the first time?

155

:

We actually do the whole central East

Europe

156

:

and establish

a nationwide network in Bulgaria.

157

:

And then we were thinking this wow, it's

so compelling,

158

:

the offer that the horse everybody

will buy, you know, connectivity from us.

159

:

You know, there's just no question there.

160

:

And of course, what happens

is that the one

161

:

market beats you, beat you to the punch.

162

:

Then you have to change your mind.

163

:

So everybody has a plan

until they punch in the face.

164

:

Quote from Mike Tyson. Right. So yeah.

165

:

Yeah, I mean we had a plan,

but then it didn't work out

166

:

because nobody was interested

to buy only the connectivity

167

:

even though they understood the value.

168

:

But enterprises, especially utilities

or any other that we talked about,

169

:

were not interested

to just buy connectivity and to do the

170

:

heavy integration themselves.

171

:

So actually up to a couple of the attempts

and basically more than a year

172

:

or so in just doing connectivity,

realize that this is not enough.

173

:

And we had to provide an end

to end solution business in segment

174

:

that there is a paying customer,

not just the hobby, because.

175

:

So in the IoT space, internet of things,

you can spend all your productive time

176

:

just doing proof of concept,

a paid, non-paid or hobby type of work.

177

:

And a lot of that

most of time has been finished there.

178

:

So we have to actually find something

that pays the bills and creates value.

179

:

And this is actually we people different

from just providing

180

:

connectivity, blanket

and waiting for customers to come.

181

:

Then we identify the tail.

182

:

Let's focus on this segment of the world,

the utility,

183

:

because that is a good fit of product

to the requirement.

184

:

And also there is

185

:

a good interruption in the status quo

that this is needed and this is required.

186

:

And we did a couple of tests

with last actually four months.

187

:

And then we found the fit

with the ecosystem,

188

:

with the actual suppliers

of the water meters, with the

189

:

integration part not associated

with the actual customers themselves.

190

:

And this is how we start the.

191

:

So from

just providing a lot of connectivity,

192

:

then we pivot to towards

providing end to end solutions

193

:

for the whole water utility sector

or just problems of the water beginning.

194

:

And I think that's something to remember

for everybody.

195

:

This is about IoT.

196

:

So don't just think about

the so-called technology.

197

:

Think about the product market fit.

198

:

So where this technology will fit

and find the paying customer

199

:

because otherwise it's not business,

you just hobby, which is still okay.

200

:

Right?

201

:

I mean, people like to do hobbies,

but this would not be a business.

202

:

Hobbies are fun. Yes. Okay.

203

:

So when you're at Nokia, you've co-founded

this worldwide IoT network grid.

204

:

So you had the experience of building

a connectivity network that was global.

205

:

But then when you get to

this one specific problem,

206

:

you realized

they're not going to use my connectivity.

207

:

They want.

208

:

The whole thing done for them

was there an initial like numbers pitch?

209

:

You know, if you put in this $300 water

meter sensor,

210

:

you're going to save $400

over the course of the next two years.

211

:

Or how did you

how did you present that piece of it?

212

:

Yeah.

213

:

So actually, the customer had a quite

good understanding why

214

:

they need to do it in Bulgaria,

like most of the places in the world,

215

:

typically the utilities

owned by the municipality.

216

:

So which is of course

a public entity in some places

217

:

it's public and private owned

because typically private entity

218

:

has more ambition to develop new services,

invest more.

219

:

While of course

municipalities have a certain restrictions

220

:

and what we did

to actually follow the requirements.

221

:

So in particular market that we work

in, the primary use case

222

:

was not for the consumer to water meters,

but for the so called main water meters.

223

:

So the water meters

connecting the main building or a major

224

:

production facilities

or major enterprise customers.

225

:

But imagine if you talk about

any kind of industrial complex,

226

:

or if you talk about a skyscraper

like in New York, or if you talk about

227

:

any type of condominium.

228

:

So you typically have a main water meter

in the basement

229

:

that connects the

water for the whole building.

230

:

And this is actually the one that

231

:

in this particular regulation

is owned by the water utility company.

232

:

And this is the one that they wanted

to have it remotely measured because

233

:

they see that some of those customers

have extra high consumption

234

:

or extra low

for the type of customer that they are.

235

:

I mean, it's quite unusual

if a big production facility

236

:

or a big block of flats

have a very low consumption, right?

237

:

Something is wrong.

238

:

That and the typical challenge

there is to identify

239

:

what are the areas

and what is the reason for that.

240

:

And most likely so number one

reason is a so-called non-technical loss.

241

:

Non-technical losses is a funny way to say

that, you know, a lot of us

242

:

in a lot of languages in the world,

and actually water

243

:

utility is one of those spaces

that when ordinary.

244

:

So when people think about it,

they never realize that in average, 40

245

:

to 70% of the water is actually lost

246

:

from the source, from the water reservoir

to the actual destination.

247

:

Or some markets can go down to 15%,

but 15 to 17 is typically what happens.

248

:

And this is not only tax, right.

249

:

This is of course

250

:

also somewhere leaking or or something

not being accounted for and so forth.

251

:

And of course, the easiest way to at least

understand it is to start measuring it.

252

:

Because once you start measuring it, then

253

:

it's quite clear that

why in a certain closed loop, you know,

254

:

a pot of water, that you have a main water

meter into all the seven meters.

255

:

I mean, this should match right?

256

:

If something doesn't match me,

that something is somewhere wrong.

257

:

And the value, of course, for the water

utilities, actually they don't care

258

:

because if the water is lost,

they're still going to give the bill

259

:

to the end consumer.

260

:

So I mean, what opportunities

like the bank, it never loses,

261

:

but what they still lose

is the extra power

262

:

needed to pump the water

or to distribute the water.

263

:

This is still an actual loss for them.

264

:

And that's the main business driver

in the water utilities space.

265

:

So basically they want to prevent

266

:

spending external money

for external services like power supply.

267

:

And they want to recover

some of that volume being shared among the

268

:

the pipeline. So downstream.

269

:

So basically what is the water going.

What is happening.

270

:

And of course along the way

there is all the other use cases that

271

:

if you have pumping stations,

you need to monitor the pressure

272

:

and the flow of the pumping station

need to be able to adjust it

273

:

so that it actually goes in certain

thresholds.

274

:

Right?

275

:

Because if it's above the threshold,

the pressure is too high,

276

:

so it may burst, the pipe is too loud

and there is not enough pressure.

277

:

So you have to manage that

278

:

of course, there is a lot of science

that not just art

279

:

and a lot of people actually,

which are much more details of how

280

:

this is managed and this is part

of whose cover system typically.

281

:

But this the disruption here

is that you can actually implement sensors

282

:

in places that previously were no sensors

or very expensive to put sensors.

283

:

And with that disruption, this is what

the low power why that actually hit.

284

:

And it became a quite

an interesting match.

285

:

You see now I use cases

286

:

and you guys started off by trying

to build or building your own network.

287

:

That wasn't something new to you.

288

:

You've been building networks

for your entire career.

289

:

And then you saw Helium and you said, oh,

maybe we can use this as well.

290

:

And if I'm reading it right,

291

:

you're actually using Helium across

most of the service area that you have.

292

:

I don't know if that's still true, but

can you walk me through that piece of it?

293

:

Yeah.

294

:

So at that time when we started,

of course, the idea

295

:

was to build our own network for cost

benefit and also to have the full control.

296

:

Sure.

297

:

And we did succeed.

298

:

I mean, again, we had to rehome network

a lot of, gateways where we had

299

:

customers.

300

:

And then at some point we start to see

at least

301

:

I started to see if there is a bit

too much noise in the network increasing.

302

:

So areas that were connected

303

:

before had trouble connecting,

especially during the joint procedure.

304

:

And this got me thinking

what the hell is happening?

305

:

And then we start to hearing from

some landlord, oh, you're here, mining.

306

:

I said, what the fuck are you doing?

307

:

Excuse my French

308

:

mining.

309

:

What?

310

:

And then,

I realized that I check that out

311

:

because I had some experience with it

mining myself.

312

:

Right.

313

:

Running some Gpio, ATX input, 2016,

you know, some other X5 80s.

314

:

Okay,

315

:

so at least I was familiar

316

:

with the concept,

but then they didn't know

317

:

that you could even use this concept for

wireless or like what is happening here.

318

:

And then I discovered the Helium network.

319

:

Like what the heck.

320

:

Yeah.

321

:

The idea I mean, I was really astonished

that you could build the biggest

322

:

at some point it reach 1 million nodes

type of a network around the world.

323

:

You could build this huge network

and you can provide the real service

324

:

without investing in infrastructure,

without investing in implementation

325

:

services,

without investing in maintenance services.

326

:

And you could still earn money

with every single installation.

327

:

This was like, wow,

328

:

what the fantastic business model

because it was tried before, right?

329

:

The things network was exactly like this.

330

:

It was a crowdsource

community network and yep, nothing, right?

331

:

It has been there for years.

332

:

It didn't go to any major development.

333

:

And here comes the new kid on the block

and out of nowhere, manages

334

:

to build the largest network

in a couple of years, even less.

335

:

And then at some point, they even destroy

the whole global supply chain.

336

:

The following up on gateways.

337

:

It is almost impossible to buy a gateway

because it.

338

:

Oh, this is not just

pumping Helium miners.

339

:

And it's like crazy.

340

:

I mean, really crazy.

341

:

But the good part of the craziness

is that when the network

342

:

was there and running,

especially now, I guess in Sofia,

343

:

we could have at some point

a couple of thousand gateways

344

:

active and you will get it

with like tens of thousands.

345

:

And if you have to think

346

:

that you have to invest, thousand euros

for an enterprise grade gateways,

347

:

and you get to put a couple hundred euros

for installation,

348

:

and you have to put a couple of hundred

per year for maintenance.

349

:

If you have to put ourself

this tens of thousands

350

:

of gate goes across, we will get a

this would have been cost prohibitive.

351

:

Right.

352

:

And to make it even sweeter,

I mean in the beginning

353

:

the cerium connectivity was very,

very cheap.

354

:

So very cheap mes didn't make any sense

from any kind of economics

355

:

point of view, because there is no way

how the connectivity

356

:

if you was paying the cost,

but still it was there.

357

:

And after some tests that we ran out,

we realized that,

358

:

wow, the places that we lack coverage,

359

:

we can actually migrate some of our device

to use Helium, then extending

360

:

or instead of trying to put ourself

coverage there and then we can use

361

:

Helium was a fantastic capacity question

and as a, as an extension of our coverage.

362

:

And this what we did.

363

:

So now actually using it

then it works quite well,

364

:

of course, with the caveat

that we need to build very strong

365

:

capabilities to move devices

between networks to make sure that,

366

:

if a single miner goes down or something

happens in the future,

367

:

we can still have a capability

to deliver services to our customers.

368

:

Got it. Okay.

369

:

And I know that's one of the big concerns.

370

:

This show,

of course, is sponsored by Helium,

371

:

although I wanted to make sure

it was a LoRaWAN first show.

372

:

But definitely

one of the concerns I hear about Helium is

373

:

how do I make sure the connectivity stays

374

:

where it is,

and that some homeowner doesn't

375

:

turn their gateway off

or move or whatever.

376

:

But it sounds like with the background

you've got on the telco

377

:

side, that's not a particularly difficult

problem for you to solve.

378

:

As far as like, all right, if the sensor

doesn't get Helium connectivity, cool.

379

:

I'll provide it some other way,

380

:

whether that's with another LoRaWAN or LTE

or how are you doing it now?

381

:

It's still a lot of fun.

382

:

So we still keep our own gateways running,

and we have a separate awareness

383

:

that we use for that.

384

:

Okay.

385

:

On the application server and devices

we take care of, switching

386

:

between the networks superseded.

One of them is not available.

387

:

Then I think that's probably

a good way to do it.

388

:

So yeah.

389

:

Yeah, I mean it's

fantastic to have the redundancy.

390

:

Okay.

391

:

And then what's you've built

that this network across Bulgaria

392

:

I don't think we've talked the numbers.

Is there a number of sensors.

393

:

I think you said you start off

with 30 gateways,

394

:

but certainly that's not enough

to cover the whole thing.

395

:

We have much more gateways ourselves.

396

:

So we have more than 200

fully operational.

397

:

We switch gateways when we have to switch.

398

:

And then how many water meters

is a couple thousand, right.

399

:

No, we have more than 40,000.

400

:

40,000 okay.

401

:

So it's a legit this is not like

a pilot project where like hey this works.

402

:

And I got five paying.

403

:

Yeah.

404

:

I mean

405

:

we became the first enterprise customer

for Helium in Europe with this network.

406

:

So I mean, it

probably shows the volume here.

407

:

And when you get to migrate

because they discontinued

408

:

doing this last year,

it was quite the painful exercise.

409

:

Yeah.

410

:

To make sure that all these centers

411

:

are migrated

without discontinuation of service.

412

:

So I mean, luckily it was possible

413

:

maybe not luckily, but good

that they designed it to be possible.

414

:

But this is a concern.

So I love the service.

415

:

I don't like

the uncertainty of the service.

416

:

I still believe this is a great way

417

:

to create networks

to use the, community capability.

418

:

Yes, in the interest of community

to maintaining to and to make this happen.

419

:

And I think, LoRaWAN is probably the best

420

:

technology to enable this to happen

globally because it is globally available.

421

:

Right?

422

:

So I do

I mean, I do want to encourage everybody

423

:

to keep the Helium IoT in mind

that up and running,

424

:

because it is creating real value

and it is helping solve real issues.

425

:

So please keep on running,

especially in Bulgaria.

426

:

Right?

427

:

Yeah. Well, I can especially. Yes, sir.

428

:

And then what's next for you in the

in the world of IoT and LoRaWAN,

429

:

are you going to go back

to these customers

430

:

you already have and say,

hey, let's put some more sensors in.

431

:

What do you see in the future of

of the IoT net company? Yes.

432

:

We want to continue to be the

the leader in the not just the automated

433

:

meter reading as it's called the EMR,

but also the analytics.

434

:

Because now in the age of AI,

435

:

you already have data for six years

and counting, right?

436

:

And you can imagine

437

:

this is a lot of contextual data that we

can already create value for our customer.

438

:

So actually that's why we are

439

:

thinking ourself as water analytics,

not just the EMR type of system.

440

:

Oh interesting. I want to make sure I we

we pause a little bit on that.

441

:

So you're seeing what I, I kind of

suspected as an outsider non-technical

442

:

person.

443

:

Is that because you've got

all of these data points,

444

:

you can now start feeding them into an

AI and say, hey, what?

445

:

What else can we learn?

446

:

Is that the kind of broad strokes idea

here, or am I missing

447

:

missing something important?

448

:

I mean, yeah, our data is structured

data, right?

449

:

It's already has labels.

She already has context.

450

:

So what better than to use the AI system

to make even more data?

451

:

Because typically,

and most likely the biggest issue

452

:

of any water utilities, that one

is something going to go wrong. So

453

:

by analyzing water

454

:

flow, we can detect other type

of technical parameters in the network.

455

:

And most like we can even predict

when an accident

456

:

or incident is going to happen,

or even when technical loss is not.

457

:

Technical losses will be there.

458

:

So and this could be a lot of money saved

and a lot of services being delivered.

459

:

I mean, community state

when there is a water burst

460

:

somewhere or pipe burst

and they're left without water. Right.

461

:

So that's actually

something quite interesting.

462

:

The we began to

463

:

and if you ask me what you want to do,

so you're going to continue providing

464

:

services. You will get you.

465

:

Of course, we also are expanding

or we have capability to do also different

466

:

type of water analytics, not

just for the utilities but also for open.

467

:

That's like rivers, like reservoirs,

water reservoirs and so forth.

468

:

And then of course

we would love to discuss with any,

469

:

any potential integrator

or the Helium community

470

:

how we can bring this part

of this technology in the world.

471

:

So, I mean, the whole system is replicable

now with the Helium connectivity.

472

:

We just

we don't need to do anything local, right?

473

:

We can just ship the sensor.

474

:

They can deliver a cloud

across the software.

475

:

And, local system integrator

can just go into the sale, potentially

476

:

do the replicate what you have done

anywhere else in the world.

477

:

And I think that's the biggest

and the most interesting part

478

:

that they see in the collaboration

with the Helium community.

479

:

So let's just take it, I mean, happy to

to connect to any local integrator

480

:

that may need to have this system meant

to make it happen in your local community.

481

:

Oh, nice.

482

:

So someone listening to this,

483

:

that is running a small or whatever IoT

business in their area

484

:

might hear this and say, cool,

this guy's got basically like a business

485

:

in a box

that I can take to my local city, unpack.

486

:

And I already know the sensors work.

I already know the system works.

487

:

Maybe I do some field testing

488

:

to check signal in my area

and deploy extra gateways as needed,

489

:

but more or less the

the single biggest obstacle

490

:

for this particular business

model will be the connection

491

:

with the the local government officials

will say yes or no.

492

:

The local water officials will say yes

or no to the to this,

493

:

but it sounds like the numbers are there

where you can

494

:

you can show them, hey, when you do this,

this is how much you save

495

:

from theft or from from whatever from

I like the non-technical sources.

496

:

That's good.

497

:

That's a non-technical.

Yeah, exactly. Yeah.

498

:

I mean, talking about community

stats will be the best way to help from.

499

:

Right.

500

:

So let's connect

501

:

I think the the challenge is

of course to to have the relationship

502

:

with the local municipality

that they can trust you, but

503

:

to deliver the job, but without references

and with somebody potentially locally

504

:

having access to any other type of segment

or even just deploying a gateway, right?

505

:

They can say, yeah,

we have done this and we have this partner

506

:

that can deliver this technology

and we are the local integrator.

507

:

So we are with the system to choke.

508

:

And of course the the cost proposition

is there all the benefits.

509

:

Right.

510

:

Because we can deliver anything

that the it runs of the world, the land

511

:

and gear or whoever of the big guys

512

:

can deliver at a fraction of the cost,

which ultimately benefits the

513

:

you as a community. Right?

514

:

Because if you are using your water,

which typically you should be,

515

:

you're part of it. Why should you pay?

516

:

Like why should the cost

be extraordinarily high?

517

:

The typical,

you know, proprietary system,

518

:

if you can even make the whole thing

519

:

or another as a service

for the community by the community. So.

520

:

Okay, almost sounds too political here,

but yeah, it's good.

521

:

It's it's super cool.

522

:

And I think it's a nice call to action

at the end of this.

523

:

Michail, I know you're super busy.

524

:

You've got a couple companies

you're running.

525

:

I really appreciate you coming on

and taking the time

526

:

to share parts of your LoRaWAN journey

and experience with us.

527

:

Thanks, man. Thanks Nik, appreciate it.

528

:

That's it for

529

:

this episode of The Business of LoRaWAN.

530

:

I built this for you.

531

:

The one person in about 100,000

who actually has an interest

532

:

in how this tiny little slice of the world

works.

533

:

Of course, this isn't just about you

and me, it's about everyone in LoRaWAN

534

:

and how we can work together

to make an exceptional thing.

535

:

LoRaWAN is a dispersed community

with little pockets of knowledge

536

:

all around the world,

and most of them don't

537

:

talk to each other as much as I'd like.

538

:

So the first and best thing

we can do to make this show better

539

:

is to get more guests

on who I don't even know exist.

540

:

I want to talk to strangers.

541

:

Strangers who are your friends.

542

:

Please

introduce me to the most rad LoRaWANeer

543

:

you know or point to my way, or help

reach out and give me a name when it comes

544

:

to running down LoRaWAN guests,

I can track a falcon on a cloudy day

545

:

if you can remember metsci.show,

you can find me

546

:

that's M-E-T-S-C-I

547

:

dot S-H-O-W

548

:

Okay, so sharing knowledge

by getting great guests on is the first

549

:

and by far the most important thing

we can do to make this better.

550

:

The next best thing for the show to do

is the usual stuff.

551

:

Subscribe to the show. Give it a review.

552

:

Share it in your corner of the world

again, that's Matija.

553

:

So finally,

if you want to support the show

554

:

financially, you can do that

over at support Dot Net Show.

555

:

You'll see options there

for one time donations.

556

:

If you really like this show

as well as an ongoing subscription option.

557

:

If you think the show is worth supporting

for the long term.

558

:

If you want to try LoRaWAN for yourself,

sign up for a meteoscientific account

559

:

at console.meteoscientific.com and

get your first 400 data credits for free.

560

:

That's enough to run a sensor for

about a year if you're firing every hour.

561

:

The show is supported by a grant

from the Helium Foundation

562

:

and produced by Gristle King, Inc.

563

:

I'm Nik

Hawks. I'll see you on the next show.

Links

Chapters

Video

More from YouTube