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

[Ryan115]

When I say heater is on I mean heater's own thermister is turning it on (as in the led of the heater is turned on) or heater is runniung. As such my heater is always on, since reef-pi didnt take any action against it, due to the temperature being within the specified range. Apologies for my confusing statements :0( .

The statement is not what I am confused about, my confusion is about the action of reef-pi towards the heater.
When my tank is between 77 & 79 there is no power being applied to the heater (the relay is turned off), so the neither the heater's red or green light is on.
I am confused about how your heater is active on it's own thermostat in this range.

 

[Ryan115]

BTW @Ryan115 , timer features , still work in progress,
Existing timer , that works against equipment

New reminder target,

Looks good.
Does the reminder come through the telemetry text/email?
Also, do you think there will be any way to have reminders that have an interval longer than a month (i.e. every other month, quarterly, semi-annual, annual)?

 

[philshel]

I doubt that the webserver will crash. it can happen, but i doubt it very much. The code in that side is pretty solid
Do you know the IP of your pi ?Can you ssh into it, if so, you can login via ssh and check log

sudo systemctl status reef-pi.service

you can also make API calls locally to check if webserver is running, so from within pi

curl -u reef-pi:reef-pi http://localhost/api/equipments

If you cant ssh, it means Pi's IP has changed, you can find the new ip from your home router admin console. You can also configure it to have a static IP (i know you have already mentioned it, but i dont know exactly how you are doing this)

If you go back couple of pages, I have also reported the same issue. reef-pi working fine, but I lost web UI connectivity. That was purely due to network connectivity lost (comcast service inturruption). In the meantime, I have configured pi to restart wifi network everynight, so in case network goes down, pi will reconnect it every midnight as part of the wifi restart process, reef-pi process does not get touched.

For the long run, i have already started working on a physical interface (posted a video of the same couple of pages back), which will give a minimal workflow using a button and LED display. As of now, I plan to support IP display and shutdown using it. I might extend it to support wifi restart and displaying tank summary. I was super stuck with the network unreachable issue, i was not able to shutdown my controller safely, thats not acceptable.
Let me know what you think, and if your problem is resolved ,

I doubt that the webserver will crash. it can happen, but i doubt it very much. The code in that side is pretty solid
Do you know the IP of your pi ?Can you ssh into it, if so, you can login via ssh and check log

sudo systemctl status reef-pi.service

you can also make API calls locally to check if webserver is running, so from within pi

curl -u reef-pi:reef-pi http://localhost/api/equipments

If you cant ssh, it means Pi's IP has changed, you can find the new ip from your home router admin console. You can also configure it to have a static IP (i know you have already mentioned it, but i dont know exactly how you are doing this)

If you go back couple of pages, I have also reported the same issue. reef-pi working fine, but I lost web UI connectivity. That was purely due to network connectivity lost (comcast service inturruption). In the meantime, I have configured pi to restart wifi network everynight, so in case network goes down, pi will reconnect it every midnight as part of the wifi restart process, reef-pi process does not get touched.

For the long run, i have already started working on a physical interface (posted a video of the same couple of pages back), which will give a minimal workflow using a button and LED display. As of now, I plan to support IP display and shutdown using it. I might extend it to support wifi restart and displaying tank summary. I was super stuck with the network unreachable issue, i was not able to shutdown my controller safely, thats not acceptable.
Let me know what you think, and if your problem is resolved ,

I can ssh in and the ip is static and there is no network interferance. I can see all the devices on my network through my router and reef-pi is where it is supposed to be. "curl -u reef-pi:reef-pi http://localhost/api/equipments" returns "http://localhost/api/equipments curl: (7) Failed to connect to localhost port 80: Connection refused". I noticed that it calls out port 80 and I never changed from port 8080 but I get the same "connection refused" on port 80 as well as 8080

 

[Ryan115]

I can ssh in and the ip is static and there is no network interferance. I can see all the devices on my network through my router and reef-pi is where it is supposed to be. "curl -u reef-pi:reef-pi http://localhost/api/equipments" returns "http://localhost/api/equipments curl: (7) Failed to connect to localhost port 80: Connection refused". I noticed that it calls out port 80 and I never changed from port 8080 but I get the same "connection refused" on port 80 as well as 8080

Did you do a full uninstall and delete the .db file when upgrading to 1.1? If so I think the change was pushed by the upgrade.
What are you typing when trying to connect through Internet browser (i.e. 192.168.1.1, 192.168.1.1:80, 192.168.1.1:8080) ?

 

[Ryan115]

@Ranjib what does your system do if the tank drops below 77? If you heater is already on, what can reef-pi do?
I also noticed in your temp chart that you posted that there is no "heater on" time recorded.

 

[philshel]

Did you do a full uninstall and delete the .db file when upgrading to 1.1? If so I think the change was pushed by the upgrade.
What are you typing when trying to connect through Internet browser (i.e. 192.168.1.1, 192.168.1.1:80, 192.168.1.1:8080) ?

