Jonesie wrote:Hey eqv,
Thanks for the excellent write up! I have a quick question for you regarding the slsnif.
I have been working on getting slsnif to compile on a Linux VM using the i.MX28 from Freescale, and I think I've got that working properly. My big problem now is that I don't know what to do to get slsnif to compile for the imx28. All the Googling I've done just leads me to pages about the setup, but not how to actually compile a program.
If you could point me in the right direction, I would be grateful. If you could provide me with a Wink-compiled version of slsnif, that would be even better.
Thanks - Jonesie
Hey Jonesie, sounds like you're almost there
It's been some time since I was messing around with this since my setup has been pretty stable. IIRC once you have the buildroot setup it's simply a matter of entering the buildroot shell (ltib -m shell) then building slsnif as you would normally (make etc). I think it setups up the env variables (CC, etc) properly. I've also attached my compiled version of slsnif, you can give that a try too.
JustinAiken wrote:So if I wanted a remote to control lights, I'd need to:
- Buy a
http://www.amazon.com/Lutron-PJ2-WALL-WH-L01-Remote-Control-Mounting/dp/B00JR202JQ/- Clone
https://github.com/evq/imx28-buildroot onto my rooted hub
- Get
http://www.freescale.com/webapp/sps/sit ... e=IMX28_SW - Untar ^^
- Place ^^ in the imx28-buildroot directory created from the git clone in the step above
- Run `docker build -t imx28 .` in that directory
- Install `goxc` (How do I do this? I tend to be lost on linux if I can't do `apt-get install thing`
- Clone
https://github.com/evq/lutron-spy to the rooted hub
- Go to that directory and type `goxc`, which complies the .go files into the binthing
- Set up the json config file
- `/etc/init.d/S60lutron-core stop` (Is this something that's from Wink, or created from your programs/steps??)
- `vi /etc/lutron.d/lutron.conf` as shown
- `./slsnif /dev/ttySP2 -x | ./lutron-spy &
- `/etc/init.d/S60lutron-core start`
- `aprontest -a -r lutron`
- ???
- Profit!!
Do I have that about mostly correct? If so, I think I'm going to order a pico or 4 and go for it...
Also, could you share your openHAB bindings/setup around it?
Hey JustinAiken. This is more or less correct. I've uploaded my precompiled verison of slsnif, and will also upload my compiled binary of lutron-spy in a few moments.The cross compiling step (goxc) as well as the clone of the lutron-spy take place on one's workstation, not the hub itself. Only the output linux arm binary is copied there.
With those two binaries in hand the process more or less boils down to your list:
- Buy the remote you linked
- Upload the binaries to the wink hub (make sure permissions allow them to be executed)
- `aprontest -a -r lutron` (Hold down the "on" button to pair IIRC)
- Set up the json config file (The remotes are indexed by serial number e.g. first one in the example is AEB551, so be sure to change these to match your paired remotes)
- `/etc/init.d/S60lutron-core stop` (Shutdown built in daemon on the wink to control lutron radio)
- `vi /etc/lutron.d/lutron.conf` as shown
- `./slsnif /dev/ttySP2 -x | ./lutron-spy &
- `/etc/init.d/S60lutron-core start` (Start up built in daemon, it initializes the radio we just spy on the result
I don't run openhab, I tried it some time ago but it just came across as rather over-complicated and bloated to me. A big part of that is the JVM, I just can't abide by it's standard footprint
I run all custom made home automation lighting and sensors. The various software glue is modular running in docker containers, a custom golang implementation of the Philips hue API sits in front of the lights, which is what you can see in the config example. I'm afraid that's probably the most transferable example I have, the other two APIs I'm planning on hooking up to it are my automatic window controls and my projector IR bridge which I am in the process of finishing off.