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

Maybe I'm missing the point, but why can't Reef-Pi email you the backup at a schedule of your choice. Same email address as you use for alerts. How big would the file be if it's just a backup of your settings / config?
it absolutely can.. we have to just agree that this is a good idea
- Do we think its ok to have backups in email
- What if the data is big, and we fail to emal? A popular way to configure alerts is via sms , and specify sms gateway as email address.
 
Is there any way to set up auto start of equipment for when the reef-pi is rebooted or in case of a power outage?
 
Is there any way to set up auto start of equipment for when the reef-pi is rebooted or in case of a power outage?
reef-pi should bring them to their expected state, if you had kept them on/off via UI, its should come back to exactly same state upon startup. Is it not working as expected?
 
it absolutely can.. we have to just agree that this is a good idea
- Do we think its ok to have backups in email
- What if the data is big, and we fail to emal? A popular way to configure alerts is via sms , and specify sms gateway as email address.

Can we figure out what the settings / setup file backup size is on a reasonably complex build?

I didn't realise people setup email to SMS alerts. That isn't a network option here in SA.

Could a feature be written to try make the file size smaller to work with SMS's?

As long as the file gets sent somewhere and the backup exists, figuring out how to access it is better than wishing you had it [emoji23]

Maybe make the addition of a valid email address part of the login process and "hardwire" ReefPi to send an email only when configuration is changed?

Just throwing ideas out. That last one came to me while I was typing this. Haven't really thought it through.

Des
 
Can we figure out what the settings / setup file backup size is on a reasonably complex build?

I didn't realise people setup email to SMS alerts. That isn't a network option here in SA.

Could a feature be written to try make the file size smaller to work with SMS's?

As long as the file gets sent somewhere and the backup exists, figuring out how to access it is better than wishing you had it [emoji23]

Maybe make the addition of a valid email address part of the login process and "hardwire" ReefPi to send an email only when configuration is changed?

Just throwing ideas out. That last one came to me while I was typing this. Haven't really thought it through.

Des

There's a service that Gmail offers, check if it's available in South Africa.
 
How to do macros? Example, I have want to turn 3 pumps off for 10 minutes for feeding, glass cleaning or water change etc.. there doesn't seem to be any option for this or am I missing something?
 
Well that's one of the obstacles, since any remote connection will require passwords for login unless we use SSH keys. Not a fan of storing passwords in scripts or in files for execution.

Still mulling things in my head, the easiest would be to have an additional USB thumb drive and write the files locally. That would be easy for most of the pi's except the zeros since they are micro USB.

:)
Isn't there a way to store the password similar like in the wpa_supplicant.conf file?
I mean the wpa_passphrase tool at https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md
 
Is anyone else able to run "make deb" on a MAC and have it work. I get errors when trying to package everything up.
 
So I am attempting to try and run a newer version of reef-pi to see if it resolves my PCA9685 issues. If I build against "master" the UI doesn't come up. So I backed off to a commit before the translation code. In this version it appears that you have to add the PCA as a "Driver". Every time I attempt to add it the UI suggests address "68". When I save I get an error "Failed to create. Error: remote I/O error". I assume I don't have the correct i2c address. Anyone know how to figure out the correct address?
 
Is anyone else able to run "make deb" on a MAC and have it work. I get errors when trying to package everything up.
I develop exclusively on Mac. You need ruby , Andy run bundle install (to install fpm), before building Debian package
 
So I am attempting to try and run a newer version of reef-pi to see if it resolves my PCA9685 issues. If I build against "master" the UI doesn't come up. So I backed off to a commit before the translation code. In this version it appears that you have to add the PCA as a "Driver". Every time I attempt to add it the UI suggests address "68". When I save I get an error "Failed to create. Error: remote I/O error". I assume I don't have the correct i2c address. Anyone know how to figure out the correct address?
You have to run “npm install “ to get all ui related packages, followed by ‘make ui-dev’ which will start webpack.

On developer machine (Mac or windows or Linux) check the dev-mode under configuration, to stub out all i2c calls. If you are getting the error in raspberry pi, then check if i2c is enabled , and check the i2c address is indeed in use by i2cdetect -y 1
 
Regarding the pca9685 frequency issue , @Michael Lane pointed out a possible bug in the driver where we are setting the frequency after wake up call... I’ll get back to this during weekend.
 
Would it be possible to get reef-pi split off into its own form catagory? 514 pages on 1 topic makes it difficult to search and understand
 
I develop exclusively on Mac. You need ruby , Andy run bundle install (to install fpm), before building Debian package