No I did not delete the DB and I was running 1.1 since you posted it with no problems until this morning. I've tried all three versions <reef-piip>, <reef-piip:80> and <reef-piip:8080>. After the lights go out, I'll try a physical power off.
Also I've tried it on chrome and edge.

 

[Ranjib]

@Ranjib what does your system do if the tank drops below 77? If you heater is already on, what can reef-pi do?
I also noticed in your temp chart that you posted that there is no "heater on" time recorded.

I have not configured heater, in that controller, i have only alert enabled,

 

[Ranjib]

Looks good.
Does the reminder come through the telemetry text/email?
Also, do you think there will be any way to have reminders that have an interval longer than a month (i.e. every other month, quarterly, semi-annual, annual)?

Doable, I'll add it in my todo list.

 

[Ranjib]

I can ssh in and the ip is static and there is no network interferance. I can see all the devices on my network through my router and reef-pi is where it is supposed to be. "curl -u reef-pi:reef-pi http://localhost/api/equipments" returns "http://localhost/api/equipments curl: (7) Failed to connect to localhost port 80: Connection refused". I noticed that it calls out port 80 and I never changed from port 8080 but I get the same "connection refused" on port 80 as well as 8080

What was the output of

sudo systemctl status reef-pi.service

 

[Ranjib]

No I did not delete the DB and I was running 1.1 since you posted it with no problems until this morning. I've tried all three versions <reef-piip>, <reef-piip:80> and <reef-piip:8080>. After the lights go out, I'll try a physical power off.
Also I've tried it on chrome and edge.

It will really helpful to get the status of the service. If IP /network is working, then I dont see any reason for reef-pi to be down.

 

[Ryan115]

I have not configured heater, in that controller, i have only alert enabled,

That makes sense then. Any reason you dont have the heater enabled on that system. I think I trust the DS18B20 over the internal of the heater, and I like the redundancy if it were to fail.

 

[philshel]

It will really helpful to get the status of the service. If IP /network is working, then I dont see any reason for reef-pi to be down.

Status of the server is :

