IRRemote Reciever returning 0 as decoded data

I'm testing out my IR Receiver by using my Air Conditioner Remote. When I press a button such as Power, it just shows the decoded IR data as '0'. Any ideas?

Code:

#include <IRremote.hpp>

void setup(){
  Serial.begin(9600);
  IrReceiver.begin(7, false);
}

void loop(){
  if (IrReceiver.decode()){
    Serial.println(IrReceiver.decodedIRData.decodedRawData, HEX);
    IrReceiver.resume();
  }
}

Does your remote work with any of the IRremote library examples?

Post a schematic of your wiring.

Post photos of your setup showing the wiring.

This seems odd.

That's is the new filename. Got me , too.

IRremote.hpp GitHub.

Here is my wiring, sorry for the bad quality. Also, when I fiddle with wires/the board it often makes the receiver go wild, giving random values very fast.

Thanks for the help.

However, it seems to partially work for my TV Remote, printing '19E60707' a few times when I press the power button on my Samsung TV Remote.

The IR receivers are sensitive to noisy power. A 0 return is a noise trigger, i just have a > 0 gate before i run my button SWITCH statement block.
Its dead easy to use, Vcc, gnd, and signal, but they want solid power. Its not just an IR LED, there's a demodulator in there as well. Try also a piece of red plastic to block out stray light on the sensor.

Sorry for the late reply, I have been busy recently.

Update:
I am receiving codes for both my fan remote and TV remote seemingly well. Can't test them yet since I don't have an IR LED/transmitter available.

The only problem I am now coming across is just the A/C remote returning 0 when it is pressed. It is not a noise trigger because it does print a new received infrared that is 0x0:

My Samsung TV seems to be returning correctly:

Thanks for the help so far.

Just ignore the 0's. They mean "bad read"

WDYM ignore 0s.
Everytime I press the POWER toggle button on my A/C remote, Serial prints 0. So it is detecting that I'm pressing something but for some reason it doesn't recognize its data. That's what I'm trying to solve.

Not all remotes use the same encoding. "Unknown protocol" is just that UNKNOWN.

but the data is 0 aswell... so i can't get it's raw data to send later

The IR module isn't just an IR diode, there's a decoder built in. If the decoder doesn't "decode", there's nothing to return. If it did send something every flash of light would send something. Better to stand silent than to shout continuously wrong things.

then why does it print anything

cause the code only runs if it has decoded something

to let you know it received SOMETHING and that the decoder isn't dead unresponsive to a direct, strong signal. Imagine your frustration of watching the rx led flicker and nothing ever happens. this way you can tell "broken" for "I don't understand"

ok, so is there no solution because its an obscure protocol/signal

yep. no law manufacturers must follow "standard" protocols. Some manufacturers do it intentionally so you have to buy from them. Ever tried to plug a pc device into an Apple?

There is a chance that the remote's modulation frequency is not the same as the receiver's. If your receiver is 38KHz the remote has to be near the same.

ok, how could i figure that out