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

I updated this morning to 1.0 and now I am having issues logging in. I did clear the cache as well as try several different browsers. I can get to the log in screen and once I try to sign in it goes right back to the login screen. I see that other users have had similar issues after upgrades. I tried restarting my pi ant then ended up downgrading back to 0.9.1 but I am still having the same issue. Any suggestions? My next step will be to delete everything including the database and start from scratch on 1.0.
I am fairly sure we are missing something small here.. if you delete the database then you have to re-create all outlets, equipment etc....I wont advice for that. You can also try out the incognito mode in browser
 
If anyone else is attempting to ease some build parts.

Installed a ds18b20 module so didnt have to use a resistor.

And to make install easier went with rj11 cable(phone wire) connections.

-Security of snap in connections.
-Ease of determining what wire connects.

Wire connection layout
2 data white/yellow
3 ground black/blue
4 power red
 
If anyone else is attempting to ease some build parts.

Installed a ds18b20 module so didnt have to use a resistor.

And to make install easier went with rj11 cable(phone wire) connections.

-Security of snap in connections.
-Ease of determining what wire connects.

Wire connection layout
2 data white/yellow
3 ground black/blue
4 power red
when you say ds18b20 module, do you mean a dedicated breakout board with the 4.7K resistor?
 
Another I am hoping from the adafruit.io integration is to get alert when the controller is down for some reason. Adafruit.io has triggers, which can send email notification based , I was looking forward to use that feature to send me alerts when reef-pi is down, since I wont get any alert from reef-pi itself in that case.
But for some reason, email triggers in adafruit.io never worked for me.. I still dont know why.. as a result I have never talked about it.. but since you asked.. this was a reason for adafruit.io integration as well. An external monitor/alert is always a full proof way to detect system issues

OK, that would be pretty awesome and something that would be nice. Maybe down the road you'll get it figured out..
 
If anyone else is attempting to ease some build parts.

Installed a ds18b20 module so didnt have to use a resistor.

And to make install easier went with rj11 cable(phone wire) connections.

-Security of snap in connections.
-Ease of determining what wire connects.

Wire connection layout
2 data white/yellow
3 ground black/blue
4 power red

Like ranjib said, unless you using something that already has it, you should need the resistor to get it to work..
 
when you say ds18b20 module, do you mean a dedicated breakout board with the 4.7K resistor?

Yes, sorry i wanted to remove the bread board i had in my housing. So looked around for somethings that were could just be screwed into the housing.
 
I've been following along with this project form the beginning with great interest; you've done an amazing job!

One thing I haven't seen (sorry if I've missed it)... will Reef Pi be able to use pH/Conductivity sensors in the future? That's the only reason I can see right now to buy a commercial controller.

EDIT: I did a thread search and I see it's been mentioned several times, lol
 
I've been following along with this project form the beginning with great interest; you've done an amazing job!

One thing I haven't seen (sorry if I've missed it)... will Reef Pi be able to use pH/Conductivity sensors in the future? That's the only reason I can see right now to buy a commercial controller.
It's in reef-pi future plan. Version 1.0 does ATO, LED, Temperature and power bar controls., will be released sometime this week.
I plan to work on following thing going forward, other than 1.0 maintenance (bugfix, non-breaking improvements and any security fixes)
  • An embedded scripting language or domain specific language to allow users program
  • Macro or feed mode
  • Support for multiple ATO and multiple temperature probes
  • pH probe (and probably salinity and ORP) using tentacle shield & atlas scientific probes
Version 2.0, or the next major public release will have all of this. If I can implement any of these features without breaking the database schema or API (that is keeping 1.0 features intact) then they'll be shipping with 1.x releases.
Thank you for the kind words :-) I really appreciate it
 
Yes, sorry i wanted to remove the bread board i had in my housing. So looked around for somethings that were could just be screwed into the housing.
Yeah, dfrobot has a nifty PCB for this as well, for those who wants a pre-fabricated board
Just the breakout board: https://www.amazon.com/dp/B01B0INNYK/
Board and sensor: https://www.amazon.com/dp/B07434MB77/

I am thinking, should I add the breakout board in temperature controller guide and the standard Bill of materials ?
 
