reef-pi :: An opensource reef tank controller based on Raspberry Pi.

2^64 addresses to ping in a smallest v6 subnet, so that method doesn't work. SLAAC also requires no coordination, and RADV can be unidirectional, so those devices just disappear. But the apps need to find the devices, so its a matter of a little reverse engineering (how the Kasa line started anyway)
Yeah I understand, not sure Kasa is supporting v6 though, my guess is it's only IPv4 but now you have me curious and will have to do a network capture and see what they are doing. this may be interesting...
 
From what I see at least from my laptop capture they are doing a udp broadcast and they target 2 destination ports 20002 and 9999

Kasa-capture.png
 
Thought I would post here and see if I get some input for how folks are discovering devices on their network, like when they need to know what the address is for a new reefpi and/or kasa strip/outlet etc. Most of use advance folks just reserve the IP/mac address in DHCP so when it comes up its assigned the same value. But wanted to see what other folks use for network discovery, looking for options and something easy to help folks out when needing to figure out IP addresses for stuff.

The old fashioned drop to a prompt and broadcast ping and then look at the arp table works but wanted to see what other ideas are out there.

Thanks :)
I use google mesh wifi , that allows me to check individual device ip and MAC address. I make sure I rename each device (I have around 230 of them ) to something I can understand. Every device generally has mac address printed on their housing as per regulatory requirements
 
I use google mesh wifi , that allows me to check individual device ip and MAC address. I make sure I rename each device (I have around 230 of them ) to something I can understand. Every device generally has mac address printed on their housing as per regulatory requirements
Yeah really I thought I had a bunch of stuff on my network, thats a bunch of stuff. :)
 
I use google mesh wifi , that allows me to check individual device ip and MAC address. I make sure I rename each device (I have around 230 of them ) to something I can understand. Every device generally has mac address printed on their housing as per regulatory requirements
I'm with you Tom, I thought 65 devices on my network was a lot...
 
I'm with you Tom, I thought 65 devices on my network was a lot...

Same. And I even have multiple VLANs, multiple APs and multiple wireless networks to seggregate all the devices so its not just one huge multicast mess.

But all of my light switches are dumb, I imagine that adds up fast.
 
Has anyone ever seen or experienced this, I have a semi new rpi zero 2 w that I bought over Christmas and moved it to my main testing rig and have noticed something that not sure what the issue is. Normally if I pull power and re-apply power they come right up, I am noticing with this unit it doesnt always want to boot, in other words I apply power and do not get the led to light up. Even if I shutdown power properly, remove and then apply it doesn't always come back on. If I let it sit and/or try several times it will eventually come back up, just never seen this behavior before and not sure what it could be. Tried different power feeds but I really do not think it's that, I think it may be related to the micro sd card, I know it won't boot if it doesnt see a card and boot images going to try a different card and see if it behaves differently.
 
Same. And I even have multiple VLANs, multiple APs and multiple wireless networks to seggregate all the devices so its not just one huge multicast mess.

But all of my light switches are dumb, I imagine that adds up fast.
I have a few smart light switches, and a butt ton smart outlets, but sounds like @Ranjib never has to touch a switch or outlet..

I do have an impressive collection of ESP32 devices... and my raspberry pi collection is starting to get to the point that my family worries about me.. ;)
 
Has anyone ever seen or experienced this, I have a semi new rpi zero 2 w that I bought over Christmas and moved it to my main testing rig and have noticed something that not sure what the issue is. Normally if I pull power and re-apply power they come right up, I am noticing with this unit it doesnt always want to boot, in other words I apply power and do not get the led to light up. Even if I shutdown power properly, remove and then apply it doesn't always come back on. If I let it sit and/or try several times it will eventually come back up, just never seen this behavior before and not sure what it could be. Tried different power feeds but I really do not think it's that, I think it may be related to the micro sd card, I know it won't boot if it doesnt see a card and boot images going to try a different card and see if it behaves differently.
Looks like it was just a dodgy sd card, I tend to have a bin full of them and re-use them and every now and then they come back and bite me. Swapped card and it's acting normal now...:)
 
