jason

I'm sorry for the delay guys. Something will come before the end of the year. I'm going to get back to firmware very shortly. I had a ton of stuff I had to finish outside of this. I'll post a blog update soon. Long story short, I scoured the internet, and found this project: https://blog.gimx.fr I reached out to him and asked him to possibly port some of his firmware to libopencm3, where I use just the USB stack. He was extremely nice, ported that over, and now I've got to work on integrating that into the rest of my firmware. I need some more time before I can get to this specifically, but it'll be completed before christmas.

Yeah, definitely possible. We just need to figure out what the key mappings are.

hint: http://blog.flirc.tv/index.php/2017/09/06/new-product-up-and-running/ Everything is working, but packaging/tooling/etc, will be a 2018 release unfortunately. Moving as fast as I can.

It wont work with the firetv stick through hdmi. I'm working on a product to address this.

Sorry, you're feeding me bits of information. Could have been the device upgrade too. Do you remember when this happened? When did you get it, when did you do the upgrade? If you put flirc into a computer, open up wordpad, textpad, then press the activity button on your remote, are any keys sent to the pc? Can you describe the activity a bit? Did you use my software to pair your flirc with your logitech remote? If you did, you don't need to, since the keys are built in. If you go to file->advanced, you'll see there are a bunch of built in profiles. It's possible that something in your activity is in the built in rom table, or a recorded key. Flirc wont wake up the machine if a signal is received that's not recorded.

before what upgrade?

Can you elaborate, what's the issue you are having?

There are two issues. One is a new feature on amazon's firetv. They added a feature for long press to get up another menu. I've tried to get in touch with Amazon for over a year, their team disbanded, and I'm trying to make a new contact. I got in touch with someone from another department last week, and they are trying to put me in touch with someone. I don't have a timeline for that because I don't know what the issue is. I need Amazon's assistance. The second issue is a new firmware feature long presses. Which will allow you to assign another button to an existing signal. Press the button quickly, get one command, long press it, get another. That's a firmware feature that will come on the new hardware and a release will most likely be ready before the end of the year. I've done a lot this year, and I've had regular blog updates that talk about my accomplishments. I even have a new status board page to create transparency: https://flirc.tv/status_board If I miss something, take @hamptonhills approach, be nice about it. But I work 7 days a week, and can't afford to hire someone. I do the best I can, being an asshole about it doesn't help anyone.

Yeah, shield runs android tv, so sleep will work on it. Should also wake it up. I'm not sure how you would do voice with bravia, does the remote have a microphone? It would need to relay that info back to your shield, not sure it can. Or did I miss something?

I've made like 30 releases this year, who said it wasn't coming? I'm one guy, it's coming.

Controller-> media keys volume up and down are there

Thanks so much! want to post your config? I'll take a look

sudo

There is a static version available: https://flirc.tv/ubuntu-software-installation-guide I list the dependencies, it should work on every version on linux.

I've pushed a firmware update, which adds support for the wake key in gen2. So any key will wake the machine, unless you record the dedicated wake key, in which case, only the wake key will wake the machine. Still always enabled. I will implement a way to disable waking the machine up from sleep sometime in the near future. Let me know if that is of any help now. If you are still having issues, let me know. I'll figure it out.

flirc has a bunch of noise rejection. But the fact that it's inhibiting flirc from working means that it's non stop actively spitting it out. Nothing I can do about that as it's inserting itself in the middle of real remote signals. Try putting your sensor behind the TV.

I have an extra repeater I bought, was going to sell it. You want it? Maybe it'll give you better results. Brand new.

The firetv remote is actually a wireless remote, not infrared. = (

Windows is really funky like that. Sounds like it installed the driver correctly for one port, but the other ports got messed up. You can try uninstalling the drivers in device manager, and let windows set that up again for you. Let me know if that helps.

Here is how the log works: 0,12,123,2532 These are pulses, starting at t=0us we have a high pulse for 12us. Then it goes low for 123us, then high again for 2532us The markers ::e:23 Means an elapsed time of 23ms has passed since the last edge Your log is being flooded with noise, it's not showing the timing of the edges because it's less than 4 pulses, which isn't a valid IR signal. So it's essentially showing you a bunch of time in ms between the noise. It's seeing hundreds of those.

I'd say keep moving. Honestly, if you put it in some obscure location in the cabinet, it should be fine. But it's clear that the transmitter is 'leaky'. It's leaving the IR light on when it's not supposed to at a low strength.

can you put the transmitter somewhere else in the cabinet?

Is it taped to the front? It definitely is, and it's probably a leaky repeater too, it's seeing light when it's not supposed to. Try removing the one in front of flirc, and let it pick up the transmission from one of it's taped neighbors

It's really sensitive. IN fact, unless you've blocked off all of the black plastic on flirc, it's getting in. IR can go through any angle of that black plastic due to where the IR sensor is positioned.

Is it in a cabinet? Can you move it outside of where the repeater is for the time being? Maybe the repeater is too strong and you have a bunch of reflection in the cabinet causing flirc to see a bunch of edges. Can you tell me a bit about your setup? What kind of repeater is it?