looking good. the graphs will look much better as time pass. This is state of the art observability (grafana+prometheus)Made progress on this board.. most things work properly now. The dosing control is still not quite there.. Don't really need it on the tank this is on though.
This has a DS18B20 on board for internal box temp, controls a fan on the cover. On the left you can see my sht31d breakout board that gets my room temp / humidity. Bottom right is 24v input power. Bottom left is one of the tank temp sensors, the other one is on the bottom right below the two PWM driven Chinese black box lights. the middle two two wire connectors are powering 24v actinic led bars. they run on an interval schedule so they are on in the AM and PM only.
There were a few issues with this board once I got it populated that needed to be addressed. The main issue was powering the pca9685 with 5v. That and the one wire connectors for temp sensing were on that power rail. I had to scab in a jumper to power them on 3.3v. Then there were various solder joints that were bad.
The 3.3v issue and the issues causing the dosing to not function have been resolved in the next revision of the board.
I should have that one in the next few weeks. Once I'm able to source parts, I will be able to let these out into the wild.
Here's a graph of everything from this install: (the black out on the right is from having it down today to put the new board in place.)
I have the zero w ( don't know what version), and want to enable remote access with vnc (so I can access it over the internet from anywhere). The one I have is not fast enough to do this. Which rpi is recommended for this?
I wouldn't run an GUI on the Zero.. Rpi 3 or 4 are fine for GUI though.
Do you guys mind sharing your query on equipment status... im a bone head.. and missing something.Made progress on this board.. most things work properly now. The dosing control is still not quite there.. Don't really need it on the tank this is on though.
This has a DS18B20 on board for internal box temp, controls a fan on the cover. On the left you can see my sht31d breakout board that gets my room temp / humidity. Bottom right is 24v input power. Bottom left is one of the tank temp sensors, the other one is on the bottom right below the two PWM driven Chinese black box lights. the middle two two wire connectors are powering 24v actinic led bars. they run on an interval schedule so they are on in the AM and PM only.
There were a few issues with this board once I got it populated that needed to be addressed. The main issue was powering the pca9685 with 5v. That and the one wire connectors for temp sensing were on that power rail. I had to scab in a jumper to power them on 3.3v. Then there were various solder joints that were bad.
The 3.3v issue and the issues causing the dosing to not function have been resolved in the next revision of the board.
I should have that one in the next few weeks. Once I'm able to source parts, I will be able to let these out into the wild.
Here's a graph of everything from this install: (the black out on the right is from having it down today to put the new board in place.)
I was looking at doing the realvnc cloud based solution, nothing to open on the router or firewalls and uses 2fa and I've changed all default passwords. Any thoughts or suggestions on this approach? Having the remote access back to monitor and make some changes as needed would be useful.This is just my opinion and I am sure lots of folks do certain things but I would never open anything on my local network to the internet at large. I am probably biased since Cyber security is my day job but I would never recommend doing that. If you want or have a need for remote access look into getting a router that supports a vpn of some sort, or some sort of Reverse proxy feature like https://guacamole.apache.org/ but depending on your level getting a replacement router that supports a vpn might be the easiest.
again just my .02
What that means based on how you have described it then realvnc is hosting a connection in the cloud that you connect to. In other words, it establishes an outbound active connection from the deivce and then you connect to it from a remote session. I would think then it comes down to how much you trust that cloud based service, im old and untrustworthy of most cloud based stuff but thats just me. I'd rather be in control of my security vs some service, but again thats just me. There are many firewalls out there that will let you do a VPN connection which I would consider a better solution but just my opinion.
Why I like the vpn option I'm not port forwarding anything, openvpn is my only open port.This is a persistent theme, and I'm cooking up something to help folks at least for secure web access back to their ReefPi from anywhere. I'll have more to share soon, as a free community service.
I'm a bit into Tom's camp from a remote access PoV (I have a good mesh of Wireguard tunnels up at all times between devices, makes roaming a dream), but its not something I'd expect from folks to understand how to setup, nor is it in their set of risk factors. Port forwarding can work, but it adds some other risk factors, and isn't workable for everyone (non-pseudo-static IPs, ISPs with less inbound allowance, etc). As Tom said, the right way is something like the venerable ngrok tunneling setup, just secure by default and no need for the silly free plan caps. More details soon.
Note that "using VNC" usually means you should either be using Reef-Pi on the web interface directly, _or_ just using SSH (for admin stuff). If you're using VNC to look at the web interface or opening the terminal, that's just silly
H probeError:write /dev/i2c-1: remote I/O error
I also use wireguard.. I do have a few things open to the internet, but wireguard on my phone makes it feel like I'm at home while at work..This is a persistent theme, and I'm cooking up something to help folks at least for secure web access back to their ReefPi from anywhere. I'll have more to share soon, as a free community service.
I'm a bit into Tom's camp from a remote access PoV (I have a good mesh of Wireguard tunnels up at all times between devices, makes roaming a dream), but its not something I'd expect from folks to understand how to setup, nor is it in their set of risk factors. Port forwarding can work, but it adds some other risk factors, and isn't workable for everyone (non-pseudo-static IPs, ISPs with less inbound allowance, etc). As Tom said, the right way is something like the venerable ngrok tunneling setup, just secure by default and no need for the silly free plan caps. More details soon.
Note that "using VNC" usually means you should either be using Reef-Pi on the web interface directly, _or_ just using SSH (for admin stuff). If you're using VNC to look at the web interface or opening the terminal, that's just silly
1) buy two of the cheap probes. Periodically check the probe your using for corrosion. If you get some or your temps get wonky then replace. Likely you never will have to.
