lets hope they are reliable enough. I have one controller running with it, full ato , light timer etc. here’s the build thread : https://www.reef2reef.com/threads/5-5g-budget-nano-reef-pi-open-design.648179/
Yes. They use auto key encryption, which I learned from the Nodejs based Kasa library. reef-pi is using exact same scheme to control these smart outlets. Your kasa app will work as it is. It’s just another thing that will control these devices. This also means you now have two places to control those outlets.
This is a bug :-( https://github.com/reef-pi/reef-pi/issues/829 , it only works at hourly or greater threshold. I was planning to fix it as part of 3.0 release. Unless you need this urgently.Hey guys,
Does the ATO Disable on Alert not work for anyone else?
I have it set to disable if it's on for more than 5 seconds but that never occurs. Just stays on. I'm dry testing this all right now with a mechanical float switch and while it does switch on and off as the levels change in the tank, the "safety" never kicks in.
Also, this is on reef-pi 2.5
I think you can get away by running it at 3-5 second interval. I have never ran it at 1 second interval, but i dont think anything will break. Real time is not possible currently, we have to implement a different type of driver and I dont think the effort is worth the benefit right now.Would you recommend running two float switches? A higher failsafe switch that cuts off the circuit from the 1st float to reef-pi to add a safety net? My ATO pump is a bit... Oversized and will fill the tank within seconds so I'm trying to figure out the best way to prevent a catastrophe
Also I noticed that the check frequency on the ATO by default is 60 seconds. This means reef-pi checks the input pin every 60 seconds and the pump will run (for a minimum) for 60 seconds. Would it be possible to have reef-pi check the input status almost real-time once the ATO is signaled ON to prevent overages from oversized ATO pumps like mine? Lol.
I set it to 1 second for the reason above, don't know if that negatively affects anything. I didn't notice any increased CPU usage on the pi.
Thank you so much for the kind words. It means everything to me and rest of the folks who makes this project possible.
I use an L293D (H-bridge board) for exactly this to power my doser pump motors. The pins are entered into reef-pi as 0,1,2,3,4, etc just like the rpi driver, but there's more of them. You'll need 6 pins, ENA, 1, & 2, and ENB, 3, & 4 - which for me are 0,1,2,3,4,& 5 on the PCA9685. If you're powering something like a motor, EN will be the "power" switch and then you'll either end up with 1 dummy pin that's always set to "off" or be able to switch between forward and reverse by turning one high and one low and vice versa.
As far as I understand, the PCA9685 is specifically for things that require a PWM signal (different from frequency), so basically leds and servos only.
You need only two pwm pins, en1 and en2. IN1/2/3/4 all can be connected to pi GPIO if you want to contol the moto diection. For LEDs it does not make sense. You can just hook them up to 3.3V rail and GND,
with 3.0 , we will be able to use pwm outputs as notmal digital output. In that case its basically 100% duty cyle or 0% duty cycle. So L293D could be entirely driven by pca9685 IC, or even relay contol. I have not tested this, theres a pca9685 driver bug that also i need to fix before i start field testing
