of my slide deck. And that's it. So, I figured, first of all, my name is Michael, and you

can call me Michael. And I figured, it's cheap, maybe we do some demos instead of long going talks, right? If you do have to go, my business cards are there if you have a question for later. People usually do leave early, my talks are really boring.

So, that's why we're going to do more demos today, if you don't mind. So, I think that works. And, push in there, and so we're set. Well, I think a nice way to start

would be to take a look at the mobile IoT lab that we have here. There is, I

don't know, because it's kind of small and hard to see from the back. It is connected to the internet, hence Internet of Things. And the thing we'll do now

is program the wall. So, I'm just going to do that with my trusty Android device here. That should be, that's what we're looking at. Basically, we're

trying to make the LED, a lot of LEDs light up. And after we do that, we'll take the screen, the packet screen, as it leaves the web browser on the phone,

and it actually lights up an LED via serial. Cross your fingers. I don't see

it happening. So, I think by using a closet goal or zero, we can loop it.

It's actually a buggy, so I'm just going to do it again. That's not so important. I guess now, on the second one, it should loop. And the third

one? Is this the last one? Is this the last one?

Anyway, so, this is what we just did. So, what we have at the very end...

OK, thank you very much. So, is this the one we're going to do for the next one? OK, that's it, thank you.

So, we have a Wi-Fi connection. That's going to the access point. This thing

here is serial, right? So, something has to control a lot of LEDs.

Like Arduino, we can use that. That's what I'm using. It's actually a test for the back there. And that connection... This looks quite complex. Let's draw over here. We've got the...

This could be a Raspberry Pi or anything. What is this? Oh yeah.

We've got a switch over here. So, if you look at the description for this

session, it has to do with data transports and protocols. And this is kind of one diagram of a hypothetical IoT network. That's basically one of the

experiments that you can demonstrate using the IoT laboratory that I can carry around with me. The next one, I think we can move to... There's no power. So, this is basically nice and bright. There's three

bulbs. One isn't turned on, unfortunately. And there are Philips Hue bulbs. There are a lot of manufacturers who make, actually, computers that look like light bulbs. Because they have transmitters and processors inside. LIFX is another in my life. I'm sure there's a few more than I know.

And the problem with the computers here is that they don't... They get enough power. They get 220 volts. But they're so miniature, the circuitry is so miniature that they can't run a Linux kernel or a TCP IP stack. So, as many of you might know, they're running like a mesh networking stack

and nothing else. They're just communicating over Zigbee in this case. Others communicate over IPv6 or Bluetooth. But Philips Hue has chosen the Zigbee protocol into data transport. So, that's a 2.4 gigahertz protocol.

Let's try it again. Success with this. What it's saying there is it's

searching for controllers over IP. Something is telling me... So, if we change concentration, let's try that. You're all so quiet.

Let's concentrate even more. Oh, okay. So, something happened here, right? We can change the colors. Yeah, that's basically the app. It's a very well-natured, well-behaved and intuitive, beautiful application. We can do it. We can access the API via REST calls and HTTP as well.

And that's what I'm trying to show. I think this time it's going to work. Maybe it works if I point a laser at it. That's already connected.

Have any of you seen Firefox OS? Be aware of funky journalists who didn't understand the message. It's not going away. So, here's a Firefox OS lock screen.

We'll just take the browser there. That's too bad because it does serve quite a nice debugging interface

where you can send REST commands directly over the interface that it serves from its web server. The controller there... Not the lightbulbs, but it looks like this.

So, it looks like this. What you see are the three lightbulbs.

The IP switch. The controller is also... Exactly. Although, all of these technologies are standard. There's a standard for that that you can read.

I think it's expensive, but you can buy it and read it. And then, obviously, everything from this end in this side is IP. Everything on that side of this equation is IP. So, what we have are just normal IP addresses. You ping this, and then we try to get all this information from computers and so on.

So, you access the system over IP, and then that speaks to the various lightbulbs. And strangely enough, the controller only connects to one lightbulb, I believe, and then the master initiates connections to its partners or neighbors,

and they do form either a mesh or a partial mesh network over Zigbee. So, that's another example of an IoT system, different devices working together with different technologies, different data transport, and different protocols, and kind of mixed together and mushed together.

And, right. So, the bridge is bridging Internet protocol with... What is it? That's right there. What is that?

Yeah, and I actually haven't opened it, but I actually don't know what's in there. Do you like all joins? Yeah. Do you want to talk about all joins? No. Well, it's smaller than that, so they must have miniaturized it somewhere.

I wouldn't be surprised if they modified a people bone or something like that, and then attached a Zigbee transceiver to it. That's the way I would do it. You know, and then you miniaturize that onto one PCB, and it looks different, but really what you're doing is...

The thing is that it's a very low power, so I don't think... I kind of doubt that it has a high-performance CPU in there. It doesn't have a cortex of AC7 or AC8. It could be something else from ARM. So, it's just speculation. And, yeah, so that's the kind of second scenario.

Let's see. So, the third scenario involves beacons. So, we have three beacons here. I'm actually going to pass them around, because I'm always amazed. Nobody's ever held one in their hands, so we're going to change that today.

