I’m experiencing an issue getting a correct response using Moes IR+RF (UFO-R2-RF-V2) blaster with Home Assistant (HA) using LocalTuya. The device is successfully registered to LocalTuya (initially with entity ID 0, later updated to 201) and is used to control RF fan lights throughout my home.
Issue Overview
- The Tuya app struggles to learn RF frequencies but eventually succeeds. Once configured, it controls the fans smoothly at 433.99 Hz.
- However, the Tuya API does not provide a direct method for retrieving learned RF codes. Instead, these codes can be found in the Tuya IoT platform under Device Debug Logs, where they are stored as Base64-encoded strings.
- When learning RF frequencies via HA, the device detects them as 433.92 Hz, but these codes do not work to control the fans.
Troubleshooting Steps Taken
- Extracted the working Base64-encoded RF codes from the Tuya IoT Device logs and added them to HA using the
localtuya.add_remote_codeaction. - Verified that Device sends the correct RF signals (
remote.send_command), as confirmed in the Tuya IoT debug logs(identical to what the Tuya app sends) , when triggered by HA - Despite this, the fan does not respond when triggered from HA.
- Observed that the RF blaster’s indicator light stays on a bit longer when using the Tuya app compared to HA.
- Repeated the command multiple times, which sometimes works but is inconsistent.
- Tried increasing the
hold_secondstimer inremote.send_command, but HA seems to ignore this setting. and the light goes off pretty fast. - Tried a combination of
repeatandhold_secondsin the (remote.send_command)
Looking for Help
Given the inconsistent behavior, I’m wondering if there’s a timing issue, or if HA is handling RF commands differently than the Tuya app.
Has anyone encountered similar issues or found a reliable workaround? Any suggestions would be greatly appreciated!
