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

Matt Carden

Valuable Member
View Badges
Joined
Apr 13, 2018
Messages
1,641
Reaction score
4,084
Location
Detroit Metro
Rating - 0%
0   0   0
Can a raspberry pi Pico be used. Those seem to be always available on Adafruit or whatever site you choose?
 
OP
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
9,843
Reaction score
17,056
Location
Pleasant Hill, Concord
Rating - 0%
0   0   0
Can a raspberry pi Pico be used. Those seem to be always available on Adafruit or whatever site you choose?
Unfortunately no. Not for running the main reef-pi software.
however I am working on some changes that will allow reef-pi to be run x86 systems (intel mini pc , desktop etc ) and also be able to use Esp32 (and may be pi pico ) to augment some of the functionality (like probe integration )
 

Wolfw28

Active Member
View Badges
Joined
Mar 13, 2022
Messages
199
Reaction score
138
Location
Myakka City
Rating - 0%
0   0   0
152D47EF-94B2-41B1-B20F-87CCEC2EC027.png 7CFEC55D-3271-4A90-BE9A-2945747AB733.png
Hive mind
I am pleased to announce the immediate availability of 5.3 . This release ships with a decent size of the changelog. Primary focus of this release was to address several UI/UX bugs around calibration , charts, control setting that was annoying. We addressed bulk of those reported issues. As usual, there was community contributions as well. Many hugs goes to the contributors. Following are the highlights:



New features and enhancements:
  • Users can now specify a transform expression to be applied on raw analog sensor reading (e.g. to convert Celsius to Fahrenheit). The transform function takes the shape of an arithmatic expression with a variable "v" interpreted as the raw analog sensor value. This feature is implemented using govaluate library that allows numerical values, arithmetic operators, parenthesis and more. Check the library manual for details. Just remember that reef-pi will inject the value of "v" as raw reading in the transform expression provided.
  • Doser subsystem will now emit metrics and doser charts will reflect the same
  • Error summary in the footer section now links to error section in configuration tab . Users can now just click and check the details of errors conveniently. contributed by @richievos
  • Footer section will now show if the controller is running in dev mode, in red as warning. We hope this makes it easy to detect cases where users inadvertently enabled dev mode.
  • Footer section will now include "year" information to represent current time. My personal requirement. Now after running reef-pi for 5+ years i miss the years in older screenshots. I felt given reef tanks last years.. it makes sense to have the year info in footer. Any screenshot that way will be amortized
  • Driver loading error will be logged under errors section for users to review and assess. No more silent driver failures. Kasa powerstrip load failure like cases were harder to detect due to this. We hope this will make it easier for users to detect driver issues (since it also has timestamp, other than the exact error details).
  • Connectors addition/update operation will now prompt only relevant driver choices (e.g. analog connectors will show only drivers with analog input pins in the driver options). Before this all drivers were being listed. This is a small user experience enhancements, suggested by another community member.

Chores
  • Equipment entries will show outlet name (restoring older behavior)
  • Get rid of spurious log section in the UI. It was there to capture UI errors and causes confusion with Configuration -> Errors tab.
Bug fixes

  • Fixed doser calibration bug. Support volume based stepper motor calibration. Make calibration UI reflective of doser type (speed, duration for dcpumps and volume for steppers)
  • Sort chart data with timestamp across all entities (ph, temperatures, ato etc). Unsorted data was causing bogus charts where new data would not line up on the time axis.
  • Fix cpu usage notify target setting type.
  • Make temperature target thresholds optional when control is not being used - contributed by @richievos
  • Cron job validation through backend instead of ui - fix spurious cron schedule validation errors in the ui. Acceptable cron syntax like "*/3" was being rejected by UI validation. Given cron expression is rich and we have backend based validation, we decided to not do the cron syntax validation in ui and just use the backend. This is more sustainable and does not reduce the awesome cron capabilities
Release builds are available at usual location:


reef-pi 4.0 or above users should be able to upgrade their installs directly through the UI. If you can please test and let us know if you have any feedback.

@Ranjib
I just upgraded full new install of 5.3 on a new SD card. All seems well except for ph reading will randomly drop either blow the correct valve or to 0 and then start working again. The real odd part about it is I have Reef-Kivy installed and running on a 7in display and it never drops out like the Reef-pi UI Does. From my understanding they are both reading from the same source. I put my old SD card with 5.1 reboot ph reads fine.
 
Last edited:

Matt Carden

Valuable Member
View Badges
Joined
Apr 13, 2018
Messages
1,641
Reaction score
4,084
Location
Detroit Metro
Rating - 0%
0   0   0
Seems like my Raspberry-Pi Zero W got fried somehow. The LEDs don't light up on the raspberry.

I managed to get a Raspberry-Pi 3 B from Adafruit by luck and it seems it is DOA! It powers up the desktop appears but the keyboard and mouse don't function. Also the Raspberry-Pi didn't log into my wifi so I can't SSH into the desktop.
 

Sral

Valuable Member
View Badges
Joined
May 2, 2022
Messages
1,006
Reaction score
976
Location
Germany
Rating - 0%
0   0   0
I was looking up usage of the Pi Pico for another project and lo and behold: you can turn the Pi Pico into an oscilloscope. The example shown uses a USB cable, but I'm pretty sure somebody will make it work over WiFi. Bonus points for having 2 channels and showing data on your Cellphone, which gives you immediate data extraction if desired.

Extra points: the Pi Pico is actually available ^^

Depending on the application you'll have to build an appropriate input circuit with Operational amplifiers like here, I guess, but hey, nice idea for tinkering ^^
 
Last edited:

DWKDiver

Community Member
View Badges
Joined
May 18, 2021
Messages
44
Reaction score
42
Location
Georgia
Rating - 0%
0   0   0
Maybe it’s misleading. I remember a similar „enable“ setting for macros, but I think that only disables the Macro itself, not the equipment it’s connected to.
I guess it might be similar with lights, in that it only enables/disables the automatic intensity profiles, but not the light itself ?
It doesn't even stay set to disable. Reverts back to enabled. The more I click on items the more I find doesn't work.
 

MadOTC

New Member
View Badges
Joined
Jul 26, 2022
Messages
4
Reaction score
4
Location
Tallahassee
Rating - 0%
0   0   0
Hey everyone, I've been working on my Reef-Pi project for a few weeks, and I really like the software. It started for me when my LED controller died, and instead of spending $100 on a new one, I was able to use a Pi 2 I had sitting in a drawer. This week I decided I wanted to do a little multitasking with my Pi, and installed Pi Hole for my network. Unfortunately when I installed it, it took over port 80 for it's interface, so I can't get to my Reef-Pi page anymore. Is there a config file I can edit to change the port that the Reef-Pi interface uses? Thanks, this thread has been an awesome source of information.
 

bishoptf

Valuable Member
View Badges
Joined
Jan 1, 2019
Messages
1,344
Reaction score
1,722
Location
Missouri
Rating - 0%
0   0   0
Hey everyone, I've been working on my Reef-Pi project for a few weeks, and I really like the software. It started for me when my LED controller died, and instead of spending $100 on a new one, I was able to use a Pi 2 I had sitting in a drawer. This week I decided I wanted to do a little multitasking with my Pi, and installed Pi Hole for my network. Unfortunately when I installed it, it took over port 80 for it's interface, so I can't get to my Reef-Pi page anymore. Is there a config file I can edit to change the port that the Reef-Pi interface uses? Thanks, this thread has been an awesome source of information.
You can change either reef-pi via the ui to use 443 or any other port like 8080 etc, and you should be able to do the same for pi-hole. I will say though that while you can combine stuff I would not recommend it, rpi's are cheap and I tend to keep reef-pi by itself but thats a personal decision they can coexist as long as memory and cpu are not an issue.
 

