My experience with Zigbee has been poor, but I think it's because so many manufacturers bend the specs and there are incompatibilities. Z-wave just dosen't have those kinds of device specific incompatibility issues.
I like that too, but WireGuard can be used in same way, and you have it little bit simplified. Both work over different media, even over DMR ! Because in Unixy you can pipe anything to anything. Reticulum is awesome for big groups where people do not always have to know each other.
Nicely explained! I started monitoring the Amsterdam Botanical Gardens using a few LoRa sensors and Home Assistant with the MQTT sensor integration and it works pretty darn sweet. The only drawback so far is that it gets quite messy quickly since the HA yaml config file gets a ton of duplication for all the sensor data. Not sure how to fix that problem yet without making a ChirpStack integration.
It might be possible to write a Chirpstack integration that just generates Home Assistant MQTT discovery entities, or maybe have a script that does that periodically. Basically, you can take the yaml configuration and publish it over MQTT to a well-known topic path, so software that's HA aware can push its own configuration over MQTT and HA will discover and add it automatically.
@@apalrdsadventuresThanks! Yes you're right, doing it the other way round and creating a ChirpStack Integration that pushes the HA MQTT discovery is probably the most elegant way to handle this.
Cool. I still don't know where the LoRa WAN module is stationed. Is that outside somewhere...perhaps I missed the diagram on how it was setup. Cool project regardless. LoRas for everything nowadays.
Great video! Any reason this wouldn't work with a RPI 3 B+ ? Do you run Home Assistant on the RPi and push the cloud data back down for to RPi for display?
My board also uses the SX1302 (it's an 8ch LoRaWAN gateway), so it's just different software. Looks like RAK provides Pi OS images which support both Semtech UDP and Chirpstack, so yeah it should work the same way.
Hello @apalrd's adventures, Its a great video with step-by-step explanation on the loraWAN setup. I really appreciated. I have also ordered and assembled the same hardware from Elecrow and give a try to setup loraWAN gateway with your this setup video explanation, but I am sorry and afraid to say that some of your setup commands not working for me. Could you please assist me to fix it? Thanks.
@@apalrdsadventures Thank you for your prompt feedback reply. its so nice of you. I have joined you at discord and will mention the error I am getting to be reviewed by you to fix it. Thanks.
I just wonder why you didn't went with WIFI HaLow, still gives you at least 1 to 2 Km of range, much faster speeds, and can seamless be integrated in any existing network infrastructure.
Mostly because there are so few devices that natively support HaLow. Most of the HaLow devices I've found are either bare chipsets or HaLow to Ethernet bridges, not complete products.
@@apalrdsadventures well, I pick up a couple of this for less than 50 bucks not expecting much of it, I'm only using one as an access point, dam, this thing gives me internet form 2 km from the house! 16 Mbits at 2 kms! :), I quite impressed by it so far.
Is the MQTT server/broker running on Proxmox, is it a VM or CT? Is the MQTT server/broker mosquitto? Is Home Assistant a VM or CT in your setup? Great presentation.
I am using the MQTT server I already use for Home Assistant, which in my case is Mosquitto in a CT. Home Assistant is a VM (HA OS). I have been using MQTT longer than I've been using Home Assistant (I started with MQTT + Node-Red), so I didn't use the HA OS addon, but that's also a good choice if you are using HA OS. You can run Mosquitto in the same CT as Chirpstack (or on the Pi directly, if you run Chirpstack on the Pi) if you'd like. It doesn't really matter who hosts the MQTT broker.
Not with redundant brokers. All of my HA stuff is running on Proxmox, and I have a separate Proxmox system for the 'important' stuff that I don't mess with regularly.
I think that I have found another project to keep me busy when I retire. Absolutely fascinating.
Home Assistant on the whole is plenty to keep anyone busy
I swear every time I’m thinking about something, you make a video about it. Great work as always.
Enjoy :)
Just forked the vendor's library, wrote examples for the node module and posted it under the bsd license.
You make it look easy :D God bless
Love the deeper dive into code in this video!
Another fantastic video! Wanted to say just after 33mins there's lat/long on-screen. Don't want you to dox yourself!
Thanks for letting me know! I thought I caught all of those.
Very Nice, thanks
What a great video.
Glad you like it!
Few years ago I did some subghz 868/915 zigbee development. 600m was the limit with our setup.
My experience with Zigbee has been poor, but I think it's because so many manufacturers bend the specs and there are incompatibilities. Z-wave just dosen't have those kinds of device specific incompatibility issues.
I think you'd appreciate the reticulum project I recently found it and think it is really really neat lol
I like that too, but WireGuard can be used in same way, and you have it little bit simplified. Both work over different media, even over DMR ! Because in Unixy you can pipe anything to anything. Reticulum is awesome for big groups where people do not always have to know each other.
Nicely explained! I started monitoring the Amsterdam Botanical Gardens using a few LoRa sensors and Home Assistant with the MQTT sensor integration and it works pretty darn sweet. The only drawback so far is that it gets quite messy quickly since the HA yaml config file gets a ton of duplication for all the sensor data. Not sure how to fix that problem yet without making a ChirpStack integration.
It might be possible to write a Chirpstack integration that just generates Home Assistant MQTT discovery entities, or maybe have a script that does that periodically. Basically, you can take the yaml configuration and publish it over MQTT to a well-known topic path, so software that's HA aware can push its own configuration over MQTT and HA will discover and add it automatically.
@@apalrdsadventuresThanks! Yes you're right, doing it the other way round and creating a ChirpStack Integration that pushes the HA MQTT discovery is probably the most elegant way to handle this.
Your a pretty cool dude.
nice. thx
Cool. I still don't know where the LoRa WAN module is stationed. Is that outside somewhere...perhaps I missed the diagram on how it was setup. Cool project regardless. LoRas for everything nowadays.
Great video! Any reason this wouldn't work with a RPI 3 B+ ? Do you run Home Assistant on the RPi and push the cloud data back down for to RPi for display?
It should work fine on the 3B+. I'm not sure if the Pi 3 would be powerful enough for Home Assistant.
I don't run HA on a Pi, just different radios.
Very Fast explanation, but this incredible
Is it possible to repeat such a project on a RAK2287 Semtech SX1302?
My board also uses the SX1302 (it's an 8ch LoRaWAN gateway), so it's just different software. Looks like RAK provides Pi OS images which support both Semtech UDP and Chirpstack, so yeah it should work the same way.
Hello @apalrd's adventures, Its a great video with step-by-step explanation on the loraWAN setup. I really appreciated. I have also ordered and assembled the same hardware from Elecrow and give a try to setup loraWAN gateway with your this setup video explanation, but I am sorry and afraid to say that some of your setup commands not working for me. Could you please assist me to fix it? Thanks.
Can you contact me on email or discord? Let me know what errors you’re getting
@@apalrdsadventures Thank you for your prompt feedback reply. its so nice of you. I have joined you at discord and will mention the error I am getting to be reviewed by you to fix it. Thanks.
do a followup when you add more devices
I like your Linux is Awesome shirt… where did you get it?
It's from vkc.sh (Veronica Explains)
Why you didn’t consider a Mikrotik LoRAWAN router instead the raspberry pi?
Mikrotik's LoRaWAN gateways cost more, that's basically it.
bloody hell: snow? I did not see it for last 25 years ;-)
I just wonder why you didn't went with WIFI HaLow, still gives you at least 1 to 2 Km of range, much faster speeds, and can seamless be integrated in any existing network infrastructure.
Mostly because there are so few devices that natively support HaLow. Most of the HaLow devices I've found are either bare chipsets or HaLow to Ethernet bridges, not complete products.
@@apalrdsadventures well, I pick up a couple of this for less than 50 bucks not expecting much of it, I'm only using one as an access point, dam, this thing gives me internet form 2 km from the house! 16 Mbits at 2 kms! :), I quite impressed by it so far.
Is the MQTT server/broker running on Proxmox, is it a VM or CT?
Is the MQTT server/broker mosquitto?
Is Home Assistant a VM or CT in your setup?
Great presentation.
I am using the MQTT server I already use for Home Assistant, which in my case is Mosquitto in a CT. Home Assistant is a VM (HA OS). I have been using MQTT longer than I've been using Home Assistant (I started with MQTT + Node-Red), so I didn't use the HA OS addon, but that's also a good choice if you are using HA OS.
You can run Mosquitto in the same CT as Chirpstack (or on the Pi directly, if you run Chirpstack on the Pi) if you'd like. It doesn't really matter who hosts the MQTT broker.
Have you setup the MQTT broker (Mosquitto) for HA, to avoid that single point of failure issue?
Not with redundant brokers. All of my HA stuff is running on Proxmox, and I have a separate Proxmox system for the 'important' stuff that I don't mess with regularly.
ah lora....ive set on the first row before
So you probably know all of the LoRaWAN gateway options then
@@apalrdsadventurescrazy youtubers just watch but dont rake notes...
audio needs a 6db boost