you are using pca9685 for pwm?
I do have a pca9685 in my build, but only for the light control, which I haven't got to configuring yet.
The pwm for my dosers is controlled by GPIO 18 & 19.
For reference, here is my list of connections:
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.
you are using pca9685 for pwm?
I almoat did the same thing, using a computer case, which is ok if you use ethernet. I have a pi zero w and was afraid a fully enclosed case would affect wifi of the pi.
Other than the wifi issue, you should have no issues. In fact with the case being grounded, everything is a safer especially your 120v stuff, and probably more immune to noiseThank you [B]Bigtrout[/B] i could use Ethernet if i need to just like to be sure no electrical noise will cause any problem.Looks nice that box and fit perfect everything .Thank you (and that case i have 12v 5v and 3.3v if i need
I dont see any issue. I find it very difficult to source 10v power adapter , which is why the current setup is. The other reason was dc pumps for dosers are 12V, and adj power strip relays are also 12v, that's why 12V preferred in the adafruit guides. Let me know if you find a good 10V adapter, im totatly down for kessil only slim controller. In fact i think we can power by 5v 3A , and used a boost converter to generate 10V.Hi Ranjib I been read up all your project forum over at adafruit and github site. I notice one of the built for mulit kessil control section your using a dc-dc buck to get 10v from the 12v power supply. I'm trying to limit the size of the overall project box as small as possible, is there a reason why not to just use an 10v regulator on the 12v power supply? btw only need 2 pwm channel so not using an pca9685 break out board.
This is awesome. Thank you so much for sharing this.For anyone interested in adding temp sensors without soldering a resister you can use the on board raspberry pi resistors to the pin of your temp sensor data line. Just make a python script that runs the pull up code for that pin and have it run at startup in something like rc.local...I've found this much more reliable as some of these temp sensors are really sensitive manipulation.
#TempPullup.py
import RPi.GPIO as GPIO
import time
GPIO.setmode(GPIO.BCM)
GPIO.setup(##, GPIO.IN, pull_up_down=GPIO.PUD_UP)
#Script End
## being the pin you put the temp sensor data line to.
Cheers.
I dont see anything that would cause obvious issues. I like the abundance of space :-)
HI,Yes :). In 3.0 prerelease you have to click on the Prometheus checkbox under Configuration -> Settings page and reload reef-pi. Once that happens, reef-pi will provide all metrics under /x/metrics endpoint. which is then you can configure in Prometheus for scraping. Finally, grafana is configured against Prometheus to fetch and chart the centrally collected data.
Let me know if you need any help with this. If theres any interest, i'd be happy to post detailed end to end setup instruction.
Not sure who else is using it. I won’t expect most, as they are not familiar with web operations like stack :-) . But here’s my setupHI,
Has anyone activated this?
Not sure who else is using it. I won’t expect most, as they are not familiar with web operations like stack :-) . But here’s my setup
![]()

1) enable Prometheus metrics under configuration -> settings , and reload reef-piI have installed prometheus, now how do I configure it to see the metrics of reef-pi?
global:
scrape_interval: 15s
scrape_timeout: 10s
evaluation_interval: 15s
alerting:
alertmanagers:
- static_configs:
- targets: []
scheme: http
timeout: 10s
api_version: v1
scrape_configs:
- job_name: prometheus
honor_timestamps: true
scrape_interval: 15s
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
static_configs:
- targets:
- localhost:9090 <--- here ip of reef-pi? /x/metrics ?
1) enable Prometheus metrics under configuration -> settings , and reload reef-pi
2) configure Prometheus to scrape reef-pi, and reload. Your configuration looks correct. I’ll highly encourage running prom and grafana in separate server.
You can cross check that reef-pi is exposing the metrics correctly by hitting pi ip /x/metrics in your browser, it should reveal all the metrics (temperate , ato usage etc) in plain text, with each metric in individual line
![]()
![]()
[/QUOTE
I'm sorry I didn't have the / x / set , now works