alarmdecoder.com

Hey guys,

Just wanted to double-check but is the AD2USB compatible with the AlarmDecoder Raspbian image (http://www.alarmdecoder.com/wiki/index.php/Raspberry_Pi) or is that *strictly* for the AD2PI? I have an AD2USB from a previous project I was trying to get working with an old Linksys NSLU2. I've pretty much given up on that unit at this point and have since picked up a RPI. Was interested in the AD2PI but wanted to try utilizing the AD2USB since I already have it.

I could definitely go back to what I was doing (ser2sock + OSSEC) but the AlarmDecoder-specific Raspbian image and features seems pretty sweet (Python APIs and webapp!)

That is the official Raspbian image, only modified to include our libraries as well as take over the "COM" port on the GPIO. The AD2USB will work great with this as well as the AD2Pi, or the AD2Serial with a USB to Serial adapter. Basically, it supports all of our products, and gives the features listed on our wiki page. In the beta image there is a web application to interface with the device including from a phone or tablet.

Thanks,
Kevin

kevin wrote:That is the official Raspbian image, only modified to include our libraries as well as take over the "COM" port on the GPIO. The AD2USB will work great with this as well as the AD2Pi, or the AD2Serial with a USB to Serial adapter. Basically, it supports all of our products, and gives the features listed on our wiki page. In the beta image there is a web application to interface with the device including from a phone or tablet.

Thanks,
Kevin

Cool! I just tried loading the stable version and was wondering why I didn't see the webapp but *just* read your post (and *just* noticed the "Includes" table at http://www.alarmdecoder.com/wiki/index.php/Raspberry_Pi)

Maybe I'll try out the Beta version next. I did notice something about the disk usage though. I used Apple Pi to dump the AlarmDecoder Raspbian zip onto an 8gb SD card and see this currently in the OS:

root@alarmdecoder:/var# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 2.6G 2.2G 254M 90% /
/dev/root 2.6G 2.2G 254M 90% /
devtmpfs 211M 0 211M 0% /dev
tmpfs 44M 216K 44M 1% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 88M 0 88M 0% /run/shm
/dev/mmcblk0p1 56M 19M 38M 34% /boot


Is there a particular reason why only 4gb of usable space has been allotted? Maybe a configuration/environment issue I didn't take into consideration when loading the zip onto the SD?

The images are fixed in size to work on the smallest uSD cards in this case 4g cards. Once you are up and running you can use the raspi-config tool to make adjustments and expand your disk. Its a good idea to backup your disk first or just be prepared to flash from scratch just in case things go wrong.

http://elinux.org/RPi_raspi-config#expa ... ll_SD_card

Re
Sean M

From the last comment in this thread, it sounds like the AlarmDecoder raspbian images are supposed to fit on a 4 GB card.

I'm trying to use the Win32 Disk Imager to burn the beta image (2014-08-18 version) onto a 4 GB (capacity identified as 3.68 GB) card but I get an error saying the image size is 8388608 sectors but only 7733248 sectors (size 512) available on the micro SD card. Windows says the image is 4,194,304 KB.

Is there a smaller version of the beta image available that still fits on a 4 GB card?

Thanks,

Dominic

We only officially support 8GB cards - that is the minimum we sell, and that is the default that comes from the Newark/Element14 NOOBS bundle - sorry if that's an inconvenience, I don't know if we are able to support multiple different images at this time. In theory, 4GB would have worked, but it's not something we've ever tested. Default Raspbian would work, I think.

No problem Kevin. I picked up an 8 GB card for $10 and got it all working. I had just been trying to use the 4 GB card since I had one lying around.

Thanks!

Dominic