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

Soulreefer · Dec 3, 2019

Ranjib said:
Thank you. To name a few, following is our tentative goals for 3.0, that exploit this feature
- Support for multiple PCA9685
- Using PWM pins (pca9685 or pi) as outlets (cause they can be switched back and forth 0 or 100%)
- support for @Roberto_b's ph board
- support for @theatrus 's pico base board
- support of MCP23017 IO expander (more inlets & outlets)
- Probably support for smart outlets (strech goal)

hello @Ranjib or other friends , is this MCP23017 can still be input into reef-pi ?, sorry I need enlightenment because I read back there is rarely anyone talking about MCP23017, I just need an additional inlet for the Ato function.

Thank you very much.

pies666 · Dec 3, 2019

Des Westcott said:
Aaaahh. I think I get what you're saying now. Reef-Pi itself doesn't actually detect the screen. You have to run it in a browser.

I followed this tutorial https://pimylifeup.com/raspberry-pi-kiosk/ and now have my Raspberry Pi running in Kiosk Mode. The Raspberry Pi boots directly into Chrome and opens the page I specified (Reef-Pi). Works brilliantly for what I want.

That's what my Raspberry Pi boots into . I'm assuming that's what you want?

Not exacly. I did have similar setup (toouchscreen with Kiosk Mode) but I have switched to official rpi screen. As long as I read here reef-pi has some sort of support for this (and only this) touchscreen. You can enable it in configuration->settings-> display. This is exacly what I'm asking about.

For some reason I'm stuck with this error: "{"error":"strconv.Atoi: parsing \"108\\n\": invalid syntax"} | HTTP 404 ". Number "xxx\\n\" depends on brightness level.
I wonder if reef-pi got any other support for official rpi touchscreen or just the brightness control.
If the only advantage of having official rpi screen is brightness control I will stick with non-official (cheaper one) in Kiosk Mode.

Also still can't get those lightning graphs to work. No matter if I use a single or dual PWM control I can't get them to render. Electrically everything works perfect - only light graphs on dashboard are blank.

Ranjib · Dec 3, 2019

pies666 said:
Not exacly. I did have similar setup (toouchscreen with Kiosk Mode) but I have switched to official rpi screen. As long as I read here reef-pi has some sort of support for this (and only this) touchscreen. You can enable it in configuration->settings-> display. This is exacly what I'm asking about.

For some reason I'm stuck with this error: "{"error":"strconv.Atoi: parsing \"108\\n\": invalid syntax"} | HTTP 404 ". Number "xxx\\n\" depends on brightness level.
I wonder if reef-pi got any other support for official rpi touchscreen or just the brightness control.
If the only advantage of having official rpi screen is brightness control I will stick with non-official (cheaper one) in Kiosk Mode.

Also still can't get those lightning graphs to work. No matter if I use a single or dual PWM control I can't get them to render. Electrically everything works perfect - only light graphs on dashboard are blank.

I’ll cross check the display thing, from the error it appears there is a new line character that’s causing the issue.
The light graph is as expected, we are yet to add chart support for different profiles. During 3.0 pwm profile rewrite this was broken

Blaxkin · Dec 3, 2019

Ok i think the Problem is gone. I installed a separate LM2596 for the Temp Sensors Only.

But now can you tell me why one Graph begins at 0 and the other at 21 ?

dmolavi · Dec 3, 2019

Blaxkin said:
Ok i think the Problem is gone. I installed a separate LM2596 for the Temp Sensors Only.

But now can you tell me why one Graph begins at 0 and the other at 21 ?

You can set the min/max display range for each sensor. I've noticed that even after doing that, it can occationally take a "little while" before it kicks in. I'm not sure if it's a log out/in thing, closing my browser, etc, nor can I quantify the time or reliably reproduce the behavior. It's a minor nit, and since I use Adafruit IO mostly, nothing I'm too concerned about.

Blaxkin · Dec 3, 2019

dmolavi said:
You can set the min/max display range for each sensor. I've noticed that even after doing that, it can occationally take a "little while" before it kicks in. I'm not sure if it's a log out/in thing, closing my browser, etc, nor can I quantify the time or reliably reproduce the behavior. It's a minor nit, and since I use Adafruit IO mostly, nothing I'm too concerned about.

Yes but only in the version before 3.0 ?

dmolavi · Dec 3, 2019

Blaxkin said:
Yes but only in the version before 3.0 ?

I've seen it in the 3.0 alpha release...

