Nevermind I play around with it and now it is fixed. I just deleted the Raspberry PI that was in the WWW folder and extracted a fresh one and it is working fine now.
There is a network icon for the wifi in the upper right corner. Click on it, select your network and enter your pass phase. You will then get network connection and the rest should work
I got the Wi-Fi working, but still had errors on all commands?
A screen grab of the console with a representative error or two might be helpful.
At least three things to be aware of with the latest release ("Jessie") of Debian/Raspbian:
- Chromium support is lacking (so far)
- in-bound html requests without an explicit path are now directed to /var/www/html instead of /var/www (which affects R'Pints - and BrewPi)
- the LXDE user startup file may have been moved to /home/pi/.config/lxsession/LXDE-pi instead of /etc/xdg/lxsession/LXDE-pi. I haven't confirmed this one so just be aware of the possibility.
I suspect that second issue will require some tweaking to the R'Pints package to straighten out...
Cheers!
You can avoid all that OS-evolutionary impact stuff by going back to the Wheezy release...
https://www.debian.org/releases/wheezy/
Cheers!
$ sudo /etc/init.d/flowmon start
$ sudo /etc/init.d/flowmon status
$ sudo /etc/init.d/flowmon stop
Check that the flowmon service is actually running (use the Status command below)...
Start the service:Check the service:Code:$ sudo /etc/init.d/flowmon start
Stop the service:Code:$ sudo /etc/init.d/flowmon status
Code:$ sudo /etc/init.d/flowmon stop
Cheers!
[edit] Just realized that the screen refresh happens but the volume doesn't change.
For that to happen I'm pretty sure flowmon must be running.
So, triple check you assigned the keg to the right tap and the corresponding Arduino pin.
If you get the pin wrong the update isn't going to work...
Cheers!
8&9, same ones I used last build, so I know they do work.
$ sudo /etc/init.d/flowmon stop
$ sudo python /var/www/python/flow_monitor.py
Sure! You can use phpmyadmin, open the raspberrypints database, open the beerStyles table, edit any desired records, then save the table.
Cheers!
#!/usr/bin/env python
import os
import RPi.GPIO as GPIO
import time
GPIO.setmode(GPIO.BCM)
cmd = 'xscreensaver-command -deactivate'
playsound = 'mpg321 /home/pi/bubbles.mp3'
PIR_PIN = 7
STATUS_PIN = 8
GPIO.setup(PIR_PIN, GPIO.IN)
GPIO.setup(STATUS_PIN, GPIO.OUT)
def MOTION(PIR_PIN):
os.system(cmd)
GPIO.output(8,True)
os.system(playsound)
GPIO.output(8,False)
try:
GPIO.add_event_detect(PIR_PIN, GPIO.RISING, callback=MOTION)
while 1:
time.sleep(100)
except KeyboardInterrupt:
GPIO.cleanup()
GPIO.cleanup()
#!/usr/bin/env python
import pwd,os
import time
import RPi.GPIO as GPIO
pir_pin = 7
GPIO.setmode(GPIO.BCM)
GPIO.setup(pir_pin, GPIO.IN)
global start_time
start_time=time.time()
sleep_threshold = 60
monitor_status = 1
cmd_sleep = 'chvt 6 && tvservice -o'
cmd_awake = 'tvservice -p && chvt 7'
time.sleep(10)
while 1:
time.sleep(10)
elapsed_time = time.time() - start_time
print elapsed_time
print monitor_status
# turn off monitor after the sleep threshold
# monitor_status value avoids turning of HDMI signal if it is already off
if elapsed_time > sleep_threshold and monitor_status == 1:
print "Turning Off HDMI"
monitor_status = 0
os.system(cmd_sleep)
# turn monitor back on upon detection
if GPIO.input(pir_pin) and monitor_status == 0:
os.system(cmd_awake)
print "Turning on HDMI"
monitor_status = 1
time.sleep(10)
start_time=time.time()
if GPIO.input(pir_pin):
start_time=time.time()
print "Resetting elapsed time to keep monitor on while movement detected"
time.sleep(10)
It looks like the code that I was using was using the TV service which completely shuts off the monitor, while the code you posted was blanking the screen with a screensaver. Here is what I was using:
Do you see anything I could do to speed up the process, or possibly a hybrid of the two that would blank the display for a few hours, and turn it off after a few more?
Hey Goat,
I would guess that how quickly a monitor recovers from power saving mode could very well be variable. Can you SSH into your RPi from a different system? If so, I suggest the following.
1. SSH into system
2. run command 'chvt 6 && tvservice -o' (without the quotes)
3. wait for monitor to be in power saving mode and then run 'tvservice -p && chvt 7' (again no quotes).
4. Note the time it takes your monitor to wake up.
If it is taking a long time there is not much you will be able to due, it is hardware dependent.
The second option is to mess with the sleep times in the script. The
time.sleep(10) right under the while 1: line simply causes the script to wait 10 seconds every time it loops. I put this in because without a delay the RPi was going nuts reading the pin for motion too often. So if you happen to arrive at the start of that 10 seconds it will not even start to wake up until that 10 seconds is complete. If you show up at the 9th second it will wake up in the next second.
So it really depends on if you find your delay is hardware or the script. Note that I would not take that delay below 4 or 5 seconds to avoid over polling the RPi pins. For my setup, I find the 10 second delay works well. When I enter my basement and walk around the corner the sensor sees me and even if it takes 5 or 6 seconds, by the time I a at my keezer the monitor is usually on, or will be in the next 2 to 3 seconds.
I hope this helps.
Chris
I tried most of last weekend and all of today so far and am about ready to sell the whole thing.
Enter your email address to join: