core: Broadlink RM pro+(0x27c3) not working after 0.115.1

The problem

After updating to HA 0.115 and 0.115.1 my RM pro + doesn’t create a new remote. The model (taken from the addon Broadlink Manager) is 0x27c3. It used to work without problem before the update.

Environment

Home Assistant Core release with the issue: 0.115.1
Last working Home Assistant Core release (if known): 0.114
Operating environment (OS/Container/Supervised/Core): OS
Integration causing this issue: Broadlink
Link to integration documentation on our website: https://www.home-assistant.io/integrations/broadlink/

Problem-relevant `configuration.yaml`

Traceback/Error logs

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 228, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/broadlink/__init__.py", line 28, in async_setup_entry
    return await device.async_setup()
  File "/usr/src/homeassistant/homeassistant/components/broadlink/device.py", line 97, in async_setup
    update_manager = get_update_manager(self)
  File "/usr/src/homeassistant/homeassistant/components/broadlink/updater.py", line 24, in get_update_manager
    if device.api.model.startswith("RM mini"):
AttributeError: 'NoneType' object has no attribute 'startswith'

Additional information

[(‘192.168.1.115’, ‘0x27c3’)]

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 15 (6 by maintainers)

Most upvoted comments

What is the error message in the logs? (please include the error code)

If you disable stealth mode, does it work?

Hi and good morning, I tried with the disabled stealth mode and no result. The error message in the core is: 2020-12-04 08:35:05 ERROR (MainThread) [homeassistant.components.broadlink.config_flow] Failed to connect to the device at 192.xxx.100.xxx: Device not found

Logger: homeassistant.components.broadlink.config_flow Source: components/broadlink/config_flow.py:114 Integration: Broadlink (documentation, issues) First occurred: 08:35:05 (2 occurrences) Last logged: 08:36:39 Failed to connect to the device at 192.168.100.223: Device not found

The timeout I used was 10

However, the router (fritz box) shows the device as connected with the correct and confirmed IP address What is confusing me, is the fact that the other 2 models are recognized and work flawlessly. (edit: 10:40 CET) OK, here is an update: I disconnected all other braodlink devices from the network I checked on the IP address of the device in question RM-Pro Plus and got it confirmed as xxx.xxx.xxx.xx3 in the fritzbox. I downloaded the broadlink manager and started the scan. It came back with the device RM2 Pro Plus correct MAC address but a different IP address, then the one my router gave me (scratch, scratch) xxx.xxx.xxx.25 I started the integration with the flow, the integration found the device and it is back alive and working.

My feeble network knowledge doesn’t allow me to find an explanation, why the router gives me a different IP-address than the device is on, according to the router, this is the IP-address of a different device (scratch, scratch).

But then again: Thanks for looking into this, Dietger

dimafemabo on Dec 4, 2020

Hi @dimafemabo! 3 things:

1. Make sure the host is correct.

2. Unlock the devices in the official app.

3. Check your firewall rules.

Hi , thanks for your quick reply.

it is the correct host (for the broadlink device), as confirmed by the router and I am using a fixed IP address.
I did, and it is on local and not remote network, and it works with the IHCP app, I can send commands and they get out to the receivers.
I allowed standard access, like all the other devices have as well.
Firewall is in stealth mode, so no devices are exposed to the internet.
and net-bios filter is active.

Anywhere else I should look? Cheers Dietger

dimafemabo on Dec 3, 2020

@DidibabaQiu Thank you! We will support this device soon.

Really thank you very very very much, I am worried that the seven devices I bought last week will turn into rubbish …^^"

DidibabaQiu on Sep 20, 2020

@DidibabaQiu Thank you! We will support this device soon.

felipediel on Sep 19, 2020

@felipediel thanks very much

ck003 on Sep 19, 2020