Episode 27

Build To The Standard - Eric Lenington - ObjectSpectrum

Eric Lenington, founder and CEO of ObjectSpectrum, talks about the power of solving customer problems with LoRaWAN, and why the real strength of the technology lies not in theoretical performance, but in its thriving ecosystem. From commercial buildings to agricultural deployments and even vacation rental monitoring, Eric breaks down how his team delivers reliable, scalable IoT solutions using off-the-shelf devices and the flexibility of LoRaWAN standards.

He explains how ObjectSpectrum integrates with networks like Helium and Senet, and why, despite new protocols like Mioty entering the scene, LoRaWAN remains the dominant force because of its mature ecosystem and device availability. “Technology X might be better than LoRaWAN,” Eric says, “but I don’t care—there’s no ecosystem.”

Eric also shares the origin story behind Prism, the software platform ObjectSpectrum built when nothing else met their standards for high-availability, scalable IoT application infrastructure. Designed to be infrastructure-agnostic and support a variety of protocols beyond LoRaWAN, Prism reflects a telecom-grade mindset applied to IoT—delivering the uptime, flexibility, and performance that complex deployments require.

Looking forward, Eric highlights NTN (Non-Terrestrial Networks) as the next major frontier in IoT connectivity. He discusses how satellite LoRaWAN providers like Lacuna are beginning to open up new possibilities, offering standards-based options in space that rival terrestrial deployments in reach and resilience.

If you're evaluating how to deploy scalable IoT solutions, this episode offers clarity on where LoRaWAN wins, how to assess new entrants like Mioty, and what to watch as NTN infrastructure accelerates.

Eric on LinkedIn

Object Spectrum

  • 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.

Transcript
Speaker:

Today's guest on MeteoScientific's.

2

:

The Business of LoRaWAN is Eric

Lennington, the founder and CEO of Object

3

:

Spectrum.

4

:

Eric has spent

decades in telecom and software,

5

:

and for the past

6

:

eight years, he's been all in on LoRaWAN,

not because it's the shiniest

7

:

or most hyped technology,

but because when it comes to solving real

8

:

world customer problems,

it gets the job done.

9

:

From monitoring thousands of acres

of farmland to managing infrastructure

10

:

and commercial buildings and vacation

homes, Eric and his team have built

11

:

reliable, scalable systems using LoRaWAN

as the backbone.

12

:

In this episode, we dig into what it means

to actually deliver on IoT promise.

13

:

Eric walks through how Object

Spectrum uses their Prism platform

14

:

to rapidly build custom solutions,

why they chose to invest in LoRaWAN early,

15

:

and how the maturity of the ecosystem,

off the shelf devices, stable standards,

16

:

and active vendor participation

makes it the go to option in most cases.

17

:

Whether you're a C-suite leader

evaluating IoT strategy, an engineer

18

:

deploying your next project,

or a hobbyist tracking launch growth,

19

:

this conversation cuts through the hype

and focuses on what matters.

20

:

Solving the problem in front of you

reliably and at scale.

21

:

This episode is sponsored by the Helium

Foundation's IoT Working Group.

22

:

Helium offers global LoRaWAN coverage

that you can use exclusively or roam onto.

23

:

If you'd like to see if Helium

coverage exists near you,

24

:

check out the links in the show notes

to get started using Helium today.

25

:

You can sign up for a console account

with Medio Scientific at

26

:

console dot medio scientific.com.

27

:

Now let's dig into the conversation

with Eric Lennington.

28

:

Eric, thanks so much for making the time

to come on the show.

29

:

Nik I'm happy to be here.

30

:

Yeah. I'm psyched.

31

:

So I'd heard about Object Spectrum

32

:

as being a really big LoRaWAN,

can you tell me how big is this thing?

33

:

Well, so we started in 2016,

which was like right on the cutting edge

34

:

of of when LoRaWAN was first starting

to get some traction.

35

:

And frankly, we're really saw it as

36

:

as a really powerful way to connect.

37

:

At the time, it was mostly agricultural.

38

:

And of course, the problem you always have

agriculture is the middle of nowhere,

39

:

and there aren't

a lot of other options for that.

40

:

And so that's how we got started in it.

41

:

We've been doing LoRaWAN,

like I said, since that time.

42

:

Since then, we've gotten into using it

for other things,

43

:

like in building applications.

44

:

We've got applications that are doing

like infrastructure monitoring inside

45

:

commercial buildings

and that sort of thing.

46

:

We've got some campus applications.

47

:

