Hi team, I flashed OpenBK7231N on AI Smart Remote Control (model:IH-F8260), received from Aliexpress and it's working with Home Assistant very well with the configuration below:
good evening everyone, I ask if you can help me convert this raw data {"IrReceived":{"Protocol":"PulseDistance","Bits":24,"Data":"0xAB054F"}} into an IRSend command to be sent via MQTT.
hello everyone, is there really no one who can help me?
Hello. Thank you for your firmware. I want to use it with my suzuki air conditioner. This is not a popular model of air conditioners, but the TCL air conditioner remote control fits it. When I try to accept commands from the remote, I get this result:
Info:MQTT:Publishing val IR_NEC 0x4 0x2 0 to obkFFAEEEED/ir/get retain=0
Info:IR:IR MQTT publish IR_NEC 0x4 0x2 0 took 5ms
Info:MQTT:Publishing val {"IrReceived":{"Protocol":"NEC","Bits":32,"Data":"0xFD02FB04"}} to obkFFAEEEED/RESULT retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obkFFAEEEED/ir/get
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic cmnd/obkFFAEEEED/irsend {"Protocol":"NEC","Bits":32,"Data":"0xFD02FB04","Repeat":2}
Error:IR:IRSend cmnd not valid [] not like [NEC-0-1A] or [NEC 0 1A 1].
Hello, dear community of Elektroda.pl. I bought an IR Blaster from AuBees - unfortunately, the manufacturer did not create models for it, but it did not do it itself, so it is highly probable that someone else did it and provided an appropriate model.
As you can see, the device is based on a CBU based on Becken 7231N and I managed to flash it with OpenBecken. The device responds normally on the network. Now I have a few questions (edit - I found the answers - I'm posting them for posterity - maybe someone else will need them):
1. How can I make sure that the 3 pins are correctly assigned - at this point I signed a bit, suggesting in the first post I assigned - pin 7 (PWM1) as IRSend, pin 8 (PWM2) as IRRecv and pin 24 (PWM4) as WiFi Led.
In the OpenBecken web application it is possible to select a device - if it is on the list (and it is), the pins are provided. If not, I suspect that you need a voltmeter and a script that will send something (and a remote control that will catalyze the receiver to find the receive pin)
2. I would like to integrate this device with HomeAssistant - what is the best way to do it? MQTT ? Script control? something else?
In my case, the best solution was a script that first turns on the projector (a separate microcontroller connected to the projector's COM port - unfortunately, the remote control does not have a direct selection of the input channel, and I use all 3 - you never know which channel was used previously). Later, in order to turn on the receiver, URL queries are sent to the blaster (reading the code from the remote control can be done by observing the application log in the blaster). Helpful sites include: to understand the ideas of action: https://www.circuitsnoop.com/2022/02/wifi-ir-blaster-hack-part2/ to help create the URL: https://www.urlencoder.org/
the last two lines are optional - the first one will be useful to complicate the script with a few commands, the last one waits until the whole thing is finished. It may look a bit clumsy at first, but it works first class :D
3. How can I record the remote control commands I would like to use? (if it helps, I need to control mainly the Yamaha HTR-2067 receiver, but I wouldn't mind controlling other things)
As I mentioned in the previous point - shoot the blaster with the remote control and watch the logs. It is a good idea to turn off unnecessary "ticks" in the log window because there is a lot going on there and you can lose the information you are interested in in the thicket of other information that you do not need at the moment.
Hi all. I have this IR module (without the box) and trying to make it work. I applied config for Tuya Generic Smart Wi-Fi IR Remote Control from Temu IRC02 and it works for sending IR commands, which I can verify with flipper zero, but it doesn't receive anything. I tried to set each pin to IRRecv and rebooting the module but so far no luck. What should I try to do?
nvm I figured it out manually) I was sending irsend NEC-EF00-2 from the module to the flipper and when I sent it back to the module it was not showing up in the logs. I enabled flag 15 to allow unknown protocols and then it showed up as Info:IR:IR IR_UNKNOWN 0x8CBEE187 0
ie. as you have the same JSON as mine (just with a bunch of additional fields).
(although we do differ on values for owm (0 vs 1) and crc (1 vs 42) ... whatever they are?!?)
Nb. I could tell I had mine setup correctly because:
* reset shows up in the logs as `Info:GEN:6 key_short_press` when I press the button
* wfst LED flashes when connecting to wifi and stays on when connected
* infrr shows up in the logs when I point a remote at the device and I have `Flag 15 - [IR] Allow 'unknown' protocol` enabled
* infre shows up when sending an example command `IRSend Onkyo 0x7A 0x354A 1` and looking at the device with an android phone to see the actual Infrared flashes of light
I then went spelunking around the code looking for why the script generation wasn't working.
However I don't see any sign of these fields in the templateParser.js.
Perhaps someone has a PR in the works to add mappings for these extra fields?
I ended up giving up on esphome and put OpenBKon this, but I have the S08 Pro which has the temp/humidity sensors in it. How would I go about configuring them in OpenBK? They are DP ID's 101 for temp and 102 for humidity.
In esphome I had to set the uart config as follows.
Hello @brianroy86 , can you provide more information on your device? Is this a TuyaMCU device? Maybe a photo of the inside? That looks like 9600, if so, you need to write autoexec.bat.
// start TuyaMCU driver
startDriver TuyaMCU
// set TuyaMCU default wifi state 0x04, which means "paired",
// because some TuyaMCU MCUs will not report all data
// unless they think they are connected to cloud
tuyaMcu_defWiFiState 4
// channel 1 will be temperature
setChannelType 1 temperature
// Map given dpID to channel 1, dpID type value
linkTuyaMCUOutputToChannel 101 val 1
I am not sure if it will work, so please check this and give feedback here, I will try to guide you step by step through the configuration. Still, I'm suprised, I wasn't aware that there is an IR remote that has TuyaMCU as well... or maybe it works in a different way?
Ok, so please check my autoexec.bat , save it to the device, reboot it, and open web app log to check if there are any TuyaMCU messages received. We'll know if it's TuyaMCU soon enough.
Added after 44 [seconds]:
EDIT: That github makes it clear it's TuyaMCU:
They suggest MCU removal, but that's not needed with OBK
Your script seems to have worked. I went and added the humidity as well. The only issue, is the temperature is not formatted correctly. It is showing as 205 degrees Celsius, I think I need to move the decimal and convert to Fahrenheit. Any idea how I would do that?
Thank you for your help so far, I got those 2 sensors working just fine, and Home Assistant translates it from C to F automatically so I don't see a need to send it in F at this time.
The last thing I need some help with is sorting out the IR codes. If I press a button on my remote I see the following in the logs.
Info:IR:IR IR_NEC 0x4 0x2 0
I've created a sensor in HA that looks like the following:
switch:
- unique_id: "OpenBKTestIR"
name: "OpenBKTestIR_Power"
command_topic: "cmnd/OpenBK/TestIR/IRSend"
qos: 1
payload_on: NEC-4-2-0
payload_off: NEC-4-2-1
retain: false
And if I press that switch I get the following in my OBK logs.
>>20397694 I tried changing the ir_Sony.hpp file
sendPulseDistanceWidth(&SonyProtocolConstants, tData, numberOfBits, aNumberOfRepeats);
to
sendPulseDistanceWidth(&SonyProtocolConstants, tData, 12, aNumberOfRepeats);
and it works! Probably the numberOfBits parameter is not initialized
>>20843045 Version? I use OpenBK7231T_App from git and Tuya mini universal IR Remote ( Chipset: BK7231N CBU Model: Unknown ) I think the problem is that commands like sony-10-13-1 do not contain information about the number of bits and the corresponding field remains null, but is used afterwards
what i do wrong?
"IRsend IR_NEC 0xF04 0xAD 1" is not blinking ir leds.
but "IRSend Onkyo 0x7A 0x354A 1" is blinking ir leds.
i am using "execute custom command" from config menu.
device is s18
firmware flashed : 1.17.308
figured : "IRsend NEC 0xF04 0xAD" is working.
next:
how to run DAIKIN AC commands?
Info:IR:IR IR_UNKNOWN 0xB3E2CB06 0
Info:IR:IR IR_UNKNOWN 0x0 0
Info:IR:IR IR_UNKNOWN 0x0 0
The board has individual +V, GND, Rx and Tx fields. To my unprofessional eye, Rx and Tx are connected to the USB port. Reading the batch did not pose any problem. The recording failed with the YP-05 converter, probably due to the lack of a decent 3.3V voltage. The ESP-01 programmer saved everything on the first try.
The problem noticed is that the device does not correctly decode air conditioning remote controls: I have Daikin and Kaisai and it's a problem.
I just upgraded to https://github.com/openshwprojects/OpenBK7231T_App/releases/tag/1.17.335 and the issue still persists. The logs show the command ran OK, but the led's do not light up. Also I've noticed that my wifi led doesn't work. I never see it light up when it boots or if its connected or disconnected from wifi.
>>20397694 I tried changing the ir_Sony.hpp file
sendPulseDistanceWidth(&SonyProtocolConstants, tData, numberOfBits, aNumberOfRepeats);
to
sendPulseDistanceWidth(&SonyProtocolConstants, tData, 12, aNumberOfRepeats);
and it works! Probably the numberOfBits parameter is not initialized
The following fix is still pending, I will look into it soon. If anyone wants to investigate more in depth, please do, and let me know.
The discussion revolves around the BK7231N Universal IR Remote Control, focusing on its disassembly, pin configuration, and firmware updates. Users share experiences with flashing the device, configuring IR send/receive functionalities, and troubleshooting issues related to IR protocols, particularly for various remote controls including air conditioners. Key points include successful firmware updates that enabled IR functionality, the importance of correct pin assignments for IRSend and IRRecv, and the challenges faced with specific protocols like Sony and Daikin. Users also discuss MQTT integration for sending IR commands and the need for additional IR protocols to support more devices. Summary generated by the language model.
![[ZIGBEE] 20A Zigbee socket with energy metering (Tuya TS011F_plug_3)](https://obrazki.elektroda.pl/1000454900_1749493372_thumb.jpg)
