It’s with great excitement to finally announce a partnership that was years in the making. Felix, the creator of Remote Buddy, and I have been working for over a year on an extensive collaboration. While I give him the majority of the credit for the bigger piece of the collaboration, I am nevertheless honored to have worked with him.

Remote Buddy 2.0 is available for download, and packs a punch of features. It’s not only powerful, extensive, but it’s beautiful.

Exclusive Features

Remote Buddy 2.0 is built on an incredible architecture, with support for a number of receivers, and a number of remotes. But being the creators of each, gave us the unique opportunity to work on features together not found anywhere else. Flirc and Remote Buddy work together in concert and with incredible integration and advanced features.

How It Works

Flirc has a number of USB interfaces. The normal ones you are already familiar with. The pairing interface, and the HID (keyboard/misc) interfaces. Alongside this interface sits the new remote buddy interface, and it’s been there since version v4.6.0 of the flirc firmware. It’s been shipping for 9 months, and is already enabled on all existing and new devices. When the remote buddy interface is active, the HID interface is not, so only one interface is supported at a time. The Flirc GUI will not interrupt Remote Buddy’s operation, and allows easy upgrades without the need to quit Remote Buddy.

Lowest Latency

Since most post processing is done through remote buddy, Flirc passes up the data as quickly as possible for the lowest latency and best experience on the market.

Beta Features

New to Remote Buddy and Flirc is a new feature for customizable wake support. You can pair a single apple remote, a range of apple remotes, or a unique key from any remote to wake up a computer From S0/S1/S3 sleep states.

To try this out, grab the latest beta firmware from the forums here. Remember to give us feedback.

Upcoming Features

We’re already hard at work on adding more new features, but would also love to hear your ideas. Leave a comment here or through the forums, or send Felix an email.

Discounted Flirc with Valid Remote Buddy 2.0 License

We worked hard to create the best IR receiver for Remote Buddy. And we want as many people as possible to enjoy the level of detail, functionality and integration we’ve achieved.

So we’re making an offer so good it’d be financially stupid to pick a different, inferior product:

Remote Buddy users with a license valid for version 2.0 will be able to purchase one Flirc for only $9.95 (excluding shipping). This offer will not expire and only be valid through the flirc.tv store.

Felix and I are working together to make this offer available through a new Benefits page that will roll out as soon as possible.

Should you have eagerly purchased a Flirc in advance from our store, around the time of this announcement, please get in touch and we’ll work together to extend the discount to you.

Head on over to the flirc store and enjoy discounts up to 50% off today and through next week. Happy Holidays!

Cases came in and we’ve started shipping them Monday. Orders are flying out, and customers should start getting email notifications with tracking.

Kodi cases are shipping to us this Friday, and will go out as soon as they arrive. Because both cases are so different, their manufacturing processes are also distinctly different. One had to be done before the other.

Orders were supposed to start shipping out about a week ago. However, as soon as I got the first units back, I did a lot of thermal testing.

This new pi runs hot. I started testing with various benchmark scripts, python, etc. But results were generally inconsistent across tests. Much depended on the initial starting conditions. Should the pi have started cooler, I’d see much different results than if I had it running idle. If I just finished a test, results were different as well.

I tried other tests and settled on cpuburn-arm.

Results were consistent. I felt like I saw the most consistent and highest power draw. Which means we could theoretically get temp as quickly as possible.

Without any case, in 26-27C ambient, I got a naked raspberry pi to nearly 90C in 5-10 minutes. Okay great. Now with the Flirc case, I get it to 80C in 25 minutes. I saw the temp hang around 80C +/- 2C for 30 minutes. Seems like we hit steady state, but I think we can do better.

So we started studying the design, the gap, and the thermal material, and simulated. I ordered some new thermal pads and did some more tests that looked great. I got some arctic cool pads off amazon with a much higher thermal conductivity, and started testing.

In my lab/warehouse 26-27C which is really hot, it took 90 minutes of cpu burn before it got to 80C. Ambient matters. I ran another test on Monday, where it was 24-25C, and in 3 hours, it never went above 77C.

But let’s talk about something important. cpuburn is meant to burn as much power as possible, it’s not realistic of any situation. Yes, cpu utilization could get up to 100%, but that doesn’t mean the processor is going to burn the same power. Cpuburn is meant to try and draw the most power. Depending on the software that’s running, power will not only be different, but it will be dynamic. Even running cpuburn, on stopping, I saw a 1C drop every second. So in actuality, a real load alleviates the stress on the cpu, allowing it breathing time to cool.

