MOVED TO NEW ORGANISERS WIKI
DoorBot Issue Log
20140627 DoorBot1: Had crashed, but a turn-it-off-and-on resulted in it not powering up. Swapping in the power supply from DoorBot3 brought it back to life. Trying the "dead" power supply on DoorBot3 and it has booted up okay, so maybe the shaking of carrying it between rooms freed something up(?)
20140627 DoorBot2: Crashed twice today, and needed rebooting.
20140423 DoorBot1: Wasn't opening the door. Could SSH into it fine, seemed to have got stuck playing stepon.wav, rebooted. - JMCK
20131104 DoorBot1: Changed wifi module options to disable powersave mode, following instructions on http://learn.adafruit.com/adafruits-raspberry-pi-lesson-3-network-setup/test-and-configure#fixing-wifi-dropout-issues
20130415 After some bugs had been fixed over the weekend DoorBot had 2 bugs: 1. Workshop door wouldn't open for some people who didn't have full access; 2. Main door wasn't logging hot desk visits. Both problems were due to the DOORBOT_ENV variable not being set before running logcards.rb. Rebooting the system would have done this correctly.
- 20130325 After modifying config and using the shell scripts to reload config on both doorbots, the doorbots no longer worked. Doorbot2 was rebooted, doorbot1 had logcards.rb ^C-ed in the screen, both worked following these actions.
20120428 When the doorbot came back up after a recent power cut, for some reason the main screen wasn't rotated to match its physical rotation. Fixed by JohnMcKerrell by removing the second screen and rebooting.