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

No interface or no devices #55

Open
zmlklfe opened this issue May 11, 2022 · 5 comments
Open

No interface or no devices #55

zmlklfe opened this issue May 11, 2022 · 5 comments

Comments

@zmlklfe
Copy link

zmlklfe commented May 11, 2022

Running broadlinkmanager on docker on synology.
I can get the web-interface working by running the container, but then i cannot find any broadlink devices.
I guess it is due to network_mode is supposed to be set to host. If i set it to host, the web interface disappears.

Does anyone know how to solve this?

@btzs
Copy link

btzs commented Jun 1, 2022

Can you post the output of your docker or docker-compose?

I have many other docker networks which caused problems. I solved it by setting the environment variable DISCOVERY_IP_LIST in my docker-compose.yml:

version: "3.6"
services:
  broadlinkmanager:
    image: techblog/broadlinkmanager
    network_mode: host
    container_name: broadlinkmanager
    restart: unless-stopped
    volumes:
      - ./broadlinkmanager:/opt/broadlinkmanager/data
    environment:
      - ENABLE_GOOGLE_ANALYTICS=False
      - DISCOVERY_IP_LIST=10.0.4.103 #set this to your host's ip address; must be same subnet as your Broadlink devices

Without setting it I had many interfaces but no devices were found (timeout issue?).


benjamin@benjamin-laptop:~/demos/broadlinkmanager-docker$ docker-compose up
Starting broadlinkmanager ... done
Attaching to broadlinkmanager
broadlinkmanager    | 2022-06-01 00:14:45.480 | DEBUG    | __main__:get_env_ip_list:69 - Environement discovered IP List []
broadlinkmanager    | 2022-06-01 00:14:45.487 | DEBUG    | __main__:get_local_ip_list:62 - Locally discovered IP List ['10.0.4.103', '172.17.0.1', '172.24.0.1', '172.22.0.1', '172.26.0.1', '172.28.0.1', '172.31.0.1', '172.18.0.1', '192.168.0.1', '172.21.0.1', '172.23.0.1', '172.29.0.1', '172.20.0.1', '172.30.0.1', '172.19.0.1', '172.27.0.1', '172.25.0.1']
broadlinkmanager    | 2022-06-01 00:14:45.487 | INFO     | __main__:<module>:124 - Broadlink will try to discover devices on the following IP interfaces: ['10.0.4.103', '172.17.0.1', '172.24.0.1', '172.22.0.1', '172.26.0.1', '172.28.0.1', '172.31.0.1', '172.18.0.1', '192.168.0.1', '172.21.0.1', '172.23.0.1', '172.29.0.1', '172.20.0.1', '172.30.0.1', '172.19.0.1', '172.27.0.1', '172.25.0.1']
broadlinkmanager    | 2022-06-01 00:14:45.489 | INFO     | __main__:<module>:133 - Configuring app
broadlinkmanager    | 2022-06-01 00:14:45.507 | INFO     | __main__:<module>:634 - Broadllink Manager is up and running
broadlinkmanager    | INFO:     Started server process [1]
broadlinkmanager    | INFO:     Waiting for application startup.
broadlinkmanager    | INFO:     Application startup complete.
broadlinkmanager    | INFO:     Uvicorn running on http://0.0.0.0:7020 (Press CTRL+C to quit)

After setting it, Broadlinkmanager only looks on this one interface:

benjamin@benjamin-laptop:~/demos/broadlinkmanager-docker$ docker-compose up
Recreating broadlinkmanager ... done
Attaching to broadlinkmanager
broadlinkmanager    | 2022-06-01 00:15:12.268 | DEBUG    | __main__:get_env_ip_list:69 - Environement discovered IP List ['10.0.4.103']
broadlinkmanager    | 2022-06-01 00:15:12.268 | INFO     | __main__:<module>:124 - Broadlink will try to discover devices on the following IP interfaces: ['10.0.4.103']
broadlinkmanager    | 2022-06-01 00:15:12.270 | INFO     | __main__:<module>:133 - Configuring app
broadlinkmanager    | 2022-06-01 00:15:12.289 | INFO     | __main__:<module>:634 - Broadllink Manager is up and running
broadlinkmanager    | INFO:     Started server process [1]
broadlinkmanager    | INFO:     Waiting for application startup.
broadlinkmanager    | INFO:     Application startup complete.
broadlinkmanager    | INFO:     Uvicorn running on http://0.0.0.0:7020 (Press CTRL+C to quit)

@footy42
Copy link

footy42 commented Jan 10, 2023

I am having the same issue. Adding - DISCOVERY_IP_LIST did not change anything.
without it, multiple ip's are checked including the host machine's. It is not finding any broadlink devices.

@dwaynelarose
Copy link

Some things that worked for me:

  • Added the ip of the system that scanning from under the Enviromental variable DISCOVERY_IP_LIST
  • make is in Docker is Host networking mode
  • make sure to unlock the device in the Broadlink app
    o Open the Broadlink app.
    o From the Home screen, tap on your Broadlink device.
    o Tap the ... in the top right.
    o Scroll down and toggle "Lock device" to Off. (may be under properties)
    o Tap OK when prompted "Confirm to unlock the device"

@MrYutz
Copy link

MrYutz commented Nov 24, 2023

If you are running on a Mac, docker does not support host networking mode.

@robertofabrizi
Copy link

If you are running on a Mac, docker does not support host networking mode.

WSL2 doesn't support it either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants