Repository navigation
My old Pioneer VSX-S300 used to work well with HAIR on august, now it doesn't accept any IR signal from it #151
Description
First, thanks for your work ! It's complete very well the HA ecosystem.
I'm using a IoTorero RF433 IR Remote along with HAIR. It works well on my Samsung TV.
In august, I decided to capture the IR signals from my old pioneer VSX-S300 (The Remote control is a Pioneer AXD7631) using a Flipper Zero.
For make it works, I had to play with repeat and use RAW/BY PASS protocol as it wasn't working with NEC Protocol (which should be the one used by this RC). After these tweaks everything was working fine.
I didn't use it since the 09th of August (last capture). Today I'm trying to execute differents signals from HAIR but none of them works for my Pioneer VSX. although I've no issue with my TV.
I didn't change anything regarding HAIR, my IoTorero RF433 IR Remote except Home Assistant and HAIR updates.
I also tried to get these signals from public databases, they were exactly the same as the one I got but it doesn't work anyway.
When I use my RC, HAIR detect correctly the signals it already has but he is unable to send it correctly to my device.
My guess is it has something to do with NEC/BY PASS protocol. Even If a configure the signal as "BY PASS", it indicates "Recognized as NEC".
Thanks for your help.
Activity
DAB-LABS commentedon Sep 6, 2026
Thanks for the detailed report, and sorry the Pioneer went quiet. 😔
The good news first: I checked, and the send path for bypassed codes has not changed since August. If the stored code is the same, HAIR is sending the same thing. So something else moved, and your setup gives us a great clue: the TV still works through the same blaster. TV codes go out in decoded form, your Pioneer codes go out raw. If raw sends broke while decoded sends still work, the suspect is how the blaster integration plays raw after the HA update, which sits below HAIR.
Three things would pin it down:
Open the Mirror right after a failed Pioneer send and tell me what that row shows: which emitter it went through, and whether the Heard column shows your receiver hearing it back. If HAIR sent it and your own receiver heard it correctly, the code left HAIR intact.
Does the Pioneer device show anything under Needs attention, and did you accept any offered fixes there after upgrading? A fix replaces stored bytes, and I want to rule that out.
Your HAIR version on August 9 if you know it, your version now, your HA version, and how the IoTorero connects (Tuya, LocalTuya, something else). And paste one of the Pioneer codes here.
We will get it going again. 💪🏻 💈
~ DAB
avbfr commentedon Sep 7, 2026
Hello,
Thanks for your help 🙏,
I actually made a few tests: I downgraded HAIR and tested different versions.
The rest stays the same : Home Assistant Core : 2026.9.1
Here are my results:
It looks like something changed between 0.9.7 and 0.9.8.
A signal exemple if it helps:
0000 006D 0022 0000 0143 00A2 0014 003D 0014 0016 0013 003D 0015 0014 0014 0015 0014 003E 0013 0015 0014 003E 0013 0015 0014 003D 0014 0016 0013 003D 0014 003D 0014 0015 0014 003E 0013 0015 0014 0015 0014 0015 0014 003D 0014 003E 0013 003E 0013 0016 0013 0015 0014 0015 0014 003E 0013 003E 0013 0015 0014 0016 0013 0016 0013 003E 0013 003E 0013 003E 0013 076D
My IoTorero firmware is build using ESPHome 2026.8.2.
Thanks :-)
DAB-LABS commentedon Sep 9, 2026
Thanks for the bisection! 💪🏻
I put 0.9.7 and 0.14.2 side by side on the bench with a receiver watching the air. In 0.9.8 we started stripping the silence at the end of each code, and with repeated sends, that silence turns into a pause which was read by your Pioneer as a sent code. 8 sends could read like one or two by the Pioneer. It has to do with the spacing between the signal sends and I want to give you control over it.
We are adding a setting so you can set the spacing it exactly. To help, could you export the Pioneer device as a wig from the device page and attach it here? That gives me your original codes and the send times you tuned.
Also, did a single send (send times 1) ever work on 0.9.7?
No need to downgrade again, the export works on your current version.
~ DAB
avbfr commentedon Sep 9, 2026
Hello !
Thanks for your help.
Yes to make it works, the signal is repeated multiple times. So in 0.9.7 it won't work if the send times is 1.
Here is my wig :
amplificateur-pioneer.wig.json
As you can see, I've count set between 4 and 8 for this device.
v0.15.0 (Even Cut): send spacing, echo ticket sized to the burst, cor…
DAB-LABS commentedon Sep 12, 2026
0.15.0 is out with the spacing setting. Update HAIR, open each Pioneer signal, set the spacing to 135, and save. That puts the repeats where they were on 0.9.7. Let me know how the Pioneer takes it.
~ DAB
avbfr commentedon Sep 13, 2026
Thanks for your help.
Unfortunately, even with spacing set to 135 or 175, it doesn't work.
It looks like the signal is not sent 8 times but only one (it's a feeling but when I click on the TEST button, the 'SENT!' appears way faster than before).
DAB-LABS commentedon Sep 18, 2026
@avbfr 🍻
I may have had the numbers backwards. A Pioneer remote repeats its frame every 90 ms, and your code itself is about 65 ms long, so the real gap is small. Before 0.9.8 HAIR could not go below roughly 175 ms no matter what, which is why eight sends helped: the timing wandered by about 60 ms either way, so now-and-then two of the eight landed close enough for the amp. One send never did. Now that the spacing is exact, 135 and 175 are simply held there every time, and neither is 90.
Try this on the Power row: spacing 90, send times 3. Then 2. If nothing, try spacing 108, same send counts.
Please do change send times while you experiment. If 90 is the right cadence you should need far fewer sends than eight, since that is what a real press looks like.
The Test button returning quickly is expected now. Your sends used to be separate calls and are now one burst, so it returns as soon as the burst is handed over.
If none of those work, send it back to me and I will put a receiver on the air against your exact code here.
~ DAB
avbfr commentedon Sep 21, 2026
Hello @DAB-LABS,
A huge thanks for your work ! Everything does work perfectly now.
It even look more reliable.
The issue is fixed for me 👍.
Thanks again for the time spent on this.
DAB-LABS commentedon Sep 22, 2026
Thanks for sticking with it. Closing this one; 90 ms spacing is now the known answer for Pioneer. 🍻