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

[5ft24]

What is the value given for memory?

That one I haven't found out yet.

 

[mr.salty]

Hi everyone. So I seem to think I have an issue with my reef pi. The clock at the bottom of the dashboard never says the correct time?

I have included some pictures as my temperature controller that I have configured to run with my tank temp probe is getting turned off even though I have set the temp to 26c with a 2c hysterisis. The tank temp is 26.5 and its turning it off?

Also have these errors but I think that's due to not having a graph uploaded on the dashboard after a restart.

Another issue is that my temp probes periodically go down to like -1300C for a split second?

Sorry for all the questions but hopefully this is where I can get the answers.

Only web view :-/

Sorry ranjib but I didn't want my question getting missed out as I'm a little stuck at the moment. What's your thoughts on the above? Thanks

 

[5ft24]

Sorry ranjib but I didn't want my question getting missed out as I'm a little stuck at the moment. What's your thoughts on the above? Thanks

did you ssh in to the pi and run sudo raspi-config to set the proper locale, timezone etc?

 

[robsworld78]

Just a heads up with those who have a Pi4 running, don't do any OS updates or your connectors will be broken or at least you'll get an error when you try to load them. I attached the error you would see.

Literally for the last 3 days I've been going back and forth with someone while two other wait trying to figure this out, it's been a nightmare. After eliminating everything it came down to a Pi4 OS update, this is not an issue with Pi3. You can do a fresh OS install on a Pi4 just don't update it. It breaks v3.2 to v3.4 and I assume anything before. When I discover an OS update can be done again I will post about it.

 

[Michael Lane]

Just a heads up with those who have a Pi4 running, don't do any OS updates or your connectors will be broken or at least you'll get an error when you try to load them. I attached the error you would see.

Literally for the last 3 days I've been going back and forth with someone while two other wait trying to figure this out, it's been a nightmare. After eliminating everything it came down to a Pi4 OS update, this is not an issue with Pi3. You can do a fresh OS install on a Pi4 just don't update it. It breaks v3.2 to v3.4 and I assume anything before. When I discover an OS update can be done again I will post about it.

I don't have a pi4, so I won't be able to recreate this; these UI errors are very difficult to track back. Is there anything in the log that might indicate a problem when you load that tab?
sudo journalctl -fu reef-pi.service

Also, can you tell if there are any issues/errors in dev tools when you navigate to that tab (other than the obvious one)? You should see the following network traffic.

 

[robsworld78]

I don't have a pi4, so I won't be able to recreate this; these UI errors are very difficult to track back. Is there anything in the log that might indicate a problem when you load that tab?
sudo journalctl -fu reef-pi.service

Also, can you tell if there are any issues/errors in dev tools when you navigate to that tab (other than the obvious one)? You should see the following network traffic.

I ran that line with it working, the 4 lines in your image shows up there and dev tools. When the connector page shows error unfortunately nothing shows in either. If there's anywhere else an error might go I can dig it up.

When I go to the console in dev tools it shows the file that is causing the problem but looking at the GitHub I think this might be generated or from something else as I can't find it.

 

[Ranjib]

What is the value given for memory?

Its % memory used: https://github.com/reef-pi/reef-pi/blob/master/controller/telemetry/health.go#L101 .

 

[Ranjib]

I ran that line with it working, the 4 lines in your image shows up there and dev tools. When the connector page shows error unfortunately nothing shows in either. If there's anywhere else an error might go I can dig it up.

When I go to the console in dev tools it shows the file that is causing the problem but looking at the GitHub I think this might be generated or from something else as I can't find it.

Do you have any error logged under the config -> error section? this can be due to driver loading failure. Its visible in logs only during reef-pi startup, so if you journalctl -fu reef-pi.service in one terminal, and systemctl restart reef-pi.service in another terminal, you should be able to see any driver loading error.

 

[Ranjib]

Sorry ranjib but I didn't want my question getting missed out as I'm a little stuck at the moment. What's your thoughts on the above? Thanks

No worries. Did you setup your timezone etc. as mentioned in the very first adafruit guide ? same as what @5ft24 mentioned.
The temperature issue could be related to circuit issue, or bad sensor or something else interfering with the sensor (inductive load, like metal halides etc)_

 

[Ranjib]

Sounds like a side project to me!

GUI for individual platforms (windows, linux, mac) are lot more work. We may end up writing mobile apps in future, but no plans on desktop app.

 

[mkane]

GUI for individual platforms (windows, linux, mac) are lot more work. We may end up writing mobile apps in future, but no plans on desktop app.

I’m debating tackling it this month with either native iOS or react native using MQTT messaging. Writing it in SwiftUI sounds like a lot of fun, plus that can be used for iOS , iPadOS and macOS.
If you guys need some official help let me know if not I’ll just side project it on a Saturday or Sunday. Ordered my pi4 and prob start with a ph probe and temp.

 

[Smin]

Hi all,
I just did an apt-get update+upgrade, I seem to have lost all connectors and get the error messages here:

Connectors configuration error after running "apt full-upgrade" · Issue #1190 · reef-pi/reef-pi

Connectors stoped working after running "apt dist-upgrade". Configuration/connectors page displays: TypeError: Cannot read property 'analog-input' of null. https://prnt.sc/tmj0g1 https://prnt.sc/tm...

github.com

I've checked the config and spi is still enabled which was my first though. Any ideas?

 

[ChrisNH]

Is this still the way to see the Prometheus feed? Its not displaying anything for me, just a blank page:

IP/x/metrics

 

[ChrisNH]

Im not sure. I think so. I have tested with 103, and 110. 100 looks very similar

I can confirm that the 100 seems to work with the 103 driver with my extensive battery of tests (turning a light on and off a few times with reef-pi)

 

[Ranjib]

Is this still the way to see the Prometheus feed? Its not displaying anything for me, just a blank page:

IP/x/metrics

reef-pi serves all prometheus data under /x/metrics endpoint. Just add that in your web browser (after reef-pi IP) and you should see all the data in plain text file.
Inside prometheus (or grafana), you'll have job tag with specific name you have configured prometheus (to scrape metrics from reef-pi), that can be used to see the metrics available.

 

[ChrisNH]

reef-pi serves all prometheus data under /x/metrics endpoint.

I went to another computer and it came up fine. It must be something about my dev machine. I am gtg, thanks.

 

[robsworld78]

Do you have any error logged under the config -> error section? this can be due to driver loading failure. Its visible in logs only during reef-pi startup, so if you journalctl -fu reef-pi.service in one terminal, and systemctl restart reef-pi.service in another terminal, you should be able to see any driver loading error.

Nothing shows up there and no driver loading errors. I'm testing with a fresh (empty) install of reef-pi so no drivers are installed or connectors.

My concern is if this latest OS updated makes it into the main Raspberry Pi OS image file the Pi4 will no longer work with reef-pi. Once this OS update is installed and the Pi is rebooted you can't access connectors. I think this is the issue @Smin and others have stumbled on.

Hi all,
I just did an apt-get update+upgrade, I seem to have lost all connectors and get the error messages here:

Connectors configuration error after running "apt full-upgrade" · Issue #1190 · reef-pi/reef-pi

Connectors stoped working after running "apt dist-upgrade". Configuration/connectors page displays: TypeError: Cannot read property 'analog-input' of null. https://prnt.sc/tmj0g1 https://prnt.sc/tm...

github.com

I've checked the config and spi is still enabled which was my first though. Any ideas?

Any chance you have a Pi 4?

If so reinstall Raspberry Pi OS (previously Raspbian) but don run the update and you'll be good.

 

[Bufu11]

I see a few builds with amazon links, anyone done a build in Canada with amazon Canada links ? Seems some
Of the parts used are not available. Would love to tackle this project, but my electrical skills are not up to par in finding similar parts with a confidence that they will work

 

[ChrisNH]

amazon Canada links ?

search for the item names on amazon.ca?

 

[Smin]

Nothing shows up there and no driver loading errors. I'm testing with a fresh (empty) install of reef-pi so no drivers are installed or connectors.

My concern is if this latest OS updated makes it into the main Raspberry Pi OS image file the Pi4 will no longer work with reef-pi. Once this OS update is installed and the Pi is rebooted you can't access connectors. I think this is the issue @Smin and others have stumbled on.



Any chance you have a Pi 4?

If so reinstall Raspberry Pi OS (previously Raspbian) but don run the update and you'll be good.

Thanks @robsworld78 I'll get on! happy to test bit and see if we can come up with a solution as well...