-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
broadlink integration error #40191
Comments
Same thing happens with rm_mini3_newblackbean, no entity is created . It`s connect fine to the old rm_mini3 . |
same issue here rm_mini_3 no entity created this shows in logs. |
same here: Logger: homeassistant.components.broadlink Failed to connect to the device at 10.0.0.x: Invalid host for this configuration flow. The MAC address should be xx:xx:xx:xx:xx:xx, but xx:xx:xx:xx:xx:xx was given and Error handling request |
broadlink documentation |
Hey there @Danielhiversen, @felipediel, mind taking a look at this issue as its been labeled with an integration ( |
The new Blackbean will be solved with #39228. |
@neotrunks Please open a terminal on your computer, install the python-broadlink library ( import broadlink as blk
devs = blk.discover(timeout=5)
print([(d.host[0], hex(d.devtype)) for d in devs])
devs = blk.discover(discover_ip_address="192.168.0.17", timeout=5) # Your device IP address
print([(d.host[0], hex(d.devtype)) for d in devs]) What is the output? |
@joten75 Once you choose a device for the configuration flow, you can no longer change it. You need to start a new configuration flow if you want to change it. This is not a bug. The second error is still obscure to me. Do you have any other clues? What were you doing (step by step) when this error appeared? |
@neotrunks Please consider sending me your device type soon, or we will miss the next release. |
@felipediel |
0x6026 is working, right? |
@felipediel |
@spiro-c Thank you! We will support this device soon. |
Yes, but not all my ir codes are showing up. Will need to look into that further when I get the chance. |
Ok. Please read the docs first, we changed a lot of things. |
Post retracted. |
[('192.168.0.136', '0x27c3')] |
@neotrunks Thank you! Your device will be supported soon. |
@felipediel i |
No. Please send me your device types so I can check. |
type: rm_mini3_newblackbean |
@joten75 RM mini 3 new Blackbean (0x5f36) will be supported after this patch. |
Thanks for all this work @felipediel. I think you already have my device in your PR, but I ran your code to get the info to be sure.
You commented as I was checking! Thanks! |
thank @felipediel i very appreciate your help. Logger: aiohttp.server Error handling request |
@joten75 I need to see the types (represented in hex). This is how you get them: #40191 (comment) |
@paynenz Thank you! I created a PR. Is the brand correct? (Broadlink) |
It's an Efergy Ego smart plug. I have been using the older broadlink switch configuration with type |
This? |
That's the one, I have the New Zealand outlet model but I doubt that it would matter |
Thank you! |
hi, i have the same problem (RM4c mini ver 2020) can you help me? |
It's open: mjg59/python-broadlink#476 |
Hi, I have SP4L-UK units that report back as: [('10.0.1.126', '0xa589')] Can you add them to the integration please? |
Sure. Could you please confirm if your device works with the SP4 class? I'm pretty sure it will work, but if it doesn't work out we also have the SP4B class to test. import broadlink as blk
d = blk.sp4(("192.168.0.16", 80), "aabbccddeeff", 0xa589) # host, mac, devtype
d.auth()
# Test power on
d.set_power(True)
# Test power off
d.set_power(False)
# Test get state
d.get_state() |
HI Felipe, Yes it works. I added a manual line into the init.py file and the integration found the devices and controls them correctly, as well as the state. |
Thank you! |
I followed these same commands with the same device and got the following error:
Anything I can try to get this working? |
@occamatic Try unlocking the device with the official app first. |
Thank you it worked! You saved me having to return these 2 units I bought. Keep up the good work! |
Thanks for reporting back! |
RM4 Pro ('192.168.1.200', '0x653c') |
Hi! I have been 5 hours trying to conect my RM PRO+ to HA but it's impossible. I select de + button to add a new a integration I put the host but the issue is: ''' Failed to connect to the device at 192.168.1.40: Device not found |
Hi @pedroeched. Try unlocking the device with the official app. |
Hi this is my device: [('192.168.16.242', '0x279d')] RM4 Pro |
This is an RM pro+. It is already supported. |
Ok, thanks, what about subdevices? Got some TC2 lightswitches, are those
already supported?
Regards.
El mié, 6 de ene. de 2021 a la(s) 23:02, Felipe Martins Diel (
notifications@github.com) escribió:
… This is an RM pro+. It is already supported.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://mailtrack.io/trace/link/fe0fb6825b49f95864e4fd7459983a2d2cfc281d?url=https%3A%2F%2Fgithub.com%2Fhome-assistant%2Fcore%2Fissues%2F40191%23issuecomment-755885680&userId=2641576&signature=9967701e9a5235e5>,
or unsubscribe
<https://mailtrack.io/trace/link/d978a675cec9d15cc3859f31d046f29a3c86f236?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARSDR4IADD5LIKIE4T7VKMDSYU57JANCNFSM4RQ3VE4Q&userId=2641576&signature=b56de05d6bbd7c77>
.
|
You can learn the RF codes and send them with your RM pro. See this thread. |
For anyone that would like to get their broadlink devices working before the broadlink integration is updated with their device code, these are the instructions I have been using after each time I update Home Assistant. I am running the Home Assistant OS.
If you're not familiar with vi, instructions can be found here |
Hi @sosolid @occamatic. We will improve SP4 support in the next updates. May I see the answer to get_state() to implement the features correctly?
>>> import broadlink as blk
>>> d = blk.hello("192.168.0.16") # Example IP address
>>> d.auth()
>>> print(d.get_state()) |
Here you go:
|
Thank you! |
The problem
I tried to use new integration for my broadlink remote (rm_pro_phicom), it worked with custom components without problems,
with new integration it fails and doesn't create new entity.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: