Elektroda.com
Elektroda.com
X
  • #32
    jkwim
    Level 10  
    p.kaczmarek2 wrote:
    So, it's not a TuyaMCU but you still got "MCU version" string in the app? Hm, interesting.


    Aubess WiFi Smart IR Controller

    Added after 1 [minutes]:

    Here are the pics of the hardware (Huggwic Tuya WiFi IR Remote Control Smart Home For TV Air Condition Universal Infrared Controller Work With Alexa Google Home):

    Aubess WiFi Smart IR Controller

    Aubess WiFi Smart IR Controller

    I have physically verified the PIN connections:

    PIN PIN Setting
    7 IRSend
    8 IRRecv
    24 LED_n

    Also I have checked Pin 7 output using GPIO Finder. The output works fine

    Picture taken with a Mobile Phone Camera:
    Aubess WiFi Smart IR Controller

    So the hardware works fine. Infact I was able to fully configure a remote of a Panasonic Fan using Tuya App. So hardwarewise everything is fine.

    OpenBK is not helping me here.

    1. IR Receive shows random data for the same button of the remote when the test is repeated. Some times I do not see any IR messages in the log also.

    2. Today when I tried IRSend Command I get an error:

    Error:CMD:cmd IRSEND NEC 0xE384 0x24 0 NOT found (args )
    Info:CMD:[WebApp Cmd 'IRSEND NEC 0xE384 0x24 0' Result] Unknown command
    
    Error:CMD:cmd IRSEND NOT found (args UNKNOWN 0x43430E7F 0)
    Info:CMD:[WebApp Cmd 'IRSEND UNKNOWN 0x43430E7F 0' Result] Unknown command


    However previously I have been able to type in the second command successfully:

    Info:IR:Delay 100ms
    Info:IR:IR send UNKNOWN 0x43430E7F  protocol 0 addr 0xE7F cmd 0x0 repeats 0
    Info:CMD:[WebApp Cmd 'IRSEND UNKNOWN 0x43430E7F 0' Result] OK



    IR Driver is active.

    Wonder how I should proceed
  • #33
    p.kaczmarek2
    Moderator Smart Home
    IRSend will only be "unknown command" if you don't have IR driver running.

    It may be also "unknown" in the rare case when you have copy/pasted code with non-standard ASCII whitespace characters. In such case the command parser fails to detect spaces and parses whole string as single word. It has already happened twice, as far as I know. Try typing command manually and see if it works.
  • #34
    jkwim
    Level 10  
    OK I sorted out the Cut&Paste issue of commands. I remember that you mentioned it to me some time back also.

    So IRSend command does work. I could see the LEDs coming on.

    Now to the issue of IRReceive.

    The problematic Panasonic remote gives similar behavior in Tasmota also. I might need to try with the Tasmota_ir.bin to check it against the full list of AC Remotes etc.

    I used another remote which uses NEC protocol for comparison with Tasmota.

    Here is the Tasmota log:

    ---- first attempt ---
    20:54:56.064 MQT: tele/xxxx/RESULT = {"Time":"2023-06-30T20:54:56","IrReceived":{"Protocol":"NEC","Bits":32,"Data":"0x04FFB24D"}}
    ---- second attempt ---
    20:56:16.519 MQT: tele/xxxx/RESULT = {"Time":"2023-06-30T20:56:16","IrReceived":{"Protocol":"NEC","Bits":32,"Data":"0x04FFB24D"}}
    20:56:16.661 MQT: tele/xxxx/RESULT = {"Time":"2023-06-30T20:56:16","IrReceived":{"Protocol":"NEC","Bits":0,"Data":"0xFFFFFFFFFFFFFFFF"}}
    20:56:16.769 MQT: tele/xxxx/RESULT = {"Time":"2023-06-30T20:56:16","IrReceived":{"Protocol":"NEC","Bits":0,"Data":"0xFFFFFFFFFFFFFFFF"}}


    I get consistent values on same button

    In contrast in OpenBK log for the same button:

    ---- first time ----
    Info:MQTT:Publishing val IR_UNKNOWN 0xBBF2A583 0 to openbk7231N-xxxx/ir/get retain=0
    Info:IR:IR MQTT publish IR_UNKNOWN 0xBBF2A583 0 took 11ms
    Info:MQTT:Publishing val {"IrReceived":{"Protocol":"UNKNOWN","Bits":32,"Data":"0xBBF2A583"}} to openbk7231N-xxxx/RESULT retain=0
    Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic openbk7231N-xxxx/ir/get
    
    Info:MQTT:Publishing val IR_UNKNOWN 0x0 0 to openbk7231N-xxxx/ir/get retain=0
    Info:IR:IR MQTT publish IR_UNKNOWN 0x0 0 took 11ms
    Info:MQTT:Publishing val {"IrReceived":{"Protocol":"UNKNOWN","Bits":0,"Data":"0x0"}} to openbk7231N-xxxx/RESULT retain=0
    Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic openbk7231N-xxxx/ir/get
    
    Info:MQTT:Publishing val IR_UNKNOWN 0x0 1 to openbk7231N-xxxx/ir/get retain=0
    Info:IR:IR MQTT publish IR_UNKNOWN 0x0 1 took 10ms
    Info:MQTT:Publishing val {"IrReceived":{"Protocol":"UNKNOWN","Bits":0,"Data":"0x0"}} to openbk7231N-xxxx/RESULT retain=0
    Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic openbk7231N-xxxx/ir/get
    
    ---- second time (same button)------
    
    Info:MQTT:Publishing val IR_UNKNOWN 0xEB6C2845 0 to openbk7231N-xxxx/ir/get retain=0
    Info:IR:IR MQTT publish IR_UNKNOWN 0xEB6C2845 0 took 13ms
    Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic openbk7231N-xxxx/ir/get
    Info:MQTT:Publishing val {"IrReceived":{"Protocol":"UNKNOWN","Bits":32,"Data":"0xEB6C2845"}} to openbk7231N-xxxx/RESULT retain=0
    Info:MAIN:Time 348, idle 18142/s, free 72384, MQTT 1(1), bWifi 1, secondsWithNoPing 258, socks 2/38 POWERSAVE
    Info:MQTT:Publishing val IR_UNKNOWN 0x0 1 to openbk7231N-xxxx/ir/get retain=0
    Info:IR:IR MQTT publish IR_UNKNOWN 0x0 1 took 7ms
    Info:MQTT:Publishing val {"IrReceived":{"Protocol":"UNKNOWN","Bits":0,"Data":"0x0"}} to openbk7231N-xxxx/RESULT retain=0
    Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic openbk7231N-xxxx/ir/get


    Issues:
    1. If OpenBK is using the same IR library from Tasmota, at minimum the NEC protocol should have been recognized
    2. Probably due to not recognizing the NEC protocol, the data captured are inconsistent

    I have a feeling that there may be some issue around the buffer reading and clearing.

    Can the code owner help check this behaviour please?
  • #35
    jkwim
    Level 10  
    I tested with a Tasmota (tasmora-ir.bin) device and was able to capture all my remotes using the RAW mode and successfully transmit them also.

    So I guess I have to conclude that OpenBK is not yet ready for serious IR application until the protocol files are updated and a RAW mode is implemented.
  • #36
    ferbulous
    Level 16  
    jkwim wrote:
    I tested with a Tasmota (tasmora-ir.bin) device and was able to capture all my remotes using the RAW mode and successfully transmit them also.

    So I guess I have to conclude that OpenBK is not yet ready for serious IR application until the protocol files are updated and a RAW mode is implemented.


    Did you replace the cbu with this?
    Any issues with irhvac send command on esp32?
  • #37
    jkwim
    Level 10  
    Quote:

    Did you replace the cbu with this?

    No I did not. I built an ESP8266 based device to be used temporarily.

    Thanks for the link, I did not know the existance of the module.

    I was looking for a ESP8266 based module which had a somewhat comparable pin arrangement for CBU module and could not find any.

    This opens up the possibility of using the device that I already have. It has a ASM1117 based LDO chip, hopefully can give out more than 500mA during boot to support ESP32.

    Quote:

    Any issues with irhvac send command on esp32?

    My guess is that there should not be an issue with an ESP32. I was able to correctly capture (on a ESP8266) a lengthy payload of a problematic Panasonic Fan remote using the RAW Mode and use the following translator to decode it. So codewise the capability should be there.

    https://tasmota.hadinger.fr/util
  • #38
    ferbulous
    Level 16  
    jkwim wrote:
    My guess is that there should not be an issue with an ESP32

    I swapped with esp32 c05, and the only issue seems to be with irhvac send.
    Still can't figure out how to fix it so just swapped with an esp8266

    jkwim wrote:
    ESP8266 based device to be used temporarily.

    tried building one myself, but i can't quite get irsend working

    jkwim wrote:
    Thanks for the link, I did not know the existance of the module.

    it's quite new, saw it updated last week in blakadder's site
  • #39
    jkwim
    Level 10  
    ferbulous wrote:
    tried building one myself, but i can't quite get irsend working


    Need a Transsistor driver circuit for the IR LED. The IR LED needs to be 940nm type (there is also a 850nm type which has a reddish glow when powered).

    Aubess WiFi Smart IR Controller
  • #41
    ployd915
    Level 2  
    Hello, I bought the same exact device but I'm having issue of it not controlling my device.

    Aubess WiFi Smart IR Controller Aubess WiFi Smart IR Controller Aubess WiFi Smart IR Controller Aubess WiFi Smart IR Controller Aubess WiFi Smart IR Controller Aubess WiFi Smart IR Controller

    Chip: CBU (BK7231N)
    Firmware tried: OpenBK7231N_QIO_1.17.205 , OpenBK7231N_1.17.206 and OpenBK7231N_use_ubuntu_20.04_docker_eec7cf31d4db

    Module Config:
    P7 (PWM1): IRSend
    P8 (PWM2): IRRecv
    P24 (PWM4): WifiLED_n

    Get Sony TV Power ON button
    Logs:
    Info:IR:IR IR_Sony 0x1 0x15 0
    Info:IR:IR IR_Sony 0x1 0x15 1
    Info:IR:IR IR_Sony 0x1 0x15 1
    Info:IR:IR IR_Sony 0x1 0x15 1
    Info:IR:IR IR_Sony 0x1 0x15 1


    Execute Custom Command:
    IRSend Sony 0x1 0x15 1


    log:
    Info:IR:Delay 45ms
    Info:IR:Delay 100ms
    Info:IR:IR send Sony 0x1 0x15 1 protocol 21 addr 0x1 cmd 0x15 repeats 1


    IR light Flashes on Android Camera but TV does not Power ON

    Any Idea what's the problem?
  • #43
    ployd915
    Level 2  
    yes from this post https://www.elektroda.com/rtvforum/viewtopic.php?p=20551713#20551713

    Custom command:
    IRSEND Sony-1-15-1


    log:
    Info:IR:Delay 44ms
    Info:IR:Delay 100ms
    Info:IR:IR send Sony-1-15-1 protocol 21 addr 0x1 cmd 0x15 repeats 1
    OK



    same result as IRSend Sony 0x1 0x15 1, IR light flashes but TV does not power ON