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.Ui errors. If nothing is in there, then it’s good.
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.
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.Ui errors. If nothing is in there, then it’s good.
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.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.
Btw this is a bug that I have to fix , it’s not acceptable for reef-pi to crash due to this type of failure.
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.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.
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: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.
mosquitto_sub -h localhost -u homeassistant -P password -v -t '#'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.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
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"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)
That’s smart! I’m going to copy. I’ve kept a note on my phone but that’s a hassle.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"
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 :DYeah that circuit will put out a 0-10v analog signal so just need a few components.
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.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"
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 profilesHey 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
Good to hear, instead of pricing by the features I went by cost, components are cheap so why not give as much as possible.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
Welcome to r2r. Can you share what you see in i2c detect and the driver configuration for pca9685 ?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

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.Ranjib,
One more question, any idea on timeline for implementing additional I/O specifically inputs ? While ago you were mentioning adding support for MCP23017.