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

Don’t UI errors show up in the errors log? If so, what is the ”log” tab fir, this is the same question I asked last week. Mine has always been blank even when I get errors in the error log.
The error section under configuration tab is for serious /backend errors that should not be ignored. Things like driver failures, missing probes etc come up there.

The ui errror tab is kinda confusing and I am thinking of getting rid of it eventually ,will discuss this more with @Zekth , in case he has some more thoughts
 
For anyone else getting this, the trick is to enable prometheus, save config, reload, refresh, THEN add mqtt details in the telemetry tab. I think it was trying to add parameters before it set them up.
As I suggested you in your threrad, MQTT Explorer is a free software for Windows, MacOS, Ubuntu (debian, mint, neon, fedora, etc…) and Linux (almost every linux)... it's very easy and clean software to use.
 
As I suggested you in your threrad, MQTT Explorer is a free software for Windows, MacOS, Ubuntu (debian, mint, neon, fedora, etc…) and Linux (almost every linux)... it's very easy and clean software to use.
The issue was reef pi error, not the lack of feed info. You can also sniff available feeds with mosquitto_sub from the command line with something like this:

mosquitto_sub -h localhost -u homeassistant -P password -v -t '#'
 
The error section under configuration tab is for serious /backend errors that should not be ignored. Things like driver failures, missing probes etc come up there.

The ui errror tab is kinda confusing and I am thinking of getting rid of it eventually ,will discuss this more with @Zekth , in case he has some more thoughts
don’t get rid of it, use it to be an event log. Outlet on, outlet off, Dosed for 30 seconds successfully, etc, etc. with a time stamp, I think this would be helpful.
 
Simple feature that would help me a lot - add a free text field to the dosers config page - so that after I calibrate the pump I can put down:

150s = 38ml
45ml = 1dkh

So I can quickly figure out how much I need to tweak dosing by when my alk is off.

(Or allow us to enter how many ml a calibration resulted in, and let us dose by ml)
A dedicated field/actual volume calculation would be nice for sure, but in the meantime, why don't you use the name field for that? My carbonate doser channel isn't called "Alkalinity", it's called "Alkalinity 2s@33%=0.2ml"
 
A dedicated field/actual volume calculation would be nice for sure, but in the meantime, why don't you use the name field for that? My carbonate doser channel isn't called "Alkalinity", it's called "Alkalinity 2s@33%=0.2ml"
That’s smart! I’m going to copy. I’ve kept a note on my phone but that’s a hassle.
 
Yeah that circuit will put out a 0-10v analog signal so just need a few components.
Didnt realize you already did all the work with Robo-Tank, considering the Ezo is $40 alone the deluxe board is a crazy deal. Was going to be getting a Apex Lite locally for 175 until I realized it couldnt do 0-10V. Now i'm getting 8 power ports and basically a full Apex after I solder everything you give and plug my existing Ph sensor in. Cheers you just saved me tons of $$ and time :D
 
A dedicated field/actual volume calculation would be nice for sure, but in the meantime, why don't you use the name field for that? My carbonate doser channel isn't called "Alkalinity", it's called "Alkalinity 2s@33%=0.2ml"
I have a spreadsheet that I use to fiddle with Dosing. I add all my calibration test data to get to what speed I want the doser to run and then I have a separate page to work out my timing for doses.

In Calibration, I think it would be nice to be able to do a couple of calibration tests (or even just one) so that you can tell reef-pi that X seconds at Y% speed = Zml. Then you can set your speed to the Y value and then specify all your doses in ml. I originally thought it might be nice to have say a 3-point calibration test, but I realised calibration might not be linear across the speed range, so setting it at one specific speed is probably better. Maybe have the calibration test enter the speed value, so there is less chance of getting that wrong?
 
Hey Reef-Pi people,
If I set up each channel of my my Kessil A160WE as separate lights instead of a two channel light will I be able to show the cycles on the dash board?
Thanks
 
Hey Reef-Pi people,
If I set up each channel of my my Kessil A160WE as separate lights instead of a two channel light will I be able to show the cycles on the dash board?
Thanks
No. Currently reef-pi dashboard does not support multi channel light dashboard. If you model individual channel as independent light , you can get charts for diurnal and couple of other profiles
 
Didnt realize you already did all the work with Robo-Tank, considering the Ezo is $40 alone the deluxe board is a crazy deal. Was going to be getting a Apex Lite locally for 175 until I realized it couldnt do 0-10V. Now i'm getting 8 power ports and basically a full Apex after I solder everything you give and plug my existing Ph sensor in. Cheers you just saved me tons of $$ and time :D
Good to hear, instead of pricing by the features I went by cost, components are cheap so why not give as much as possible.
 
Hate to ask but I've been reading and reading and can't find an answer. I'm trying to add pca9685 driver and keep getting "I/o error http 500" what are solutions?? I2cdetect is showing the board
 
Hate to ask but I've been reading and reading and can't find an answer. I'm trying to add pca9685 driver and keep getting "I/o error http 500" what are solutions?? I2cdetect is showing the board
Welcome to r2r. Can you share what you see in i2c detect and the driver configuration for pca9685 ?
 
Ranjib,

Thank you for adding the MQTT support . I am having issues when I enable and configure it. Not sure if I am doing something wrong but I have same results across 3 separate Reef-Pi's

The Mosquito server is working fine, I have about 60 devices talking over MQTT, just can't get the Reef-Pi to communicate.

Any ideas....

Thanks Mark

MQTT issue.JPG
 
Ranjib,

One more question, any idea on timeline for implementing additional I/O specifically inputs ? While ago you were mentioning adding support for MCP23017.
 
Ranjib,

One more question, any idea on timeline for implementing additional I/O specifically inputs ? While ago you were mentioning adding support for MCP23017.
I am interested too, I bought already a pcb with the MCP23017 about half a year ago, hoping it would be supported, I can do some testing to get it working.
 
I am using the Diurnal cycle with my Kessil A160WE, and my blue channel will not turn on with less than a setting of 10. I have the minimum set to 10 to try to work around this, but now during the cycle ramp up the blue channel flashes until it gets to 15. I can manually change the minimum level for that channel to 15 but then the light does not turn all the way off a the end of the cycle. Any suggestions?

thanks
 

TOP 10 Trending Threads

Back
Top
Home
Post thread…
Market
What's new