This is an openHAB binding for use with the Samsung Smartthings hub. On 3/5/19 it was submitted to openHAB for review and addition to openHAB bindings collection. Until it has been accepted and added to the openHAB platform you can install it from here.
This binding only works with the Smartthings Classic app for your phone.
- The org.openhab.binding.smartthings-2.5.0-SNAPSHOT.jar file which is located at org.openhab.binding.smartthings/target has to be copied to the addons folder in your openHAB installation. If you are using Openhabian this will be in the Samba share: openHAB/addons.
- If openHAB is currently running it will need to be restarted (On Linux: sudo /etc/init.d/openhab2 stop followed by sudo /etc/init.d/openhab2 start).
- Then follow the setup instructions in the README.md file in the org.openhab.binding.smartthing directory. Make sure to perform the Smartthings Configuration steps described in that file.
If you discover one of your devices doesn't work as expected please follow the instructions in the Troubleshooting file and raise an issue on my Github Repo BobRak
- This update requires that you redeploy the smartthings code as described in the Smartthings Installation document. The location of the smartthings code has changed. It is now here
- The RGB bulb wasn't previously working. I recently purchased a Sengled bulb just to test this. I discovered that Samrtthings defines the hue as 0-100 and openHAB defines hue in the industry standard range of 0-360. The code has been updated. The README file has been updated with an example configuration for the Sengled RGB bulb.
- Since I started development of this binding Samsung has added capabilties for many of their appliances. I have had some requests to add that to this binding. I will do that but not until I complete code changes requested bu openHAB and it has been added to the base openHAB system. One reason for this delay is because I don't own any of these appliances and will have to build simulators first. So overall this will be a considerable amount of work.
Right after the 4/5 release I had reports that Discovery was no longer working. I retested discovery in my development environment and found it working. I also discovered some files that should have been deleted were still present so I removed them.