Do you need LoRa for LONG RANGE Sensor Networks? Locally-Hosted Setup w/ Chirpstack

as I wander through this paper birch Forest I wonder how hard would it be for me to put sensors out here so you probably know I'm into all things data sensors home automation and the outside world is just something that's kind of hard so some examples you might need if you're into gardening you might want to have soil sensors or moisture sensors outside long distance from your house maybe your mailbox is far away across the street you want to monitor that house is is all the way back there not going to get Wi-Fi out here zigg and zwave probably aren't going to work either 433 MHz has Zone quirks what if there was a better solution for long range outdoor sensing at home and that solution is Laura and Laura Wan so in this video I'm going to set up a full-on Laura WAN network Gateway the cloud the sensors the decoders and get all that data into home assistant so come along with me on this adventure so to Aid in my exploration of Laura Electro was kind enough to send over a few goodies for me to try out so here's all the stuff I got temperature and humidity sensor capacitive soil moisture sensor in case you need to do some data logging in your garden light sensor that could be useful lauran hat lauran Gateway so this is a luran node module so this node has a Laura W node module and an rp240 that's the Raspberry Pi Pico m C you and it has a bunch of ports for sensors they sent me some sensors to go with it and the start of the show lauran Gateway so this is the LR 1302 lauran Gateway module and then this should be the hat and it is so this is the Hat this goes on top of a Raspberry Pi it's got a built-in GPS module and a slot that fits the lauran module so these two guys talk to the p and we get a full-on Laura Wan Gateway so this guy is going to go here and he's got a built in fan to cool my pie Gateway module goes in here this is not actually mini PCI it's using the same connector but it's USB spy and I squ [Music] C get in there there a very tiny little RF cable okay got it so this is the Lura antenna this is GPS GPS guys under there we'll jump up to Lowa board so now we got the board set up up got my antenna's ready to go just got to set up the SD card so after a quick trip to Raspberry Pi OS imager I set up my Laura wind Gateway in my cat's bedroom and he is disappointed to lose that end table so I might be getting a little bit ahead of myself now what is Laura anyway well it's a technique called chirp spread Spectrum modulation so like most forms of wireless communication today it relies on modulating radio ways now we have a lot of techniques we've develop over the years as Humanity to do this including the classic amplitude modulation phase modulation frequency modulation you might have heard of am or FM or PM you can combine all of these a common technique and Digital radio is quam quadri amplitude modulation all of these are forms of modulating a signal on top of an analog carrier at some frequency and encoding some data into that so Laura uses a bit of a different technique or you I guess you could consider it a former frequency modulation essentially it creates chirps which are a linear ramp in frequency from a low frequency to a high frequency and by chirping these chirps it's easy for a decoder to find this long ramp so one of the problems of a lot of Wireless Communications is how do you work at low signal strength so lower signal strength means your transmitters need less power they save more battery and also you can decode them from further away both of which are things that are very important to Laura so this chirp modulation creates a a linear wave through the Spectrum and demodulators can look for that and find it relatively easily even through the noise so Lura is able to demodulate down below the noise floor which is pretty unique among communication systems another neat thing is that it encodes a lot of data in these chirps between seven and 12 bits of data so that's comparable to something like 496 quam which is a really high bandwidth encoding used in Wi-Fi which which also encodes 12 bits 496 symbols now don't get ahead of yourself it's not nearly as fast as Wi-Fi the downside of this modulation is as extremely slow so Laura's capacity is measured at best at about 50 kilobits per second which is slower than the fastest form of dialup and that's at its best at its worst it's measured in bits per second usually though messages on lur are limited to around 50 bytes of data which is perfectly fine if you're trying to measure sensor data even at a relatively frequent interval like once a minute you can get your sensor data transmitted back with just a few bytes so now that we understand what Lura is and why it's so useful for long range lowp speed communication let's see if I can get my Laura Wan Gateway set up so now that my Pi is set up with Raspberry Pi OS it's time to see about the software now Electro provide software for this board on their GitHub and their software is essentially direct from sech who's the maker of the chip unfortunately sech software was rather old it was last updated in like 2019 and it's kind of crusty around the edges so I made a few changes especially in the make install so it actually installs itself properly instead of leaving itself in slome slpy and also added support for IPv6 because they were hardcoding afin sockets so this is what my Fork looks like you can see all the changes I made if you really want to but I'm just going to go ahead and copy that link as we're going to use this so over on my Pi I've named it Laura the Explorer we're just going to get clone and then we'll go in [Applause] there and we'll do make after that we do pseudo make install and that should work so now that's compiled the code from Semtech it put it in user local bin which is a good place to put binaries and it created a configuration directory for it in Etsy Etsy Laura packet forward and also a system deserved and registered and all that good stuff so now we need a global config file for the Semtech packet forwarder this is what's going to forward our lower packets back to the cloud so we have some examples here to start from so depending on what region you are you might need the EU 868 or you might need the US 915 realistically you're going to need this file or this file unless you bought one of the USB versions instead of the Spy then need the USB ones our Gateway also needs an eui 64 address that's kind of like a MAC address with 64 bits there's a script here that will generate one from the MAC address the Raspberry Pi which is handy so we're going to have to Generate random numbers so to start I'm going to start with us 915 and I'm just going to copy it to Global comp. [Applause] Json so now I have a global. Json now I'm going to update the Gateway ID [Applause] so it decided to use this address that's the MAC address of e Zero by the way the Raspberry Pi eth zero is actually its name if you don't have an e zero this script will get very confused so now let's take a look at the changes I made to my configuration file for my setup they may be different for yours so take a look at this so this is a diff so we're looking at a diff here and so the Gateway ID was populated by the script I changed my server address to be tex. p.net later in the video we'll find out what this address is I increased the push timeout from 100 to 1,000 this is cuz I was testing with the things Network and with the things Network I was using their cluster in London it was about 100 millisecond round trip so I was losing some connections because of that bumped it up not a problem anymore and I also changed the GPS to be s0 because the defaults are not having one so once we're happy with this config we can copy it into Etsy low packet forward and we can start the packet [Applause] forward and now we can start it with system [Applause] control [Applause] so this is going to go through and it's going to reset the chip start it up once your cloud service is running this should respond with push a and pull ax for now though it's just going to sit there trying over and over so now our Laura Wan Gateway is set up so you might have noticed I've mentioned Laura Wan a few times in this video so what is Laura W and what makes it different from just Laura so Laura is the chirp spread Spector modulation technique developed by sech they're now sech and that is essentially a way of transmitting binary data over the air but it's not a protocol we can't speak Laura I mean we could speak Laura but it wouldn't be terribly useful us we need some sort of higher level protocol to give meaning to these bits of data and there's a few protocols out there that are based on Laura so mesh tastic is another protocol you may have heard of that's based on Laura and that's a system for sending text messages in the range of kilometers point to point between people and that's extremely useful but that's not what we're looking for here Laur Wan is a technique for sending data from low power sensors to moderate power base stations and having those base stations relay that data to the cloud so lowo Wan was also developed by sech and the low Alliance for widescale communication the goal for lowo Wan is to have nodes essentially everywhere so that a sensor is always within range of one of these nodes and since the range is something like a kilometer or two it doesn't have to be that close you don't need a ton of nodes to make this work but because it's cloudbased all of the data gets tunneled from the Gateway back to the cloud and that means that we could conceivably have Aura sensor node or transmitter move it all around the country and if we had a great enough network of gateways we'd be able to get our data back home safely now there are two networks that implement this in practice in the real world there's the things Network and there's the helium um cryptocurrency I guess you could call it which is sort of a way to give a business model to this thing paying people for running these gateways but there's nothing stopping me from running my own cloud so if I have a Gateway at my house I could run the cloud at my house too suddenly I have a fully self-contained luran node in the 1 km radius around my house and I don't know about you but I don't really need sensors to talk to me more than a kilometer away from my house so I'm pretty happy with that another neat trick from Laura Wan is that all the communications are encrypted and identified so every node has a unique ID and unique key that's generated and programmed into it at the factory usually they have a QR code sticker on them or for devices we program in our doino we write it in oursel and we know what it is and if we put those numbers into the cloud it can establish a session create session keys and the sensor can securely send data but this encryption is done all the way back to the cloud the gateways aren't involved at all so we don't have to trust the gateways with our sensors we just have to trust the gateways exist and we're in range to relay our data luran also gives us the ability to send packets to port numbers so it has an 8bit port number so we can send up to 253 different ports kind of like a UDP Port message it's not session oriented like TCP but we can send small packets of about 50 bytes to up to 253 ports which is plenty for this kind of low power sensor stuff so in my case I'm going to set up the sensor board later in the video I can hook up multiple sensors to it each sensor can broadcast this data to a different port number all that data makes it way back to my Gateway ultimately my cloud and from there I can get to home assistant so future Apple art here I actually realized in editing I forgot to mention you can send data down in addition to up so one of the big differences between Laura and some other protocols that we never wake the device up so the device cannot be woken from sleep except from its own timer so if we want to send a downlink message to a device we cue it in the cloud on the chirp stack and we just wait for it to respond and then once it sends a message up we have a few seconds where the device will stay awake and let us send messages back so if we want to reconfigure a device say we want to tell it to send data every 5 minutes instead of every 30 we have to wait for that next 30 minute ping and as soon as we get that data 30 minutes we have a few seconds send a packet back down the node will receive it we're all good so you really can't use this for real time interactions but you can do this for things like changing schedules changing settings it is bidirectional in that sense so now that I have the electro Gateway set up and running let's get the open- source chirp stack Laura Cloud set up get our data piped into home assistant so I hope the architecture of Laurel Wan makes some more sense to you we have the cloud service that's where all of our encryption happens that's where managing a devices happens then we have these gateways located potentially all over or maybe just one that are sending our traffic from the airwaves back to the cloud if you have a large property you could put these in a few different places the range is really good though so I'm going to have a hard time finding need for more than one Gateway locally but certainly possible now we already set up one Gateway earlier in the video if you set up more they'd follow the same process and so that's the Semtech packet forwarder the first step there are three four other pieces of software we have to make work to integrate this all together so there's chirp stack itself this is what processes the low W packets now chirpstack uses mqtt to transport its data so if you don't already have an mqtt server Network you need to set one up too I'm going to assume you already have one set up from home assistant that's what I have then we need a way to get the packets from the sutech packet forwarder into chirpstack and chirpstack provides a bridge for this it listens for the UDP protocol from sech and converts that to the mqtt protocol that chirpstack expects you can run this bridge either on the Raspberry Pi or the server that runs chirpstack and actually if you want you can run all three of these parts the Semtech Gateway the mqdt server the packet forwarder uh for trip stack and SHP stack itself all on the same Raspberry Pi if you want you can follow their instructions for Debian they have packages compiled for arm 64 so coming over here to the chirp stack instructions I clicked on Debian Ubuntu it says Ubuntu 22 and Debian 11 but I tested this on Debian 12 and it was just fine now I created a container in proxmox you don't have to you could run this directly on the Raspberry Pi if you want but that's what I did so I'm not going to walk through the exact commands here because this is actually written very well but you can basically follow through their commands to get the software set up so you add an app repository they have packages for x86 and for arm 64 you install the Gateway Bridge that's what goes from Semtech to mqt you configure it for your region and then you can start it or enable it then you can install trip stack itself and create a config file so I'm going to show you now the configuration settings that I used for my config they'll hopefully help you create your configs so first we'll look at the Gateway Bridge so this is all default type of SE Tech UDP so I change UDP bind from 0.0 to colon colon just to enable IPv6 then down here it defaults to EU 868 I think but we need to change it to a frequency plan and a channel number so in Laura Wan every Gateway supports eight channels of the 64 possible frequencies I guess the exact number depends on what region you're in in the US there are 64 possible frequencies they're broken up into eight channel groups so a given Laura WAN network chooses one channel group for the entire network this is eight frequencies I have chosen Channel group one for this purpose it's the same one of the things Network uses that's why I chose it a lot of software defaults to using this channel group the individual devices will use one of eight frequencies in the channel group but they use a different one for each transmission and the gateways support all eight at the same time so here us 9151 so that's the second because zero is the first and and then in this case my mqtt server is on Local Host so I just put that in and I'm running without encryption right now or authentication so you would put in your mqtt information here for your mqtt server so next up we have the chirp stack config for the app itself so going all the way down there's a network identifier so in Laura Wan Transmissions include a network identifier which is three bytes this is how you identify like individual Network so helium has one the things network has one the things industries who run runs the things Network supports multiple of these if you're just testing on your own you're supposed to use the number zero or the number one those are both reserved for testing there's no organization that publicly assigns these so it's kind of messy if you use other numbers so then I come down to enabled regions and I commented are everything except us 9151 which is the frequency I'm using so further down I again change the bind from 0.0 to the IPv6 version um there's a secret here supposed to replace that you probably should do and then I'm using Local Host again for this again you can use whatever mqd server you're using and so that's what basic infig of chirp stack looks like let's go into the gooey and see how it looks in the web interface so once you get chirp stack running it's on Port 880 the default username is admin and admin and let's go so chirpstack is one of these new fancy applications that's designed to scale so it's a reports multi-tenant multi- application per tenant um I'm not operating this big of a scale so I don't have I'm not using multiple tenants I'm only using one application and it's kind of big for me but it is what I have so in my tenant down here I can look at my gateways so I have this guy here this is lur of the Explorer I created earlier I'll walk through how to set that up in a minute and then I have device profiles so I created a device profile for basic node and again I'll walk through that in a minute um and then I have applications so I created an application called home within the application we have devices so each node has a node profile it has a name it has an eui and it's bound to an application within a tenant so that's kind of the hierarchy of how things work each application also supports Integrations this is where data goes so if you're using this kind of a scale you would have sets of sensors each I guess type of data you're doing or each back end would have its own application so if you have some sort of data monitoring and then you have some sort of other project that's using luro separately they could be separate applications within your tenant and each of them would have its own devices assigned to its application and the data would go back to the back end in my case all the data is going to mqtt so I just need to have an application there so I created home if I had more than one location I could do that it's up to you it's flexible the gateways are not bound to an application they're just bound to a tenant so they'll handle all the data from all the different sensors one Quirk I found here that drove me crazy is all of these Integrations you can choose plus to add except mqdt just says get certificate and I could not figure out why I couldn't add it and it turns out it's just enabled by default so there's no need to add it if you want to use mqtt the mqt integration you just connect to the same mqtt server that tripack already using the data is all there so now I deleted my Gateway so let's go through the process of creating a gateway it's pretty easy we just click add Gateway we give it a name so I've got Laura the Explorer and I just need the eui 64 so over here un lower the Explorer I have this as my Gateway ID so we'll copy that paste it in you can give it a description if you want it's in the Cat's bedroom it's named Lura the Explorer it's located in the middle of the ocean this will figure itself out in the future fut and we submit so now if I go back to my gateways and I refresh should pop up within a minute or so there we go it took it about a minute it's there if I click on it so that's another reason these things have GPS the GPS of the Gateway gets sent back here it's possible if your application wants to try to triangulate sensors all the data is available in the Integrations to do so if you want to do that I'm not doing that so while I am going to demo a completely custom Laura w node using the electro board I actually went out and I bought a temperature and humidity sensor just to see what a commercial off-the-shelf device looked like this was not that expensive I'll put the price on the screen somewhere it comes with a battery that lasts basically forever and it's got temperature and humidity and we're going to pair it box it came in includes all the numbers I need all the security codes so I'll just have to type those in so I stopped and read the manual for this this guy has temperature and humidity it's preconfigured with the frequencies of the things Network so me using the same frequencies is a good idea so before we push the button in this guy we're going to go into trip stack configure a device type for this model that tells it how to decode the data then we're going to create this specific device with the eui and all those other information then we can have it be so here in device profiles we can create types of devices so this is like a device model and it includes information on how to decode the data you can create templates up here if you have multiple tenants it have multiple tenants so I'm just creating profiles here in my tenant so this is a lht 65n so that's my name so region is going to be us and we're going to be on channels 8 to 15 the lower version is 13 in this case and we're on parameter set a and everything else is good and we're not going to all roaming so roaming is a neat feature of Laura Wan where your network can roam with other networks so I could for example roam with the helium Network so my sensors are on my own network when I'm at home when I go out they use helium likewise people could use my gateways as helium gateways um I'm not going to set that up but it's possible so that's this page next we have join most of the time we use otaa which means it's automatic we're not manually setting Cipher parameters Class B and Class C devices wake up less frequently this is not a Class B or C device and then codec so this this is how to decode the data if we say none it's just going to keep it as binary we can come down here and say JavaScript functions and then we need to write a decode function I bought this node from dragino so I can come down here and look for their decoder lht 65n I want the trip stack 4 decoder we'll just go raw don't translate it and we'll just copy and paste that in so let's submit and so now the lht 65n with its codec is created so I go to Applications home I don't have any devices yet so let's add a device what are we going to call [Applause] this now we need some information so we need the devices eui 64 and this is called the join eui 64 sometimes it's also called the app eui 64 and in my case they came on the inside of the box so I'm going to type these out there is a QR code that has the device eui 64 it doesn't include the security code which I'm going to do later and device profile we're going to pick lht 65n that we already created and device is not disabled because it is real let's submit that now it's going to tell us it needs the application key this is the security key and we'll type that one out so now that our device is created we can tell it's a join when it joins it's going to send out a broadcast and it's G to try to find a Gateway that can decode its app ID and since our Gateway has already been configured it should be just fine so I should be able to just push the button for 5 seconds let's see if this works two three four oh it's blinking I oh look at that I checked in so this is what it looks like in mqg Explorer I'm connected to my Gateway tripex so the us991 five topic has information that's not relevant but that's internal to trip stack and under application I have the uuid of home here is The UU ID but that's The UU ID of home and then I have device and then I have the MAC address of the device or the eyi of the device and event and we had an Uplink and so let's look at that Uplink data so data is that garbage and then decoded we get battery status 3 temperature there so I just got another packet so it overwrite the data so humidity is 33 temp DS that must be the external sensor and then sht that must be the internal sensor this guy's fun and all but I'm going to build my own node with this board ofro sent me show you how this works too so you can build your own nodes mix and match with the Shelf nodes in your lower Network so so next I'm going to make my own sensor node to send data to Laura Wan parse that data back out in mqdt and get that into home assistant now there are a number of chipsets you can buy that do Laura some of them also do Laura Wan the chipset on this board is the r8h it does Laura Wan it's entirely self-contained we just have to configure it using AT commands on the serial port and it's not that hard to do Electro has two versions of this board one version of the board just has the r88 some level shifters and the antenna Jack you can get that if you want to use your favorite microcontroller if you don't want to use your favorite microcontroller they also have this board available that I have which includes the rp240 that's the chip from the Raspberry Pi Pico and this acts just like a Raspberry Pi Pico you can program it in Arduino so we got the pi Pico the r8h which is the loroan chip set we got some sensor interfaces on the back uh there's a connector for a battery I actually have a battery battery so this is a single cell lithium battery they're super common easy to find just plug it right in and it's got a connector for a solar cell too so this could make a really great outdoor battery solar powered node never need to change the battery if your solar panel is big enough you're not transmitting forever so that's what I got for this project going into this I'm going to assume you've already set up the Arduino environment for Raspberry Pi Pico there's plenty of guides on that part on the internet once we have that set up we can start downloading code to this now there's no library for the r808 that I could find so I wrote some of my own functions if you go to my GitHub page there's some example code you can start from how to transmit data so coming over to my GitHub this is currently what the ra8 looks like so Laura ra8 and basically each of these folders is an Arduino project so Arduino demands that the Ino file is in the folder of the same name so node and IO has to be in the node folder so I've got three Arduino files so the first one's called app key and what this one does is it generates a random eui 64 so using the random function and it generates a random Dev eui app eui and then an app key which is 128bit random number that's used in the cryptographic process when you buy a lower node they're supposed to come pre-programmed with these numbers the ra8 comes programmed with all zeros so not terribly secure is it but we can just override it over the serial interface so just download this run it once it'll spit back out your eui 64s and the app key you'll need those later so save them once you've done this once the keys are set they're stored in Flash so you don't have to run that program again also of slight note I'm using the rp240s hardware random number generator if you are not using rp240 you have to comment that out and use the regular random function which might not be as good so up next I have a simple debugging program that just passes at commands back and forth basically the um ra8 is a Serial Port the USB is a Serial port to the computer it just Bridges those two so you can type in commands and read them back and see how they look currently my third program is called node and this program is just going to send a number every so many seconds so currently that's set to 10 seconds so 10,000 milliseconds so all the way at the bottom we have this function ra8 xmit so that takes a bite array and it takes the port number and the number of bytes and some other information and transmits that over loroan so this is currently just an example every time it transmits it increments its counter so we're going to get a two byte value that's the number of times it's counted if you watch it carefully it's also blinking so we'll do a long blink for a 10 and a short blink for a one this is how I do range testing I carry this around with me I look at it closely I'm like ah that was a 22 then I get back home I look at did I receive number 22 if yes then it must work at that range so I also wrote a simple decode function for this this is going to be on the GitHub as well once I'm done with it basically you get decode Uplink which has the Uplink port number and a bite array and you return a JavaScript object that has all your data so I'm just saying if fport is one then we decode it as a 16bit integer and return the parameter count so coming over here to trip stack let's add a device profile for my custom [Applause] counter and it's in the US region again channels all that good stuff and then we want a codec we want to use JavaScript so we'll paste that in so like I said decod Uplink trip stack will give us an input that includes these three Fields so bytes as a bite array fport is the Uplink Port that's 1 to 253 and device variables so we just return an object and then we can add any variables we want to the object and that gets sent to the output so I'm just taking this as a two byte number because that's what it is it's in big NN so let's go over here and let's add my device so here's what I ended up programming into it so that's my Dev eui device profile as a counter so let's submit that and we need the key so I have this thing configured to join every time it boots up so that assumes it will stay booted up the whole time you don't have to do that but I'm not sure how to persist the join information into nonvolatile memory on the ra8 so maybe someone who wants to read the data sheet more could figure that one out so I'm just going to unplug it when I plug it back in it'll do a join and then we'll see it come up okay so I refreshed a few times this took maybe a minute but it is up so we can look at it and it sure is up so popping over here to mqtt explor that's my eui so we look at the Uplink data and object count there we go count one now count is two so this is basically how I'm creating lauran nodes for the sensors I have so using the ra8 board either the one with the p Pico or without and set up some sensors read the sensors in convert it to B bytes send it over Laura Wan code the btes in JavaScript that gets me to mqtt so now the data is in mqtt we just have to get into home assistant from here so finally we've set up the Gateway we've configured chirp stack we've configured all of our codecs for all of our devices we've joined our devices now our data is in mqdt we can finally get into home assistant so here's an example of what I want to happen at the end so this is a value that came from the sensor it's just a counter that counts up I have another version of it where I'm calculating a floating point value some sort of scaling I assume you'll probably want to send data that has decimal places instead of just integers the easiest way to do that is just to multiply it by like 10 1006 256 something like that and then divide it back out in JavaScript so instead of trying to send a full range floating Point number either a half or a single or double or whatever so you just make it a fixed Precision single point send it in binary convert it back so we're going to have that and then I also want to get the RSSI and signal noise ratio from our reception here so just showing what I mean about this decode float so if I take this number that's a 16bit number and I just divide it by 100 until JavaScript it's a flat then we could say this is now a percentage maybe it's a deg celsus so for example if you want to send degrees celsus you could just multiply it by 100 send it as an integer and then divide it by 100 when we get there so we get two decimal places hundreds place so for this setup we have to use manually configured mqtt entries this means we're going into configuration. yaml if you're the kind of person that has a lot of structure to configuration. yaml you probably know where your mqtt entries go you might have your own file for them I don't know but I'm just going to put them straight in configuration. yaml you'll probably know where this goes if you're doing something more advanced also got the documentation from home assistant up here so it says we should start with an entry that looks like this I'm just going to copy this and paste it in and so we're just going to call this the [Applause] counter counter value so now we need a topic and we need a way to parse it so coming over to mqtt Explorer here's our data here's the up so I can just scroll on this side and it's a long string here and I can just click copy don't have to worry about figuring out all those uu IDs so we'll come over here and we will paste so now the problem is if we don't tell it how to parse this it's going to assume it can just turn it into a number so home assistant is going to get this topic and the value is going to be this huge Json struct so we need to un Json the Json struct so home assistant has a much longer example here of all of the different options we can have so we can use unit of measurement we can use value templat so I'm just going to copy these two and in value template we use a ginger template Ginga is really commonly used in home assistant and so we can parse values out of the Json so if we come over here so that's the root objects that' be value Json and within that object we have an object called object we have an object called count so we need doob do count Val json. object. count so let's save that let's see how this goes so there we go we got a counter value of three so what about the rest of those numbers they might be a little bit hard four a little bit harder to parse so now if I want to make a new one we'll just copy and paste this so now instead of value we want percent and that one can be float and we can add a unit of [Applause] measurement while we're at it let's do the other ones as well so this is going to be [Applause] [Music] RSSI [Applause] MTP and SNR also in DB so back over here at mqdt Explorer so we have the data from object count float and our RSSI and SNR are within this RS RX info structure so that's in a array and it shows all the different gateways that received it and so we need RSSI and SNR out of the first receiver I'm just going to assume that the first receiver is the good one so this would be RX info z. [Applause] SNR and this one would be RX info z. RSSI so let's see how this works so there we go we got an update so it's 10 is the value divided by 100 we get 0.1% um so we have two decimals there and we had an S&R of 10 which is positive which is pretty good lower can go down to like -10 or so without problems and our RSSI which is the signal strength is 87 DB negative 87 DB so now we finally got our data into home assistant where it belongs so thanks for sticking with me on this whole video as I go through the ins and outs of setting up a Laura Wan system completely self-hosted for all of your iot sensors and home assistant hopefully this video inspired you to do something cool monitor some Far Away sensors do something like that of course you can buy sensors for loroan off the internet I bought this temperature humidity sensor there's a lot of sensors for things like soil moisture soil PH things like that if you're doing gardening this could be very useful for you I found someone else on YouTube who's used Laura from monitoring his mailbox it's too far away for a lot of other protocols but Laura works just fine or maybe you want to build your own thing with the node board like I showed in this video it's all up to you if you want to buy any of the products I used in this video links are down there in the description thanks to Alro for sending me this Gateway module to play with I had a great time with it hopefully you guys learned something too um we're losing him if you want to join my Discord server link down below for that as well if you're interested in tipping me for any my content if you find it useful link to Kofi down below you're free to donate I always appreciate it and as always I'll see you guys on the next adventure

Channel: apalrd's adventures

Views: 9,088

Keywords:

Id: HWF6Qm7JhJU

Length: 40min 14sec (2414 seconds)

Published: Sat Mar 23 2024