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

OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
8,365
Reaction score
14,871
Location
Palo Alto, Bay Area
Nothing to do... I tried :80 and :8080.
At this point I think I have to connect by ssh and reset the reef-pi datatbese!!! :-(
Is it right?
That is the last resort. But if you are comfortable with there are many workaround that does not involve resetting database. for example, you can stop reef-pi and run
Code:
reef-pi db show reef-pi settings

that will show reef-pi settings which will include a field named "address", that has ip and port reef-pi is using
 
Top Shelf Aquatics
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
8,365
Reaction score
14,871
Location
Palo Alto, Bay Area
Hey Reef-Pi people,
I am having issues controlling my Kessil A160WE. I am able to manually adjust the two channels with the slider, and channel 1 is white and channel 2 is blue. My problem is that if I lower channel 2 below 10, both channels turn off? Channel 1 can go to zero and the channel 2 blue lights will stay on at what ever intensity its set to. Is this by design? Can you have White light without blue?
Additionally, I am wondering if anyone can speak to the TRRS adapter that came with my light? Is it required? Is there any benefit to using a TRRS cable and jack at the reef-pi?
TIA
This is expected. Kessil does not dim till 0. In my experience below 13 pwm values (0-100) my A80, A360 etc will start blinking. This is the reason we introduced "min" value for individual channels early on. that tells reef-pi to set the channel value to 0 when the computed value (From profile) is below the minimum value.
 

Freccialata

Community Member
View Badges
Joined
Jan 31, 2020
Messages
46
Reaction score
91
That is the last resort. But if you are comfortable with there are many workaround that does not involve resetting database. for example, you can stop reef-pi and run
Code:
reef-pi db show reef-pi settings

that will show reef-pi settings which will include a field named "address", that has ip and port reef-pi is using
I connected by ssh and wrote the commands you suggested.
This is the output... port is not showed (it should be :80 by default).

[email protected]:~ $ sudo systemctl stop reef-pi.service
[email protected]:~ $ sudo reef-pi db show reef-pi settings
{"name":"Freccialata's Aquarium","interface":"wlan0","address":"0.0.0.0","display":false,"notification":true,"capabilities":{"dev_mode":false,"dashboard":true,"health_check":true,"equipment":true,"timers":false,"lighting":false,"temperature":true,"ato":false,"camera":false,"doser":false,"ph":true,"macro":false,"configuration":true,"journal":false},"health_check":{"enable":true,"max_memory":500,"max_cpu":2},"https":true,"pprof":false,"rpi_pwm_freq":100,"prometheus":false}
[email protected]:~ $ sudo systemctl start reef-pi.service

I aslo tried to open chromium-browser by terminal...

[email protected]:~ $ chromium-browser http://192.168.178.230
--disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
libEGL warning: DRI2: failed to authenticate
[4304:4304:1122/090203.048757:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
[4252:4437:1122/090203.726939:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[4252:4437:1122/090203.727980:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[4252:4437:1122/090203.728991:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
Fontconfig error: Cannot load default config file

I tried the follow commands too:

chromium-browser http://192.168.178.230:80
chromium-browser http://192.168.178.230:8080
chromium-browser https://192.168.178.230:80
chromium-browser https://192.168.178.230:8080


Any other suggestion?
 
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
8,365
Reaction score
14,871
Location
Palo Alto, Bay Area
I connected by ssh and wrote the commands you suggested.
This is the output... port is not showed (it should be :80 by default).

[email protected]:~ $ sudo systemctl stop reef-pi.service
[email protected]:~ $ sudo reef-pi db show reef-pi settings
{"name":"Freccialata's Aquarium","interface":"wlan0","address":"0.0.0.0","display":false,"notification":true,"capabilities":{"dev_mode":false,"dashboard":true,"health_check":true,"equipment":true,"timers":false,"lighting":false,"temperature":true,"ato":false,"camera":false,"doser":false,"ph":true,"macro":false,"configuration":true,"journal":false},"health_check":{"enable":true,"max_memory":500,"max_cpu":2},"https":true,"pprof":false,"rpi_pwm_freq":100,"prometheus":false}
[email protected]:~ $ sudo systemctl start reef-pi.service

I aslo tried to open chromium-browser by terminal...

[email protected]:~ $ chromium-browser http://192.168.178.230
--disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
libEGL warning: DRI2: failed to authenticate
[4304:4304:1122/090203.048757:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
[4252:4437:1122/090203.726939:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[4252:4437:1122/090203.727980:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[4252:4437:1122/090203.728991:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
Fontconfig error: Cannot load default config file

I tried the follow commands too:

chromium-browser http://192.168.178.230:80
chromium-browser http://192.168.178.230:8080
chromium-browser https://192.168.178.230:80
chromium-browser https://192.168.178.230:8080


Any other suggestion?
Ouch.. its looks like the port is set to blank and as a result, reef-pi is crashing. You can save the settings in a file, change the address to include :443 , i.e "0.0.0.0:443" and then reupload it, start reef-pi back,.

Code:
 sudo reef-pi db show reef-pi settings > s.json 
 # edit the s.json file to change address and include port 443 in it. 
sudo reef-pi db update reef-pi settings -input s.json

And start reef-pi again . After this you should. E able to access reef pi just as https://ip , because 443 is default port for https
 

Freccialata

Community Member
View Badges
Joined
Jan 31, 2020
Messages
46
Reaction score
91
Ouch.. its looks like the port is set to blank and as a result, reef-pi is crashing. You can save the settings in a file, change the address to include :443 , i.e "0.0.0.0:443" and then reupload it, start reef-pi back,.

Code:
sudo reef-pi db show reef-pi settings > s.json
# edit the s.json file to change address and include port 443 in it.
sudo reef-pi db update reef-pi settings -input s.json

And start reef-pi again . After this you should. E able to access reef pi just as https://ip , because 443 is default port for https
[email protected]:~ $ sudo systemctl stop reef-pi.service
[email protected]:~ $ sudo reef-pi db show reef-pi settings > s.json
[email protected]:~ $ nano s.json

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

[email protected]:~ $ sudo reef-pi db update reef-pi settings -input s.json

The terminal of the ssh connection stucks.... nothing happens! :-(
 
Last edited:
Shop Online with Zoanthids.com!
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
8,365
Reaction score
14,871
Location
Palo Alto, Bay Area
[email protected]:~ $ sudo systemctl stop reef-pi.service
[email protected]:~ $ sudo reef-pi db show reef-pi settings > s.json
[email protected]:~ $ nano s.json

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

[email protected]:~ $ 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)
 

borillion

Community Member
View Badges
Joined
Jul 28, 2014
Messages
58
Reaction score
76
Location
United States
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
 
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
8,365
Reaction score
14,871
Location
Palo Alto, Bay Area
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.
 

borillion

Community Member
View Badges
Joined
Jul 28, 2014
Messages
58
Reaction score
76
Location
United States
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.
 

Des Westcott

Well-Known Member
View Badges
Joined
May 29, 2018
Messages
583
Reaction score
951
Location
Durban - South Africa
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
 

Dukereefnz

Community Member
View Badges
Joined
Aug 23, 2020
Messages
50
Reaction score
26
Location
Hunua - New Zealand
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
 
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
8,365
Reaction score
14,871
Location
Palo Alto, Bay Area
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:
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
8,365
Reaction score
14,871
Location
Palo Alto, Bay Area
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
 

Des Westcott

Well-Known Member
View Badges
Joined
May 29, 2018
Messages
583
Reaction score
951
Location
Durban - South Africa
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
 

Freccialata

Community Member
View Badges
Joined
Jan 31, 2020
Messages
46
Reaction score
91
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)?
 

AbjectMaelstroM

Valuable Member
View Badges
Joined
Jul 21, 2019
Messages
1,216
Reaction score
1,492
Location
RVA
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:

How's your tank currently looking?

  • Never better

    Votes: 45 15.1%
  • Pretty good

    Votes: 135 45.2%
  • Just OK

    Votes: 66 22.1%
  • Not great

    Votes: 29 9.7%
  • Prett Bad

    Votes: 10 3.3%
  • Yuck

    Votes: 5 1.7%
  • Other (please explain)

    Votes: 9 3.0%

Online statistics

Members online
655
Guests online
3,081
Total visitors
3,736
Top