I'm with you Tom, I thought 65 devices on my network was a lot...
I have more than a dozen reef-pi running on tanks, as house temperature monitors, as model railroad controller , for seed starting rack , garden stuff etc. then there are half a dozen Wyze camera, around a dozen of Shelly in wall outlets , while bunch of kasa products , laptops, desktop, octoprint and the list goes on and on .. :-) . I need to move to ubiquity .. google mesh does not work well beyond 150-200 devices
 
Same. And I even have multiple VLANs, multiple APs and multiple wireless networks to seggregate all the devices so its not just one huge multicast mess.

But all of my light switches are dumb, I imagine that adds up fast.
I need something like that.. soon
 
I have more than a dozen reef-pi running on tanks, as house temperature monitors, as model railroad controller , for seed starting rack , garden stuff etc. then there are half a dozen Wyze camera, around a dozen of Shelly in wall outlets , while bunch of kasa products , laptops, desktop, octoprint and the list goes on and on .. :) . I need to move to ubiquity .. google mesh does not work well beyond 150-200 devices
Eh ubiquity is not that great, use it at several locations that I support, the hardware is not too bad but the software leaves a lot to be desired. Controller makes managing things easy but not sure you will find that the mesh is any better, most likely you will find its worse, YMMV. To get the real stuff is not cheap, Ruckus, Aruba etc etc...
 
Eh ubiquity is not that great, use it at several locations that I support, the hardware is not too bad but the software leaves a lot to be desired. Controller makes managing things easy but not sure you will find that the mesh is any better, most likely you will find its worse, YMMV. To get the real stuff is not cheap, Ruckus, Aruba etc etc...


I switched recently to a mikrotik router at home. I've been very happy with its performance. I've been using TP-Link Deco for WiFi and am not exactly thrilled with it. May move to mikrotik on that as well.
 
Saltwateraquarium.com did a video coverage on reef-pi, anchor is one of my favorite, Mark Callahan

That was really nice video @Ranjib. One thing I would have pointed out to the interviewer is that with some of the newer board builds you do not need as much electronic knowledge as you once did, always helps but heck some of these plug and play units are pretty easy. :)
 
That was really nice video @Ranjib. One thing I would have pointed out to the interviewer is that with some of the newer board builds you do not need as much electronic knowledge as you once did, always helps but heck some of these plug and play units are pretty easy. :)
Yes , we have come a long long way :-0). I really need to update / work on docs . That was a consistent feedback.
I was thinking what if we start build guides here, now that we have dedicated forums section. We can maintain the guides here with community backed edits
 
I am going to post this here and see what I am missing, I am trying to clone a rpi image and pretty sure this has worked before, but when I create the image the /rootfs partition is not recognized. I am using DD and not doing it from the rpi booted, but for whatever reason the /boot partition is fine but the /rootfs is not. Just using plain ole dd if=/dev/sda of=/pathtoImage.img

Not sure why its not working..anyone has any thoughts let me know..:)
 
I've never had much luck with cloned images via dd..

Anymore, I just keep a folder of stuff to copy over and install fresh, if it's only doing reef-pi..
Yeah it's not working for cloning an rpi image, no idea since it should be a bit for bit copy...really kind of odd but the ext4 partition is unrecognized. Clonezilla works but it does it using partclone I believe. Kind of stubborn but not sure why it's not working, really odd...
 
I am now back up and running reef-pi again! Lots of new development since the last time I ran it. I have been using reef-pi since June 2017 (I think beta builds back then) but I moved cross country in 2020 and sold off my old tank. I just set up a new frag tank, booted back up reef-pi, and upgraded to the latest version! Nice the see the project is still going strong. I now have a pretty complete Neptune Apex system and some Focustronic devices but I love tinkering and reef-pi is awesome for that
 

TOP 10 Trending Threads

Back
Top
Home
Post thread…
Market
What's new