Skip to content
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 SP4M-US Integration #60669

Closed
spencerthayer opened this issue Dec 1, 2021 · 4 comments
Closed

Broadlink SP4M-US Integration #60669

spencerthayer opened this issue Dec 1, 2021 · 4 comments

Comments

@spencerthayer
Copy link

spencerthayer commented Dec 1, 2021

The problem

The problem is that the Broadlink SP4M-US use FastCon™ Bridging which is just a proprietary mesh network for Broadlink devices. According to Broadlink's documentation FastCon works as follows.

BroadLink 4th gen smart plugs support FastCon™ Bridging which allows
devices building their own sub networks with one of them acting as
master and others as clients to minimize the connection load of Wi-Fi
router. When the device was added in the network. It will look for
better network routes in 1-2 minutes and may join a sub network.

This causes issues with the existing Homeassistant integration since we cannot access the switches via their IP address. The following forum posts go into greater detail.

Is it, or could it be possible, to access and control the SP4M-US over the FastCon "sub network" via the device MAC address? It is worth noting that for all users at least one SP4M-US, functioning as the hub for FastCon, does connect to Homeassistant.

What version of Home Assistant Core has the issue?

core-2021.11.5

What was the last working version of Home Assistant Core?

core-2021.11.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

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

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

The advised hack were users disconnect the each SP4M-US from the internet via the router to prevent FastCon does not work for the latest SP4M-US firmware and as of this posting there is no existing work around.

@probot-home-assistant
Copy link

broadlink documentation
broadlink source
(message by IssueLinks)

@probot-home-assistant
Copy link

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!
(message by CodeOwnersMention)

@spencerthayer
Copy link
Author

spencerthayer commented Jan 7, 2022

@Danielhiversen, @felipediel, and/or @L-I-Am I do not believe this ticket warrants being closed since the problem is still persistent.

@spencerthayer
Copy link
Author

Resubmitted this ticket since it doesn't seem that the bot will re-open it.
#63853

@github-actions github-actions bot locked and limited conversation to collaborators Feb 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants