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

[Ranjib]

Thank you for your answer. I will start playing with one temperature sensor next week. I will use 1-6-3.

So, If I would like to use another one sensor, I should connect it in 17-9-5... is it right?

Ph sensor needs 3.3V or 5V pin?

5v

 

[AbjectMaelstroM]

So it's been about a week since pH calibration....now that I look at it, does it really stay this steady? Is this because I have an empty tank? Or is there something up...?

The little spike was from having probe out of water to recolate. Otherwise it's between 8.36-8.41.

 

[Bigtrout]

So it's been about a week since pH calibration....now that I look at it, does it really stay this steady? Is this because I have an empty tank? Or is there something up...?

The little spike was from having probe out of water to recolate. Otherwise it's between 8.36-8.41.

If nothings in the tank to change things it would stay that steady. My tank has a steady rise of .2 ph and a fall from the plants using co2. But the graph is still very steady with a slow rise as the light ramps up and a slow fall as it ramps bacl down.

 

[Ranjib]

Its not steady. its varying.. but the old values is making the chart y axis so large that the new calibrated values are not being visualized correctly. Bare with me, I'll list down the steps to use reef-pi db command to get rid of the old values,

1. Stop reef-pi (sudo systemctl stop reef-pi.service)
2. Use reef-pi db command to list the ph probes (sudo reef-pi db list phprobes). Obtain the probe id from here. For me it shows something like this

   {
   "1": {
   "id": "1",
   "name": "TestPH",
   "enable": true,
   "period": 2,
   "analog_input": "1",
   "control": false,
   "notify": {
   "enable": false,
   "min": 0,
   "max": 0
   },
   "upper_eq": "",
   "downer_eq": "",
   "min": 0,
   "max": 0,
   "hysteresis": 0,
   "is_macro": false
   }
   }

