- Joined
- Feb 14, 2020
- Messages
- 985
- Reaction score
- 1,325
- Location
- Edmonton, Canada
- What state or country do you live in
- Canada
I'm really sorry to hear of your lose, some people here are good at spotting things in the logs, if you can post them maybe the why could be answered.Hi all,
Word of warning for all Reef Pi users. I went away for a couple of weeks with a neighbour watching over my tank and feeding every couple of days together with close my close monitoring via Reef Pi. He alerted me that the tank was a little quiet a couple of days ago, I tried to logon to Reef Pi (via VNC) but it didn't work (I didn't think anything of it and I assumed it was something with VNC). Unfortunately I retuned last night to a tank at 35/95 Celsius/Farenheight and full of dead livestock.
I tried logging into the app via the usual home WIFI - but I still couldn't and had to power cycle the whose raspberry pi and which point I was able to login and I received a flurry of emails that the temperature was too high.
It appears the app/raspberry pi crashed with the heater in the 'on' position. For reference, I'm using a full system built by robo-tank (although to be clear this wasn't hardware related - the relay is working perfectly).
This isn't a complaint or moan I am very grateful to Ranjib and all the other developers of this free platform but:
1. I would strongly advise everyone to invest in an audible temperature alarm (can be bought off Amazon for < $10). I have literally lost 000's of dollars by not having this.
2. I would advise against using a non-thermostatic heater (i had a 500W titanium heater)
3. I would be happy to share any files/more information from my Reef Pi instance that would help prevent this happening again
Last edited:


The I2C communications can make it unreliable especially in DIY setups where wires are involved or if some piece of equipment is causing lots of interference such as an LED driver that was mentioned the other day. When a command is sent to the pca9685 it's basically figures crossed it made it in tact so it understands what it should do, if not the pin won't switch until another command is sent. I've played extensively with I2C in the past and quickly learned one shouldn't get carried away with too many devices connected and extra checks in the code is needed to verify things along the way. It is possible to read the state of any output and verify the command sent actually did what it was supposed to, here's a post explaining. If this was implemented chances of a pin not switching would be greatly reduced. Unfortunately I wasn't able to add it to reef-pi.



