[Broadlink] Initial contribution

bom/openhab-addons/pom.xml

@@ -276,6 +276,11 @@
       <artifactId>org.openhab.binding.bosesoundtouch</artifactId>
       <version>${project.version}</version>
     </dependency>
+    <dependency>
+      <groupId>org.openhab.addons.bundles</groupId>
+      <artifactId>org.openhab.binding.broadlink</artifactId>
+      <version>${project.version}</version>
+    </dependency>
     <dependency>
       <groupId>org.openhab.addons.bundles</groupId>
       <artifactId>org.openhab.binding.broadlinkthermostat</artifactId>

bundles/org.openhab.binding.broadlink/NOTICE

@@ -0,0 +1,13 @@
+This content is produced and maintained by the openHAB project.
+
+* Project home: https://www.openhab.org
+
+== Declared Project Licenses
+
+This program and the accompanying materials are made available under the terms
+of the Eclipse Public License 2.0 which is available at
+https://www.eclipse.org/legal/epl-2.0/.
+
+== Source Code
+
+https://github.com/openhab/openhab-addons

bundles/org.openhab.binding.broadlink/README.md

@@ -0,0 +1,189 @@
+# Broadlink Binding
+
+This binding supports a range of home networking devices made by (and occasionally OEM licensed from) [Broadlink](https://www.ibroadlink.com/).
+
+## Supported Things
+
+| Thing ID   | Description                                                                   |
+|------------|-------------------------------------------------------------------------------|
+| a1         | Broadlink A1 multi sensor                                                     |
+| mp1        | Broadlink MP1 WiFi Smart Power Strip (4 sockets)                              |
+| mp1-1k3s2u | Broadlink MP1 1K3S2U WiFi Smart Power Strip (3 sockets, 2 USB)                |
+| mp2        | Broadlink MP2 WiFi Smart Power Strip (3 sockets, 3 USB)                       |
+| sp1        | Broadlink SP1 WiFi Smart Socket                                               |
+| sp2        | Broadlink SP2 WiFi Smart Socket with night light                              |
+| sp2s       | OEM SP2 Mini WiFi Smart Socket with night light                               |
+| sp3        | Broadlink SP3/Mini WiFi Smart Socket with night light                         |
+| sp3s       | Broadlink SP3s WiFi Smart Socket with Power Meter                             |
+| rm-pro     | Broadline RM Pro WiFi IR/RF Transmitter with temperature sensor               |
+| rm3        | Broadlink RM3/Mini WiFi IR Transmitter                                        |
+| rm3q       | Broadlink RM3 WiFi IR Transmitter with Firmware v44057                        |
+| rm4pro     | Broadlink RM4 Pro WiFi RF/IR Transmitter with temperature and humidity sensors|
+| rm4mini    | Broadlink RM4 mini WiFi IR Transmitter                                        |
+
+## Discovery
+
+Devices in the above list that are set up and working in the Broadlink mobile app should be discoverable by initiating a discovery from the openHAB UI.
+
+> The `Lock Device` setting must be switched off for your device via the Broadlink app to be discoverable in openHAB.
+
+## Thing Configuration
+
+| Name                | Type    | Default       | description                                                                       |
+|---------------------|---------|---------------|-----------------------------------------------------------------------------------|
+| ipAddress           | String  |               | Sets the IP address of the Broadlink device                                       |
+| staticIp            | Boolean | true          | Enabled if your broadlink device has a Static IP set                              |
+| port                | Integer | 80            | The network port for the device                                                   |
+| macAddress          | String  |               | The device's MAC Address                                                          |
+| pollingInterval     | Integer | 30            | The interval in seconds for polling the status of the device                      |
+| nameOfCommandToLearn| String  | DEVICE_ON     | The name of the IR or RF command to learn when using the learn command channel    |
+| ignoreFailedUpdates | Boolean | false         | If enabled, failed status requests won't put the device `OFFLINE`                |
+
+## Channels
+
+| Channel           | Supported Devices        | Type                 | Description                                     |
+|-------------------|--------------------------|----------------------|-------------------------------------------------|
+| power-on          | MP2, all SPx             | Switch               | Power on/off for switches/strips                |
+| night-light       | SP3                      | Switch               | Night light on/off                              |
+| temperature       | A1, RM Pro, RM4          | Number:Temperature   | Temperature                                     |
+| humidity          | A1, RM4                  | Number:Dimensionless | Air humidity percentage                         |
+| noise             | A1                       | String               | Noise level: `QUIET`/`NORMAL`/`NOISY`/`EXTREME` |
+| light             | A1                       | String               | Light level: `DARK`/`DIM`/`NORMAL`/`BRIGHT`     |
+| air               | A1                       | String               | Air quality: `PERFECT`/`GOOD`/`NORMAL`/`BAD`    |
+| power-on-s1       | MP1, MP1_1k3s2u          | Switch               | Socket 1 power                                  |
+| power-on-s2       | MP1, MP1_1k3s2u          | Switch               | Socket 2 power                                  |
+| power-on-s3       | MP1, v_1k3s2u            | Switch               | Socket 3 power                                  |
+| power-on-s4       | MP1                      | Switch               | Socket 4 power                                  |
+| power-on-usb      | MP1_1k3s2u               | Switch               | USB power                                       |
+| power-consumption | MP2, SP2s,SP3s           | Number:Power         | Power consumption                               |
+| command           | all RMx                  | String               | IR Command code to transmit                     |
+| learning-control  | all RMx                  | String               | Learn mode command channel (see below)          |
+
+
+## Learning Remote Codes
+
+To obtain the command codes, you can get this binding to put your Broadlink RMx device into "learn mode" and then ask it for the code it learnt. 
+Here are the steps:
+
+0. In the openHAB web UI, navigate to your RMx Thing
+1. Set the *Name of IR/RF command to learn* property to the name of the command you want the device to learn
+2. Click on its *Channels* tab
+3. For IR find the *Remote Learning Control* channel and create an Item for it, for RF use the *Remote RF Learning Control* channel instead.(Only needed the first time)
+4. Click the item, and click the rectangular area that is marked NULL
+5. In the pop-up menu that appears, select *Learn IR command* for IR or *Learn RF command* for RF
+6. *The LED on your RM device will illuminate solidly*
+7. Point your IR/RF remote control at your RM device and keep pressing the button you'd like to learn. For RF, this can take 10-30 seconds
+8. *The LED on your RM device will extinguish once it has identified the command*
+9. If the command has been identified succesfully, the channel will have changed it name to "Learn command" or *RF command learnt*
+10. If no succes, the channel will be named "NULL". Inspect the `openhab.log` file on your openHAB server for any issues
+11. Check and save the IR/RF command by clicking the item once more and select "Check and save command". 
+12. Keep pressing the remote control with the command to check and save
+12. If succesfull, the channel will change name to the command saved
+13. If no succes, the channel be named "NULL", restart from step 3.
+
+### Modify or Delete Remote Codes
+
+The binding is also capable of modifying a previously stored code, and to delete a previously stored code.
+
+To modify a previously stored code, the procedure is the same as the one shown above, except that in step 4, the option to choose is *Modify IR command* or *Modify RF Command*
+
+*Please note that the "Learn command" will not modify a previously existent code, and the "Modify" command will not create a new command. 
+This is done to avoid accidentally overwriting commands*
+
+In order to delete a previously stored code, the procedure is as follows:
+
+0. In the openHAB web UI, navigate to your RMx Thing
+1. Set the *Name of IR/RF command to learn* property to the name of the command you want the device to learn
+2. Click on its *Channels* tab
+3. For IR find the *Remote Learning Control* channel and create an Item for it, for RF use the *Remote RF Learning Control* channel instead (Only needed the first time).
+4. Click the item, and click the rectangular area that is marked NULL
+5. In the pop-up menu that appears, select *Delete IR command* for IR or *Delete RF command* for RF
+
+*VERY IMPORTANT NOTE: Unlike the previous binding, writing the codes into the files is handled by openHAB. While it is possible to create a file externally, copy it in the proper location and use it as a remote codes database (As it is done in the case of Remote codes file migration) IT IS STRONGLY DISCOURAGED to modify the file while the binding is acive. Please make sure the binding is stopped before you modify a remote codes file manually. Also, have the following things in mind:*
+
+*-openHAB does not interpret a missing code file as empty. It will assume the file is corrupt and try to read from one of the backups, which can lead to confusion. if you want to empty your code file, create an empty file with a set of culry brackets, one per line*
+
+*-Remember if you manipulate the code file manually, remember to provide the proper location, and the proper ownership and permissions (Location is `$OPENHAB_USERDATA`, and permissions are `-rw-r--r-- 1 openhab openhab*
+
+## Full Example
+
+Items file example; `sockets.items`:
+
+```
+Switch BroadlinkSP3 "Christmas Lights" [ "Lighting" ] { channel="broadlink:sp3:34-ea-34-22-44-66:power-on" } 
+```
+
+## Migrating legacy map file
+
+Up to openHAB version 3.3, there was a previous version of this binding that was not part of the openHAB distribution. 
+It stored the IR/RF commands in a different place and a different format. 
+If you want to mirgrate from those versions to this version of the binding, please read this section.
+
+The Broadlink RM family of devices can transmit IR codes. The pro models add RF codes.
+The map file contains a list of IR/RF command codes to send via the device.
+
+IR codes are store in `$OPENHAB_USERDATA/jsondb/broadlink_ir.json` and for the RM Pro series of devices the RF codes are store in `$OPENHAB_USERDATA/jsondb/broadlink_rf.json`
+
+In previous versions of this binding, the file used the [Java Properties File format](https://en.wikipedia.org/wiki/.properties) and was stored in the `<OPENHAB_CONF>/transform` folder.
+By default, the file name was `broadlink.map` for the IR codes, but could be changed using the `mapFile` setting. 
+In similar fashion, the RM pro models stored the RF codes in the `broadlinkrf.map` file. 
+
+Here is a map file example of the previous file format:
+
+```
+TV_POWER=26008c0092961039103a1039101510151014101510151039103a10391015101411141015101510141139101510141114101510151014103a10141139103911391037123a10391000060092961039103911391014111410151015101411391039103a101411141015101510141015103911141015101510141015101510391015103911391039103a1039103911000d05000000000000000000000000
+heatpump_off=2600760069380D0C0D0C0D290D0C0D290D0C0D0C0D0C0D290D290D0C0D0C0D0C0D290D290D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D290D0C0D0C0D0C0D0C0D0C0D0C0D0C0D290D0C0D0C0D0C0D0C0D290D0C0D0C0D0C0D0C0D0C0D0C0D290D0C0D290D290D290D290D290D290E0002900000
+```
+
+The above codes are power on/off for Samsung TVs and Power Off for a Fujitsu heat pump.
+To send either code, the string `TV_POWER` or `heatpump_off` must be sent to the `command` channel for the device.
+For RF, the `rfcommand` channel is used. 
+
+Storage of codes is handled by openHAB. The map files are stored in the $OPENHAB_USERDATA/jsondb directory. 
+As an advantage, the files are now backed up by openHAB, which is more practical for migrations, data robustness, etc. having the storage of the codes handled by openHAB also provides uniformity in where the files are stored.
+
+With the change of the storage mechanism, the files are also changing format, and codes are now stored in json. 
+As an example, a file with the commands shown in the previous example would look like this:
+
+```
+{
+  "TV_POWER": {
+    "value": "26008c0092961039103a1039101510151014101510151039103a10391015101411141015101510141139101510141114101510151014103a10141139103911391037123a10391000060092961039103911391014111410151015101411391039103a101411141015101510141015103911141015101510141015101510391015103911391039103a1039103911000d05000000000000000000000000"
+  },
+  "heatpump_off": {
+    "value": "2600760069380D0C0D0C0D290D0C0D290D0C0D0C0D0C0D290D290D0C0D0C0D0C0D290D290D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D0C0D290D0C0D0C0D0C0D0C0D0C0D0C0D0C0D290D0C0D0C0D0C0D0C0D290D0C0D0C0D0C0D0C0D0C0D0C0D290D0C0D290D290D290D290D290D290E0002900000"
+  }
+}
+```
+
+The code shown below is a Python script that can be used to convert from the old format to the new one:
+
+```
+import csv
+import json
+import sys
+import argparse
+
+parser=argparse.ArgumentParser(description= "Broadlink converter argument parser")
+parser.add_argument('-i','--input_filename', help='Input File Name', required=True)
+parser.add_argument('-o','--output_filename', help='Output File Name')
+args=parser.parse_args()
+
+result={}
+with open(args.input_filename,'r') as f:
+    red=csv.reader(f, delimiter='=')
+    for d in red:
+        result[d[0]] = { "class": "java.lang.String" , "value":d[1]}
+if args.output_filename:
+    with open(args.output_filename, 'w', encoding='utf-8') as f:
+        json.dump(result, f, ensure_ascii=False, indent=2)
+else:
+    print(json.dumps(result,indent=2))
+```
+
+
+## Credits
+
+- [Cato Sognen](https://community.openhab.org/u/cato_sognen)
+- [JAD](http://www.javadecompilers.com/jad) (Java Decompiler)
+- [Ricardo] (ricardol)

bundles/org.openhab.binding.broadlink/pom.xml

@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+
+  <modelVersion>4.0.0</modelVersion>
+
+  <parent>
+    <groupId>org.openhab.addons.bundles</groupId>
+    <artifactId>org.openhab.addons.reactor.bundles</artifactId>
+    <version>4.3.0-SNAPSHOT</version>
+  </parent>
+
+  <artifactId>org.openhab.binding.broadlink</artifactId>
+
+  <name>openHAB Add-ons :: Bundles :: Broadlink Binding</name>
+
+  <dependencies>
+    <dependency>
+      <groupId>junit</groupId>
+      <artifactId>junit</artifactId>
+      <version>4.13</version>
+      <scope>test</scope>
+    </dependency>
+  </dependencies>
+</project>

bundles/org.openhab.binding.broadlink/src/main/feature/feature.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<features name="org.openhab.binding.broadlink-${project.version}" xmlns="http://karaf.apache.org/xmlns/features/v1.4.0">
+	<repository>mvn:org.openhab.core.features.karaf/org.openhab.core.features.karaf.openhab-core/${ohc.version}/xml/features</repository>
+
+	<feature name="openhab-binding-broadlink" description="Broadlink Binding" version="${project.version}">
+		<feature>openhab-runtime-base</feature>
+		<bundle start-level="80">mvn:org.openhab.addons.bundles/org.openhab.binding.broadlink/${project.version}</bundle>
+	</feature>
+</features>