Blog

[ do default stuff if no widgets ]

Archive for August, 2017

Software and SDK Updates

Thursday, August 17th, 2017

Software v2.6.0 Released

Version 2.6.0 of the GUI has been release. In this version there are two updates, new firmware version, and the ability to enable / disable built in profiles. Under advanced, you can now enable and disable each profile independently. This feature was done and promised for nearly a month, and we decided the feature, problem, and solution were novel, so we filed a patent. In order to try and protect anything globally, we couldn’t release the software until after the patent filing.

Firmware v4.2.1 Released

Also included in this version is a new firmware which will allow sending of RAW IR signals as outlined in the previous blog post.

SDK Updated

Kinda botched the original release with a ton of garbage commits as I got all my build software working. So I scratched it and started over. Also included in this version are static and dynamic libraries for Windows.

SDK Release, Linux, RPi, IR Transmit Support

Sunday, August 6th, 2017

Linux Updates

Over this past week I’ve re-written my linux deployment scripts. It was brought to my attention that things weren’t working right. A number of errors related to packages not being signed and trusted, which was fine on older versions of linux, but newer versions of debian weren’t having it. Also in combination with the released of the SDK, this had to get done.

I’ve also cleaned up the installation instructions and am now building standalone versions for users without debian. Not quite enough time to try and do RPM support, but it is planned. This should be more than sufficient for now. I’ll need to throw some instructions in the standalone version, but at least I have something up versus nothing at all.

You can find all this on the linux downloads page.

Raspberry Pi Release

As part of the linux deployment scripts, I’ve also taken the time to do one for the raspberry pi. Now the raspberry pi has it’s own apt repository, commandline version, and GUI. Long overdue. This was also a necessary step in order to build a static library for the released SDK.

SDK Release

We build all the flirc software around the SDK. So everyone can grab the SDK on the Flirc github page.

Needed is a lot of documentation. However, this is 99% identical to the same flirc_util cli that ships with the GUI. The only thing that’s not identical is the version command, which I’ll address later. But it serves as a complete example to integrating flirc pairing into your own application.

The libraries will be updated as part of GUI releases. It’s all part of the same build scripts. You’ll notice a lot of erroneous commits, that was just me working on my deployment scripts. That will stop.

Still needed is a python/perl wrapper, dynamic libs, a windows lib, and some better documentation.

IR Transmit Support

One of the new features on the new flirc is the ability to transmit IR code. There is a very small transmitter in flirc, it’s power isn’t the best, but it could certainly be useful for some home automation. I have some better features planned regarding this, but for now, an initial release is ready for users to start playing with. It only works with raw code right now and doesn’t understand protocol. The format is a comma delimited list of edges, that coincidentally can be retrieved with the GUI. Enable IR Debugging, hit a button on your remote, and you’ll get your list of edges. The :e:<num> is the delay in ms seen between packets. A big number means you haven’t hit the button in a while.

The latest API supports sending IR through a simple interface:

The commandline also supports sending a packet out with the exact list of edges seen.

Example code in the SDK is fairly straight forward, it parses the list of comma delimited edges, checks for errors, puts it in a buffer, and calls the api:

For the IR transmit to work, you’ll need firmware version v4.2.+

I’ll post this in the forums somewhere, or you can email me, but I expect to release this publicly in about a week after I do some more testing.