iobroker-community-adapters / ioBroker.broadlink2

ioBroker adapter for broadlink devices like the RM remote or SP switches
MIT License
41 stars 14 forks source link
broadlink broadlink-a1 broadlink-rm broadlink-sm broadlink-sp iobroker-adapter

Logo Controls BroadLink compatible devices

NPM version installed Downloads Travis-CI

Deutsche Anleitung translated by google

Русские инструкции переведены с гуглом

Adapter for different Broadlink compatible WLan-devices (RM++,SP++,A1, Floureon, S1C, LB1)

This is an ioBroker adapter for multiple Broadlink switch like RM2, RM3, RM Plus, SP1, SP2, SP3, Honeywell SP2, SPMini, SPMini2, SPMiniPlus and some OEM products from them. ALso remote controllers are supported like RM2, RM Mini, RM Pro Phicomm, RM2 Home Plus, RM2 Home Plus GDT, RM2 Pro Plus, RM2 Pro Plus2 and RM2 Pro Plus BL. Multiple controllers will generate their own entries and need to be trained separately. It scans the network to find compatible devices and installs them (currently only switches type SP?).

If you learned states for RM* and then rename their name the state-ID will change to the new name as well!

You can create also your own new commands in LearnedStates if you use 'code'+ your code as the value (with 'CODE' preceeding the code or even better (because of it will remain if you rename the state) add a field 'code' to native with the admin.object pencil and put there the hex code (without 'CODE'!).

The adapter has fixed states to send codes from RM-devices or to learn them It can also send individual scenes (actions on multiple devices).

If devices which are configured on a certain IP are not found again they will be flagged 'notReachable'! If they are connected again they will be useable normally.

If a device is not answering for 5 minutes in a row it's set to unreachable. notReachable devices will give a log warning message every x scans. After some scans the adapter will try to find them again on the same mac address before.

Please delete old devices from admin.objects in case you remove them permanentely or renamed them in your router!

The adapter tries to find the device at first by it's name and then by it's mac addresses. If name changes due to a change of ip address for example and mac address stays the same then device will continue to use old name. If device changes to a new device with new mac you can use rename device in config to use an old device name instead.

Note on polling

Configuration

How-To learn codes on RM's

It is also possible to use the codes from RM-Bridge. Just create an object (state, type button) with value where you prepend "CODE" or with native entry code without any 'CODE'.

Note on new RM4/LB1 devices

Use scenes

Use states

Use send messages to adapter

The adapter understands also 'sendTo' commands.

Floureon or Beok313 Thermostats

Config additional dnew devices

Rename devices

Debug mode

Known-Issues

Changelog

2.3.0 (2024-05-21)

2.2.0 (2024-04-05)

2.1.5

2.1.4

2.1.2

Todo for later revisions

Installation

with ioBroker admin, npm install iobroker.broadlink2 or from https://github.com/frankjoke/ioBroker.broadlink2

License

The MIT License (MIT)

Copyright (c) 2024, iobroker-community-adapters iobroker-community-adapters@gmx.de Copyright (c) 2014-2020, frankjoke frankjoke@hotmail.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.