Error fetching Loft Socket (Middle Front) (BG800/BG900 at 192.168.0.98) data: [Errno -4000] Network timeout: No response received within 10s

[miketarg]

The problem

Logger: homeassistant.components.broadlink.updater Source: helpers/update_coordinator.py:386 integration: Broadlink (documentation, issues) First occurred: 5:52:53 PM (2 occurrences) Last logged: 5:53:50 PM

Error fetching Loft Socket (Middle Front) (BG800/BG900 at 192.168.0.98) data: [Errno -4000] Network timeout: No response received within 10s Error fetching TV Socket Lower (Livingroom) (BG800/BG900 at 192.168.0.141) data: [Errno -4000] Network timeout: No response received within 10s

What version of Home Assistant Core has the issue?

core-2024.10.1

What was the last working version of Home Assistant Core?

core-2024.8.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Broadlink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/broadlink

Diagnostics information

none yet (now enabled debug logging)

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, @eifinger, 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.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[eifinger]

Thank you for opening an issue. According to the log message this is a problem with your network and nothing home-assistant can fix. Please make sure your devices are reachable.

[miketarg]

This has only happened since updating, and nothing has changed.

On Wed, 9 Oct 2024, 20:25 Kevin Stillhammer, @.***> wrote:

Thank you for opening an issue. According to the log message this is a problem with your network and nothing home-assistant can fix. Please make sure your devices are reachable.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128041#issuecomment-2403270002, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7YJPQ6OL4WWECGBNJYKIM3Z2V7J5AVCNFSM6AAAAABPU7HI42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBTGI3TAMBQGI . You are receiving this because you authored the thread.Message ID: @.***>

[gamajunior]

I got [Errno -4000] and I deleted the integration. After that it can't be discovered.

[escobarin3]

I'm having the exact same issue... No updates, no network problems (as far as I know).

[miketarg]

Yep this is not a network issue for me either I have no other problems other than this since updating. I'd really appreciate it if the Devs can look at this rather than just dismissing it as a network issue.

On Sat, 16 Nov 2024, 04:00 escobarin3, @.***> wrote:

I'm having the exact same issue... No updates, no network problems (as far as I know). Screenshot_20241115_225835_Home.Assistant.jpg (view on web) https://github.com/user-attachments/assets/6122b695-46a1-44be-a36b-2196c8ce7f2d

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128041#issuecomment-2480381867, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7YJPQ7ZAG3EWFNJEZDBDA32A27OFAVCNFSM6AAAAABPU7HI42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQGM4DCOBWG4 . You are receiving this because you authored the thread.Message ID: @.***>

[felipediel]

This is a network issue, not a problem with Home Assistant itself. I see three possible causes:

1. The device's IP address has changed: Update the integration configuration by re-adding the device with the correct IP address.
2. The device is blocking connections from Home Assistant: Ensure external connections are unlocked in the Broadlink app to enable communication.
3. Bad routing in your network: Check your network configuration to ensure proper routing between Home Assistant and the device.

[escobarin3]

Yep this is not a network issue for me either I have no other problems other than this since updating. I'd really appreciate it if the Devs can look at this rather than just dismissing it as a network issue. … On Sat, 16 Nov 2024, 04:00 escobarin3, @.> wrote: I'm having the exact same issue... No updates, no network problems (as far as I know). Screenshot_20241115_225835_Home.Assistant.jpg (view on web) https://github.com/user-attachments/assets/6122b695-46a1-44be-a36b-2196c8ce7f2d — Reply to this email directly, view it on GitHub <#128041 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7YJPQ7ZAG3EWFNJEZDBDA32A27OFAVCNFSM6AAAAABPU7HI42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQGM4DCOBWG4 . You are receiving this because you authored the thread.Message ID: @.>

I I managed to get it working. Although my network was working perfectly and I could connect to Broadlink through the app, the message "this is a problem with your network and nothing Home Assistant can fix" stuck with me. So, to give this option the benefit of the doubt, I restarted my entire network... turned off routers and modems for one minute, and voilà... it’s working again.

I didn’t want to try this restart since my network was functioning fine, and a restart usually brings its own set of issues. But I went ahead and did it, and now it’s working again. I believe there’s something about how the Broadlink integration connects with Home Assistant, as it doesn’t seem to work as efficiently as other integrations. As I mentioned, mine stopped working out of nowhere... no new integrations, no updates, no network changes.

[escobarin3]

This is a network issue, not a problem with Home Assistant itself. I see three possible causes:

1. The device's IP address has changed: Update the integration configuration by re-adding the device with the correct IP address.
2. The device is blocking connections from Home Assistant: Ensure external connections are unlocked in the Broadlink app to enable communication.
3. Bad routing in your network: Check your network configuration to ensure proper routing between Home Assistant and the device.

Thanks for the guidance. However I had already reviewed and tried those three options without success... but after restarting my entire network, it started working again. My device's IP is fixed, and everything else is perfectly configured. In my case, it started failing out of nowhere.

As I explained above, the solution was to restart my entire network. This makes me think that the Broadlink integration needs some improvement (I’m not sure exactly what, since I’m not a developer... haha) in how it connects to Home Assistant.

[miketarg]

I still don't think it's a network issue as this is the only issue I have nothing else is failing I have tried all suggestions here yet it still continues to be an issue. But still I'm told it is a network issue. . .

On Sat, 16 Nov 2024, 15:24 escobarin3, @.***> wrote:

This is a network issue, not a problem with Home Assistant itself. I see three possible causes:

1. The device's IP address has changed: Update the integration configuration by re-adding the device with the correct IP address.
2. The device is blocking connections from Home Assistant: Ensure external connections are unlocked in the Broadlink app to enable communication.
3. Bad routing in your network: Check your network configuration to ensure proper routing between Home Assistant and the device.

