i think its on the cheapest range in off the shelf category... its quality is not that great. We have had defects in many cases.. Even if you build from scratch it will cost more with new parts (outlets , relays etc). If you have those parts, or find them by other means (i had gutted an existing surge protector when i first prototyped..) that would be cheaper.
the first guide uses the breadboard for testing initial setup and demo/dry run. You can run reef-pi with breadboard, but its not safe or secure (physically). Since most builds expected to run for years individual guides always use hat or proto boards.
I'll be checking again the ato alert, but last i did i was not able to reproduce this.
Oh wow@Ranjib posts coral pics to lighten the mood in this thread.
I have some neat news. A pair of angelfish successfully spawned and hatched eggs in my community tank! Dont know what to do. Let them be and nature take its course or try to move them to the empty section of the sump.
. Congratulations. My son will be super curious to see these tiny fishies .. i'll show this to him first thing tomorrow . Thank you for sharing
So.. "disable on alert" is working? the usage thing is a known bug. I'll get to it soon. Im trying to consolidate the ATO issue.. i definitely want to fix it asap, but having a hard time compiling it. Let me start a github issue.. where we can add the details
Wow... thats not good. Do you have macro or anything that will enable/disable ato?Just ran this as another test. Ran for 180 seconds with no alert or disable.
you have to use python ezo library from atlas to configure the ezo circuit in i2c mode. By default it uses UART, which reef-pi does not recognize
Got it. Can you disable this ato and create a new ato with same setting and see if that works? Im trying to diagnose if this is related to the past usage data or some other thing.
This is neat.randomly stumbled upon this because I am trying to generate a 0-10v apex like control from my system to manage the speed of my pumps. I am slowly getting rid of ecotech stuff because it is so closed. So a new pump on the way takes apex style 0-10v. Anyway...
Here is my setup...in case it helps anyone who wants to DIY it. I'll get around to putting the code and detail on GitHub.
It measures the main parameters, watches the sump level, pump details and other instrumentations so I can start and stop things as needed.
For example, I have a process on the RPi in Node-red that turn on and off the heaters. But I have a second process on the Ubuntu system that watches this information as a backup process. All of these are on UPS. I recognize this is a bit extreme
My favorite part is how I can control everything in HomeKit, so when I go to the basement to check on something I can turn things on and off on my phone.
Also, since this is mostly mediated by MQTT I can create synthetic devices. For example, I have a device called "do swap" and that turns off the pump, stops the heaters, and a bunch of other things and then turns on an evacuation pump for 15 min. Then turns on a pump to put saltwater back into the sump. But it only does this if the swap salt is close to the same SG/pH/Temp as the tank.
Once you instrument...you can do lots of stuff!
If anyone is interested I can detail out the sensors and wiring and other things.
My goal is to make this easier on the next person! So ask away...
Created a new ATO with the same parameters as the previous one and it worked as expected.
Edited parameters to higher threshold and they also worked
You cant , easily. Theres reef-pi db command that you can use to purge the data, but its more involved than simply using UI. If possible just recreate the temp controller/ato etc,
