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

+1 for this...
I'm working on a build for a power bar right now that solves a lot of challenges, but I can foresee a similar modular approach across the board.
My build is to add upon Ranjib's power build (props for ripping apart that Prime strip to get the 5V PSU and surge circuitry), but I'm using 2 Arduinos* to do the actual power relay control, interfacing with Reef-pi as an i2c device. I could see the same for a doser module, a sensor cluster module, etc. Let the RPi do the high-level stuff and leave the realtime down and dirty to modular boxes.

*Why Arduinos? First, <5 sec boot time. Return power to the critical components faster after a hard power failure. Why 2? High availability. One primary, one secondary, sharing state. If the primary fails, the secondary takes over. Reef-pi would be able to write state changes to ports and store persistent (power-on) states to the 'duino, and use it as a power sensor.
Esp32 modules would work here as well!
 
Very strange, I do have port forwarding enabled for 443 so I can access anywhere from my phone. I am not sure why a reboot happened, we are having ice and snow storms although I dont think bad enough to hit power. I only took a short snip of the logs I may have to look a little closer when I get home.

Ymmv but I would never port forward to my internal Network even over 443, that's just me I'm an infosec person so just see way to many bad things going on but that's just my .02.
 
Ymmv but I would never port forward to my internal Network even over 443, that's just me I'm an infosec person so just see way to many bad things going on but that's just my .02.

I dumbed it down a little. I have a DMZ setup with a second router. Still not the best solution but its what I had on hand.
 
Much prefer wired everything. My original LEDBrick lights still run BLE and... yeah, if you don't need it, don't use wireless :-D
Thats what attracted me to reef pi, everything wired, Im not a fan of everything having to reach the cloud to be connected... but some wireless modules could be useful.
 
This would be fantastic. Bonus points if it can rasterize the dashboard charts (= dependencies :))
we can do some server side rendering.. or use plotlib/R stuff to generate graphs.. I'll think about it
 
I was thinking about something but on my simple level of a cron job (how often is up to you) tailing the last 50 to 100 lines from syslog and sending that via email, reef-pi is pretty chatty so should be a pretty good summary, maybe make it 200 lines..what I was thinking for health check in, quick and dirty but useful.
One improvement may be . Use the API to get some data instead of syslog. Or use some fancy grep to get relevent stuff from syslog
 
So all this talk about failures. I looked at my dashboard and my historical CPU usage had been reset along with historical ATO and heater usage. My dosers missed the normal dose at 11:05 and dosed at 11:22 instead. I looked at aadafruit IO and noticed a dip in my lights at 10:44 and also noticed my CPU usage dropped to zero around 10:17. So I went and checked the logs and something strange happened. I am not home so it may have been a power outage and all appears to be running on the screen lol I will know more when I get home tonight. But I looked through the logs and found some strange stuff. Looks like at 10:17 reef-pi rebooted for some reason? I am not sure about the TLS handshake error that coincides with my lighting dip in adafruit IO but I am assuming maybe a communication error with IO? I dont recognize the IP address but I x'd out the last two octets just in case.

Feb 12 10:43:57 myReef reef-pi[308]: 2019/02/12 10:43:57 http: TLS handshake error from 143.85.X.X:56111: EOF

Feb 12 10:43:57 myReef reef-pi[308]: 2019/02/12 10:43:57 http: TLS handshake error from 143.85.X.X:52124: EOF

Feb 12 10:43:58 myReef reef-pi[308]: 2019/02/12 10:43:58 http: TLS handshake error from 143.85.X.X:59768: EOF

Feb 12 10:43:58 myReef reef-pi[308]: 2019/02/12 10:43:58 http: TLS handshake error from 143.85.X.X:52107: EOF


Feb 12 10:17:03 myReef fake-hwclock[84]: Tue Feb 12 15:17:01 UTC 2019

Feb 12 10:17:03 myReef systemd[1]: Started Create Static Device Nodes in /dev.

Feb 12 10:17:03 myReef systemd[1]: Starting udev Kernel Device Manager...

Feb 12 10:17:03 myReef systemd-fsck[118]: e2fsck 1.43.4 (31-Jan-2017)

Feb 12 10:17:03 myReef systemd-fsck[118]: rootfs: clean, 129237/1926848 files, 1373258/7779456 blocks

Feb 12 10:17:03 myReef systemd[1]: Started File System Check on Root Device.

Feb 12 10:17:03 myReef systemd[1]: Starting Remount Root and Kernel File Systems...

Feb 12 10:17:03 myReef systemd[1]: Started udev Kernel Device Manager.

Feb 12 10:17:03 myReef systemd[1]: Started Remount Root and Kernel File Systems.

Feb 12 10:17:03 myReef systemd[1]: Starting Load/Save Random Seed...

Feb 12 10:17:03 myReef systemd[1]: Starting Flush Journal to Persistent Storage...

Feb 12 10:17:03 myReef systemd[1]: Starting udev Coldplug all Devices...

Feb 12 10:17:03 myReef systemd[1]: Started Load/Save Random Seed.

Feb 12 10:17:03 myReef systemd[1]: Started Flush Journal to Persistent Storage.

Feb 12 10:17:03 myReef systemd[1]: Started Set the console keyboard layout.

Feb 12 10:17:03 myReef kernel: [ 0.000000] Booting Linux on physical CPU 0x0
This is not reef-pi related (the controller software I meant), but your system (pi/raspbian) was rebooted. I can also see a huge delta in timestamp (reverse :-( ), which is not good (10:43 to 10:17). You can ignore the TLS error messages, those are benign.
 
This is not reef-pi related (the controller software I meant), but your system (pi/raspbian) was rebooted. I can also see a huge delta in timestamp (reverse :-( ), which is not good (10:43 to 10:17). You can ignore the TLS error messages, those are benign.

What does that mean lol. The two time frames are not pasted in order. I just copied a small section from each time frame and pasted them here.
 
Hello, I am hoping that someone can offer some advice on fixing the settings that I have made that causes these errors.
IMG_0021.JPG
 
What does that mean lol. The two time frames are not pasted in order. I just copied a small section from each time frame and pasted them here.

Reboots can be Linux kernel panics, or power issues.

Do you port forward just 443 or put the device in a DMZ (is port 22 also exposed to the internet?)
 
@theatrus I have two routers connected to each other. My ISP router serves as the makeshift DMZ. This where my reefpi resides. This router has port forwarding turned on for 443 all the time and 22 is normally off but I turned it on today because I Wanted to poke around in the terminal. My second router connects to the main router and is where my home network is.
 

TOP 10 Trending Threads

ARE YOU READY TO CONFESS TO CRAZIEST, DUMBEST, FUNNIEST THING YOU’VE EVER DONE IN REEFING?

  • Yeah, I'll confess! (Share your story in the comments!)

    Votes: 26 56.5%
  • Nah, I'll keep mine a secret...(Don't be like that, share with the class!)

    Votes: 20 43.5%
Back
Top
Home
Post thread…
Market
What's new