get an appropriate meanwell driver and connect pi pwm to that, and let meanwell supply the current to led,
Thanks for the help - figured out my issue. The Dosing pumps are running of the pca9685 - not the pi itself - so I adjusted the frequency in the driver for that - and now they're running at a speed that makes more sense.
Nothing to do... I tried :80 and :8080.
That is the last resort. But if you are comfortable with there are many workaround that does not involve resetting database. for example, you can stop reef-pi and run
reef-pi db show reef-pi settingsThis is expected. Kessil does not dim till 0. In my experience below 13 pwm values (0-100) my A80, A360 etc will start blinking. This is the reason we introduced "min" value for individual channels early on. that tells reef-pi to set the channel value to 0 when the computed value (From profile) is below the minimum value.
I connected by ssh and wrote the commands you suggested.
bject_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service filesbject_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service filesbject_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
Ouch.. its looks like the port is set to blank and as a result, reef-pi is crashing. You can save the settings in a file, change the address to include :443 , i.e "0.0.0.0:443" and then reupload it, start reef-pi back,.I connected by ssh and wrote the commands you suggested.
This is the output... port is not showed (it should be :80 by default).
pi@raspberrypi:~ $ sudo systemctl stop reef-pi.service
pi@raspberrypi:~ $ sudo reef-pi db show reef-pi settings
{"name":"Freccialata's Aquarium","interface":"wlan0","address":"0.0.0.0","display":false,"notification":true,"capabilities":{"dev_mode":false,"dashboard":true,"health_check":true,"equipment":true,"timers":false,"lighting":false,"temperature":true,"ato":false,"camera":false,"doser":false,"ph":true,"macro":false,"configuration":true,"journal":false},"health_check":{"enable":true,"max_memory":500,"max_cpu":2},"https":true,"pprof":false,"rpi_pwm_freq":100,"prometheus":false}
pi@raspberrypi:~ $ sudo systemctl start reef-pi.service
I aslo tried to open chromium-browser by terminal...
pi@raspberrypi:~ $ chromium-browser http://192.168.178.230
--disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
libEGL warning: DRI2: failed to authenticate
[4304:4304:1122/090203.048757:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
[4252:4437:1122/090203.726939:ERROR
[4252:4437:1122/090203.727980:ERROR
[4252:4437:1122/090203.728991:ERROR
Fontconfig error: Cannot load default config file
I tried the follow commands too:
chromium-browser http://192.168.178.230:80
chromium-browser http://192.168.178.230:8080
chromium-browser https://192.168.178.230:80
chromium-browser https://192.168.178.230:8080
Any other suggestion?
sudo reef-pi db show reef-pi settings > s.json
# edit the s.json file to change address and include port 443 in it.
sudo reef-pi db update reef-pi settings -input s.jsonpi@raspberrypi:~ $ sudo systemctl stop reef-pi.service
If the db update worked , you should be able to see it in db show command , and starting reef pi should not show any error in the log , . Can you check those two (db show and log during start)
Yes. Please use 3.5 version
are you running raspberry pi os or ubuntu? reef-pi pi3 package is compiled for arm7. i have tested it with pi 4 + raspberry pi os.