Ranjib · Dec 3, 2019

Blaxkin said:
Ok i think the Problem is gone. I installed a separate LM2596 for the Temp Sensors Only.

But now can you tell me why one Graph begins at 0 and the other at 21 ?

This is an annoyance introduced in 3.0. In 2.0 we used to get a bogus error of utilization data not found upon creation of new sensors . This is because the sensor had not been monitored yet. To suppress that I introduced a change that will initialize a zero value utilization for new sensor . This is a visual /eye sore and should not trigger any control logic
In retrospect, this is a poor workaround and I should have initialized an Empty utilization data instead
I’ll make sure to address this in next minor release. Thank you for calling this out. Now that 3.0 is out of the door I’m sitting back and using the controller and also discovering bunch of such minor nuisances . I expect them to settle after a couple of minor releases

Zippyfear · Dec 3, 2019

Ranjib said:
Any powerstrip consideration? Use a HAT and ph board to simplify your wiring. Just the kessil 5->10V pwm related circuit needs to be done by hand

Just installed 3.0 on a fresh new Pi3, and a few questions - When I click on connectors, it gets an error -
Details
TypeError: Cannot read property 'analog-input' of null

maybe I didn't enable something on the Pi first? if that's the case, maybe you could add that to the error message .
** Solved - by enabling SPI from running raspi-config **

Second, I'd like to test my TP link hs103's before getting the HS300, but it asks for an address when I add the driver. The only address I see in the Kasa app is the MAC address. is there something else I need there?

Finally, The service seems to start up on a system restart, but the UI doesn't. (can't access it on via HTTP) - Do I need to do anything to enable that to run at startup?

Thanks for all your work on this project btw.. looking forward to getting my reef-pi hat and PH board and probe!

Ranjib · Dec 3, 2019

Zippyfear said:
Just installed 3.0 on a fresh new Pi3, and a few questions - When I click on connectors, it gets an error -
Details
TypeError: Cannot read property 'analog-input' of null

maybe I didn't enable something on the Pi first? if that's the case, maybe you could add that to the error message .
** Solved - by enabling SPI from running raspi-config **

Second, I'd like to test my TP link hs103's before getting the HS300, but it asks for an address when I add the driver. The only address I see in the Kasa app is the MAC address. is there something else I need there?

Finally, The service seems to start up on a system restart, but the UI doesn't. (can't access it on via HTTP) - Do I need to do anything to enable that to run at startup?

Thanks for all your work on this project btw.. looking forward to getting my reef-pi hat and PH board and probe!

You have to provide the ip address:9999 , you can find the IP either via the arp command or by checking your gateway (like comcast routers or google wifi app)

Ranjib · Dec 3, 2019

Ranjib said:
You have to provide the ip address:9999 , you can find the IP either via the arp command or by checking your gateway (like comcast routers or google wifi app)

ping the broadcast address and then invoke arp -a for getting ip from mac address , if you dont have access to gateway. here is a post on how to do this: https://thebackroomtech.com/2010/08/22/determine-ip-address-from-a-mac-address/

Zippyfear · Dec 3, 2019

Ranjib said:
ping the broadcast address and then invoke arp -a for getting ip from mac address , if you dont have access to gateway. here is a post on how to do this: https://thebackroomtech.com/2010/08/22/determine-ip-address-from-a-mac-address/

Easy enough! Works perfectly on my HS105 btw, so you can maybe call those HS103/HS105.

Next issue. ugh. sorry about all this. I can't seem to get my GPIO equipment outlets working.. same wiring setup I used before with my other Pi3 that was just working. so I was just moving it over to a replacement Pi3. so I know for a fact that it's something in the OS settings. Temp sensors are working fine, just not the equipment outlets.

I updated all the settings as per this page.. anything else I might be missing or should check? **Edit - Also verified I can't get an LED light to turn on with GPIO. maybe something wrong with this new pi3?

reef-pi Guide 1: Setup and Demonstration

reef-pi is an opensource reef tank controller capable of automating day to day reef keeping chored including equipment control, temperature control, water level control, dawn to dusk light cycle. T...

learn.adafruit.com

Bigtrout · Dec 3, 2019

Zippyfear said:
Easy enough! Works perfectly on my HS105 btw, so you can maybe call those HS103/HS105.

Next issue. ugh. sorry about all this. I can't seem to get my GPIO equipment outlets working.. same wiring setup I used before with my other Pi3 that was just working. so I was just moving it over to a replacement Pi3. so I know for a fact that it's something in the OS settings. Temp sensors are working fine, just not the equipment outlets.