Oh, did it fall down? No, no. Do you want to pass them around? No, no. Can you put it back, because those are... I'll use those for the demo. But you can pass these around if you don't mind. And, basically, if you feel courageous, you can open it up and look inside. It's a little hard to open it up.

You just have to use your fingernails and the hammer and... Be careful, but you can do it. So, after you open it up, you can see where the battery slides in. These have no batteries, so they're turned off. Some models, the newer generation of these are the Lindworm from Netherlands. The newer generation has a dual power management from the battery side, 3.3 volts,

and then has a 5 volt intake from a USB cable. So, they're very useful, kind of neat, good for museums, where you have a place to plug in cables. Right. That one we just got in the lab from Beacon Inside.

It's a really hefty thing with standard sized batteries in there. So, that's another thing that you can do with something else. Take a look at those beacons. Oh, there's a USB key. So, basically, what I'm going to do now,

is use this part of the device once more. Basically, this application here, the physical web,

this exists for at least Android and IOS. So, you can actually download that right now, if you like, because we will have the chance to fool around with these beacons in the next, what, five minutes. So, basically, the question is, how much in the room?

How much? How much? So, okay, you can carry on. No one wants us to stop, just raise your hand. We'll carry on. I mean, they're not bored yet, because they're really quiet. Are you bored? Okay, great. So, look at this. Okay, physical web. What is a physical web? It's basically a Google project.

Early on, they developed a new protocol for beacons, because Apple had the IE beacon protocol, which basically broadcasts, it looks like Mac addresses, a string of numbers. It's not as useful in some situations where you'd like to have more context, like a real URL. And Google being the web platform they are,

and doing a lot with the web, decided we would have a new standard for beacons that would broadcast not only Mac address type of identifiers, but URLs as well. So, basically, that's what we're going to do now, is we're going to read the URLs off of these beacons, which are broadcasting Eddystone.

That's the name of the protocol. And, by doing that, we can attach the beacons to the physical and animate objects, like even trees, for example, things that are not even electronic at all, and then have some, kind of, form some kind of system using beacons. We can discover, yes, this tree is ripe, our harvest is kind of down, that one is not, and so on.

So, there's a lot of use cases for that. Let's do this. Probably should adjust the screen. I'm just going to click on that. And this is the part where you have to take my word for it. Actually, well, I can pull one down and then walk over to the device,

because you're supposed to be walking to the beacon, but then you don't see it on the screen, right? So, I'm going to put that right on there. And, oh, that would be even better if I just did that. You see that? Yeah. Even better.

Okay.

That's about to fall down. But, this is what you do when you, okay, so it's reading the other one as well.

I didn't place it far enough from the source, kind of jiggling and going back and forth. The beacon that I did place over there, once I would walk over there, it could be a wall-operated television, right? So, this could be a wall that you don't understand anything about, but maybe there's a small sign, maybe in Japanese or some language that you don't understand.

You walk to the wall, and you get a notification sent to your telephone, because your telephone has a Bluetooth stack or any mobile device. The beacon is transmitting over Bluetooth the beacon Eddystone packets, and then that picks it up, and you get the notification.

Try again. And once you get that notification, you have the option of basically clicking or not. So, I'm going to say click there. Keyless entry panel. Okay, so then we have some kind of, I mean, I have to just put a static graphic on there,

but it could be a web application, you know, something dynamic with JavaScript and so on. And it could be an access control, it could be, so, if any of you have that application, if you downloaded that, then you're welcome to walk around, because there is a beacon on that table there,

and there's a beacon on this table up here, and because we're running out of time, I would actually just show you a few devices, you know, the kind of things we're working with in the lab, doing investigation with that there.

For example, so this is how you can make beacons. It's a generic Bluetooth development. Are we still interested? Other five minutes? Is the next speaker here? No, no, you have to be on the floor. As long as I'm on both speakers. Yeah, that's too fast to bend, isn't it? The next speaker's not here, right?

So anyway, this is what we've been doing in the lab with beacons and so on. Take a look at what we just used, what is hanging up on the walls. It's an estimo beacon. You can't open it, because it has no, I mean, it does have a cover, but it's formed onto the base, so it makes it a little more waterproof, I suppose, but it also means you can't replace the battery.

So we decided to destroy one, because that's what you do, right? We cut open the cover that's inside, and it's basically an NRF-51. It's this chip that's right here. It's that chip there. And that's the semiconductor. And you can make beacons with this board.

When you run the workshops that take two hours, we give out, or we loan out 30 or 40 of these boards, one to a student or one to every other student, and we basically make beacons with them. So this is a generic development board running on ARM Cortex-M0, so it doesn't have lineups stacked,

but you can program ARM assembly code, send it over to the cloud to compile on ARM devices, because if they have a web-based framework, so it works in every web browser, you get the binary back from the cloud, and then you can burn that onto these devices,

and they start running your code, and then you can do whatever you want. You can abuse any standard and make it longer than 14 characters or something like that, or any kind of Bluetooth application you'd like to develop, you can do it with this board. And obviously, once you arrive at a production stage