We actually run a couple of university

campuses, and they use that for everything

48

:

from keeping track of their,

you know, golf carts on campus to

49

:

to students using it for projects

and that sort of thing.

50

:

So, like you, UT

Dallas is one of the first campuses

51

:

that we deployed, and they use it

for air quality monitoring on and on. So.

52

:

So yeah, it's been a good choice.

53

:

You know, LoRaWAN as an ecosystem in

54

:

my mind is the thing that really makes

it stand out.

55

:

You know, and again in 2016

there wasn't much of an ecosystem.

56

:

So it was a little bit of a crystal ball

kind of thing.

57

:

But I'm very glad

that we made that choice.

58

:

And, you know, as you probably know,

we don't exclusively do LoRaWAN.

59

:

It's not the answer for all things. Okay.

60

:

But when you have a cluster of devices

61

:

in a particular area

that need to communicate,

62

:

even if you have cellular

or some other connectivity

63

:

available, it's often

still the best way to do it.

64

:

And I would say, you know, looking back

now over the last 8 or 9 years,

65

:

the big thing that LoRaWAN has going for

it is really the ecosystem

66

:

in 90 plus percent of the cases,

if we need a device of some kind,

67

:

we can probably find that LoRaWAN standard

68

:

within the LoRaWAN system

just, you know, as you know,

69

:

thousands of developers and manufacturers

making these devices.

70

:

Now we can’t always do that.

71

:

Sometimes we have to make our own.

72

:

But a lot of times

you can just go and get it.

73

:

And that to me is the thing

that sets it apart.

74

:

Every once in a while

you probably hear this too.

75

:

It's like somebody says, oh, well,

you know, technology X

76

:

is better than LoRaWAN

for these five reasons.

77

:

And I'm like, I don't care. There's

no there's no ecosystem.

78

:

What do you do with that technology.

79

:

Yeah.

80

:

So in a way it's kind of a Betamax VHS

argument if you remember that old thing.

81

:

But yeah, you know, it's like, great,

82

:

we can talk all day

about how Betamax was a better technology,

83

:

but it didn't really matter

because nobody had a BetaMax player.

84

:

And so here we are,

you know, with LoRaWAN.

85

:

There may be better technologies

in certain aspects, and that's great.

86

:

But the ecosystem is really what makes it

what makes it the go to technology.

87

:

Yeah,

I was just talking with a guy on LinkedIn

88

:

the other day and he's like,

I've got 40,000 nodes over 300km².

89

:

I think I'm going to go to Mioty

He was like, hey, could be super cool.

90

:

May or may not be the right application,

but man, there are a lot of options

91

:

in LoRaWAN Absolutely

and most of the bugs are hammered out.

92

:

And you mentioned Mioty, you know, and

that's obviously one that comes up a lot.

93

:

Yeah.

94

:

You know,

I think you could make the case that

95

:

from a technical perspective,

it has some technical advantages.

96

:

It came it came later than LoRaWAN.

97

:

Yeah I would expect it to be better.

98

:

Newer thing is can somehow be be better

because they love the older thing.

99

:

But here's the point.

100

:

If this application that you're talking

about these 40,000 nodes,

101

:

if he wants to build them and manage them

and they are homogenous

102

:

and he basically wants to run

that entire infrastructure, great Mioty

103

:

may be the absolute fine answer for that.

104

:

In our case, our customers

105

:

most of the time

are looking for off the shelf solutions

106

:

and where we have to build something

which we will and we do.

107

:

It's because we cannot find

the right option available.

108

:

And sometimes we'll use LoRaWAN if we

build something and sometimes we won’t.

109

:

But the point is,

is that the LoRaWAN ecosystem gives us

110

:

that flexibility and melody,

and none of the other related.

111

:

Yeah.

112

:

So Sigfox gave it a good run for a while.

113

:

But, you know, that's

114

:

that has become very much

kind of a proprietary technology now too.

115

:

Yeah.

116

:

Yeah, yeah.

117

:

Horses, horses for courses.

118

:

I think how the English said.

119

:

And then do

120

:

you guys roam on to other networks,

or are you only on your own LoRaWAN.

121

:

We have done some stuff with what

used to be called what were they called?

122

:

Netmore has bought everybody Senet.

123

:

Yeah, Senet. Yeah, yeah.

So we integrated with Senet early.

124

:

Early on we were integrated with Helium.

125

:

So we do we can do applications on that.

126

:

You know whenever you're looking

at a deployment architecture

127

:

and whether it's LoRaWAN or anything else