● reef-pi.service - raspberry pi based reef tank controller
Loaded: loaded (/lib/systemd/system/reef-pi.service; enabled; vendor preset:
Active: active (running) since Thu 2018-01-11 21:33:00 PST; 11h ago
Main PID: 329 (reef-pi)
CGroup: /system.slice/reef-pi.service
└─329 /usr/bin/reef-pi -config /etc/reef-pi/config.yml

Jan 12 09:24:18 raspberrypi reef-pi[329]: 2018/01/12 09:24:18 lighting-subsystem
Jan 12 09:24:47 raspberrypi reef-pi[329]: 2018/01/12 09:24:47 Lighting: Calculat
Jan 12 09:24:47 raspberrypi reef-pi[329]: 2018/01/12 09:24:47 lighting-subsystem
Jan 12 09:24:48 raspberrypi reef-pi[329]: 2018/01/12 09:24:48 Lighting: Calculat
Jan 12 09:24:48 raspberrypi reef-pi[329]: 2018/01/12 09:24:48 lighting-subsystem
Jan 12 09:24:49 raspberrypi reef-pi[329]: 2018/01/12 09:24:49 health check: Used
Jan 12 09:25:17 raspberrypi reef-pi[329]: 2018/01/12 09:25:17 Lighting: Calculat
Jan 12 09:25:17 raspberrypi reef-pi[329]: 2018/01/12 09:25:17 lighting-subsystem
Jan 12 09:25:18 raspberrypi reef-pi[329]: 2018/01/12 09:25:18 Lighting: Calculat
Jan 12 09:25:18 raspberrypi reef-pi[329]: 2018/01/12 09:25:18 lighting-subsystem

Tried a power off, did not help still refuses to connect. Guess I may have to reinstall reef-pi.

 

[Ranjib]

Status of the server is :

● reef-pi.service - raspberry pi based reef tank controller
Loaded: loaded (/lib/systemd/system/reef-pi.service; enabled; vendor preset:
Active: active (running) since Thu 2018-01-11 21:33:00 PST; 11h ago
Main PID: 329 (reef-pi)
CGroup: /system.slice/reef-pi.service
└─329 /usr/bin/reef-pi -config /etc/reef-pi/config.yml

Jan 12 09:24:18 raspberrypi reef-pi[329]: 2018/01/12 09:24:18 lighting-subsystem
Jan 12 09:24:47 raspberrypi reef-pi[329]: 2018/01/12 09:24:47 Lighting: Calculat
Jan 12 09:24:47 raspberrypi reef-pi[329]: 2018/01/12 09:24:47 lighting-subsystem
Jan 12 09:24:48 raspberrypi reef-pi[329]: 2018/01/12 09:24:48 Lighting: Calculat
Jan 12 09:24:48 raspberrypi reef-pi[329]: 2018/01/12 09:24:48 lighting-subsystem
Jan 12 09:24:49 raspberrypi reef-pi[329]: 2018/01/12 09:24:49 health check: Used
Jan 12 09:25:17 raspberrypi reef-pi[329]: 2018/01/12 09:25:17 Lighting: Calculat
Jan 12 09:25:17 raspberrypi reef-pi[329]: 2018/01/12 09:25:17 lighting-subsystem
Jan 12 09:25:18 raspberrypi reef-pi[329]: 2018/01/12 09:25:18 Lighting: Calculat
Jan 12 09:25:18 raspberrypi reef-pi[329]: 2018/01/12 09:25:18 lighting-subsystem

Tried a power off, did not help still refuses to connect. Guess I may have to reinstall reef-pi.

this means reef-pi is running. The http server starting logic is in the beginning, you can check that log for details on what ip and port its using.
We need the log for reef-pi when it just started, it should have something in the line of: "Starting http server at: localhost:8080"

sudo journalctl -u reef-pi.service  | grep "Starting http sever"

 

[philshel]

this means reef-pi is running. The http server starting logic is in the beginning, you can check that log for details on what ip and port its using.
We need the log for reef-pi when it just started, it should have something in the line of: "Starting http server at: localhost:8080"

sudo journalctl -u reef-pi.service  | grep "Starting http sever"

This is from my power off restart last night: "Jan 11 21:33:01 raspberrypi reef-pi[329]: 2018/01/11 21:33:01 Starting http server at: 10.144.113.147:8080" This is the address I'm using to try and connect. Still get a "connection refused" page.

 

[Ranjib]

This is from my power off restart last night: "Jan 11 21:33:01 raspberrypi reef-pi[329]: 2018/01/11 21:33:01 Starting http server at: 10.144.113.147:8080" This is the address I'm using to try and connect. Still get a "connection refused" page.

This means reef-pi web server is listening to 10.144.113.147 ip, at port 8080.
Both of this should work:
curl http://10.144.113.147:8080/api/info (from any device in the network),
as well as
curl http://localhost:8080/api/info (from within Raspberry Pi command line)
I could debug this if i had access (using tcpdump or something that can track whats going on network or run "lsof -i :8080" on the pi, to check if the port is being used),

 

[philshel]

This means reef-pi web server is listening to 10.144.113.147 ip, at port 8080.
Both of this should work:
curl http://10.144.113.147:8080/api/info (from any device in the network),
as well as
curl http://localhost:8080/api/info (from within Raspberry Pi command line)
I could debug this if i had access (using tcpdump or something that can track whats going on network or run "lsof -i :8080" on the pi, to check if the port is being used),

Sorry for all the trouble. http://10.144.113.147:8080/api/info just get the connection refused. I tried running the "lsof -i :8080" by ssh and it reports "command unknown".
I am using the pi headless so ssh, and network are my only options without breaking everything down and finding the equipment to hook it up to. I'm not great with Linux but am pretty experienced with windows and windows networks, I have not run into this before. Everything on my network sees the pi but nothing can connect to the http server.

 

[Ranjib]

Sorry for all the trouble. http://10.144.113.147:8080/api/info just get the connection refused. I tried running the "lsof -i :8080" by ssh and it reports "command unknown".
I am using the pi headless so ssh, and network are my only options without breaking everything down and finding the equipment to hook it up to. I'm not great with Linux but am pretty experienced with windows and windows networks, I have not run into this before. Everything on my network sees the pi but nothing can connect to the http server.

No worries, as long as you can tag along, i bet we can get to the bottom of this.

sudo apt-get install lsof

will install the tool,after that you can run `lsof -i:8080`

 

[Ranjib]

w

Sorry for all the trouble. http://10.144.113.147:8080/api/info just get the connection refused. I tried running the "lsof -i :8080" by ssh and it reports "command unknown".
I am using the pi headless so ssh, and network are my only options without breaking everything down and finding the equipment to hook it up to. I'm not great with Linux but am pretty experienced with windows and windows networks, I have not run into this before. Everything on my network sees the pi but nothing can connect to the http server.

what was the output of `curl http://localhost:8080` , run locally from raspberry pi command line prompt?

 

[philshel]

w

what was the output of `curl http://localhost:8080` , run locally from raspberry pi command line prompt?

The output was "curl: (7) Failed to connect to localhost port 8080: Connection refused". I installed lsof and ran `lsof -i:8080` which returned nothing, just a new line with a command prompt.

 

[Ranjib]

The output was "curl: (7) Failed to connect to localhost port 8080: Connection refused". I installed lsof and ran `lsof -i:8080` which returned nothing, just a new line with a command prompt.

Well, this means nothing is running at port 8080. Can you try `sudo lsof -i :8080` ??