3. Notice my phprobe id is 1. Next use this id to obtain the ph readings values

   sudo reef-pi db show ph_readings 1 > readings.json

   . This should dump the readings in readings.json file, edit to and remove all the bogus values (you'll see values in the range of 1000s (way outside 0-14), delete those.
4. The reupload the file like this:

    cat readings.json | sudo reef-pi db update ph_readings 1

5. Start reef-pi again (sudo systemctl start reef-pi.service)

Thats it. your old data is gone now.. and the graph should automatically reset and show you the new values which should be in 5.5-10 range at worst, but with daily cycle.

For ease of editing i pass the reef-pi db output via jq command, it indents the json file , making it easy to read/edit.
To install jq command

sudo apt-get install jq

Then to use it execute the 3rd step like this:

sudo reef-pi db show ph_readings 1 | jq . | readings.json

Sorry for your trouble. Let me know if you try this and if it worked. Happy to helo you through this...

 

[Ranjib]

Its not steady. its varying.. but the old values is making the chart y axis so large that the new calibrated values are not being visualized correctly. Bare with me, I'll list down the steps to use reef-pi db command to get rid of the old values,

1. Stop reef-pi (sudo systemctl stop reef-pi.service)
2. Use reef-pi db command to list the ph probes (sudo reef-pi db list phprobes). Obtain the probe id from here. For me it shows something like this

   {
   "1": {
   "id": "1",
   "name": "TestPH",
   "enable": true,
   "period": 2,
   "analog_input": "1",
   "control": false,
   "notify": {
   "enable": false,
   "min": 0,
   "max": 0
   },
   "upper_eq": "",
   "downer_eq": "",
   "min": 0,
   "max": 0,
   "hysteresis": 0,
   "is_macro": false
   }
   }

3. Notice my phprobe id is 1. Next use this id to obtain the ph readings values

   sudo reef-pi db show ph_readings 1 > readings.json

   . This should dump the readings in readings.json file, edit to and remove all the bogus values (you'll see values in the range of 1000s (way outside 0-14), delete those.
4. The reupload the file like this:

    cat readings.json | sudo reef-pi db update ph_readings 1

5. Start reef-pi again (sudo systemctl start reef-pi.service)

Thats it. your old data is gone now.. and the graph should automatically reset and show you the new values which should be in 5.5-10 range at worst, but with daily cycle.

For ease of editing i pass the reef-pi db output via jq command, it indents the json file , making it easy to read/edit.
To install jq command

sudo apt-get install jq

Then to use it execute the 3rd step like this:

sudo reef-pi db show ph_readings 1 | jq . | readings.json

Sorry for your trouble. Let me know if you try this and if it worked. Happy to helo you through this...

@AbjectMaelstroM This was for you.. or anyone planning to remove bogus un-calibrated data. or sometimes bogus connectors/equipment with non-existing driver etc.. like the macro issue surfaced before. Definitely reef-pi should do a better job validating this and providing first-class user experience to address common issues (like the uncalibrated data), but that will take time (to implement and to detect) . The db command, on the other hand, is a general-purpose surgical tool to help us in such occasions, lets put it to test if possible.

 

[AbjectMaelstroM]

Its not steady. its varying.. but the old values is making the chart y axis so large that the new calibrated values are not being visualized correctly. Bare with me, I'll list down the steps to use reef-pi db command to get rid of the old values,

1. Stop reef-pi (sudo systemctl stop reef-pi.service)
2. Use reef-pi db command to list the ph probes (sudo reef-pi db list phprobes). Obtain the probe id from here. For me it shows something like this

   {
   "1": {
   "id": "1",
   "name": "TestPH",
   "enable": true,
   "period": 2,
   "analog_input": "1",
   "control": false,
   "notify": {
   "enable": false,
   "min": 0,
   "max": 0
   },
   "upper_eq": "",
   "downer_eq": "",
   "min": 0,
   "max": 0,
   "hysteresis": 0,
   "is_macro": false
   }
   }

3. Notice my phprobe id is 1. Next use this id to obtain the ph readings values

   sudo reef-pi db show ph_readings 1 > readings.json

   . This should dump the readings in readings.json file, edit to and remove all the bogus values (you'll see values in the range of 1000s (way outside 0-14), delete those.
4. The reupload the file like this:

    cat readings.json | sudo reef-pi db update ph_readings 1

5. Start reef-pi again (sudo systemctl start reef-pi.service)

Thats it. your old data is gone now.. and the graph should automatically reset and show you the new values which should be in 5.5-10 range at worst, but with daily cycle.

For ease of editing i pass the reef-pi db output via jq command, it indents the json file , making it easy to read/edit.
To install jq command

sudo apt-get install jq

Then to use it execute the 3rd step like this:

sudo reef-pi db show ph_readings 1 | jq . | readings.json

Sorry for your trouble. Let me know if you try this and if it worked. Happy to helo you through this...

Good deal! I'll give it a go tomorrow.

 

[Schreiber]

Thank you for your answer. I will start playing with one temperature sensor next week. I will use 1-6-3.

So, If I would like to use another one sensor, I should connect it in 17-9-5... is it right?

That would work! Just keep in mind when you're configuring Reef-Pi, that you need to enter the GPIO number, not the physical pin number. So your first sensor on pin 3 will be GPIO 2 (you'll enter 2 into Reef-Pi's configuration) & your second sensor will be GPIO 3 (you'll enter 3 into Reef-Pi's configuration).

 

[stefanm]

I've got my Reef-pi back up and running on v3.0 yesterday, my dosers are programmed to pump for 1 second every two hours, which they do. However the statistics on the dash board is telling a different story.

Any solution for this?

 

[AbjectMaelstroM]

@Ranjib tried what you posted above and it seemed to have worked. Definitely fixed the historical graph, however it's still using the 0-12 scale so small changes (in 0.XX's) are hard to see.

Is there a way to force 5-10 range? Or did I miss something?... Which is possible because of the wall of text I had to wade through. I tried installing the jd command which seemed to have installed but said unknown command when I tried to use it, so I used the the one in Step 3, thus the wall of text haha. I may look at it later.

In other news, I think one of the relays for my outlet had failed. I was doing a WC yesterday and accidentally double tapped the on/off/on on my return outlet and it got "stuck". The outlet defaults to normally on so it still works but it no longer actuates on/off (no audible clock). Might be time to grab a TPlink powerstrip.

 

[lilgrounchuck]

You are 100% correct. That was exactly what I was looking for. ;)

Thanks!

I was in the same boat this morning! I've become so used to plug n' play stuff that manually setting up the driver wasn't even on my radar.

 

[lilgrounchuck]

I'm not sure if anyone has this issue buried in this thread somewhere, but I can't seem to get anything but HW health (CPU/MEM) to display on the dashboard. I started with a blank SD card last night, installed the latest Raspbian build, updated, then installed reef-pi 3.1. My temp probes and pH probe are showing up and reading correctly, and I can see the graphs if I go to each page, but for whatever reason they won't show on the dashboard. They all show up as options on the dashboard configuration page and I am able to select each one. I have it set for 2 x 2 with Health, pH, Temp 1, Temp 2.

 

[AbjectMaelstroM]

I'm not sure if anyone has this issue buried in this thread somewhere, but I can't seem to get anything but HW health (CPU/MEM) to display on the dashboard. I started with a blank SD card last night, installed the latest Raspbian build, updated, then installed reef-pi 3.1. My temp probes and pH probe are showing up and reading correctly, and I can see the graphs if I go to each page, but for whatever reason they won't show on the dashboard. They all show up as options on the dashboard configuration page and I am able to select each one. I have it set for 2 x 2 with Health, pH, Temp 1, Temp 2.

Its a known bug in 3.1. You can wait on the next build or roll back to 3.0 if you need the dashboard.

 

[lilgrounchuck]

Its a known bug in 3.1. You can wait on the next build or roll back to 3.0 if you need the dashboard.
[/

Awesome! Thanks for the quick reply. No real need for the dashboard until I put this thing on the tank, I just thought it was odd.

 

[lilgrounchuck]

I’m waiting on my dosing pump and power supply to arrive this week before moving on with my build, but one thing I’m on the fence on still is power control. I was originally planning on going the relay route, but with the added support for the tp link smart strips I’m thinking of giving that a try. Before I order the kasa hs300 I was wondering if anyone else is relying on one of those with reef pi already? Just curious to know if anyone is seeing it drop in and out, go off and do it’s own thing and release skynet, etc.

 

[Ranjib]

I’m waiting on my dosing pump and power supply to arrive this week before moving on with my build, but one thing I’m on the fence on still is power control. I was originally planning on going the relay route, but with the added support for the tp link smart strips I’m thinking of giving that a try. Before I order the kasa hs300 I was wondering if anyone else is relying on one of those with reef pi already? Just curious to know if anyone is seeing it drop in and out, go off and do it’s own thing and release skynet, etc.

I dont know of anyone. I am using it for almost two months now, without any issue., I run google wifi (mesh) with a dedicated ssid for all my iot stuff. I still netwok outage frequently, thanks to comcast and google wifi design (that takes local network down everytime it loses connection with motherhsip). So far i have not encountered any big issues. I do get sporadic errors on current reading (heater outlet current is modeled as a ph probe :-) ).

 

[mrlqqe]

hi guys,

I have a Temperature-, pH- and EC-Probe hooked up to a Whitebox Tentacle T3 Shield for my raspi4. The Shield uses Atlas Scientific Chips (EZO-RTD, EZO-pH, EZO-EC). Does anybody know, if its possible to implement/use those sensors with reef-pi?
I was kinda hoping so, because it didn't seem to far fetched, with EZO-pH being used in the tutorial. I've already tried it with the temperature probe (ezo-rtd) only, but couldn't get it to work. It probably does work with the pH, at least, which I will try later today. But yeah, i think i have to look for another solution, when i can't get it running with a all probes/sensors.

Any help much appreciated. Thank you!

 

[Ranjib]

Hi everyone,
I have just published 3.2 release builds. Its pretty small change, primarily fixing the dashboard issue. Due to a bug in 3.1/3.0, you may have to reconfigure the dashboard again via UI. Data and rest everything should not be impacted. Its exclusively UI related issue.
Release builds can be found in the usual location: https://github.com/reef-pi/reef-pi/releases/tag/3.2

 

[Ranjib]

I'm not sure if anyone has this issue buried in this thread somewhere, but I can't seem to get anything but HW health (CPU/MEM) to display on the dashboard. I started with a blank SD card last night, installed the latest Raspbian build, updated, then installed reef-pi 3.1. My temp probes and pH probe are showing up and reading correctly, and I can see the graphs if I go to each page, but for whatever reason they won't show on the dashboard. They all show up as options on the dashboard configuration page and I am able to select each one. I have it set for 2 x 2 with Health, pH, Temp 1, Temp 2.

I just published 3.2 with a bugfix to address this specific issue. Sorry for the trouble.

 

[lilgrounchuck]

I just published 3.2 with a bugfix to address this specific issue. Sorry for the trouble.

No worries, and if anyone makes you feel the need to apologize for providing this amazing tool for free, well they can go eat a bag of (insert unpleasantries of your choice)

 

[lilgrounchuck]

I dont know of anyone. I am using it for almost two months now, without any issue., I run google wifi (mesh) with a dedicated ssid for all my iot stuff. I still netwok outage frequently, thanks to comcast and google wifi design (that takes local network down everytime it loses connection with motherhsip). So far i have not encountered any big issues. I do get sporadic errors on current reading (heater outlet current is modeled as a ph probe :) ).

So even hosting on a dedicated LAN sees network drops? Is that drops between the pi and outlet or drops between the outlet an googles servers? In all honesty, I don’t think I’d really care if it ever reached out to google or amazon successfully as long as it maintained a solid connection to the pi in a closed LAN. I see the possibility of having a separate programmed routine for life support function should the pi drop out as a massive leg up on the traditional relay bar.