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

[JT26]

Just got hs300 and a chinese Black box and want to add on, however I might have to reset my reef-pi , as i haven’t login for a long time and don’t remember the password, even try the default password and can’t get in.

Can anyone give me the step to reset? I also need to upgrade to the latest version as well.

 

[cnidus]

Just got hs300 and a chinese Black box and want to add on, however I might have to reset my reef-pi , as i haven’t login for a long time and don’t remember the password, even try the default password and can’t get in.

Can anyone give me the step to reset? I also need to upgrade to the latest version as well.

depending how much config you have, it could be easiest to just reset the db from Linux she’ll via ssh. I believe that will Reset everything, including password back to defaults

 

[BenB]

Just got hs300 and a chinese Black box and want to add on, however I might have to reset my reef-pi , as i haven’t login for a long time and don’t remember the password, even try the default password and can’t get in.

Can anyone give me the step to reset? I also need to upgrade to the latest version as well.

Reset DB inclusive reefpi password (SSH in to your pi and enter the 3 commands below one by one):
sudo systemctl stop reef-pi.service
sudo rm -rf /var/lib/reef-pi/reef-pi.db
sudo systemctl start reef-pi.service

 

[Ranjib]

Ok small update. It seems only one of my HS300’s is not working, the other strip is working fine via reef-pi.

both strips work via the kasa app.

