Jump to content
Flirc Forums

redec

Members
  • Content count

    23
  • Joined

  • Last visited

Community Reputation

0 Neutral

About redec

  • Rank
    Advanced Flirc-er
  1. No thanks, it's not the repeater it's the TV....apparently it's not an uncommon problem for LCD TVs to spit a bunch of IR interference when they're first turned on....just googling for it spits a ton of hits of people having the exact same problem as me with specific components that don't handle IR noise well. In fact it seems I might be lucky in that mine stops after a minute or so, many people say theirs lasts for 30 or 45 minutes after turning their TV on. I'd expect any repeater will likely have the same behavior. I'm playing with mechanisms to dull the noise from the TV (lenses, masking tape, etc) so that the flirc can cope, but I dunno it's not looking super promising. I'm starting to think my only realistic options are to get a different TV or replace the flirc, and the latter is much cheaper than the former....which sucks cuz I really do like the flirc, it's an awesome little gadget. Do you think there's any chance in the future that the flirc could be made to handle IR noise a little better? Is that a firmware thing or a hardware thing?
  2. Hmmm well....upon further testing the noise actually does not stop after it "warms up" - the flirc just seems to get better at handling it...and even more confusing I've determined that the noise itself is coming from the TV, not the windows...so when it's sitting idle it's not even seeing noise (the tv is off) so I have no idea why it would get worse the longer it sits. My repeater does not appear to have any adjustable sensitivity, however putting masking tape over the receiver does seem to help a lot - kills the noise and real commands still get through
  3. Thanks for the debug log info, that is hugely useful. As best I can figure out, I think my repeater must have some sort of dynamic sensitivity where it'll adjust its sensitivity based on the strength of the incoming light it detects. Unfortunately this seems to mean that it just sends more and more noise the longer it sits idle - it looks like it's picking up trace amounts of IR light from the windows and amplifying that and blasting it to the devices. It doesn't matter where I put the transmitter in relation to the flirc as it seems the noise is being amplified just as any proper signal would be, so if the flirc can see a proper signal, then it is also receiving the noise...and the flirc simply does not appear to be as good at handling the noise as all the other devices. Once I start sending actual IR commands my repeater takes a little bit to tune its 'dynamic sensitivity' back down to a sane level, which stops the noise and then the flirc starts to respond properly. This is my current theory...I'm not sure where this leaves me, assuming it's correct I guess I have a few options: See if my repeater's sensitivity can be manually adjusted/controlled in some way Run the flirc on a big long USB extension and mount it beside my repeater's receiver Replace the repeater Replace the flirc Hope/pray for a firmware update that handles noise a little better :) Not super crazy about any of them. I wonder if putting something like this (https://www.amazon.com/LightDims-Original-Strength-Electronics-Appliances/dp/B009WSJNCW) over the repeater's receiver would eliminate enough of the noise that the flirc could cope, without actually hindering my ability to control the system...might be worth a try
  4. ok, I'll play with that a bit more and see if I can find a setup that works better. Would anything be showing up in the debug log for the leaked light? I don't see anything when I'm not pressing buttons....I guess is there any way I can "check" if the flirc is seeing this leaked light? (is there anything specific in the debug output that indicates that?). Having a 3-4 hour testing cycle is a little painful :) At any rate, thanks so much for your help on this, your feedback and advice (and ability to release new software versions so responsively) has been quite awesome and unexpected :). Thanks!
  5. Well, with the transmitter about a foot away from the flirc it's maybe a *little* better....maybe? I only waited ~3 hours so even with it taped right on the receiver it wouldn't get too bad in just 3 hours. This time it responded in maybe 3 or 4 seconds, but then continued to miss key presses for the next 20 secs or so.....attached the log... irdebug3.log
  6. Yeah I'll try it...will have to wait a few hours to see if it helps tho
  7. Hmm nope, just taking the emitter off it doesn't work at all...it's not seeing any light
  8. Is the "too many edges" thing a normal(ish) thing to see? Curious that I see that even without the repeater.... I wonder if the emitter is over-powering the receiver....just reading a bit about IR repeaters apparently that is a thing that can happen when the receiver is quite sensitive...
  9. Ok, I wrapped it up *really* good (https://www.dropbox.com/s/5d0wnfw56jvomfj/File 2017-08-24%2C 5 51 24 PM.jpeg?dl=0) and it has made no difference. Maybe the signal is bouncing around *inside* the tape/flirc casing? I dunno I'm so confused. It's really weird that it sorts itself out after a minute or so and then it works great. I wonder if I had a cron job that just periodically did a send_ir_raw if that would prevent it from getting into that state...it seems like the longer it sits idle the worse it gets...
  10. it is one of these: https://www.amazon.ca/IR-Repeater-System-Hidden-Control/dp/B0016PM63W it's not really in a cabinet, it's just in/under an open shelving unit...When I initially did the setup I was having reflection issues with all the devices so I actually tape the emitters directly to the IR receivers and cover up the rest of the IR receiver with electrical tape so I don't get external reflections, and that has worked great. Maybe the flirc is really sensitive and is picking up signals through the tape?...maybe I just need to add a couple more layers. I can try that tonight....altho if that was the problem I would expect it to always have that problem, not just for the first minute...
  11. ooooh, a little embarrassing I don't know how I didn't think of this before, but I am using an IR repeater. I've been using it for years for literally all my devices and I've never had a problem....however I just tried the flirc without it and it seems to work fine without it. (although the "too many edges" thing is still there, see attached). Sorry I don't know how it didn't occur to me to check the IR repeater, your USB extension comment just made me think of it. Would it be possible to make it work through the repeater though? My entire setup runs through this repeater, and over the years I've used this same repeater for many many devices (like probably 30-40) and it's always worked flawlessly...kinda weird the the flirc is the only device that doesn't seem to like it. I mean the flirc works perfectly with it too, other than the first minute or so where it seems to be recovering from some sort of backlog or lag or something. irdebug_norepeater.log
  12. attached irdebug log. This is a single button press - I held the 'up' arrow until kodi responded (took ~10 secs) irdebug.log
  13. awesome, thanks! Heheh, it overflowed my scrollback buffer pretty quick....I'll reset and try again and have you a log in a few hours
  14. Does anyone know is there any way to run the ir debugger in openelec? Also, is anyone here running the 1st or 2nd gen flirc on openelec on a pi? If the 1st gen works better I may just return this one and get a 1st gen instead....wife+kids are quite impatient
×