I have ruby and have run bundle install. To be more specific to what I am doing, I am running
Code:
make clean
make pi-zero
make deb
This results in this error
Code:
mkdir -p dist/var/lib/reef-pi/ui dist/usr/bin dist/etc/reef-pi
cp bin/reef-pi dist/usr/bin/reef-pi
cp assets/favicon.ico dist/var/lib/reef-pi/ui/favicon.ico
cp -r ui/* dist/var/lib/reef-pi/ui
cp build/reef-pi.yml dist/etc/reef-pi/config.yml
mkdir dist/var/lib/reef-pi/images
bundle exec fpm -t deb -s dir -a armhf -n reef-pi -v 2.1-52-gc74e8f6 -m [email protected] --deb-systemd build/reef-pi.service -C dist  -p reef-pi-2.1-52-gc74e8f6.deb .
Adding action files
Debian packaging tools generally labels all files in /etc as config files, as mandated by policy, so fpm defaults to this behavior for deb packages. You can disable this default behavior with --deb-no-default-config-files flag {:level=>:warn}
Process failed: tar failed (exit code 1). Full command was:["tar", "-C", "/var/folders/tm/676jfg9516s8cwfh5g78y5cw0000gn/T/package-deb-build-f66a215c065e4e510dee2e574c96aa13d5fbd0aa07d761e5b24b23974457/control", "-zcf", "/var/folders/tm/676jfg9516s8cwfh5g78y5cw0000gn/T/package-deb-build-f66a215c065e4e510dee2e574c96aa13d5fbd0aa07d761e5b24b23974457/control.tar.gz", "--owner=0", "--group=0", "--numeric-owner", "."] {:level=>:error}
 
Would it be possible to get reef-pi split off into its own form catagory? 514 pages on 1 topic makes it difficult to search and understand
"Split off its own form category".. I am sorry I am not able to understand this. Can you explain what is category, what if form? Give us an example
 
I have ruby and have run bundle install. To be more specific to what I am doing, I am running
Code:
make clean
make pi-zero
make deb
This results in this error
Code:
mkdir -p dist/var/lib/reef-pi/ui dist/usr/bin dist/etc/reef-pi
cp bin/reef-pi dist/usr/bin/reef-pi
cp assets/favicon.ico dist/var/lib/reef-pi/ui/favicon.ico
cp -r ui/* dist/var/lib/reef-pi/ui
cp build/reef-pi.yml dist/etc/reef-pi/config.yml
mkdir dist/var/lib/reef-pi/images
bundle exec fpm -t deb -s dir -a armhf -n reef-pi -v 2.1-52-gc74e8f6 -m [email protected] --deb-systemd build/reef-pi.service -C dist  -p reef-pi-2.1-52-gc74e8f6.deb .
Adding action files
Debian packaging tools generally labels all files in /etc as config files, as mandated by policy, so fpm defaults to this behavior for deb packages. You can disable this default behavior with --deb-no-default-config-files flag {:level=>:warn}
Process failed: tar failed (exit code 1). Full command was:["tar", "-C", "/var/folders/tm/676jfg9516s8cwfh5g78y5cw0000gn/T/package-deb-build-f66a215c065e4e510dee2e574c96aa13d5fbd0aa07d761e5b24b23974457/control", "-zcf", "/var/folders/tm/676jfg9516s8cwfh5g78y5cw0000gn/T/package-deb-build-f66a215c065e4e510dee2e574c96aa13d5fbd0aa07d761e5b24b23974457/control.tar.gz", "--owner=0", "--group=0", "--numeric-owner", "."] {:level=>:error}
do you have tar installed? Looks like fmp is invoking tar which is in turn failing. Makefile has the fmp command codified in it, you can invoke it directly to get debug output
 
Regarding the pca9685 frequency issue , @Michael Lane pointed out a possible bug in the driver where we are setting the frequency after wake up call... I’ll get back to this during weekend.
It would be great if it was something pretty simple and easy to find!
 
"Split off its own form category".. I am sorry I am not able to understand this. Can you explain what is category, what if form? Give us an example
As in you just have a whole section for Reef Pi (not part of DIY). Then all reef Pi related questions can go there with their own topics and headings and discussions that are easier to search.
 
It would be great if it was something pretty simple and easy to find!
I'm finishing the assembly on a small batch of boards this weekend. I'll probably jump on the pwm issue this weekend if Ranjib doesn't get to it first. I think I realized the reef-pi issue when I was working on the test script for my boards.

I'm sure we'll have the pwm issue sorted very soon!
 

IF YOU HAD TO TAKE A REEFING EXAM, WOULD YOU PASS?

  • Yes!

    Votes: 32 45.7%
  • Not yet, but I have one that I want to buy in mind!

    Votes: 9 12.9%
  • No.

    Votes: 26 37.1%
  • Other (please explain).

    Votes: 3 4.3%
Back
Top