or something like that, you want to miniaturize that. And then you don't need all the things like the Arduino shield assembly and the power intakes and a bunch of other things. You just need that small little chip and then whatever microcontroller you're going to use for it. Yeah, and I do mention the workshop because that's actually what I submitted the two-hour version of this.

And then, yeah, so I guess it worked out to be 25 minutes, and that was the process that I came at with showing these demonstrations. And basically, we've seen three different things, right? We have seen the... We started out with... We started out with the Lada LEDs.

Is this still lit up? No, no, no. Oh, okay. Anyway, so we started out with that. It was a serial USB, right, with a bunch of nodes in between. And then we went to Zigbee.

So we started with serial and cable-connected copper Ethernet connections. Most of them went to Zigbee and started with Wi-Fi over 2.4 gigahertz with a controller that's bridged from Zigbee to IP or Internet. And then we finished... Actually, we don't have a diagram before we finish, but we finished with BlueJeet,

another 2.4 gigahertz technology that, like someone else said, they're trying to move towards mesh to catch up with the Zigbee and the Z-Wave folks, right? So we have those three models that we finished in 30 minutes. Not flawless, but good luck, I guess.

I think it's great to see such a... best representative set of devices. Can you use the microphone, please? I'm going to repeat the question. Have you looked at energy harvesting sensors? Yeah, so the question is if we have taken a look at energy harvesting sensors

and actuators. And what that means is a device which requires no battery or solar or anything like that that works using its own power. So nOcean is one manufacturer that comes to mind. You can use them.

The lab is my partner that does most of the work. So nOcean might want to take a look at. What we've had with those are the clickers. So these emit an RF signal. I'm not sure. I think it's 868 megahertz. And basically to emit RF, you need energy, right? But they don't have any batteries in there,

so how does that work? When your finger pushes down on that button, it's causing motion. And in some way, which I don't understand, maybe you do, it's harvesting that energy and then storing it for a very small amount of time, a capacitor of some kind probably, and then using that to transmit the RF signal.

Does that answer your question? In your first memo, you used MQTT. Where in your scheme do you have the message broker and what did you use for it? I think I missed something there, didn't I? Because that's very interesting. Here, there is a broker. And where would the heat go? So basically, it's on the back.

Hard to see, I'm sorry. But most of the power that I have on this laboratory is on the back. But there is one exception. So this is like power bricks. There's an upstream router. There's one exception. There's one computer on the back there.

And that's a Raspberry Pi. So it's kind of, I'm just using it for a broker and almost nothing else. That's what's doing all of the MQTT broking for the entire network of computers on the front. And I didn't mention it, but there are two Galileo's. So those are Intel i832-bit,

i832 are construction set computers on the front, similar to Raspberry Pi, but not ARM. There is an Edison as well. It's an extremely small computer, which is low power. It's actually very old. So the newer generations of Intel, similar technology are incredibly low power. Last I heard, the Curie boards, for example,

that are about the size of a button, they discharge power while running about the same as a battery that's held up into the air and discharges from moisture. I'm not sure if I believe that. So keep your eyes and ears open. And basically, the MQTT broker is on the back and it looks like this on the diagram.

So we have the Galileo there. Is it fixed? Downward? Three, four, three, guys from the... Does that make sense?

Yeah. So the switch is connecting the MQTT broker to the MQTT client, which is then, you know, reading a topic or subscribing to a topic

and then whenever it does get a message, it changes the LED context. Any other questions? Well, I guess I can't make a photo.

Yeah, okay. If I had a mirror, I could. So the question is what is the device that I'm using to move these projections, right? So I can put my hand there or I have an old pen or whatever. And the device is a Microsoft webcam.

I don't even know. Cinema or studio or something like that. Pro. I can't read the model number. And it's mounted on a very sturdy, very well-made, whatever, close range. What is the name of this? It's made by Lumetrade and... Can-Obe.

Yeah, I can do that. But that won't help you too much because my friend who makes these, his name is Matthias, and he lives in Munich where I live as well. He stopped production. So he may have a few more, but they are quite interesting things. Pretty cool, aren't they?

So if I do this, what happens? Put that at the scene. Have an interesting... Anything else? Is this anything about Z-Wave maybe that we didn't talk about or other frequencies or other protocols? We already had COAP in the morning. We had CMQ.

Yeah, you see that would be really neat. And that's kind of the next generation. Most people have heard more of SafeBox. These are 868 megahertz transmitters and usually, I guess, I guess you can receive,

yeah, the transceivers, you can receive them. Anyway, so that's not part of the setup, but that's what we're looking at getting into next. And it uses the same ARM framework as these boards here. So that will be very interesting. It's very easy to program.

Easy to program for LoRa members as well. LoRa, what does that stand for? Low Power Low Range. Let's just say low range. That's not low range. Low range. I want to allow all the protocols,

like VLC or X10, those that we are not allowed in. You want to see that again? X10. X10. X10. VLC.

VLC, yeah. So the question is, what about the broken data transports, actually, that are transmitting data over electrical 220 volt standard house connections and building connections? And I guess that does make it very light and well in the lighting aspect.

But I don't have anything to show you that. You too.