- Joined
- Jun 11, 2019
- Messages
- 118
- Reaction score
- 152
I will make a screenshotI'll do some test, thank you!!
Can you please share your timer and macro config? On my Controller Timer and Macro seems to do nothing on light...
Last edited:
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.
I will make a screenshotI'll do some test, thank you!!
Can you please share your timer and macro config? On my Controller Timer and Macro seems to do nothing on light...
Correct, or you have to wait until the moment the timers are set and kick in....Thank you!! So with the macro you "initiate" the system right? Because I've seen that the timer won't trigger the lights on or off by itself...
@Ranjib There's no easy way to use the same channel both as Diurnal and Moonlight? Or maybe a simple way to control light enable/disable with timer without using macros..
Alright, I had a look at the code for the PWM-profiles on github and diurnal works with a cosine to the power of 3. The profile looks like this for different min/max settings:
![]()
The diurnal profile is at the minimum value outside the start and end times. In between the Start and End Time it ramps up and down.
At exactly the start time (denoted 0) it starts ramping up from the minimum, to the maximum. This takes about 1/5 or 20% of the time interval between Start and End. After about 1/10 or 10% of the interval the light is in the middle between minimum and maximum value ( in the plot: (80%+10%)/2 = 50% )
The same thing happends towards the end, at about 4/5 or 80% of the interval between start and end the light starts ramping down. It will have fallen half the way towards the minimum at about 9/10, or 90% of the interval between Start and End. At exactly the End time it will reach the minimum again.
Practical Example:
I set my light to Minimum 0% and Maximum 80%, since my light is a bit too strong, between 08:00 and 16:00.
It will slowly start up at exactly 08:00, reaching 80% shortly past 9:30 (20% of 8 hours are about 1 hour 30 minutes).
A few minutes before 14:30 it will start ramping down, reaching 0% exactly 16:00.
Something I saw as well, which @Ranjib mentioned in another thread:
there is a light profile called "composite", which seems to stitch together different light profiles for their respective programmable interval. In my case I could use this to, for example, have a diurnal between 08:00 and 16:00 and afterwards run a much weaker lunar profile between 16:00 and 08:00.
It's not exposed in the GUI yet, put I'm hopefull that I can either set this manually or wait for the update.
I am getting a similar error with a fresh install on Pi-3 when installing Reef-Pi V6.0.I don't think so. Today is 3rd day I'm trying to install it on different hosts - from oldest Raspberry 1 (at least started), next is Raspberry Pi Zero W, and also tried on Orange Pi Zero 2W. At ALL boards I see error that embedded rpi driver cannot be accessed:
started reef-pi.service - raspberry pi based reef tank controller.
Jun 16 11:50:15 reef-pi reef-pi[1279]: 2024/06/16 11:50:15 driver-subsystem: Failed load raspberry pi driver. Error: can't build hal pin 9: strconv.Atoi: parsing "31+rpt": invalid syntax
Can someone try to reproduce?
another version of this error:
Jun 16 12:00:25 reef-pi systemd[1]: Started reef-pi.service - raspberry pi based reef tank controller.
Jun 16 12:00:25 reef-pi reef-pi[1495]: 2024/06/16 12:00:25 ERROR: failed to initialize drivers. Error: can't build hal pin 2: strconv.Atoi: parsing "31+rpt": invalid syntax
Jun 16 12:00:25 reef-pi reef-pi[1495]: 2024/06/16 12:00:25 Successfully started subsystem: system
I tried many versions from 4.3 to 6.0 - all gives me the same.
I am getting a similar error with a fresh install on Pi-3 when installing Reef-Pi V6.0.
I have previously run V5.1 successfully so I did a fresh install with 5.1 using the exact same process and did not get the error. Tried V5.3 and got the error again. I have tried this several times with the same results.
I just loaded the latest from the Imager - looks like that is bookwormAre you running Raspberry Pi OS Bullseye?
I believe so, https://github.com/reef-pi/reef-pi/issues/566 think it lists it as PCA9685 - wether thats the same or notJust curious after searching this thread and the github, were MCP23017 drivers ever added?
There's definitely still life in it, i just think one has to lower their expectations since the last "update" as we all know was Nov 2022...I understand that since RPI foundation removed old methods of GPIO access, there is a temporary work around to revert the kernel in bookworm back to Kernel 6.1.74, which still supports the older methods of GPIO access. Try:
sudo rpi-update d86b5843d68b9972a5430a6d3da1b271cfc83521
I've not tried, but came across this in my reading as I need to redo my reef-pi set up as my 24vdc power supply went up in smoke and took out my system with AC power getting through to my goby hat and taking out sections of the PCB tracks
I hope there is still life yet in reef-pi as I was just about to get on with rebuilding my system.......