looking for devices…
Found device : Unknown [192.168.1.7]
Writing compatible device not detected!
You can skip that step and proceed with the service broadlink.learn to get the id codes,
Following that procedure hope it helps you.
1.After successfuly pairing with wifi network and the device has already a static IP enter the follow config on configuration.yaml or on your switch.yaml whatever you have:
3.Go to service and search for broadlink.learn, define your host: xxx.xx.x.x and call service.
4.After successful device call you can see on device the white indicator then you can put near the ir device and press the button you want to learn 3 seconds after that you will get the key on home assistant sidebar, notifications.
You can check the following Video after 5:34 min
to see step by step the manual(home assistant) procedure
Do you have any protection on your computer like antivirus firewall?
did you set static ip from your router on the IR Controller as the video describe?
its weird because if you can see the learn code and put the right host name you must get the codes…
i suppose you make restart the HA after that config right?
With that exact steps mine worked, i think you have connection problem between HA and Broadlink you can check the log file to see for details
thank you very much for this marvelous program. I downloaded Broadlink Manager started with the instructions made by Dr.Zzs and the IR for my TV is working perfectly.
Sadly the same thing cannot be said for the RF learning. No matter how hard I tried and read through the how-to’s I failed to get an RF signal to be learned. Even tried the E-Control app and the RM plugin lite like suggested in the before mentioned video by Dr.Zzs it failed to turn on the signal that was converted to Base64.
Broadlink Manager got stuck at the point of “Hold the button down!”
Same picture on my RM2 pro plus 3:
Hope that Tomer_Klein didn’t gave up on developing this.
As you can see the broadlink manager also for IR has many communication problems, you can use instead much more faster and better tools to auto learn your device, you can use this custom compoment,
With that my problems solved and i have a very good AC control
thank you for the advice. Unfortunately Broadlink Manager is working flawlessly with the IR integration and everything I need through IR is already working.
My point here is that I really need RF. Since I have several RF power plugs that are working with IHC and through Google Home but I can’t integrate the signal in HA.
Most of the RF power plugs are really far away (in fact there are 18 plugs all together) and I couldn’t find a better solution for “smart” Home control with such a low price tag.
Thatswhy I’m looking forward to have the RF-signals also working in HA.
@Phillip I have one of the broadlink devices that doesn’t learn RF with this app. I was able to get the codes in using the method outlined here: https://www.home-assistant.io/integrations/broadlink/#using-e-control-remotes
It is not hard, but involves installing and running a python program. Worked well though. Although I really do want to use this app, or better yet have it be fixed in HA to use that.
Also note that some of the broadlink devices don’t work with 315mhz. I ordered one on amazon and it didn’t work with my pool light remote. I found one on ebay that explicitly worked with 315mhz and it worked right away.
I am also finding something similar I have a RM4 Pro.
Using python-broadlink
Connected to the network and appears to be talking to it
devices[0].auth() > True
devices[0].host[0] > ‘192.168.1.172’
Cant get the type (so this may be a concern or compatibility issue)
devices[0].get_type() > ‘Unknown’
devices[0].enter_learning() > AttributeError: device instance has no attribute ‘enter_learning’
Broadlink Manager > “Writing compatible device not detected!”
Home Assistant 0.109.0b5 (Using as Remote)
Shows in the Overview as Remote
Service Call : remote.learn_command
–entity_id: remote.broadlink
–device: Samsung
–command: On
–alternative: true
–timeout: 15
– ERROR (MainThread) [homeassistant.components.broadlink.remote] Failed to learn ‘On/Samsung’: no signal received
Broadlink App - I can add devices and control them no problem at all
I can’t help but think possibly the RM4 Pro isn’t supported
I’m sorry but I am really surprised with something. I thought that wireless keyboard, the ones that have a little usb dongle, and you plug it in the computer, were using IR, or RF signals to send the information. I am trying right now 2 different keyboards, and they are not sending the command to Broadlink Manager.
I mean, I put the Broadlink manager into “learn new command” state, and as much as I press keys on the wireless keyboard, nothing happens!
Of course, doing the same with a TV remote works great.
What it is in the technology that makes it different?
@NKH I ended up getting the IR side working ok using home assistant. Although never had any luck with the RF (which I don’t believe the RM4mini has, so I assume your issue is IR).
With regard to RF I have been testing and working with some of the devs (not sure how much help I was ). I think a fix is there but they are waiting to build it into a release with other stuff. As soon as I hear will post something.
Key things I didn’t do
Be 100% sure there is no cloud connection
In the switch configuration, I had to include type: rm4_pro
Couldn’t get the sensor configuration working but appears I need a HTS2 cable, which I didn’t have
My process on the IR side which is now working fine was
Current Setup
Home Assistant 0.109.3
Broadlink RM4 Pro
Remove from any cloud connection
Delete the Remote device from Broadlink App
Press and hold reset for >10sec for AP mode (few quick blinks pause few quick blinks)
Added to network using python-broadlink
import broadlink
broadlink.setup(‘myssid’, ‘mynetworkpass’, 3)
Checking comms with device
devices[0].host[0] > ‘IPADDRESS’ - PASS
devices[0].enter_learning() > AttributeError: device instance has no attribute ‘enter_learning’ - FAIL (Never did have any joy here)
Under Home assistant added as switch - configuration.yaml
NB: despite the notes suggesting the type was optional mine wouldn’t learn until I added “type: rm4_pro” or I guess in your case rm4mini