buddy.

Active Member
View Badges
Joined
May 16, 2018
Messages
291
Reaction score
617
Location
Australia
Rating - 0%
0   0   0
Great to hear ! What features are you using ?
Ive used most of them over the years, but with my current set up its fairly simple. Temperature, dosing, all equipment controlled by reef-pi, a bunch of timers, auto top off, a bunch of float switches protecting different things, email alerts which have definitely saved my tank at least one time!
I would love a salinity monitor / alert if its ever an option.
 

Sral

Valuable Member
View Badges
Joined
May 2, 2022
Messages
1,006
Reaction score
976
Location
Germany
Rating - 0%
0   0   0
Ive used most of them over the years, but with my current set up its fairly simple. Temperature, dosing, all equipment controlled by reef-pi, a bunch of timers, auto top off, a bunch of float switches protecting different things, email alerts which have definitely saved my tank at least one time!
I would love a salinity monitor / alert if its ever an option.
I’ll try to build one myself for my freshwater aquarium. If that works we could try adapting it to saltwater :)
 

bishoptf

Valuable Member
View Badges
Joined
Jan 1, 2019
Messages
1,344
Reaction score
1,722
Location
Missouri
Rating - 0%
0   0   0
@Ranjib or anyone else know how I can fix the database without starting over, I updated some equipment labels but it must not have liked what I used, not sure if it was the "." but I did a reload and its exited, here is the code:

Aug 13 20:30:39 octopi reef-pi[19740]: panic: descriptor Desc{fqName: "equipment_doser_yellow_1.1ml_h202_dj5_state", help: "Module:equipment Item:Doser Yellow 1.1ml h202 dj5-state", constLabels: {}, variableLabels: []} is invalid: "equipment_doser_yellow_1.1ml_h202_dj5_state" is not a valid metric name


So I just need to fix the equipment label so I can get the website working again, it appears to be functioning but the website is whats not able to come up. I will do some google searching but I think I should be able to fix the equipment labels with out having to restore and rebuild everything. Kicking myself since I been meaning to set up a cron to nightly save a copy of the database, lol. I think I am running version 4.1, thanks.
 

bishoptf

Valuable Member
View Badges
Joined
Jan 1, 2019
Messages
1,344
Reaction score
1,722
Location
Missouri
Rating - 0%
0   0   0
This is the entry that I think I need to update using the reef-pi db command:

