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

pi@raspberrypi:~ $ sudo systemctl stop reef-pi.service
pi@raspberrypi:~ $ sudo reef-pi db show reef-pi settings > s.json
pi@raspberrypi:~ $ nano s.json

Here i modify "address":"0.0.0.0" in "address":"0.0.0.0:443".
^O and ^X

pi@raspberrypi:~ $ sudo reef-pi db update reef-pi settings -input s.json

The terminal of the ssh connection stucks.... nothing happens! :-(
If the db update worked , you should be able to see it in db show command , and starting reef pi should not show any error in the log , . Can you check those two (db show and log during start)
 
I probably should be more clear, its it possible to build for 64 bit? This way we have access to more than 4 GB ram and can use it for in memory data, etc. I guess I can try building myself and see how it goes. Not sure all the hardware enablement features are there from the Raspberry pi foundation so that could be a conundrum too.
Yes. Please use 3.5 version
 
I probably should be more clear, its it possible to build for 64 bit? This way we have access to more than 4 GB ram and can use it for in memory data, etc. I guess I can try building myself and see how it goes. Not sure all the hardware enablement features are there from the Raspberry pi foundation so that could be a conundrum too.
are you running raspberry pi os or ubuntu? reef-pi pi3 package is compiled for arm7. i have tested it with pi 4 + raspberry pi os.
 
Right now I have Raspberry Pi OS 64-bit on this board, I haven't tried setting anything up so was just asking what to expect, or if anyone had tried it yet.
are you running raspberry pi os or ubuntu? reef-pi pi3 package is compiled for arm7. i have tested it with pi 4 + raspberry pi os.
 
My "Error" tab is always full of errors - the number seems to be around 40/41 at the moment. I can clear them and then they are all back within a few hours with more recent time stamps. Some are obvious, like the ones relating to temp sensor failure, but some relating to the Adafruit error are not obvious to me at all.

Are these benign, or is there something I should do to clear them? I am getting my feeds to AIO as expected.

2020-11-24.png
 
HI - My temp sensor has locked up, I can not turn it on or off, can not delete it.
I have swap the sensors over 1-2 in reef pi and both are reading when using calibration.
Reboot, power off etc does not help.
Also have error {"error":"stats for id: '2' not found"} | HTTP 404

Sensor 1 - locked up
Senor 2 - working fine

If you turn of things like does pumps, temp sensors does this cause errors? Just asking.
If the dashboard has a graph and the dosing or temp is turned off, does that cause an error?

Thanks
 
My "Error" tab is always full of errors - the number seems to be around 40/41 at the moment. I can clear them and then they are all back within a few hours with more recent time stamps. Some are obvious, like the ones relating to temp sensor failure, but some relating to the Adafruit error are not obvious to me at all.

Are these benign, or is there something I should do to clear them? I am getting my feeds to AIO as expected.

2020-11-24.png
sorry about that, i finally got to the bottom of it. there was a couple of bugs. I just fixed them

I just cut 4.0 (release announcement coming soon) .. if possible upgrade. There should not be any dataloss and it should be seamless
 
Last edited:
Hive minds,
I have just cut 4.0 release. It is not a big bang release like 2.0 or 3.0, because since 3.0 we have shipped quiet a few big feature incrementally (macro, ads115 driver, one shot controller, alert in macros and more), but 4.0 does bring a few awesome long awaited feature asks, namely
- Ability to download the current database (for backup) and import an existing database from UI
- Ability to install/upgrade reef-pi versions from UI
- MQTT based metric emission
- Light api will return current values of individual channels
- Doser can be direcly controlled via macro now (i.e. macro on will turn on doser and macro off will turn off doser)
- Bug fixes for adafruit.io
- Bug fix for ph hysteresis
- Bug fix for under voltage detection code
and a whole lot of tech chores (CI, tests, dep upgrades etc)


Release builds are available in usual location: https://github.com/reef-pi/reef-pi/releases/tag/4.0


This major release is backward compatible schema wise, i.e, you will not loose any data and should be able to upgrade seamlessly. There are few changes from existing behavior though, the light api (return current channel values), doser api (direct on/off using macro instead of enable/disable) that are only possible through major version.


I'll make a dedicated post first thing tomorrow morning, thank you so much everyone involved in testing, bug filing, development and all around community support. You all are at the heart of this project and deserve a much bigger shout out in the main announcement post.
hugs
ranjib
 
Hive minds,
I have just cut 4.0 release. It is not a big bang release like 2.0 or 3.0, because since 3.0 we have shipped quiet a few big feature incrementally (macro, ads115 driver, one shot controller, alert in macros and more), but 4.0 does bring a few awesome long awaited feature asks, namely
- Ability to download the current database (for backup) and import an existing database from UI
- Ability to install/upgrade reef-pi versions from UI
- MQTT based metric emission
- Light api will return current values of individual channels
- Doser can be direcly controlled via macro now (i.e. macro on will turn on doser and macro off will turn off doser)
- Bug fixes for adafruit.io
- Bug fix for ph hysteresis
- Bug fix for under voltage detection code
and a whole lot of tech chores (CI, tests, dep upgrades etc)


Release builds are available in usual location: https://github.com/reef-pi/reef-pi/releases/tag/4.0


This major release is backward compatible schema wise, i.e, you will not loose any data and should be able to upgrade seamlessly. There are few changes from existing behavior though, the light api (return current channel values), doser api (direct on/off using macro instead of enable/disable) that are only possible through major version.


I'll make a dedicated post first thing tomorrow morning, thank you so much everyone involved in testing, bug filing, development and all around community support. You all are at the heart of this project and deserve a much bigger shout out in the main announcement post.
hugs
ranjib

Can't wait to get home and install and check it out.

Thanks @Ranjib
 
If the db update worked , you should be able to see it in db show command , and starting reef pi should not show any error in the log , . Can you check those two (db show and log during start)
Ranjib, thank you for your support... I decided to reset the database and configure reef-pi again... I'm lucky because I have few settings to arrange.

I have installed the update (btw... thank you very much for what you and your staff are doing for everyone).

I see a new feauture (MQTT based metric emission)... how can I send data (in partucular temperature and ph data) to home assistant (I have installed mosquitto on my Home Assistant docker)?
 
Hive minds,
I have just cut 4.0 release. It is not a big bang release like 2.0 or 3.0, because since 3.0 we have shipped quiet a few big feature incrementally (macro, ads115 driver, one shot controller, alert in macros and more), but 4.0 does bring a few awesome long awaited feature asks, namely
- Ability to download the current database (for backup) and import an existing database from UI
- Ability to install/upgrade reef-pi versions from UI
- MQTT based metric emission
- Light api will return current values of individual channels
- Doser can be direcly controlled via macro now (i.e. macro on will turn on doser and macro off will turn off doser)
- Bug fixes for adafruit.io
- Bug fix for ph hysteresis
- Bug fix for under voltage detection code
and a whole lot of tech chores (CI, tests, dep upgrades etc)


Release builds are available in usual location: https://github.com/reef-pi/reef-pi/releases/tag/4.0


This major release is backward compatible schema wise, i.e, you will not loose any data and should be able to upgrade seamlessly. There are few changes from existing behavior though, the light api (return current channel values), doser api (direct on/off using macro instead of enable/disable) that are only possible through major version.


I'll make a dedicated post first thing tomorrow morning, thank you so much everyone involved in testing, bug filing, development and all around community support. You all are at the heart of this project and deserve a much bigger shout out in the main announcement post.
hugs
ranjib
Disregard found my answer.

Made the move from 3.3.1 to 4.0...So far so good. Fantastic work as usual!
 
Last edited:
Ranjib, thank you for your support... I decided to reset the database and configure reef-pi again... I'm lucky because I have few settings to arrange.

I have installed the update (btw... thank you very much for what you and your staff are doing for everyone).

I see a new feauture (MQTT based metric emission)... how can I send data (in partucular temperature and ph data) to home assistant (I have installed mosquitto on my Home Assistant docker)?
Just add mqtt server details (host:port) and reef-pi will emit all the metrics to mqtt. Including ph, temperature, equipment state etc. name of the topic will be deduced from name (e.g. ph_reading). I am not knowledgeable for home assistant integration part , may be @sfgabe or someone who is using it can chime in. This is the required first step for mqtt integration , we are likely to have more features in future around mqtt
 
Just add mqtt server details (host:port) and reef-pi will emit all the metrics to mqtt. Including ph, temperature, equipment state etc. name of the topic will be deduced from name (e.g. ph_reading). I am not knowledgeable for home assistant integration part , may be @sfgabe or someone who is using it can chime in. This is the required first step for mqtt integration , we are likely to have more features in future around mqtt

This is awesome. Can't wait to plug it into HASS.
 
Just add mqtt server details (host:port) and reef-pi will emit all the metrics to mqtt. Including ph, temperature, equipment state etc. name of the topic will be deduced from name (e.g. ph_reading). I am not knowledgeable for home assistant integration part , may be @sfgabe or someone who is using it can chime in. This is the required first step for mqtt integration , we are likely to have more features in future around mqtt
I'm excited about this new development @Ranjib ! I need to update to the latest version, but using MQTT instead should take care of the expired cookies that I need to manually refresh every so often with the API method.

As for @Freccialata 's question - I currently use the reef-pi API so I don't have any direct knowledge of the new MQTT setup. In Home Assistant, you'll need to make sure you have an MQTT host set up (check the HASS docs for that), and that reef-pi is pointing to that as the MQTT host. Once that's up and running you should be able to test the reef-pi integration by going into the HASS MQTT integration and "listening" to the topic - it should be something like /reef-pi/ph_reading/ . After you see that that returns a value, you can use that as an mqtt sensor as defined in the hass docs.

@Ranjib is there a doc that has the possible topic addresses? (apologies if it's somewhere in the previous thread, feel free to link)
 
I'm excited about this new development @Ranjib ! I need to update to the latest version, but using MQTT instead should take care of the expired cookies that I need to manually refresh every so often with the API method.

As for @Freccialata 's question - I currently use the reef-pi API so I don't have any direct knowledge of the new MQTT setup. In Home Assistant, you'll need to make sure you have an MQTT host set up (check the HASS docs for that), and that reef-pi is pointing to that as the MQTT host. Once that's up and running you should be able to test the reef-pi integration by going into the HASS MQTT integration and "listening" to the topic - it should be something like /reef-pi/ph_reading/ . After you see that that returns a value, you can use that as an mqtt sensor as defined in the hass docs.

@Ranjib is there a doc that has the possible topic addresses? (apologies if it's somewhere in the previous thread, feel free to link)
Not yet. the topic is same as prometheus metric name. generally in the form of "name_reading" . you can get an idea here: https://github.com/reef-pi/reef-pi/search?q=EmitMetric , i plan to add details in the docs soon.
 

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: 33 54.1%
  • Nah, I'll keep mine a secret...(Don't be like that, share with the class!)

    Votes: 28 45.9%
Back
Top
Home
Post thread…
Market
What's new