Tests: Linux/Mac: Windows:

This is an ioBroker adapter for multiple Broadlink switch like RM2, 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_'!).

I could not test all of the possible devices because I have only a RM2 Pro Plus and some SM2.

SP1 devices cannot be polled.

• This adapter is based on original Broadlink adapter v0.1.1 found here: https://github.com/hieblmedia/ioBroker.broadlink

• Enter prefix of network address in configuration which should be removed when generating device names
• Enter the number of seconds between polls. On each poll all SP* devices expluding SP1 are asked what the switch status is. This feature can be disabled by setting the poll delay to 0. On some RM devices with temperature readout the temperature will be updated as well.

• In Objects of ioBroker you can find "broadlink2.[n].[devicename].Learn".
• Set this object to true. (you can click on the button in object view)
• Now press some button on your remote control within 30 seconds.
• An new Object should now appear within the Object "broadlink.[n].[devicename].LearnedState" with the name ">>> Rename learned @ YYYYMMDDTHHmmSS"
• You can click on the button in object view to send the code.
• To rename the item click on the name (starting with >>>) and change the name. It should not include ,, . or ;

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_'.

• If you learn the same signal multiple times the code can be different everytime. This can not be changed.
• Sometimes it does not find devices if they do not respond to the search. Restart adapter to restart the scan.

• Requires node >=v4.2

• Renamed to ioBroker.broadlink2 on Git
• Bug fix on 1.0.1

• Added learned state renaming, just rename the name and the ID will be renamed as well.
• Added debugging with 'debug!' at beginning of IP suffix and you will see debug messages without setting Adapter to debug.

• Don't create substates for switches
• Problem with tests resolved

• Changed message to inform about found devices.
• Moved device info from custom to native to avoid blue mark in adapter object list.

• Cleaned up code
• Debug and Info messages corrected

• Small bugs for node 4.x removed
• Poll more devices and some better debug code.
• first RM2++ device integration with learning!

• Poll frequency can be set to check the switches (which are able to do so, SM2 for example) and change the state if they are changed by the user on the device.

• Changed naming convention and used type:name instead of type.name to reduce ioBroker subdivision of devices
• generate device object only if device is a remote control

• Implemented SP2 switches and they are working to set them!
• Currently ONLY SP1 && SP2 (SP3?) are working, please test!
• Disabled RM? devices, no test available, ordered one for later re-implementation