I’m confident in the case and the new pad. Confident in saying that any strenuous situation will be fine without the need for active cooling or worrying about overheating.

I got in touch with arctic directly, and were shipping with their pads.

It is with great excitement that alongside the Raspberry Pi 4’s release today, we are announcing two brand new Raspberry Pi cases to accommodate all the changes of this amazing new hardware.

We’ve been hard at work and have started high volume manufacturing of a brand new case. We kept all the details that made the original case one of the top selling raspberry pi cases, and along side our own case, we’re releasing a newly designed and limited edition Kodi case, for the same exact price.

We expect to ship both in roughly 3-4 weeks. Pre-order now for special pricing and save 30%.

Grab em’ here: Kodi Raspberry Pi 4 Case and Raspberry Pi4 Case

Today, I’m saying goodbye packagecloud. They had an amazing unique service that solved a huge headache. I spent a lot of time trying to host my own repositories, and it was too much of a headache to constantly keep up. Packagecloud was an amazing, affordable service that solved this problem with elegance. But they decided to tripple their price which made the service no longer worth it.

So today, I’ve changed my build system, installation instructions, and scripts to use gemfury. A great alternative and free for public packages.

You can head over to the linux downloads section, and re-run the installer script to add the new repository. Sorry for the inconvenience. More announcements next week, stay tuned.

Come visit our booth at the Bay Area Maker Faire. Were previewing some unreleased products and we love chatting.

Long Presses and Macros Released

By far the coolest update for flirc, was today. Everyone’s flircs just got a lot cooler. Today, I’m happy to announce the addition of long presses and macros. Two features that I’ve been planning on for quite some time, and they are definitely worth the wait.

Macros

Macros allow you to assign more than one function to a single remote control button. Basically, I can have a string of text or a bunch of commands, etc, all execute when I press a single button on my remote. That’s now possible with todays firmware. There is currently no limit on the amount of buttons, but you might see some issues with anything more than 16. We can always change that, the limit is artificial right now.

Long Presses

Some of my favorite remotes don’t have a lot of buttons. Specifically, the apple remote. This update will allow you to assign a second function on any remote control button if you hold it down for more than half a second. Tapping on the button as normal will do the first function, holding it for half a second will not send out the first function, but send out the second.

Long Presses + Macros

You can also combine the two features. Press a button and have a single action, press and hold that same button, and do a macro. Check out the short demo video

Worthy Notes

1. There is currently no GUI support for these two features. This is going to be quite tricky to do, so although the software and API’s are all well thought out, I’ll need a bit of time before these can be standard in the GUI. For now, you’ll need the command line utility, and documentation on how to do these features can be found in the current manual.
2. To do a long press, you have to hold down the button for half a second, this is currently hard coded, might change this in the future
3. Macros keys are all sent out as soon as possible, may update this so users can change these timings
4. Deleting a key that has macros or long press functionality will delete every single key associated with that remote control button.

Other Updates

Plugin Support

One of the coolest silently released features was plugin support. All thanks to Yawor who did all the work. He did a fantastic job, and has posted a few items on the forums. This will be formalized into the release soon, and more documentation will be created. Basically, this allows you to create an SVG and XML file, and the graphics and functionality will be dynamically loaded into the GUI. Users will be able to share theirs to help other setup unique setups.

General GUI Improvements

Also thanks to Yawor, a lot of the important GUI items have been re-written to be a bit more dynamic and cleaned up a lot of issues. I’m in debt for his help, he’s a fantastic engineer.

Hosting Updates

I’m giving up on hosting packages. It’s a pain in the ass and took a lot of time and work. I found packagecloud and they take a lot of the work out all the security related issues. If you have the old repo in your distro, make sure you remove that and install the new ones. You can find instructions on the downloads page.

Build Updates

I’ve migrated all the build and release to travis, which although a bumpy start, was absolutely the right thing to do. It’s not a great idea to do build releases on a development machine for many reasons, but I held all the tools on my laptop. No other employee or partner could do a release without me, that’s no longer the case.

SDK Fallen Behind

Because we have everything built on Travis now, the SDK library build and release tools have fallen behind. I should have these built into travis by next week or shortly after.

Raspberry Pi Version Behind

Not quite sure how to do pi release yet on travis, so those have fallen behind. I’ll manually update these versions soon.

Happy Holidays

A very happy holidays and a happy and healthy new years to everyone. Feel free to leave comments, shoot me emails, or start forum discussions.

A ways to go, this is the bring up board. But it’s up and running, and I’ll be excited to release it. Code name Rogue1.

Any correct guesses, and you’ll get one for free.

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.