As an Amazon Associate we earn from qualifying purchases.
Oh that board and sensor... me likey.. Guess I missed that when I was looking for probes to start with...
 
Last edited:
reef-pi documentation work is pretty much done . Last night I updated the temperature controller , and with that all three basic guides (install, wiring & housing) and build guides (power, lighting, ato, temperature and telemetry) are fairly complete and consistent. I know for sure that every part of the doc can be improved, but that will be the case always.

One thing that I caught my attention (and I am sure someone had pointed this out), that I use the word "equipments" across documentation, reef-pi web interface, API etc. Though this is not something that impacts the functionality, it might be a major annoyance for some one else. So, I tried to fix it, and because of the widespread use of this word it was a major change. I have a patch ready to fix all use of "equipments" to just "equipment", but this will incur database changes (i.e. existing equipment settings will be lost). I am in dilemma what to do next. If I fix this, it will be gone, but existing users have to recreate the equipment. If I dont do this, we have to live with it for at least another year :-/ , suggestions?
 
reef-pi documentation work is pretty much done . Last night I updated the temperature controller , and with that all three basic guides (install, wiring & housing) and build guides (power, lighting, ato, temperature and telemetry) are fairly complete and consistent. I know for sure that every part of the doc can be improved, but that will be the case always.

One thing that I caught my attention (and I am sure someone had pointed this out), that I use the word "equipments" across documentation, reef-pi web interface, API etc. Though this is not something that impacts the functionality, it might be a major annoyance for some one else. So, I tried to fix it, and because of the widespread use of this word it was a major change. I have a patch ready to fix all use of "equipments" to just "equipment", but this will incur database changes (i.e. existing equipment settings will be lost). I am in dilemma what to do next. If I fix this, it will be gone, but existing users have to recreate the equipment. If I dont do this, we have to live with it for at least another year :-/ , suggestions?

It doesnt bother me at all.. I can see where it could bother people, but to me it just isnt a big deal.
 
Do you need 20 mosfets? I would assume you only need 1 per channel.. so if you are dividing the leds in 4 channels, you need 4 mosfets

I really hope that I don’t need them all - the most are spare MOSFETs. Just in case I end up killing the one or the other!

Actually I’ve almost finished my first 6-channel prototype.
D93F0D2C-0610-43C7-AB7E-933359634B9F.jpeg 5769F189-DC27-4034-B5B4-93BB4F367737.jpeg
 
It doesnt bother me at all.. I can see where it could bother people, but to me it just isnt a big deal.

My thoughts are usually that any deliverable item (i.e. a release version of a software package) should be as polished as reasonably possible. Obviously, it's impossible for every item to be perfect, but things like labels in the interface would be checked off the bug list.

Everyone's mileage will certainly vary on those thoughts.
 
I have decided that the current 1.0 release candidate is the final candidate. Which means this is the release that will be supported till next major release (hopefully around 2018 X-Mas). I have also made a separate 1.0 announcement thread here: https://www.reef2reef.com/threads/reef-pi-1-0-released.343672/ . If you are running reef-pi based controller, please upgrade to 1.0. I would also appreciate if you can share any build pics /setups on the 1.0 thread, it will be very interesting to look back in time and see all these builds. I hope to start working on next set of feature soon after the X-Mas. :-)
 
I am fairly sure we are missing something small here.. if you delete the database then you have to re-create all outlets, equipment etc....I wont advice for that. You can also try out the incognito mode in browser
Maybe I changed the password, I can’t remember lol. I ended up starting from scratch with 1.0 and it is working well now!
 
  • pH probe (and probably salinity and ORP) using tentacle shield & atlas scientific probes

Hello all, joined recently and yesterday spent almost whole day to read topic. Don't you think this would be expensive option (tentacle shield) which would bring this build by price quite close to something well established like GHL?
 

IF YOU HAD TO TAKE A REEFING EXAM, WOULD YOU PASS?

  • Yes!

    Votes: 32 45.7%
  • Not yet, but I have one that I want to buy in mind!

    Votes: 9 12.9%
  • No.

    Votes: 26 37.1%
  • Other (please explain).

    Votes: 3 4.3%
Back
Top