Blitzwolf IR blaster

111 views
Skip to first unread message

gad...@gmail.com

unread,
Nov 13, 2021, 3:58:25 AM11/13/21
to TasmotaUsers
Hi,
I recently flashed Tasmota (9.1) onto a BW-RC1 and configured a rule so that when I switch on my Samsung TV the blaster sent out the power on command for my external Marantz amplifier.
All was working great until I did the stupid thing of upgrading the firmware to 10.1 with an OTA update.
Now it stopped working! The codes recieved from the remote are shown as different codes and even when I setupp another rule with the new codes it still doesn't trigger the rule.

This was the rule I was using (tv power code in yellow):
{"Rule1":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":119,"Free":392,"Rules":"ON IrReceived#Data=0xE0E040BF DO IRsend {\"Protocol\":\"RC5\",\"Bits\":12,\"Data\":\"0x40C\",\"DataLSB\":\"0x2030\",\"Repeat\":0} ENDON"}}

I suspect the IRreceive data is now not recognised correctly, now get this when I power the TV on
08:38:17.382 MQT: sonoffs/irblast-001/RESULT = {"Time":"2021-11-13T08:38:17","IrReceived":{"Protocol":"UNKNOWN","Bits":34,"Hash":"0xF4BA2988"}}
08:38:17.482 MQT: sonoffs/irblast-001/RESULT = {"Time":"2021-11-13T08:38:17","IrReceived":{"Protocol":"UNKNOWN","Bits":34,"Hash":"0xF4BA2988"}}
08:38:17.632 MQT: sonoffs/irblast-001/RESULT = {"Time":"2021-11-13T08:38:17","IrReceived":{"Protocol":"UNKNOWN","Bits":34,"Hash":"0xF4BA2988"}}
08:38:17.732 MQT: sonoffs/irblast-001/RESULT = {"Time":"2021-11-13T08:38:17","IrReceived":{"Protocol":"UNKNOWN","Bits":24,"Hash":"0x9996EA65"}}

Should the "Hash" normally show as the "value"?

I then downgraded the firmware back to 9.1 but it still doesn't work, my step is to flash the IRblaster from scratch again with the FTDI and Tasmota 9.1.

Could the update to 10.1 have affected the IR code database?

Any suggestions?

Cheers

Philip Knowles

unread,
Nov 13, 2021, 4:12:05 AM11/13/21
to gad...@gmail.com, TasmotaUsers
Possibly as the release notes say the IR library was updated. Downgrading to 9.1 might not resolve that.
What might work is OTA flashing minimal then flashing lite and doing a full reset then trying 9.1 again (perhaps the specific IR blend).

I always work on the principle that if it ain't broke don't fix it. I've got devices (Sonoff TH) running happily on V6 because they don't need any new features.

Regards

Phil K

From: sonof...@googlegroups.com <sonof...@googlegroups.com> on behalf of gad...@gmail.com <gad...@gmail.com>
Sent: Saturday, November 13, 2021 8:58:25 AM
To: TasmotaUsers <sonof...@googlegroups.com>
Subject: Blitzwolf IR blaster
 
--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/79bc1426-83b9-40c1-8dff-23c32d5f72c8n%40googlegroups.com.

gad...@gmail.com

unread,
Nov 13, 2021, 12:52:37 PM11/13/21
to TasmotaUsers
Yes, I never learn, should have left it well alone!

Anyway I've opened it up and going to Tasmotize it again from scratch with 9.1 and hope that works.

Cheers

gad...@gmail.com

unread,
Nov 13, 2021, 1:38:12 PM11/13/21
to TasmotaUsers
Well I've got it running with 9.1 again and I can now see the correctly decoded Samsung IR codes instead of unknown, I can send the IR power codes for the Amp via the console and it works but I can't get the rule to work.

Does this look right?
Rule1 ON IrReceived#Data=0xE0E040BF DO IRsend {\"Protocol\":\"RC5\",\"Bits\":12,\"Data\":\"0x40C\",\"DataLSB\":\"0x2030\",\"Repeat\":0} ENDON"}

I don't get any error it just doesn't respond.

Cheers

Philip Knowles

unread,
Nov 13, 2021, 3:25:48 PM11/13/21
to gad...@gmail.com, TasmotaUsers

You haven’t got the correct number of ( ) brackets – 1 close and 0 open plus your endon is within the { }.

 

Sent from Mail for Windows

 

From: gad...@gmail.com
Sent: 13 November 2021 18:38
To: TasmotaUsers
Subject: Re: Blitzwolf IR blaster

 

Well I've got it running with 9.1 again and I can now see the correctly decoded Samsung IR codes instead of unknown, I can send the IR power codes for the Amp via the console and it works but I can't get the rule to work.

 

Does this look right?

Rule1 ON IrReceived#Data=0xE0E040BF DO IRsend {\"Protocol\":\"RC5\",\"Bits\":12,\"Data\":\"0x40C\",\"DataLSB\":\"0x2030\",\"Repeat\":0} ENDON"}

 

I don't get any error it just doesn't respond.

 

Cheers

On Saturday, 13 November 2021 at 17:52:37 UTC gad...@gmail.com wrote:

Yes, I never learn, should have left it well alone!

 

Anyway I've opened it up and going to Tasmotize it again from scratch with 9.1 and hope that works.

 

Cheers

 

On Saturday, 13 November 2021 at 09:12:05 UTC knowles...@gmail.com wrote:

Possibly as the release notes say the IR library was updated. Downgrading to 9.1 might not resolve that.

What might work is OTA flashing minimal then flashing lite and doing a full reset then trying 9.1 again (perhaps the specific IR blend).

 

I always work on the principle that if it ain't broke don't fix it. I've got devices (Sonoff TH) running happily on V6 because they don't need any new features.

 

Regards

 

Phil K

 

From: sonof...@googlegroups.com <sonof...@googlegroups.com> on behalf of gad...@gmail.com <gad...@gmail.com>
Sent: Saturday, November 13, 2021 8:58:25 AM
To: TasmotaUsers <sonof...@googlegroups.com>
Subject: Blitzwolf IR blaster

 

Hi,

I recently flashed Tasmota (9.1) onto a BW-RC1 and configured a rule so that when I switch on my Samsung TV the blaster sent out the power on command for my external Marantz amplifier.

All was working great until I did the stupid thing of upgrading the firmware to 10.1 with an OTA update.

Now it stopped working! The codes recieved from the remote are shown as different codes and even when I setupp another rule with the new codes it still doesn't trigger the rule.

 

This was the rule I was using (tv power code in yellow):

{"Rule1":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":119,"Free":392,"Rules":"ON IrReceived#Data=0xE0E040BF DO IRsend {\"Protocol\":\"RC5\",\"Bits\":12,\"Data\":\"0x40C\",\"DataLSB\":\"0x2030\",\"Repeat\":0} ENDON"}}

 

I suspect the IRreceive data is now not recognised correctly, now get this when I power the TV on

08:38:17.382 MQT: sonoffs/irblast-001/RESULT = {"Time":"2021-11-13T08:38:17","IrReceived":{"Protocol":"UNKNOWN","Bits":34,"Hash":"0xF4BA2988"}}

08:38:17.482 MQT: sonoffs/irblast-001/RESULT = {"Time":"2021-11-13T08:38:17","IrReceived":{"Protocol":"UNKNOWN","Bits":34,"Hash":"0xF4BA2988"}}

08:38:17.632 MQT: sonoffs/irblast-001/RESULT = {"Time":"2021-11-13T08:38:17","IrReceived":{"Protocol":"UNKNOWN","Bits":34,"Hash":"0xF4BA2988"}}

08:38:17.732 MQT: sonoffs/irblast-001/RESULT = {"Time":"2021-11-13T08:38:17","IrReceived":{"Protocol":"UNKNOWN","Bits":24,"Hash":"0x9996EA65"}}

 

Should the "Hash" normally show as the "value"?

 

I then downgraded the firmware back to 9.1 but it still doesn't work, my step is to flash the IRblaster from scratch again with the FTDI and Tasmota 9.1.

 

Could the update to 10.1 have affected the IR code database?

 

Any suggestions?

 

Cheers

--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers..@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.

Phil Grant

unread,
Nov 13, 2021, 3:52:20 PM11/13/21
to Philip Knowles, TasmotaUsers
Haha,  the perils of copy and paste and then reading what you thought you should have written instead of what you actually wrote 😩

Thanks
63EFE763F2E1475FB75E1FFE9979F741.png

gad...@gmail.com

unread,
Nov 13, 2021, 5:09:37 PM11/13/21
to TasmotaUsers
Still won't work, I think I have the rule syntax sorted now, I also had escaped the "s with \s which I've removed, I now have this

Rule1 ON IrReceived#Data=0xE0E040BF DO IRsend {"Protocol":"RC5","Bits":12,"Data":"0x40C","DataLSB":"0x2030","Repeat":0} ENDON

But still no joy !! 

I'm at a loss as to see what's wrong.

Philip Knowles

unread,
Nov 13, 2021, 5:31:24 PM11/13/21
to gad...@gmail.com, TasmotaUsers

First thing to do is check that rule1 is switched on (I know but it’s amazing the number of times when it’s not)

Then create a rule with the trigger just turning on power1 so you know the trigger is working

Then do the IRSend as a command to check that works.

 

If they all work can put it together

gad...@gmail.com

unread,
Nov 14, 2021, 4:01:32 AM11/14/21
to TasmotaUsers
OMG!!!! I looked at the result from rule? and saw "Sate":"off"  and suspected this might mean it was off but when I looked in the help documents I couldn't see that it meant this but with hindsight it was flipping obvious.

This is the first time I've used a rule and didn't know you could switch them off or that they may be off by default, it's on and working now thanks for your help and I now know a bit more about the rules.

Thanks again for taking the time to help.

Phil

Philip Knowles

unread,
Nov 14, 2021, 4:31:44 AM11/14/21
to gad...@gmail.com, TasmotaUsers
Default is off. Sometimes you need to look at the Commands pages too.
Tasmota has grown organically and sometimes stuff that's 'bleeding obvious' isn't.
I submitted an edit to the Power Measurement section yesterday because it says EnergyReset has been replaced but not what it's replaced by...
Sent: Sunday, November 14, 2021 9:01:32 AM
To: TasmotaUsers <sonof...@googlegroups.com>
Subject: Re: Blitzwolf IR blaster
 

gad...@gmail.com

unread,
Nov 14, 2021, 10:58:29 AM11/14/21
to TasmotaUsers
Strange that the first time i set up a rule it was enabled because I never enabled it as I didn't realise I had to!

The other thing it confirms is that the change to the IR library in version 10 breaks something as it no longer correctly recognises Samsung codes as version 9.5 does.

Philip Knowles

unread,
Nov 14, 2021, 5:27:21 PM11/14/21
to gad...@gmail.com, TasmotaUsers

If you followed an example they often have rule1 1 in the example so people don’t notice they’ve done it.

 

Sent from Mail for Windows

 

From: gad...@gmail.com
Sent: 14 November 2021 15:58
To: TasmotaUsers
Subject: Re: Blitzwolf IR blaster

 

Strange that the first time i set up a rule it was enabled because I never enabled it as I didn't realise I had to!

 

The other thing it confirms is that the change to the IR library in version 10 breaks something as it no longer correctly recognises Samsung codes as version 9.5 does.

On Sunday, 14 November 2021 at 09:31:44 UTC knowles...@gmail.com wrote:

Default is off. Sometimes you need to look at the Commands pages too.

Tasmota has grown organically and sometimes stuff that's 'bleeding obvious' isn't.

I submitted an edit to the Power Measurement section yesterday because it says EnergyReset has been replaced but not what it's replaced by...

Reply all
Reply to author
Forward
0 new messages