Thanks for the guidance. However I had already reviewed and tried those three options without success... but after restarting my entire network, it started working again. My device's IP is fixed, and everything else is perfectly configured. In my case, it started failing out of nowhere.

As I explained above, the solution was to restart my entire network. This makes me think that the Broadlink integration needs some improvement (I’m not sure exactly what, since I’m not a developer... haha) in how it connects to Home Assistant.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128041#issuecomment-2480614268, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7YJPQ4BKLWTOV5RXQJ4TYT2A5PTBAVCNFSM6AAAAABPU7HI42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQGYYTIMRWHA . You are receiving this because you authored the thread.Message ID: @.***>

[gamajunior]

I got [Errno -4000] and I deleted the integration. After that it can't be discovered.

Resolved Issue with BROADLINK RM4 PRO Connection

Hello everyone,

I recently encountered an interesting issue when transitioning my Home Assistant setup from a Mini PC to a laptop. On the Mini PC, the BROADLINK RM4 PRO worked perfectly with a wired network connection. However, after switching to a laptop that only supports Wi-Fi connectivity (using an Intel AX201 adapter), the integration with the BROADLINK stopped functioning. Interestingly, this was the only feature that did not work with the new Wi-Fi setup.

To resolve the issue, I purchased a USB-C gigabit Ethernet adapter for the laptop. As soon as I returned to using a wired connection, the BROADLINK RM4 PRO was immediately recognized and began functioning normally again.

It seems counterintuitive that such a simple change in connection type would affect the integration, but reverting to a wired connection proved to be an effective solution!

I hope this experience can assist others who might be facing a similar issue.

If anyone has further insights into why this occurred, I would be glad to hear them!

Cheers!

[engperini]

Hi everyone. I had the same issue, it's started to fail after an restart of my network when power goes down. I will try to delete the HA integration and configure it again. The broadlink app works fine, the HA works fine except for the broadlink integration (it worked fine since I installed until a couple days(

[miketarg]

This is clearly not a network issue again I state the same as above the Broadlink app works fine but the Broadlink integration fails to work.

Please can someone look at this ?

On Tue, 17 Dec 2024, 01:03 PeriniDev, @.***> wrote:

Hi everyone. I had the same issue, it's started to fail after an restart of my network when power goes down. I will try to delete the HA integration and configure it again. The broadlink app works fine, the HA works fine except for the broadlink integration (it worked fine since I installed until a couple days( Screenshot_20241216_215920_Home.Assistant.jpg (view on web) https://github.com/user-attachments/assets/79596d56-ecf7-407c-982d-1138d5fec3a2

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128041#issuecomment-2547281684, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7YJPQ3XN7D4DOJNEILV6YL2F5Z5LAVCNFSM6AAAAABPU7HI42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXGI4DCNRYGQ . You are receiving this because you authored the thread.Message ID: @.***>

[marc95200]

Same problem here

[miketarg]

Can the owner of the integration please look at this issue as it's clearly still a problem?

On Sat, 18 Jan 2025, 16:33 marc95200, @.***> wrote:

Same problem here

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128041#issuecomment-2599778456, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7YJPQ45QVLRCYGBD242WKL2LJ65PAVCNFSM6AAAAABPU7HI42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJZG43TQNBVGY . You are receiving this because you authored the thread.Message ID: @.***>

[marc95200]

Same problem here

Finaly, i manage tovresolve it but i was in a exact same situation like you.

I found my device online in the boradlink app but unable to find it by HA.

I have a usb wifi extension. I had an issue with it, i reconfigure it and the error disapear, i can use it with HA

[marc95200]

Same problem here

Finaly, i manage to resolve it but i was in a exact same situation as you.

I found my device online in the boradlink app but unable to find it by HA.

I have a usb wifi extension. I had an issue with it, i reconfigure it and the error disapear, i can use it with HA

[marksieczkowski]

I agree not a real network issue. I resolved it by deleting the Broadlink Integration, restarting Home Assistant, and starting from scratch.

[ravenade]

Same problem (not related with it infrastructure) and same solution.

It would be great if someone could fix it.

[miketarg]

This is still an issue, can someone please look at this issue, it's been open for months and months and no one looks at this thread, extremely annoying

[miketarg]

This socket is online and responding in the broadlink app but Home assistant can't connect to it.

[MarcStavroguin]

This is definitely a connectivity issue between BroadLink devices and certain routers. I experienced the same problem for several months. After testing my BroadLink RM4 Pro on a friend’s router, it connected through the BroadLink app without any issues.

In my case, the solution was to manually select channels 1, 6, and 11 on my 2.4 GHz network. Once the device was connected, I assigned it a static IP address.

This solution was provided by the BroadLink support team, so I’m sharing the details they gave me in case someone else encounters the same issue and wants to try the different alternatives:

1.Check the router settings and ensure the 2.4 GHz network is set to WPA2 security mode.

2.Turn off the firewall (optional).

3.Set the 2.4 GHz Wi-Fi protocol to 802.11 b/g/n.

4.Enable port forwarding for TCP ports 80, 8080, 16384, and 1812 (optional).

5.Disable PMF (Protected Management Frames).

6.Make sure the Wi-Fi SSID isn’t too long, and that the password is no more than 32 characters.

If the issue persists after adjusting the router settings, you can try the hotspot method:

1.Use another phone to create a 4G hotspot with the same SSID and password as your home Wi-Fi.

2.Turn off your home Wi-Fi, then use the BroadLink app to add the device to the hotspot.

3.Once the device is added, turn off the hotspot and re-enable your home Wi-Fi to see if the device connects automatically.

Good luck!

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ravenade]

The issue still persists

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.