only difference I noticed was I had named the outlets on one strip in Kasa (return pump vs default of ‘plug 3’ etc. this is the strip that’s not working with reef-pi.

Would that have an effect on the API naming perhaps? (Will go look up the API from the hs300 reef pi driver I guess).

What else should I be doing to troubleshoot? I was avoiding removing the driver as I have macros, temps, timers etc that refer to these ports, so I’d have to remove all them first to avoid db reference issues?

Do you see any error under the configuration section ? Try turning on the relevant equipment and check log during that time . Sometime the driver load fails due to reef-pi starting before network. Reloading reef-pi should solve that, without rebooting pi

 

[Ranjib]

Ok small update. It seems only one of my HS300’s is not working, the other strip is working fine via reef-pi.

both strips work via the kasa app.

only difference I noticed was I had named the outlets on one strip in Kasa (return pump vs default of ‘plug 3’ etc. this is the strip that’s not working with reef-pi.

Would that have an effect on the API naming perhaps? (Will go look up the API from the hs300 reef pi driver I guess).

What else should I be doing to troubleshoot? I was avoiding removing the driver as I have macros, temps, timers etc that refer to these ports, so I’d have to remove all them first to avoid db reference issues?

Yes . Don’t delete driver without deleting its references . It will cause mayhem. I’m trying to fix that in future release . Reef-pi will not allow deleting an entity that’s being used

 

[Ranjib]

I remember when I first started the reefpi the standard stereo audio jacks where consistently failing for a lot of people, myself included. Did we ever source a more robust jack?

I’m still using 3.5 mm audio jack. I have seen aviation connectors having good rapport. Robotank and few others are using jst type connectors .

 

[Ranjib]

Just got hs300 and a chinese Black box and want to add on, however I might have to reset my reef-pi , as i haven’t login for a long time and don’t remember the password, even try the default password and can’t get in.

Can anyone give me the step to reset? I also need to upgrade to the latest version as well.

You can stop reef-pi and use reef-pi reset-password

 

[Ranjib]

Reset DB inclusive reefpi password (SSH in to your pi and enter the 3 commands below one by one):
sudo systemctl stop reef-pi.service
sudo rm -rf /var/lib/reef-pi/reef-pi.db
sudo systemctl start reef-pi.service

This is a very common issue. We have a dedicated command to fix it. Other than that, since reef-pi 3.2 (I think , could be 3.0) we have reef-pi dB command that can selectively update /delete /backup things . It’s all command line though

 

[JT26]

Thank you for all the help guys ran :
sudo systemctl stop reef-pi.service
sudo rm -rf /var/lib/reef-pi/reef-pi.db
sudo systemctl start reef-pi.service

I can log in now. Have to brush up on reef-pi now. Searching for update to latest version and go back in to setup temp sensor and hs300. I'm using ML HAT and connect pi

That was easy enought got upgrade to reef-pi 3.4. now onto setting up other things

 

[JT26]

That was easy e

You can stop reef-pi and use reef-pi reset-password

Too late, wipe out the db and now starting over. Now it's not seeing the temperature sensor :(

you think maybe the temperarture go out? Whats the odd of this?

 

[bishoptf]

I’m still using 3.5 mm audio jack. I have seen aviation connectors having good rapport. Robotank and few others are using jst type connectors .

Yeah I am using JST-SM connectors for all of my connectors, some are using mini-xlr and some are using aviation connectors. So far I really like the JST-XM connectors but depening on how you do things might require a crimper. I would forget about the reset of the pi if you pull out a temp sensor, no issues with the JST connectors or other style connectors, plenty options to choose from.

:)

 

[cnidus]

Yes . Don’t delete driver without deleting its references . It will cause mayhem. I’m trying to fix that in future release . Reef-pi will not allow deleting an entity that’s being used

I ended up deleting equipment on hs300a, deleted the driver, Re-added it and then changed connectors to use the new driver, reset up everything after that. All working now.

I don’t think it was a simple network race condition, since the other hs300 was actually working.

It would be good to have some sort of ‘driver status’ and ‘retry connection’ or something to help with drivers that are attaching to network connections in the future though.

 

[AbjectMaelstroM]

I ended up deleting equipment on hs300a, deleted the driver, Re-added it and then changed connectors to use the new driver, reset up everything after that. All working now.

I don’t think it was a simple network race condition, since the other hs300 was actually working.

It would be good to have some sort of ‘driver status’ and ‘retry connection’ or something to help with drivers that are attaching to network connections in the future though.

That's strange that it's dropping out and something to watch for. I'm running a 303 and 103s on my QT setup and it's been running 24/7 for about two months now. *knock on wood*

 

[Auto-pilot]

Hey guys i was hopping someone could give me some advice on how to get my ph probe working. Ive had my system running for a while but never got the ph working. I have a blue acro pico board a pinpoint ph probe and im running 3.3.1. I started and couldnt figure it out its been several months and i'm trying again!

 

[Des Westcott]

Hey guys i was hopping someone could give me some advice on how to get my ph probe working. Ive had my system running for a while but never got the ph working. I have a blue acro pico board a pinpoint ph probe and im running 3.3.1. I started and couldnt figure it out its been several months and i'm trying again!

You can try the instructions from @MichaelLane here - might help.

 

[EL_HARVEY]

Hi folks, I’m struggling to get a dosing unit going. I set up a pi zero setup following the dosing guide but the guide I have found is dated. I’m on the new pi03.4 version and everything works till I try to save a new pump. When I hit save I get 2 immediate “404 page not found | HTTP 404” errors and the pump fails to save. I don’t understand the error msg so it’s super difficult to diagnose. I can’t tell if this is a problem with the jack setup(I think it’s odd that the pins in the jack setup are 0 and 1 vs a PIN number but I’m not that familiar with PWM setups,) the reef pi version difference, 3.4 software, or I’f there’s something wrong with the wiring/setup on the proto board. Any help will be very appreciated. Meanwhile I’m going to find some python code to see if I can get the pumps working outside Reef-pi to make sure the wiring is all correct.

 

[Auto-pilot]

You can try the instructions from @MichaelLane here - might help.

I'm not sure if theres supposed to be a link? I was looking at the git hub and found a fix for the pico board but did not know how to to use it. Not sure what environment is needed.

 

[Ranjib]

Hi folks, I’m struggling to get a dosing unit going. I set up a pi zero setup following the dosing guide but the guide I have found is dated. I’m on the new pi03.4 version and everything works till I try to save a new pump. When I hit save I get 2 immediate “404 page not found | HTTP 404” errors and the pump fails to save. I don’t understand the error msg so it’s super difficult to diagnose. I can’t tell if this is a problem with the jack setup(I think it’s odd that the pins in the jack setup are 0 and 1 vs a PIN number but I’m not that familiar with PWM setups,) the reef pi version difference, 3.4 software, or I’f there’s something wrong with the wiring/setup on the proto board. Any help will be very appreciated. Meanwhile I’m going to find some python code to see if I can get the pumps working outside Reef-pi to make sure the wiring is all correct.

Can you share a screenshot of your dosing screen and connector screen ?

 

[Ranjib]

Hey guys i was hopping someone could give me some advice on how to get my ph probe working. Ive had my system running for a while but never got the ph working. I have a blue acro pico board a pinpoint ph probe and im running 3.3.1. I started and couldnt figure it out its been several months and i'm trying again!

Which version of pico board you are using ? I have not been able to test pico board ph functionality due to firmware issues with the board I have. Cross check with @theatrus . I don’t know very many people who have it running , which makes it hard for me to know for sure if it’s working at all in the wild .

 

[Auto-pilot]

Which version of pico board you are using ? I have not been able to test pico board ph functionality due to firmware issues with the board I have. Cross check with @theatrus . I don’t know very many people who have it running , which makes it hard for me to know for sure if it’s working at all in the wild .

It says rev D on the board