"8": {
"id": "8",
"name": "Doser Yellow 1.1ml h202 dj5",
"outlet": "8",
"on": false

Well I took the easy path and just deleted the ID 8, easy enough to re-create, so here is what I did:

sudo reef-pi db delete equipment 8

Then restarted reef-pi service and this time it started right up, so I assume I cannot use "." in the name/labels? I have a doser that is 1.1ml/min and was trying to use that in the name but I could do 1_1ml.
 
Last edited:
OP
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
9,843
Reaction score
17,056
Location
Pleasant Hill, Concord
Rating - 0%
0   0   0
Just here to say that my reef-pi has been running flawlessly this whole time... thanks @Ranjib !!!
thank you for the update. its good to hear things are humming along.
 
OP
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
9,843
Reaction score
17,056
Location
Pleasant Hill, Concord
Rating - 0%
0   0   0
This is the entry that I think I need to update using the reef-pi db command:

"8": {
"id": "8",
"name": "Doser Yellow 1.1ml h202 dj5",
"outlet": "8",
"on": false

Well I took the easy path and just deleted the ID 8, easy enough to re-create, so here is what I did:

sudo reef-pi db delete equipment 8

Then restarted reef-pi service and this time it started right up, so I assume I cannot use "." in the name/labels? I have a doser that is 1.1ml/min and was trying to use that in the name but I could do 1_1ml.
hmm.. i have never tried names with period. i cant think of any code that will break due to this.. but i have to test it out
 

bishoptf

Valuable Member
View Badges
Joined
Jan 1, 2019
Messages
1,344
Reaction score
1,722
Location
Missouri
Rating - 0%
0   0   0
hmm.. i have never tried names with period. i cant think of any code that will break due to this.. but i have to test it out
Here is the output from the journal...

Code:
http2: panic serving 10.99.99.146:52016: descriptor Desc{fqName: "equipment_doser_yellow_1.1ml_dj5_state", help: "Module:equipment Ite
m:Doser Yellow 1.1ml dj5-state", constLabels: {}, variableLabels: []} is invalid: "equipment_doser_yellow_1.1ml_dj5_state" is not a valid metric name
Aug 13 19:57:51 octopi reef-pi[12763]: goroutine 6080056 [running]:
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.(*http2serverConn).runHandler.func1(0x2e68560, 0x33a3fc4, 0x35376c0)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/h2_bundle.go:5713 +0x11c
Aug 13 19:57:51 octopi reef-pi[12763]: panic(0x618bc8, 0x310d480)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/runtime/panic.go:969 +0x118
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/prometheus/client_golang/prometheus.(*Registry).MustRegister(0x2d3f340, 0x310d468, 0x1, 0x1)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/pkg/mod/github.com/prometheus/[email protected]/prometheus/registry.go:403 +0x80
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/prometheus/client_golang/prometheus/promauto.Factory.NewGauge(0x7aaff0, 0x2d3f340, 0x0, 0x0, 0x0, 0x0, 0x308a4e0, 0x26, 0x2edf380, 0x32, ...)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/pkg/mod/github.com/prometheus/[email protected]/prometheus/promauto/auto.go:297 +0xc0
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/prometheus/client_golang/prometheus/promauto.NewGauge(...)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/pkg/mod/github.com/prometheus/[email protected]/prometheus/promauto/auto.go:191
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/telemetry.(*telemetry).EmitMetric(0x2dd8000, 0x6b03ad, 0x9, 0x2dc95e0, 0x1c, 0x0, 0x0)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/telemetry/telemetry.go:189 +0x510
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/modules/equipment.(*Controller).updateOutlet(0x2d09e60, 0x31f904f, 0x1, 0x2dc9540, 0x16, 0xbb8070, 0x1, 0x0, 0x0, 0x
0)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/modules/equipment/controller.go:83 +0xd8
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/modules/equipment.(*Controller).Update(0x2d09e60, 0x31f904f, 0x1, 0x31f904f, 0x1, 0x2dc9540, 0x16, 0xbb8070, 0x1, 0x
0, ...)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/modules/equipment/equipment.go:58 +0xcc
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/modules/equipment.(*Controller).UpdateEquipment.func1(0x31f904f, 0x1, 0x2f6a300, 0x0)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/modules/equipment/api.go:166 +0x4c
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/utils.JSONUpdateResponse(0x5d66c0, 0x2f6a300, 0x33a3d00, 0x7ab770, 0x2e68560, 0x32d4d00)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/utils/http_json.go:95 +0x124
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/modules/equipment.(*Controller).UpdateEquipment(0x2d09e60, 0x7ab770, 0x2e68560, 0x32d4d00)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/modules/equipment/api.go:168 +0x7c
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.HandlerFunc.ServeHTTP(0x2f4c880, 0x7ab770, 0x2e68560, 0x32d4d00)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:2012 +0x34
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/gorilla/mux.(*Router).ServeHTTP(0x2d2f7a0, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/pkg/mod/github.com/gorilla/[email protected]/mux.go:210 +0xac
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/utils.(*auth).Authenticate.func1(0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/utils/auth.go:57 +0x294
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.HandlerFunc.ServeHTTP(0x304eb70, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:2012 +0x34
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.(*ServeMux).ServeHTTP(0xbf40b0, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:2387 +0x16c
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.serverHandler.ServeHTTP(0x2d80120, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:2807 +0x88
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.initALPNRequest.ServeHTTP(0x7aca10, 0x2f56dc0, 0x2cf7e00, 0x2d80120, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:3381 +0x5c
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.(*http2serverConn).runHandler(0x35376c0, 0x2e68560, 0x34acc80, 0x3103430)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/h2_bundle.go:5720 +0x74
Aug 13 19:57:51 octopi reef-pi[12763]: created by net/http.(*http2serverConn).processHeaders
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/h2_bundle.go:5454 +0x418

I then changed the 1.1 to 1_1 and its all good now, this was running v4.1..I should always have a backup but this stuff rarely happens since you spoiled us with good code...:)

AND was easy to fix with the DB commands.
 
Last edited:
OP
OP
Ranjib

Ranjib

7500 Club Member
View Badges
Joined
Apr 16, 2016
Messages
9,843
Reaction score
17,056
Location
Pleasant Hill, Concord
Rating - 0%
0   0   0
Here is the output from the journal...

Code:
http2: panic serving 10.99.99.146:52016: descriptor Desc{fqName: "equipment_doser_yellow_1.1ml_dj5_state", help: "Module:equipment Ite
m:Doser Yellow 1.1ml dj5-state", constLabels: {}, variableLabels: []} is invalid: "equipment_doser_yellow_1.1ml_dj5_state" is not a valid metric name
Aug 13 19:57:51 octopi reef-pi[12763]: goroutine 6080056 [running]:
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.(*http2serverConn).runHandler.func1(0x2e68560, 0x33a3fc4, 0x35376c0)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/h2_bundle.go:5713 +0x11c
Aug 13 19:57:51 octopi reef-pi[12763]: panic(0x618bc8, 0x310d480)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/runtime/panic.go:969 +0x118
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/prometheus/client_golang/prometheus.(*Registry).MustRegister(0x2d3f340, 0x310d468, 0x1, 0x1)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/pkg/mod/github.com/prometheus/[email protected]/prometheus/registry.go:403 +0x80
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/prometheus/client_golang/prometheus/promauto.Factory.NewGauge(0x7aaff0, 0x2d3f340, 0x0, 0x0, 0x0, 0x0, 0x308a4e0, 0x26, 0x2edf380, 0x32, ...)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/pkg/mod/github.com/prometheus/[email protected]/prometheus/promauto/auto.go:297 +0xc0
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/prometheus/client_golang/prometheus/promauto.NewGauge(...)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/pkg/mod/github.com/prometheus/[email protected]/prometheus/promauto/auto.go:191
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/telemetry.(*telemetry).EmitMetric(0x2dd8000, 0x6b03ad, 0x9, 0x2dc95e0, 0x1c, 0x0, 0x0)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/telemetry/telemetry.go:189 +0x510
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/modules/equipment.(*Controller).updateOutlet(0x2d09e60, 0x31f904f, 0x1, 0x2dc9540, 0x16, 0xbb8070, 0x1, 0x0, 0x0, 0x
0)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/modules/equipment/controller.go:83 +0xd8
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/modules/equipment.(*Controller).Update(0x2d09e60, 0x31f904f, 0x1, 0x31f904f, 0x1, 0x2dc9540, 0x16, 0xbb8070, 0x1, 0x
0, ...)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/modules/equipment/equipment.go:58 +0xcc
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/modules/equipment.(*Controller).UpdateEquipment.func1(0x31f904f, 0x1, 0x2f6a300, 0x0)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/modules/equipment/api.go:166 +0x4c
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/utils.JSONUpdateResponse(0x5d66c0, 0x2f6a300, 0x33a3d00, 0x7ab770, 0x2e68560, 0x32d4d00)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/utils/http_json.go:95 +0x124
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/modules/equipment.(*Controller).UpdateEquipment(0x2d09e60, 0x7ab770, 0x2e68560, 0x32d4d00)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/modules/equipment/api.go:168 +0x7c
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.HandlerFunc.ServeHTTP(0x2f4c880, 0x7ab770, 0x2e68560, 0x32d4d00)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:2012 +0x34
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/gorilla/mux.(*Router).ServeHTTP(0x2d2f7a0, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/pkg/mod/github.com/gorilla/[email protected]/mux.go:210 +0xac
Aug 13 19:57:51 octopi reef-pi[12763]: github.com/reef-pi/reef-pi/controller/utils.(*auth).Authenticate.func1(0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /Users/ranjib/gocode/src/github.com/reef-pi/reef-pi/controller/utils/auth.go:57 +0x294
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.HandlerFunc.ServeHTTP(0x304eb70, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:2012 +0x34
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.(*ServeMux).ServeHTTP(0xbf40b0, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:2387 +0x16c
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.serverHandler.ServeHTTP(0x2d80120, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:2807 +0x88
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.initALPNRequest.ServeHTTP(0x7aca10, 0x2f56dc0, 0x2cf7e00, 0x2d80120, 0x7ab770, 0x2e68560, 0x34acc80)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/server.go:3381 +0x5c
Aug 13 19:57:51 octopi reef-pi[12763]: net/http.(*http2serverConn).runHandler(0x35376c0, 0x2e68560, 0x34acc80, 0x3103430)
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/h2_bundle.go:5720 +0x74
Aug 13 19:57:51 octopi reef-pi[12763]: created by net/http.(*http2serverConn).processHeaders
Aug 13 19:57:51 octopi reef-pi[12763]:         /usr/local/Cellar/go/1.14.2_1/libexec/src/net/http/h2_bundle.go:5454 +0x418

I then changed the 1.1 to 1_1 and its all good now, this was running v4.1..I should always have a backup but this stuff rarely happens since you spoiled us with good code...:)

AND was easy to fix with the DB commands.
you are using grafana /prometheus? . is not allowed by prometheus, thats what causing the crash. im bit surprised though, this should not happen as we sanitize the metric name in code,. may be this version didnt had that fix
 

bishoptf

Valuable Member
View Badges
Joined
Jan 1, 2019
Messages
1,344
Reaction score
1,722
Location
Missouri
Rating - 0%
0   0   0
you are using grafana /prometheus? . is not allowed by prometheus, thats what causing the crash. im bit surprised though, this should not happen as we sanitize the metric name in code,. may be this version didnt had that fix
Yup I am using prometheus/grafna for sure, allows me to keep track of things and really is the dashboard that I use daily vs the reef-pi dashboard. Yeah I'm on a pretty old version, I'm kind of stubborn since if it works and I don't need any of the new features then I tend to stay put. I keep meaning to get my test unit up and working where I can run newer versions but just haven't spent the time to do it. Really wasn't an issue once I figured out what the issue was and gave me an opportunity to use the database command and it worked like a treat. :)

On an another note, I have dosers that are controlled by power outlet relay and looking for a better way to graph in grafana, the state is either on or off and the graph at least the one I am using is time based. I have dosing amounts in the 30s range and would like a better way to capture the data so that I can track it and look at my graph and know its working properly.

If anyone has any suggestions on how to do that in grafana would appreciate the advise. :)
 

Fusion in reefing: How do you feel about grafted corals?

  • I strongly prefer grafted corals and I seek them out to put in my tank.

    Votes: 2 4.3%
  • I find grafted corals appealing and would be open to having them in my tank.

    Votes: 31 67.4%
  • I am indifferent about grafted corals and am not enthusiastic about having them in my tank.

    Votes: 10 21.7%
  • I have reservations about grafted corals and would generally avoid having them in my tank.

    Votes: 2 4.3%
  • I have a negative perception and would avoid having grafted corals in my tank.

    Votes: 1 2.2%
Back
Top