core: Broadlink RM mini 3 0x27cc Not working after 0.115

The problem

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

Environment

  • Home Assistant Core release with the issue: 0.115
  • 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

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 25 (10 by maintainers)

Most upvoted comments

It may take a little while, but soon we will have a release with all these types.

Thanks for the update on the subject and the quick replies as well last night.

@felipediel thanks for the link to the broadlink addition here: https://github.com/mjg59/python-broadlink/commit/b4aa15617aef4c24075bc06a99b929b725681838

I ended up adding that into my file here: /srv/homeassistant/homeassistant_venv/lib/python3.7/site-packages/broadlink/__init__.py

Gave HA a reboot and now it works perfectly as intended through the Integrations page 👍

Doesn’t look like there’s been a new release on that repo for months, you think it’ll be some time before that commit comes along to release?

onfig_entries.py", line 228, in async_setup result = await component.async_setup_entry

the same problem but my devtype is “0x27d0” (RM mini 3), this devtype “0x27d0” is not the same as others, really inexplicable.

This problem does not exist anymore. You just need to wait.

Thanks for the quick response! No problem, I’ll roll back until it gets released.

I get the same error as @rwarner and am also using smartIR. It appears that only the RM4 Minis in my system are affected (4 of them). The RM3 Mini that I have appears to be connected.

I will attempt to remove that integration and let you know shortly.

I’ve removed the integration multiple times and re-added it and doesn’t seem to make a difference. Mixing reboots in between — I keep getting this in my logs:


Logger: homeassistant.config_entries
Source: components/broadlink/updater.py:24 
First occurred: 10:30:09 PM (1 occurrences) 
Last logged: 10:30:09 PM

Error setting up entry Living_Room for broadlink
Traceback (most recent call last):
  File "/srv/homeassistant/homeassistant_venv_3.7.5/lib/python3.7/site-packages/homeassistant/config_entries.py", line 228, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/srv/homeassistant/homeassistant_venv_3.7.5/lib/python3.7/site-packages/homeassistant/components/broadlink/__init__.py", line 28, in async_setup_entry
    return await device.async_setup()
  File "/srv/homeassistant/homeassistant_venv_3.7.5/lib/python3.7/site-packages/homeassistant/components/broadlink/device.py", line 97, in async_setup
    update_manager = get_update_manager(self)
  File "/srv/homeassistant/homeassistant_venv_3.7.5/lib/python3.7/site-packages/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'

It does seem to “connect” to the device when I put in the IP address in the configuration workflow, comes back with chinese characters that I replace with “Living_Room” also tried with “Living Room”