…and FWIW I am now experimenting with RF control. I had found that on discovering my device, it recorded it as “DevType 9863” and not supporting RF. I just edited “BroadlinkDevices.json” to say
and then the Learn RF button appeared, but although it appeared to be trying to learn it was not able to save RF codes from my remote (maybe it’s not doing the full “sweap frequency”?).
I was going to give up then, but decided to try a little harder. So I then used the ?e-Control" app (not ?eWeLink?) to record the codes from my fireplace remote. Tested to make sure that they worked from the app, and I then used ?share? in the app and, ?share to other phones in WLAN?, and then opened a web browser to http://my mobile address:48815/ to download the data. I then got the python script from https://github.com/NightRang3r/Broadlink-e-control-db-dump, installed simplejson on by raspberry pi (apt-get install python-simplejson), copied the script and e-Control data files onto the pi and extracted the codes. In my case they were (to turn my fireplace on):
to turn it off.
I then created a fireplace folder, temporarily recorded two commands using IR, then edited the BroadlinkCommandSets.json file so that “Type” was RF and changed the code to match the code that I’d discovered, and… didn’t work. Ah well, worth a try.