September 4

Boxee box and Boxee hacks XBMC

A good friend was kind enough to give me his Boxee box, since it was just collecting dust and the remote stopped working.

Step one root it:

Follow the instructions above, when you get to renaming the Host Name make sure you had a semicolon after boxeebox label.

Step two install xbmc:

I decided to install it on the device/internal memory rather than use the flash drive (sdcard is horrible for this).  I found this executible  but it didn’t work for me.

instead I telneted into the box: on port 2323 with password ‘secret’… the box is running

Linux IntelCE 2.6.28 #8 PREEMPT Wed Oct 12 07:18:29   BusyBox v1.10.2

wget -O /tmp/ && sh /tmp/ to install

Step three add flash drive anyways:

Main reason is there is only around 120Mb of space left, on the internal 1Gb of memory once your install is done…. so make sure its mounted under /media and that you update xbmc in settings to push all thumbnails etc… over to the drive. (**I had an issue with the second, most central USB port… don’t know if this is only on my Bbox but once I had the drive on the outer most USB port it worked without a hitch.)

Kinda nice to finally get a system up so quickly… the only drawback is that if you use the back button too many times any option selected seems “unselectable” you hear and see the select action happen but with out result… I then need to reboot to get the system to respond again.

Finally  if you want to add other services to run on this box think again… its running BusyBox which is extremely limited.

  • 8 May 2008 — BusyBox 1.10.2 (stable)BusyBox 1.10.2. (gitpatcheshow to add a patch)Bugfix-only release for 1.10.x branch. It contains fixes for echo, httpd, pidof, start-stop-daemon, tar, taskset, tab completion in shells, build system.

    Please note that mdev was backported from current svn trunk. Please report if you encounter any problems with it.

using LEEF as my external flash drive… (*you can use a 16Gb without issue unless you want to save your media on the box, a raspberry pi would work better for distribution/repository).

September 3

DCS1832 RFK5500 and wireless issues

Had an “open Zone” issue…after removing one of my motion sensors.

I thought it could have been an issue that I may have accidentally incurred, so at first I tried to isolate the problem by removing and then adding the wireless sensor in question… *8 , installer code [5555],  804 (wireless section) and then 001  then 01 which is the zone I had assigned to the front door.

This did not work and I must have made it worse because  the other doors in the same zone seemed to stop responding to open/close…I also tried removing and adding and that didn’t work at all…..

RESET: 969

Finally in frustration I decided to reset the keypad *8 , installer code [5555],  969, [5555],969….wait for the long beep.


Proceeded to add each of the sensors back in using wireless mode *8, installer code[5555], 898. Then open and close the windows doors and set the types (01=delay entry,05=motion for stay, 03=everything else/immediate)

Finally all the doors worked again….EXCEPT the front door… At this point I realized the sensor must be bad and I had wasted my time with the initial steps…..:hit wall

I removed the old sensor and added the new one using the wireless mode and everything is kosher again.