Can we input multiple days?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Never mind. I was able to open that link. Thank you.
Could we get if-then-else statements for the macros that take sensor data and equipment statuses as parameters? Or are the different subsystems too dissimilar under the hood?
Could have a wide range of applications, from custom alerts, to automated fallback procedures in case of emergencies like a floor water sensor tripping or a power outage being sensed somehow, maybe even regulating different reactors without having to code an entire subsystem for each one-off application.
Unless it already exists somewhere and i am too stupid to see it?
reef-pi will not have DSL (domain specific language) like Apex. The if/else/then like construct are exposed via ATO (binary sensor) and temperature/ph (analog sensor). reef-pi will allow seamless integration of those modules with macro (linear steps with reversible execution). DSL require more work and exposes arbitrary workflows that are very hard to diagnose when things go wrong.Could we get if-then-else statements for the macros that take sensor data and equipment statuses as parameters? Or are the different subsystems too dissimilar under the hood?
Could have a wide range of applications, from custom alerts, to automated fallback procedures in case of emergencies like a floor water sensor tripping or a power outage being sensed somehow, maybe even regulating different reactors without having to code an entire subsystem for each one-off application.
Unless it already exists somewhere and i am too stupid to see it?
We have to do much better job at validation on reef-pi side. Currently only outlet deletion are validated. Across the board connectors , drivers , modules (temperature, ph, light , etc) all components must validate zero dependency before deletion. In absence of this , users are prone to get into inconsistent state leading to a lot of issues. That’s not acceptable , I’ll make sure we get this in 3.x series .Yesterday I had the temp probe / calibration / loose wire issue. Personally I don't think it was a bad connection issue, as unplugging one probe and replugging it caused all 3 temp readings to immediately re-appear - but I could be wrong - it just doesn't feel right.
Last night I went to feed - I have a "Feed" Macro that turns off pumps, skimmer etc for certain durations and then back on to minimise uneaten food. Every time I hit the Macro, I would get the "Fatal Error" like below.
I thought it was WiFi related, so waited a while and tried various devices and all the same thing. Then I discovered that I could go to the equipment tab and control individual equipment directly without getting the error. Try "Feed" macro again, same error. Try run other macros, no error.
Obviously sleeping on this problem has led to an epiphany, because within minutes of waking up this morning, I remembered something. Step one in my "Feed" macro is to turn temperature control off. Yesterday's temp probe issue had me delete my main temp control and re-configure it - renaming it in the process. This made the macro point to a temp control that doesn't exist any more. I fixed the macro by telling it the correct temp control and problem solved.
So the issue was entirely of my own making, but maybe a more relevant error message would make it easier for people to troubleshoot the issue when faced with a similar mistake.
We have to do much better job at validation on reef-pi side. Currently only outlet deletion are validated. Across the board connectors , drivers , modules (temperature, ph, light , etc) all components must validate zero dependency before deletion. In absence of this , users are prone to get into inconsistent state leading to a lot of issues. That’s not acceptable , I’ll make sure we get this in 3.x series .
Slight problem, my reef pi was running perfectly for quite a while, I recently noticed that the calcium had stopped dosing, despite being programmed correctly, also my main temperature sensor whilst working was displaying weird numbers.
So I decided to run the update from 2.3 to 3.0, the dosers didn't work at all and one temperature sensor went off line.
So I went back to the updated 2.3 isn't available for uploading, so I tried 2.5 dosers are working now, though my calcium dosers LED is dimly illuminated full time. Now non of my temperature sensors are working at all.
Any suggestions?
You have to clear the db and rebuild the programming.
sudo systemctl stop reef-pi.serviceHow do I do that?
Thank you, I'll try that when I reach back from work.sudo systemctl stop reef-pi.service
sudo rm -rf /var/lib/reef-pi/reef-pi.db
sudo systemctl start reef-pi.service
How do I do that?
sudo systemctl stop reef-pi.service
sudo rm -rf /var/lib/reef-pi/reef-pi.db
sudo systemctl start reef-pi.service
Do it when you get home. It's going to completely wipe the reef-pi, including any login information.Thank you, I'll try that when I reach back from work.
Do it when you get home. It's going to completely wipe the reef-pi, including any login information.
Ok, I've done it and installed 3.0, got the temperature sensors working, it's late now and I'm too tired to figure anything else out. Lots of things not running right now! Something's in my notes aren't making sense, so I'll need to open everything up tomorrow.
Quick question, do I need to reconfigure everything from the console again?
Hi all.
second post... first question:
Is it possible to connect the BS18B20 temperature sensor to the raspberry? which jumpers?