I updated all the settings as per this page.. anything else I might be missing or should check? **Edit - Also verified I can't get an LED light to turn on with GPIO. maybe something wrong with this new pi3?

reef-pi Guide 1: Setup and Demonstration

reef-pi is an opensource reef tank controller capable of automating day to day reef keeping chored including equipment control, temperature control, water level control, dawn to dusk light cycle. T...

learn.adafruit.com

Double check your wiring maybe you have a bad ground somewhere.

Ranjib · Dec 3, 2019

Zippyfear said:
Easy enough! Works perfectly on my HS105 btw, so you can maybe call those HS103/HS105.

Next issue. ugh. sorry about all this. I can't seem to get my GPIO equipment outlets working.. same wiring setup I used before with my other Pi3 that was just working. so I was just moving it over to a replacement Pi3. so I know for a fact that it's something in the OS settings. Temp sensors are working fine, just not the equipment outlets.

I updated all the settings as per this page.. anything else I might be missing or should check? **Edit - Also verified I can't get an LED light to turn on with GPIO. maybe something wrong with this new pi3?

reef-pi Guide 1: Setup and Demonstration

reef-pi is an opensource reef tank controller capable of automating day to day reef keeping chored including equipment control, temperature control, water level control, dawn to dusk light cycle. T...

learn.adafruit.com

hmm.. GPIO does not need any specific setting.

Whatever it is, we can figure it out if we do systematic troubleshooting. Lets focus on the specific issue first (GPIO not turning on LED). Share your setting, i.e. which GPIO you are using, how outlet and equipment is declared in reef-pi and finally your circuit. Share a picture if possible to illustrate the circuit and if you have multimeter take the voltage reading. Also share the reef-pi log when you click the equioment on/off button

Zippyfear · Dec 3, 2019

Bigtrout said:
Double check your wiring maybe you have a bad ground somewhere.

Is my config file supposed to look like this?

dtparam=i2c_arm=on
dtoverlay=w1-gpio
dtoverlay=pwm-2chan
dtparam=spi=off

Zippyfear · Dec 3, 2019

Ranjib said:
hmm.. GPIO does not need any specific setting.

Whatever it is, we can figure it out if we do systematic troubleshooting. Lets focus on the specific issue first (GPIO not turning on LED). Share your setting, i.e. which GPIO you are using, how outlet and equipment is declared in reef-pi and finally your circuit. Share a picture if possible to illustrate the circuit and if you have multimeter take the voltage reading. Also share the reef-pi log when you click the equioment on/off button

Right now, just broke the system down to the simplest components. verified the led's light on direct power. - gpio 23 and 24. pics attached. where are the logs located?

PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

just fyi on what version I'm running

Also, just FYI. I reloaded my original Pi3 and having the same issue. so I verified that it's not a hardware issue. because I've been using that one for a while with no issues.

Ranjib · Dec 3, 2019

wiring looks ok, for logs

Code:

journalctl -fu reef-pi.service

Check with multimeter the voltage on the +ve side of the LED or the connecting jumper, it should read 3.3v when on and 0 when off. You should also see 1 or 0 written in corresponding sysfs file

Code:

cat /sys/class/gpio/gpio23

Zippyfear · Dec 3, 2019

Ranjib said:
wiring looks ok, for logs

Code:

journalctl -fu reef-pi.service

Check with multimeter the voltage on the +ve side of the LED or the connecting jumper, it should read 3.3v when on and 0 when off. You should also see 1 or 0 written in corresponding sysfs file

Code:

cat /sys/class/gpio/gpio23

showing 0 on the multimeter - I see the posts when I click the button.

Dec 03 22:06:11 raspberrypi reef-pi[1781]: 2019/12/03 22:06:11 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:15 raspberrypi reef-pi[1781]: 2019/12/03 22:06:15 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:19 raspberrypi reef-pi[1781]: 2019/12/03 22:06:19 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:23 raspberrypi reef-pi[1781]: 2019/12/03 22:06:23 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Reading temperature from device: 28-f0a0a0abbd4f
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Reading temperature from device: 28-04177049bcff
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Temperature controller is running in dev mode, skipping sensor reading.
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 temperature sub-system: sensor Probe 3 value: 80.05
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Reading temperature from device: 28-2392abcabcabc
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Temperature controller is running in dev mode, skipping sensor reading.
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 temperature sub-system: sensor Probe 2 value: 80.94
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 temperature sub-system: sensor Probe 1 value: 80.69
Dec 03 22:06:25 raspberrypi reef-pi[1781]: 2019/12/03 22:06:25 health check: Used memory: 14.57 Load5: 0.62
Dec 03 22:06:26 raspberrypi reef-pi[1781]: 2019/12/03 22:06:26 API Request:' POST /api/equipment/7' from: 10.10.0.138:55250
Dec 03 22:06:26 raspberrypi reef-pi[1781]: 2019/12/03 22:06:26 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:06:27 raspberrypi reef-pi[1781]: 2019/12/03 22:06:27 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:30 raspberrypi reef-pi[1781]: 2019/12/03 22:06:30 API Request:' POST /api/equipment/7' from: 10.10.0.138:55250
Dec 03 22:06:30 raspberrypi reef-pi[1781]: 2019/12/03 22:06:30 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:06:31 raspberrypi reef-pi[1781]: 2019/12/03 22:06:31 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:35 raspberrypi reef-pi[1781]: 2019/12/03 22:06:35 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:39 raspberrypi reef-pi[1781]: 2019/12/03 22:06:39 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:43 raspberrypi reef-pi[1781]: 2019/12/03 22:06:43 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:47 raspberrypi reef-pi[1781]: 2019/12/03 22:06:47 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:51 raspberrypi reef-pi[1781]: 2019/12/03 22:06:51 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:52 raspberrypi reef-pi[1781]: 2019/12/03 22:06:52 API Request:' POST /api/equipment/7' from: 10.10.0.138:55250
Dec 03 22:06:52 raspberrypi reef-pi[1781]: 2019/12/03 22:06:52 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:06:54 raspberrypi reef-pi[1781]: 2019/12/03 22:06:54 API Request:' POST /api/equipment/7' from: 10.10.0.138:55250
Dec 03 22:06:54 raspberrypi reef-pi[1781]: 2019/12/03 22:06:54 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:06:55 raspberrypi reef-pi[1781]: 2019/12/03 22:06:55 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:59 raspberrypi reef-pi[1781]: 2019/12/03 22:06:59 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:07:03 raspberrypi reef-pi[1781]: 2019/12/03 22:07:03 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:07:05 raspberrypi reef-pi[1781]: 2019/12/03 22:07:05 API Request:' POST /api/equipment/4' from: 10.10.0.138:55250
Dec 03 22:07:05 raspberrypi reef-pi[1781]: 2019/12/03 22:07:05 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:07:06 raspberrypi reef-pi[1781]: 2019/12/03 22:07:06 API Request:' POST /api/equipment/4' from: 10.10.0.138:55250
Dec 03 22:07:06 raspberrypi reef-pi[1781]: 2019/12/03 22:07:06 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:07:07 raspberrypi reef-pi[1781]: 2019/12/03 22:07:07 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:07:09 raspberrypi reef-pi[1781]: 2019/12/03 22:07:09 API Request:' POST /api/equipment/14' from: 10.10.0.138:55250
Dec 03 22:07:09 raspberrypi reef-pi[1781]: 2019/12/03 22:07:09 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:07:10 raspberrypi reef-pi[1781]: 2019/12/03 22:07:10 API Request:' POST /api/equipment/14' from: 10.10.0.138:55250
Dec 03 22:07:10 raspberrypi reef-pi[1781]: 2019/12/03 22:07:10 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:07:11 raspberrypi reef-pi[1781]: 2019/12/03 22:07:11 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:07:15 raspberrypi reef-pi[1781]: 2019/12/03 22:07:15 API Request:' GET /api/me' from: 10.10.0.138:55250

Michael Lane · Dec 3, 2019

Soulreefer said:
hello @Ranjib or other friends , is this MCP23017 can still be input into reef-pi ?, sorry I need enlightenment because I read back there is rarely anyone talking about MCP23017, I just need an additional inlet for the Ato function.

Thank you very much.

Support for MCP23017 was not implemented in 3.0. On the other hand, we added support for using the PCA9685 as GPIO outputs, so that could free up some GPIO inputs.

Zippyfear · Dec 3, 2019

Zippyfear said:
showing 0 on the multimeter - I see the posts when I click the button.

Dec 03 22:06:11 raspberrypi reef-pi[1781]: 2019/12/03 22:06:11 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:15 raspberrypi reef-pi[1781]: 2019/12/03 22:06:15 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:19 raspberrypi reef-pi[1781]: 2019/12/03 22:06:19 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:23 raspberrypi reef-pi[1781]: 2019/12/03 22:06:23 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Reading temperature from device: 28-f0a0a0abbd4f
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Reading temperature from device: 28-04177049bcff
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Temperature controller is running in dev mode, skipping sensor reading.
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 temperature sub-system: sensor Probe 3 value: 80.05
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Reading temperature from device: 28-2392abcabcabc
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 Temperature controller is running in dev mode, skipping sensor reading.
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 temperature sub-system: sensor Probe 2 value: 80.94
Dec 03 22:06:24 raspberrypi reef-pi[1781]: 2019/12/03 22:06:24 temperature sub-system: sensor Probe 1 value: 80.69
Dec 03 22:06:25 raspberrypi reef-pi[1781]: 2019/12/03 22:06:25 health check: Used memory: 14.57 Load5: 0.62
Dec 03 22:06:26 raspberrypi reef-pi[1781]: 2019/12/03 22:06:26 API Request:' POST /api/equipment/7' from: 10.10.0.138:55250
Dec 03 22:06:26 raspberrypi reef-pi[1781]: 2019/12/03 22:06:26 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:06:27 raspberrypi reef-pi[1781]: 2019/12/03 22:06:27 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:30 raspberrypi reef-pi[1781]: 2019/12/03 22:06:30 API Request:' POST /api/equipment/7' from: 10.10.0.138:55250
Dec 03 22:06:30 raspberrypi reef-pi[1781]: 2019/12/03 22:06:30 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:06:31 raspberrypi reef-pi[1781]: 2019/12/03 22:06:31 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:35 raspberrypi reef-pi[1781]: 2019/12/03 22:06:35 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:39 raspberrypi reef-pi[1781]: 2019/12/03 22:06:39 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:43 raspberrypi reef-pi[1781]: 2019/12/03 22:06:43 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:47 raspberrypi reef-pi[1781]: 2019/12/03 22:06:47 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:51 raspberrypi reef-pi[1781]: 2019/12/03 22:06:51 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:52 raspberrypi reef-pi[1781]: 2019/12/03 22:06:52 API Request:' POST /api/equipment/7' from: 10.10.0.138:55250
Dec 03 22:06:52 raspberrypi reef-pi[1781]: 2019/12/03 22:06:52 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:06:54 raspberrypi reef-pi[1781]: 2019/12/03 22:06:54 API Request:' POST /api/equipment/7' from: 10.10.0.138:55250
Dec 03 22:06:54 raspberrypi reef-pi[1781]: 2019/12/03 22:06:54 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:06:55 raspberrypi reef-pi[1781]: 2019/12/03 22:06:55 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:06:59 raspberrypi reef-pi[1781]: 2019/12/03 22:06:59 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:07:03 raspberrypi reef-pi[1781]: 2019/12/03 22:07:03 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:07:05 raspberrypi reef-pi[1781]: 2019/12/03 22:07:05 API Request:' POST /api/equipment/4' from: 10.10.0.138:55250
Dec 03 22:07:05 raspberrypi reef-pi[1781]: 2019/12/03 22:07:05 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:07:06 raspberrypi reef-pi[1781]: 2019/12/03 22:07:06 API Request:' POST /api/equipment/4' from: 10.10.0.138:55250
Dec 03 22:07:06 raspberrypi reef-pi[1781]: 2019/12/03 22:07:06 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:07:07 raspberrypi reef-pi[1781]: 2019/12/03 22:07:07 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:07:09 raspberrypi reef-pi[1781]: 2019/12/03 22:07:09 API Request:' POST /api/equipment/14' from: 10.10.0.138:55250
Dec 03 22:07:09 raspberrypi reef-pi[1781]: 2019/12/03 22:07:09 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:07:10 raspberrypi reef-pi[1781]: 2019/12/03 22:07:10 API Request:' POST /api/equipment/14' from: 10.10.0.138:55250
Dec 03 22:07:10 raspberrypi reef-pi[1781]: 2019/12/03 22:07:10 API Request:' GET /api/equipment' from: 10.10.0.138:55250
Dec 03 22:07:11 raspberrypi reef-pi[1781]: 2019/12/03 22:07:11 API Request:' GET /api/me' from: 10.10.0.138:55250
Dec 03 22:07:15 raspberrypi reef-pi[1781]: 2019/12/03 22:07:15 API Request:' GET /api/me' from: 10.10.0.138:55250