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

I'm unable to access my reef pi from any browser. I can remote into it through putty via ssh and the ip address. When I try checking to see if the service is running I get the following error:

Jan 10 01:53:27 150Gallon reef-pi[4024]: 2020/01/10 01:53:27 Successfully started subsystem: timers
Jan 10 01:53:27 150Gallon reef-pi[4024]: 2020/01/10 01:53:27 Successfully started subsystem: system
Jan 10 01:53:27 150Gallon reef-pi[4024]: 2020/01/10 01:53:27 reef-pi is up and running
Jan 10 01:53:27 150Gallon reef-pi[4024]: 2020/01/10 01:53:27 Starting http server at: 150gallon.local
Jan 10 01:53:27 150Gallon reef-pi[4024]: 2020/01/10 01:53:27 ERROR: Failed to run http server. Error: listen tcp: address 150gallon.local: missing port in address
Jan 10 01:53:27 150Gallon reef-pi[4024]: Methods: [GET]
Jan 10 01:53:27 150Gallon reef-pi[4024]: 2020/01/10 01:53:27 API Doc path: /api/settings
Jan 10 01:53:27 150Gallon reef-pi[4024]: 2020/01/10 01:53:27 Starting health checker
Jan 10 01:54:27 150Gallon reef-pi[4024]: 2020/01/10 01:54:27 health check: Used memory: 6.22 Load5: 0.03
Jan 10 01:55:27 150Gallon reef-pi[4024]: 2020/01/10 01:55:27 health check: Used memory: 6.49 Load5: 0.04


Any ideas?
Did you update the address? Looks like it’s missing port number . You have to reset it. St
@Ranjib 3.1

So I click configure
1578616378973.png

Then it shows nothing i had in there
1578616405470.png

So I set everything I want
1578616433682.png

And then it ignores temp or ph
1578616453375.png
This is a bug. I just noticed this. I dont know how i missed this, as i was working to fix this page. Sorry folks :-( . I'll release a patch soon.
 
Last edited:
Is that what's causing this, and my temp sensors not showing up? I just recently updated to the latest!


1/10/2020, 4:56:33 AMUIERROR{"error":"First line of device file does not ends with YES"} | HTTP 404
 
I've just noticed something strange. I upgraded from 3.0 to 3.1

On/Off buttons for Temp and ATO show on my laptop and phone, but not on the screen I have attached directly to the Pi. As you can see, the screen attached to the Pi is showing it's running 3.1.

Weird.


2020-01-10.png

011cc0feaa93cafe87088c74145cb1e25935f956de.jpg
 
I've just noticed something strange. I upgraded from 3.0 to 3.1

On/Off buttons for Temp and ATO show on my laptop and phone, but not on the screen I have attached directly to the Pi. As you can see, the screen attached to the Pi is showing it's running 3.1.

Weird.


2020-01-10.png

011cc0feaa93cafe87088c74145cb1e25935f956de.jpg
whats the screen resolution?
 
Is that what's causing this, and my temp sensors not showing up? I just recently updated to the latest!


1/10/2020, 4:56:33 AMUIERROR{"error":"First line of device file does not ends with YES"} | HTTP 404
Possibly. The error here indicates at that time the sensor returned corrupted data (checksum mismatched error). reef-pi will discard such result. But if the timeline matches (error logged and spike in the graph), it likely means during that time period there were few values which has checksum correct but incorrect reading.
 
Is this an acceptable method of running my equipment every 2.5 hours ?

Capture.JPG
Most likely not. You want the equipment to just turn on/off after every 2.5 hours?
 
yes, its for dosing pumps that are run for 1 second. I'd like to just keep it simple and set the number of minutes. Between each dose. would there be another way to do this?
Im realizing we cant not do this easily, if at all. My first attempt is to come up with two different timers, one with
hour: 1,6,11,16,21 minute: 0, second:0, day/month:*
the other
hour: 3,8,13,18,23 minute 30, second:0, day/month:*
but this leaves the last dosing 1:30 hours apart, not 2:30 :-/

Let me think about this more. If i dont find any decent solution, I'll add a new feature. A simpler timer that just lets you define the periods in between action, instead of calendar time.
 
Im realizing we cant not do this easily, if at all. My first attempt is to come up with two different timers, one with
hour: 1,6,11,16,21 minute: 0, second:0, day/month:*
the other
hour: 3,8,13,18,23 minute 30, second:0, day/month:*
but this leaves the last dosing 1:30 hours apart, not 2:30 :-/

Let me think about this more. If i dont find any decent solution, I'll add a new feature. A simpler timer that just lets you define the periods in between action, instead of calendar time.

That sounds amazing. My tank is at that point where it is rapidly accelerating in alk and CA consumption and I have to often adjust the number, dose frequency would be awesome and so much easier
 
That sounds amazing. My tank is at that point where it is rapidly accelerating in alk and CA consumption and I have to often adjust the number, dose frequency would be awesome and so much easier
@Ranjib it seems a feature could be a simple entry to let you put in a modulo; it would still mean he'd have to get an even number of times per day, but what about a feature like this:

Enable macro/timer when:
[ dropdown for seconds/minutes/hours/days ]
modulo [ text entry for int value ] [dropdown for seconds/minutes/hours/days/months]
equals [ text entry for int value ]

then he could choose [minutes], type [144], choose [day], type [0].

Whenever the number of minutes in the day % 144 = 0, it runs the macro/timer.
He'd get exactly 10 doses per day
 
@Ranjib it seems a feature could be a simple entry to let you put in a modulo; it would still mean he'd have to get an even number of times per day, but what about a feature like this:

Enable macro/timer when:
[ dropdown for seconds/minutes/hours/days ]
modulo [ text entry for int value ] [dropdown for seconds/minutes/hours/days/months]
equals [ text entry for int value ]

then he could choose [minutes], type [144], choose [day], type [0].

Whenever the number of minutes in the day % 144 = 0, it runs the macro/timer.
He'd get exactly 10 doses per day
I was thinking more in the line of after every N seconds (or minutes or hours). Simple and intuitive.
 
Possibly. The error here indicates at that time the sensor returned corrupted data (checksum mismatched error). reef-pi will discard such result. But if the timeline matches (error logged and spike in the graph), it likely means during that time period there were few values which has checksum correct but incorrect reading.

Any ideas how to troubleshooting ???
 
I made a live stream of my tank...no audio. This will let me watch while I'm at work :)



Very nice!

FWIW - had to go to YouTube to watch the video due to your YouTube settings. I presume you already know this but, just in case you do not, figured I would let you know.
 

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

    Votes: 14 41.2%
Back
Top
Home
Post thread…
Market
What's new