Broadlink RM4C mini became unavailable

[ssrsmart]

The problem

I have 4 broadlink RM4C mini to control my air conditioners, it's frequently became unavailable and the only way to fix it by deleting the devices and re integrate it, the devices it's self have no issues, connected to the wifi and works normally from the broadlink app

What version of Home Assistant Core has the issue?

2023.9.3

What was the last working version of Home Assistant Core?

HAOS

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Broadlink

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @danielhiversen, @felipediel, @l-i-am, mind taking a look at this issue as it has been labeled with an integration (broadlink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of broadlink can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign broadlink Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

broadlink documentation broadlink source _{^{(message by IssueLinks)}}

[felipediel]

Probably caused by a dynamic IP address. We don't support dynamic IPs currently, the address cannot change, so you have to figure it out in the network layer 👍

[ssrsmart]

Probably caused by a dynamic IP address. We don't support dynamic IPs currently, the address cannot change, so you have to figure it out in the network layer 👍

All the IP are static, when it becomes unavailable To solve the issue I have to deleting the device and re integrating it by adding the same static ip and it back to work normally, also I have a broadlink rgb bulb works with out any issues, only the RM4C is going offline

[felipediel]

Did you block access to the internet?

[feel2006]

I have the same message as in the picture. The only difference is that I can see the device, but Temperature and Humidity are no longer available. I checked in the Broadlink app, it still appears there.

[ssrsmart]

Did you block access to the internet?

Yes, after I connect it to the router via broadlink app, I disconnected the device from the power and deleted it from the app and restarted it and I integrated it to home assistant, recently I noticed that the issue accure when the router restart, also the last time it fail I noticed it back to work after home assistant operation system update، by the way I did the same think with the rgb bulb, I deleted it from the app but it works great without any issues, also the problem was frequently accure even before it deleting the device from the app

[ssrsmart]

I have the same message as in the picture. The only difference is that I can see the device, but Temperature and Humidity are no longer available. I checked in the Broadlink app, it still appears there.

There is no difference, so I can see the device, but the remote are no longer available

[gorbep]

I have the same problem with RM4C mini. Power OFF and ON the Broadlink device helps for a while... The IP adress is the same, and in the Broadlink app shows the device online... This issue beats only the RMC4 mini?

[djvj1]

I also have the same issue. I just got the RM4 Mini, added it to home assistant. Couple days later I got the notice in HA "Integration requires reconfiguration". I click the "Reconfigure" button in devices and get the error: Error Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

But it's working fine in the broadlink app. I think I did update HA in between from October to November release. The device has a static IP from my router, so the IP never changed.

In the devices logbook when I power cycle it, it shows it detected it's presence, yet still says I have to reconfigure it: November 10, 2023 BroadLink RM 4 Mini IR Remote was detected at home 13:08:13 - 11 hours ago BroadLink RM 4 Mini IR Remote was detected away 12:54:24 - 11 hours ago

If I disable the device, then re-enable it. It comes back online in HS. But HA still asks to reconfigure it.

[ssrsmart]

Home assistant core 2023.11.2 Home assistant supervisor 2023.11.3

The problem still exists

[claesr]

Same here. Had to bring back backup to core version 2023.11.1 and now it works again.

[MrMxyzptlk]

Ditto here, shows in Broadlink app on Android, static IP set on router.

[tomlyo]

Broadlink device (RM4) has been non-functional for a while now due to this. If I delete the integration and re-add it works, next day I look it broken again, likely after several hours

EDIT: I'd like to add that it isn't actually as random as I initially thought and is tied to an event such as power outage or APs going offline

[OmenBoy]

I've had this problem for over a year. My IP addresses are static, and this only happens if I restart my router. I've tried multiple routers. I doubt it's anything to do with our routers, and more to do with HA being garbage. 🤷‍♂️

[OmenBoy]

I checked my core.config_entries and sure enough the IP addresses were all changed to invalid IP addresses. I was gonna sub to Nabu Casa but after dealing with this for over a year, with no fix in sight, I'm just over HA. It really is a worthless platform.

[MagnusHass]

Same problem here. Static Ip that I can ping from HA. Try to reload integration manually with no success, but after a restart of HA then BroadLink will reload successfully. After a couple of days, same problem again. Runs HA 2023.12.4. BroadLink RM4C mini

[felipediel]

Does the problem persist with DHCP enabled on Hass? And disabled?

[tomlyo]

Does the problem persist with DHCP enabled on Hass? And disabled?

Presently my HASS install is configured for DHCP, it is my router that maintains all my static IP reservations for my devices. Are you suggesting I try disabling DHCP (i.e. setting a static IP on HASS itself)? Or perhaps I'm misunderstanding what you're asking.

[felipediel]

DHCP discovery, there is an integration for this, do you have it enabled?

[OmenBoy]

DHCP discovery, there is an integration for this, do you have it enabled?

There’s an add on called “DHCP server” is that what you’re talking about? I don’t have any integrations or add ons called “DHCP discovery”, nor are there any in the add on store or in add integrations.

[tomlyo]

DHCP discovery, there is an integration for this, do you have it enabled?

Yes, it looks like the integration is part of the default config, and I have the default_config: line in my configuration.yaml file.

[felipediel]

Ok, disable it and let's see if the problem persists

[tomlyo]

Ok, disable it and let's see if the problem persists

How do I disable DHCP discovery integration? From what I've read, I'd have to remove the default_config: integration, which has 42 other integrations that would get disabled unless I specified all 42 manually in my config.

[felipediel]

You can disable integrations in Configuration -> Integrations -> ... -> Disable. If you don't see the DHCP discovery integration there, there's no other way, you need to rewrite the default config.

[tomlyo]

You can disable integrations in Configuration -> Integrations -> ... -> Disable. If you don't see the DHCP discovery integration there, there's no other way, you need to rewrite the default config.

No, DHCP discovery does not show in the integrations list. I've removed default_config from my yaml file and added the following:

automation: assist_pipeline: backup: bluetooth: config: conversation: counter: energy: frontend: hardware: history: homeassistant_alerts: cloud: image_upload: input_boolean: input_button: input_datetime: input_number: input_select: input_text: logbook: logger: map: media_source: mobile_app: my: network: person: schedule: scene: script: ssdp: stream: sun: system_health: tag: timer: usb: webhook: zeroconf: zone:

Thereby disabling DHCP discovery.. When I get home today I'll try restarting my APs/forcing the integration to break.

[tomlyo]

I'm not sure if it was a recent update (running HASS 2023.12.4), or by disabling DHCP discovery, but I haven't yet had the issue.. this extends to my Kasa stuff as well. I ended up cleaning up my config and using the https://github.com/arturpragacz/hass-cc-default-config-exclude integration to exclude dhcp. DHCP discovery wouldn't do much good for me anyway as all my IOT devices are on a different VLAN from Home Assistant.

[felipediel]

When the DHCP discovery component is enabled, this integration listens for DHCP requests on the network and tries to reach any registered Broadlink device on the new IP address when it sees one. If the device responds, the IP address is changed in the config entry.

So a new IP address is being assigned to the device at least for a brief moment and the integration is changing the config entry to that address.

[Jannik99]

After my RM4 Mini was unavailable for a while, I deleted the integration and wanted to reinstall it. However, my RM4 Mini is no longer found in the network, even if I enter the (static!) IP. I would like to try if it works with an old version, but unfortunately my backups don't include some tinkering solutions, so that's not an option at the moment. Core 2024.1.6 Supervisor 2023.12.1 Operating System 11.4 Front end 20240104.0

[felipediel]

Your device is probably locked, you can unlock it in the Broadlink app

[Jannik99]

Your device is probably locked, you can unlock it in the Broadlink app

Nah, it isn't. As I said, it worked before and I double checked if it's locked.