Hey all,
I just talked to Tavio from Phat Beets, he had a few cards that did not
seem to be working. I tested all three and got unreliable results. I got
every combination of both light (green blink, green solid, red blink) and
failure / success of opening latch.
Especially of note, is that one card of a type I'm fairly certain does not
work correctly, when swiped incorrectly, creates a red light, but also
successfully opens the latch. This gives me the impression that an error
code (rather than a card's unique code) has been incorrectly added to the
whitelist!
And overall, swiping is incredibly inconsistent even for my own card, which
I know to have worked well for a long time.
I'm going to buy at least one usb magnetic card reader right now, please
join me in fixing this system so it works consistently, reliably, and
securely ASAP.
// Matt
I noticed that a bunch of people are being added to the access control
system without any contact info. Just a name and the name of the person
adding them.
Is it reasonable to require an email or phone number for people who have
access to the omni? I suppose if the collective they're a part of is
listed then it should be OK to just put their name..
also, when people put someone into the access database, i think they
should either be entered with #ANNOUNCE "handle" or #OPTOUT so that we
know whether people have been offered the announce feature or not.
presently if someone doesn't have ANNOUNCE enabled i assume that they
haven't been offered and ask them if they will opt-into announce.
Although that's hard if there is no contact information listed for them.
-jake
The magstripe card access system at the front door works again.
The problem? It got unplugged from electricity. It needs to be plugged
in. Presently it's plugged into an extension cord.
There is a backup battery in it, which can operate for a really long time,
and as soon as it's unplugged, it starts telling us in IRC (hacker
chatroom) and we start telling each other to plug it back in, but none of
us are there.
This happened, and everyone in the chat was like "lol plug it back in pls"
but it didn't happen. Instead people came by Omni and marveled at the
various wires in the system, thinking they must be the problem. One
person replaced the wires to the door, wiring them incorrectly in the
process.
Eventually it got plugged back into the extension cord and powered up
again, but I had to fix the rewiring that happened while people were
trying to fix it. It works now.
Moral of the story: we are going to wire the thing into the AC wiring of
the building so this doesn't happen anymore.
If you have questions please let's discuss it on the appropriate list,
which is:
access(a)lists.sudoroom.org
thank you!
-jake
I should have posted last night, but anyway the front door access is
working again.
the magnetic strip card reader is on the right side now. When you swipe
your card, you will hear a happy note and the door will click, and you can
pull it open for 8 seconds.
If your card is not entered in the system or you swipe it wrong, you will
hear a sad note, and someone from sudoroom might come investigate :)
the passive door is presently only held in place by a latch at the top.
We need to put a stick on the lower half of the door so it latches at the
bottom too. The panic bar mechanism has a place to pull a lower stick
upward to release, so really all we need is a steel pole and a hole in the
cement for it to catch in. Who wants to do this?
-jake
ok i worked on the front door a lot and i got it physically decent with
the electric strike now working.
replaced the fried arduino, and made a DC power cable to the USB hub since
the 5V line on the beaglebone black got fried when the arduino got fried,
when the people taking out the old door presumably ripped everything out.
i changed the serial device name in index.js for doorjam, but for whatever
reason it doesn't autostart. if i run node index.js from the commandline
it works! but psy log doorjam returns nothing, ever, because psy is not
running it. why? I don't know. who knows?
when i run /etc/init.d/doorjam start, it says
root@omnidoor:/etc/init.d# ./doorjam start
Starting doorjam (via systemctl): doorjam.serviceJob failed. See system journal and 'systemctl status' for details.
failed!
so i edited /etc/init.d/doorjam to refer only to /root/doorjam/index.js
and NEVER to /opt/doorjam which I renamed so people stop using it already.
nobody uses /opt ok
so i tried this:
psy start --logfile /var/log/doorjam.log --name doorjam -- node /root/doorjam/index.js
and then in another window i ran psy log doorjam, here's what it said:
!!! PROCESS SPAWN: PID 1422
module.js:340
throw err;
^
Error: Cannot find module '/opt/doorjam/index.js'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:902:3
!!! PROCESS EXIT: 8
!!! PROCESS SLEEP
over and over and over again. why is it looking for /opt/doorjam/index.js
?????????????????/ i don't know, my psy command (above) did not mention
opt.
so i ran screen, and in screen i ran "node index.js" and it's working.
fix it.
oh, don't forget our git branch is "oldstyle" not master
-jake
I'm cutting hard keys and beginning to distribute.
Would be better to keep the # of hard keys down, and more digital keys.
Anyone planning to work on this?
I'm sitting here with new sudoer Morgan who is giving it a shot at the
moment... probably could use more help.
// Matt
Howdy folks,
I've got new keys to:
+ Front Door
+ Secure Storage
+ Basement Storage
+ Green Room or A/V Room
+ Editing Room
As a member, please obtain approval to be a keyholder via your member collective, and gather a mandatory $5 deposit.
As a non-member please submit a request to keys(a)omnicommons.org responding to the questions on our Key wiki page:
https://omnicommons.org/wiki/Keys
// Matt
Omni has a new front door, the locks have been changed, and our new
key policy is in effect:
https://omnicommons.org/wiki/Event:2015/05/07_Weekly_Delegates_Meeting#Prop…
Any member will be allowed to have a key card, but Sudoroom still has
to decide who gets a hard key. Should we give one to every member who
wants one? Should members have to specifically ask at a meeting?
For the record, I want one.
