Portainer Templates logo

Portainer Templates

Broadlink Manager Broadlink Manager

Stack

Smart Home

BroadlinkManager is a Flask powerd, easy to use system that hepls you to work with Broadlink Devices.

Image details

Pulls: 1.3M
Architecture: amd64, arm64, arm/v7, arm
Image size: 202 MB
Latest: 6.0.0
User: techblog
Created: Jun 03, 2020
Updated: 2 years ago
Status: active

Configuration

Type
Compose
Platform
linux
Image
techblog/broadlinkmanager
Volumes
/opt/broadlinkmanager/data : /portainer/Files/AppData/Config/broadlinkmanager
Restart
unless-stopped
Source

Template by xneo1·Source

Standalone Install

Select an install method, to see config/commands for deploying Broadlink Manager

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Broadlink Manager, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  broadlinkmanager:
    image: techblog/broadlinkmanager
    network_mode: host
    container_name: broadlinkmanager
    restart: unless-stopped
    volumes:
      - /portainer/Files/AppData/Config/broadlinkmanager:/opt/broadlinkmanager/data

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/broadlink-manager.yml up -d

More install options in our documentation.

Please :star: this repo if you find it useful


PayPal

BroadlinkManager

BroadlinkManager is a Flask powerd, easy to use system that hepls you to work with Broadlink Devices. With Broadlink manager you can:
  • Scan your network for devices.
  • Lean and Send IR or RF Codes
  • Random generate RF Codes
  • Change Repeats for Exisiting codes (IR/EF)

Credits:

python-broadlink broadlinkcli
Random-Broadlink-RM-Code-Generator

Supported Devices and Models

#### sp2:
0x2711,  # SP2
0x2719, 0x7919, 0x271a, 0x791a,  # Honeywell SP2
0x2720,  # SPMini
0x753e,  # SP3
0x7D00,  # OEM branded SP3
0x947a, 0x9479,  # SP3S
0x2728,  # SPMini2
0x2733, 0x273e,  # OEM branded SPMini
0x7530, 0x7546, 0x7918,  # OEM branded SPMini2
0x7D0D,  # TMall OEM SPMini3
0x2736  # SPMiniPlus

rm:

0x2712,  # RM2
0x2737,  # RM Mini
0x273d,  # RM Pro Phicomm
0x2783,  # RM2 Home Plus
0x277c,  # RM2 Home Plus GDT
0x272a,  # RM2 Pro Plus
0x2787,  # RM2 Pro Plus2
0x279d,  # RM2 Pro Plus3
0x27a9,  # RM2 Pro Plus_300
0x278b,  # RM2 Pro Plus BL
0x2797,  # RM2 Pro Plus HYC
0x27a1,  # RM2 Pro Plus R1
0x27a6,  # RM2 Pro PP
0x278f,  # RM Mini Shate
0x27c2,  # RM Mini 3
0x27d1,  # new RM Mini3
0x27de  # RM Mini 3 (C)
    

rm4:

0x51da,  # RM4 Mini
0x5f36,  # RM Mini 3
0x6026,  # RM4 Pro
0x6070,  # RM4c Mini
0x61a2,  # RM4 Pro
0x610e,  # RM4 Mini
0x610f,  # RM4c
0x62bc,  # RM4 Mini
0x62be,  # RM4c Mini
0x6539  # RM4c Mini
0x653c   # RM4 Pro

a1:

0x2714,  # A1
    

mp1:

0x4EB5,  # MP1
0x4EF7  # Honyar oem mp1
        

hysen:

0x4EAD,  # Hysen controller

S1C:

0x2722   # S1 (SmartOne Alarm Kit)

dooya:

0x4E4D,  # Dooya DT360E (DOOYA_CURTAIN_V2)
    

bg1:

0x51E3, # BG Electrical Smart Power Socket
    

lb1:

0x60c8,    # RGB Smart Bulb

Usage

Run from hub

docker-compose from hub

version: "3.6"
services:
  broadlinkmanager:
    image: techblog/broadlinkmanager
    network_mode: host
    container_name: broadlinkmanager
    restart: always
    restart: unless-stopped
    volumes:
      - ./broadlinkmanager:/opt/broadlinkmanager/data
Now open your browser and enter your docker container ip with port 7020: http://docker-ip:7020

Screenshots

Device Listing
RF Code Generator
Learn and Send IR/RF Codes
Base64 and Hex Conversation

Donation


Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/broadlinkmanager

Image won't pull

Test the pull directly on the host: docker pull techblog/broadlinkmanager

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7, arm
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Broadlink Manager is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Broadlink Manager needs bundled into one download. This template pulls techblog/broadlinkmanager, which Docker fetches once (about 202 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Broadlink Manager's comes from Docker Hub, published by techblog.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 6.0.0. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, arm, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Volumes

A volume is where Broadlink Manager keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /opt/broadlinkmanager/data from /portainer/Files/AppData/Config/broadlinkmanager on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts Broadlink Manager after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Broadlink Manager sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container broadlinkmanager. That's what you'll spot in the containers list and use in commands like docker logs broadlinkmanager.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Broadlink Manager up. Add the template list to Portainer once, then deploying Broadlink Manager is a click rather than a wall of config.