at 10,000ft, almost anything will work.

128

:

Okay.

129

:

But when you get down to the details,

130

:

you got to really understand

what you're doing, okay.

131

:

And so you think about stuff like Helium

okay.

132

:

Helium is not good for in-building

applications in 99% of the places

133

:

that you might want to do that,

you just doesn't have the penetration.

134

:

There's not enough

infrastructure out there.

135

:

So it could work for certain things.

136

:

But if you're going to put, you know, leak

detection systems

137

:

in a skyscraper, it's

probably not your best choice, you know?

138

:

Yeah. Unless you're going

to deploy the gateways.

139

:

Well, that's exactly right.

140

:

So then the question becomes, okay, in our

particular case, why would we do that?

141

:

Okay.

142

:

We run the LoRaWAN network

infrastructure already because we need to.

143

:

And so I could see somebody maybe saying,

you know what, I need to do this.

144

:

I don't want to run the network servers.

145

:

I don't want to have that infrastructure.

146

:

So Helium is a reasonable choice.

147

:

And maybe you could make the case

148

:

that it's a lower cost option

than something like Netmore etc.

149

:

in our particular case,

150

:

it doesn't really apply because

we already do run the infrastructure.

151

:

And frankly, for a lot of stuff

it boils down to high availability.

152

:

Okay.

153

:

So like we have we have an application

where a customer that monitors

154

:

basically infrastructure

that is not attended.

155

:

So think about remote sites

and things like that okay.

156

:

We typically will use cellular backhaul.

157

:

But if we're deploying LoRaWAN gateways

for local sensor networks.

158

:

We'll deploy two separate gateways

with 100% overlap

159

:

because we'll put each one

on a different cellular network.

160

:

Okay.

161

:

That's the kind of high availability

162

:

you can't really get

unless you really go build it.

163

:

So for a lot of things like that, that's

I don't want to say we're forced into it.

164

:

But when you look at the parameters,

that's what makes the most sense.

165

:

Yeah.

166

:

I mean, you're running a business

and you got to accomplish the client's

167

:

kind of

you got to solve the client's problem.

168

:

And that's the that's the deal.

169

:

So that's a nice lead

into this Prism thing.

170

:

Tell me what it is

and why did you build it?

171

:

Well, so I've been

in the software business my whole life.

172

:

And prior to starting Object Spectrum,

173

:

I spent about the prior

15 years in the telecom area.

174

:

So we went through the whole voice over

IP thing and all that evolution whatnot.

175

:

And so my view of how things were supposed

to work

176

:

is five nines reliability,

as they like to say

177

:

in the telecom world, okay,

with an 8.5 minutes of downtime per year.

178

:

That was the way you did things.

179

:

And so when I started looking at ways

that we could go

180

:

about building our infrastructure

and how we were going to build

181

:

applications that sat on top of that,

that was a huge influence is like,

182

:

I actually I actually didn't

183

:

really plan to even build Prism.

184

:

I expected that I would go and find it

185

:

and license it, and I could not.

186

:

Yeah, that's.

187

:

Yeah,

I saw the best solutions come around.

188

:

I know, I know.

189

:

And so we said, all right,

if we're going to build an infrastructure

190

:

with a focus on the key things,

you got to have high availability,

191

:

scalability and security.

192

:

I mean, those are those

are the foundational aspects of this.

193

:

We want to find something

that is good for the ops team.

194

:

It's good for the developers

195

:

and both both kinds of developers,

front end to back end developers.

196

:

And I know there's lots of people that are

full stack developers, and that's great.

197

:

But most of the time you have people

that have special talent in one side

198

:

or the other, right?

199

:

And so we originally said, all right,

we're going to build an infrastructure.

200

:

We're going to base it

on a lot of what I had been exposed to

201

:

in the telecom world and in fact, in IoT,

it's really quite very similar.

202

:

Okay,

you're dealing with lots of transactions

203

:

and you're dealing with different

protocols and so on and so forth.

204

:

So it sounds like a very different thing,

but it's really not.

205

:

And so we started with that foundation

206

:

and the end result basically a Prism

of course it's software.

207

:

So it's continually evolving.

208

:

We run

if we have a choice in the matter on AWS

209

:

because we like AWS, just like,

okay, it's a good platform.

210

:

We have run on Azure.

211

:

I think we even have a customer

that runs on Google Cloud,

212

:

and we have a couple of customers

that run on their own bare metal.

213

:

And so we built Prism

to be completely infrastructure agnostic.

214

:

That was a key thing.

215

:

And in fact, most of our customers,

the vast majority,

216

:

we are hosting their application

and we are hosting that application in an

217

:

AWS virtual cloud.

218

:

But we

always want to make the option available.

219

:

And like I said, we have a handful

that have taken us up on it.

220

:

If they say, you know what?

221

:

For whatever reason, I want to run this

on my own, in my own data center,

222

:

my own infrastructure,

they have that capability.

223

:

So that was one of the key

design requirements.

224

:

The other big deal is

we didn't want to have to constantly

225

:

rewrite the foundational elements

to a new application.

226

:

Okay.

227

:

We are not a drag and drop

application built.

228

:

That is not what we do, okay?

229

:

In fact, we intentionally decided

that that was not what we wanted to have

230

:

because those are fine tools

and they can be used for a lot of things.

231

:

But at the end of the day,

you are always locked into the vision

232

:

that the developer of the tool had

for what you might do with it.

233

:

Okay. So we're more of a modular system.

234

:

We've got the foundational elements that

you need to build the actual application.

235

:

And so we like to say

and of course it's a rule of thumb, but

236

:

we like to say that 70% of

your application is already done, okay.

237

:

And maybe it's 60%, maybe it's 80%.

238

:

But the bottom line is, is that not only

can we use Prism

239

:

as kind of a secret weapon to rapidly

deploying, obviously this is translates

240

:

to less time and less cost and all those

things, while also to a very high degree

241

:

of customization capability,

because we're not a drag and drop builder.

242

:

We don't have any designs about what

what look and feel like,

243

:

what the whole user experience

should be like and things like that.

244

:

So it's an evolving tool.

245

:

We use it for everything.

246

:

We have customers that actually

write their own software on Prism,

247

:

and so that's great.

That's certainly possible too.

248

:

I'm not going to lie

and say there's no learning curve.

249

:

There is a learning curve.

250

:

Yeah. And most customers

don't want to do that.

251

:

Most of our customers really rely on us

to be their technical back office.

252

:

Sure.

And so we do the whole thing turnkey.

253

:

What does that look like for a

I mean, maybe a recent new client

254

:

you can walk me through kind of

what do they come to you with?

255

:

And then how did you guys solve

the problem? Yeah.

256

:

So an interesting one,

257

:

which in some ways doesn't sound like IoT,

but it really is.

258

:

Have you ever been to a restaurant

where they have a little a little kiosks

259

:

on the table that you can order drinks

and pay your bill and stuff like, okay,

260

:

so that company is called Ziosk

261

:

and we manage all those devices for them.

262

:

Okay.

263

:

So those are literally hundreds

of thousands of little IoT devices.

264

:

They're running Android

but they're also running.

265

:

They've got a credit card reader

and RFID chip and Bluetooth communication.

266

:

So they know where they're physically

267

:

at in the restaurant

and different things like that.

268

:

And all of that life cycle monitoring,

health monitoring of the device,

269

:

locating the device, remote firmware

updates, remote content updates

270

:

and things like that.

271

:

Okay, so they came to us

and they said, we have a situation

272

:

where we've basically outgrown the system

that we originally built

273

:

to manage all these devices.

274

:

And so they had done

a really interesting job.

275

:

And you know, they were using some off

the shelf software,

276

:

some commercial software

and some in-house software.

277

:

And frankly, it had just grown

to the point where it was so hard

278

:

to manage that they knew

they needed to do some different.

279

:

And so that is a particular system

where the connectivity

280

:

is Wi-Fi connectivity,

Wi-Fi in the restaurant.

281

:

Okay.

282

:

So we don't actually control the network,

283

:

which presents an interesting challenges

sometimes.

284

:

Yeah.

285

:

But at the end of the day,

those are IoT devices.

286

:

They're turned on in the morning,

287

:

they come up, they connect to our cloud,

they go through their diagnostics.

288

:

We can do remote remote testing

and remote diagnostics.

289

:

And so their support team

has access to be able to run for, run

290

:

various types of like,

you know, speed tests to scan for Wi-Fi

291

:

networks and all the things that they need

to do to support their customers.

292

:

And so that was a case

where we were again, able to use Prism,

293

:

both the software Prism

and the infrastructure Prism,

294

:

to basically onboard those hundreds

of thousands of existing devices

295

:

in a way that allows them to scale

without having to worry

296

:

about all of the details

of managing that back office system.

297

:

Oh, super cool.

298

:

So it ends up being this piece

read, basically,

299

:

the customer comes to you

with this problem

300

:

and you say, hey, it can be Wi-Fi, can be

LoRaWAN, can be Bluetooth, like whatever.

301

:

Absolutely. We'll do

whatever the best thing is for you.

302

:

And in that case it was Wi-Fi.

303

:

But in other cases it's it's

whatever else.

304

:

Okay, cool.

305

:

I would say that is and always

was one of the key concepts around Prism,

306

:

even though we were doing LoRaWAN actively

in that very early stage,

307

:

we didn't build Prism to be a LoRaWAN

basis.

308

:

Right?

309

:

Oh, it is, and it can be, but we run

310

:

cellular and we run Wi-Fi

and we run, you know, Bluetooth.

311

:

And we even do some satellite.

312

:

So you have to if, if you want to

313

:

if you want to serve people,

you got to solve their problem.

314

:

That's 100%.

315

:

Yeah. Okay.

316

:

So we've gone through kind of what it is,

what Prism is

317

:

and how you guys have gotten into LoRaWAN.

318

:

I guess we kind of wrap this piece up.

319

:

It seems like we talked for hours

about the whole thing,

320

:

but like to keep this thing

321

:

short for people to listen, say, okay,

that was super cool.

322

:

I can dig that.

323

:

What are you

super psyched about in the next,

324

:

let's say, like six months to a year,

325

:

specifically in LoRaWAN with what you guys

are doing at Object Spectrum?

326

:

Yeah.

327

:

If anything.

328

:

Well, so I think there's there's sort of

329

:

two areas and one of them is directly

LoRaWAN related.

330

:

And the other one

is sort of tangentially LoRaWAN, really?

331

:

Yeah.

332

:

So the one that is directly

LoRaWAN related is, again,

333

:

I continue to see more expansion

in the LoRaWAN ecosystem.

334

:

It's a growing, healthy ecosystem.

335

:

There's new devices

coming out all the time.

336

:

There's new vendors

that are entering that market.

337

:

It's making it,

I would say, easier and easier

338

:

to deploy complex solutions

using off the shelf hardware.

339

:

Okay.

340

:

As I mentioned, we we do design hardware.

341

:

Obviously we don't manufacture anything.

We outsource that.

342

:

But you know, we will design hardware

if we need to have a project right now,

343

:

it has to do with rental homes, okay,

vacation homes and that type of thing.

344

:

And so again,

these are typically unattended

345

:

or they're attended by by third parties

okay. Yes.

346

:

And what do you want to monitor there.

347

:

Okay. You own this property.

348

:

That might be a thousand miles away.

What do you want to monitor.

349

:

We want to monitor probably water leaks.

350

:

And you know there's a power on

and temperature, you know.

351

:

And is that

is the air conditioner running properly.

352

:

Is there a septic tank?

353

:

You know, how's it doing.

354

:

So you get all these different factors.

355

:

So far, everything that we are needing to

do for this customer is available.

356

:

And off the shelf device in the hallway.

357

:

Oh super cool.

358

:

So does that mean

359

:

you just put a gateway in every house

and you're like, yes, 100%, 100%.

360

:

Gateways are are inexpensive.

361

:

Good, good. Gateways are inexpensive.

Okay.

362

:

One gateway in a typical rental property

is going to provide

363

:

ample coverage for everything inside

that rental property.

364

:

And we're actually choosing to use

cellular backhaul,

365

:

not because there might not be internet

access available

366

:

because we don't want to be part

of their internet problem

367

:

if they have an internet.

368

:

Yeah.

369

:

So we are out of band system

using using multi carrier cellular.

370

:

Okay.

371

:

So that's a that's the law

which is one the other that's

372

:

that's tangentially related

certainly from a backhaul standpoint.

373

:

But also one of the vendors is LoRaWAN

and that is low-Earth

374

:

orbit satellite communications. Okay.

375

:

Since Lacuna is the one I'm talking about,

obviously it is LoRaWAN to space,

376

:

which is crazy but very interesting.

377

:

And then you've got literally 3 or 4 dozen

378

:

other players that are credible players

entering this market.

379

:

And we've all heard the, you know,

the big names like Skylo and obviously,

380

:

you know, SpaceX and whatnot.

381

:

But there's other.

382

:

So again

Murata is one for example out of Australia

383

:

we've used them using their

I guess they would call it

384

:

their proprietary system

that they've had for years.

385

:

We've used that

for some remote applications,

386

:

but they're also going into 3G,

4G to the sky type of thing. Yep.

387

:

What we call NTN Non-terrestrial.

388

:

It's got to have a cool guy name for it.

389

:

Yeah, exactly.

390

:

It's called like, it's

going up to space. Yes.

391

:

And so whether the ultimate technology

ends up being LoRaWAN

392

:

or ends up being a 3G, 4G technology.

393

:

And to be honest with you, I don't

remember exactly which one is being used.

394

:

I think it might be a version of NB-IoT

or something like that.

395

:

But the bottom line is

what is different about these

396

:

and all other past and existing

satellite is they’re standards based.

397

:

Okay, I know people say well LoRaWAN’s

not a standard.

398

:

Well, yeah,

399

:

it is a standard as far as I'm concerned

because everybody adheres to it.

400

:

Right? Yeah.

401

:

And certainly all the,

all the cellular stuff is standard

402

:

that now makes the satellite option

403

:

not only viable because we're going to get

some competition in the space, okay.

404

:

But also the ability

to not be single source with one vendor.

405

:

You probably remember Swarm,

they got bought by SpaceX.

406

:

We had done some stuff with swarm

and swarm said, okay, we're done

407

:

and we're not doing this anymore.

408

:

And suddenly you've got a bunch of devices

out there that can't talk to you, right?

409

:

And that's not a fun project

that anybody wants.

410

:

So once you have multiple options

in orbit, then you have the

411

:

at least the option to say, hey,

we're going to use this technology

412

:

and there's three or 4

or 5 different vendors that we can use.

413

:

We're not going to end up with a bunch

of remote devices that we can't talk to.

414

:

So I think that's very exciting.

415

:

And that is unfolding right now.

416

:

And a year from now,

that whole world is going

417

:

to look very different than it does today.

418

:

Yeah,

and I'm super pumped on the NTN stuff.

419

:

I what I was talking to tell Telemacho

from EchoStar

420

:

a couple of shows ago, and I'm working

to line up someone from Lacuna.

421

:

So it's

422

:

I mean,

it's a super exciting part of LoRaWAN

423

:

I think Lacuna had a launch yesterday.

424

:

If I don't if I remember right. Okay.

425

:

Yeah. Right.

I'll, I'll have to go check them out. So.

426

:

Right. Eric,

thanks so much for making the time.

427

:

I know you're super busy as a founder

runner of a company, so thanks.

428

:

for coming on, I appreciate it.

429

:

Nice talking to you, Nik That's it for

this episode of The Business of LoRaWAN.

430

:

I built this for you.

431

:

So whether you're a business owner,

a LoRaWAN professional or a hobbyist,

432

:

the intent is to give you great LoRaWAN

information.

433

:

Of course,

the best information doesn't come from me.

434

:

It comes from the conversations

435

:

we have with the people building

and deploying this tech in the real world.

436

:

And that's where you come in.

437

:

LoRaWAN is a global

patchwork of talent and ideas.

438

:

And ironically,

for a globally connected network,

439

:

most of the brilliant folks

working on it are connected yet.

440

:

Help me change that.

441

:

Introduce me

to someone awesome in your network.

442

:

Someone doing meaningful work in LoRaWAN

work.

443

:

Just shoot me a name.

444

:

I'll take it from there

445

:

and get them on the show

so we can share their work with the world.

446

:

You can always find me at metsci.show.

447

:

That's M-E-T-S-C-I dot

448

:

S-H-O-W, metsci.show.

449

:

If you want to support the show

in other ways, you can subscribe,

450

:

leave a review,

share it with your corner of the world.

451

:

All those are super helpful.

452

:

If you'd like to support financially,

you can go to support.metsci.show

453

:

for both one time and recurring options.

454

:

We're also open to sponsors.

455

:

If your company serves

the LoRaWAN community

456

:

and you want to reach this dedicated

audience, let's talk.

457

:

If you want to try LoRaWAN for yourself,

create a MeteoScientific account

458

:

at console.meteoscientific.com

and get your first 400 DC for free,

459

:

which is enough to run a device

sending hourly for about a year.

460

:

This show is supported

461

:

by a grant from the Helium Foundation

and produced by Gristlel King, Inc..

462

:

I'm Nik Hawks.

I'll see you in the next show.

All Episodes Previous Episode

About the Podcast

Show artwork for The Business of LoRaWAN
The Business of LoRaWAN
Learn From the Pros

Listen for free

About your host

Profile picture for Nik Hawks

Nik Hawks

Incurably curious, to stormy nights and the wine-dark sea!