Spotify, Jawbone, Spritz & Other Morning News
Smartthings App Spotify Password
Mar 06, 2014. Spotify just bought the company that powers most online radio.And has just purchased The Echo Nest. Interesting, to say the least. (Engadget). After four decades as “the next big thing,” the smart home finally arrives. If you just want Spotify, Spotify Connect will do this without worrying about Smartthings. Google Home and Alexa can then connect and play the music if you wish, or just use the spotify app. I've seen a device handler for Smarthings and Musiccast on Github, but I've not tried it.
Here’s what’s been catching our eye recently in tech, culture, and the space in between.
• Brrrr-aving it. It’s been a rather frigid week in Washington, DC. But at SmartThings HQ, the show must go on. (Instagram)
• Spotify just bought the company that powers most online radio. And has just purchased The Echo Nest. Interesting, to say the least. (Engadget)
• After four decades as “the next big thing,” the smart home finally arrives. Four reasons why the smart home is here to stay. (Forbes)
• Jawbone’s new “Up Coffee” app tells you when you’ll go down. It’s no secret that we’re big fans of Jawbone and are working on some exciting integrations moving forward (ahem, see below video that came out yesterday). Kudos to their team for unveiling this cool new iPhone app today.
Smartthings App Spotify Account
• Don’t mock speed-reading apps, like Spritz. Fine, Slate, but we’re not sure how we feel about this quite yet. (Slate)
• Meet Moov.Started by ex-Apple engineers, this “AI personal coach” may be worth keeping your eyes on.
• Internet of Things can battle climate change. How a connected home can reduce waste, save energy, and turn the tide on climate change. (USA Today)
This binding integrates the Samsung Smartthings Hub into openHAB. This is implemented as an openHAB 2 binding.
# Supported things
This binding supports most of the Smartthings devices that are defined in the Smartthings Capabilities list. If you find a device that doesn't work follow these instructions to collect the required data so it can be added in a future release.
# Discovery
Discovery allows openHAB to examine a binding and automatically find the Things available on that binding.Discovery is supported by the Smartthings binding and is run automatically on startup.
# Smartthings Configuration
Prior to running the binding the Smartthings hub must have the required openHAB software installed. Follow these instructions
The binding will not work until this part has been completed, do not skip this part of the setup.
# openHAB Configuration
This binding is an openHAB binding and uses the Bridge / Thing design with the Smartthings Hub being the Bridge and the controlled modules being the Things. The following definitions are specified in the .things file.
# Bridge Configuration
The bridge requires the IP address and port used to connect the openHAB server to the Smartthings Hub.
where:
- smartthings:smartthings:Home identifies this is a smartthings hub named Home. The first two segments must be smartthings:smartthings. You can choose any unique name for the the last segment. The last segment is used when you identify items connected to this hubthingTypeId.
- smartthingsIp is the IP address of the Smartthings Hub. Your router should be configured such that the Smartthings Hub is always assigned to this IP address.
- smartthingsPort is the port the Smartthings hub listens on. 39500 is the port assigned by Smartthings so it should be used unless you have a good reason for using another port.
Warning This binding only supports one Bridge. If you try to configure a second bridge it will be ignored.
# Thing Configuration
Each attached thing must specify the type of device and it's Smartthings device name. The format of the Thing description is:
where:
- thingTypeId corresponds to the 'Preferences Reference' in the Smartthings Capabilities document but without the capability. prefix. i.e. A dimmer switch in the Capabilities document has a Preferences reference of capability.switchLevel, therefore the <thingTypeId> is switchLevel.
- name is what you want to call this thing and is used in defining the items that use this thing.
- deviceName is the name you assigned to the device when you discovered and connected to it in the Smartthings App
- Optional: timeout is how long openHAB will wait for a response to the request before throwing a timeout exception. The default is 3 seconds.
Example
# Items
These are specified in the .items file. This section describes the specifics related to this binding. Please see the Items documentation for a full explanation of configuring items.
The most important thing is getting the channel specification correct. The general format is:
The parts (separated by ? are defined as:
- smartthings to specify this is a smartthings device
- thingTypeId specifies the type of the thing you are connecting to. This is the same as described in the last section.
- hubName identifies the name of the hub specified above. This corresponds to the third segment in the Bridge definition.
- thingName identifes the thing this is attached to and is the 'name' you specified in the Thing definition.
- channelId corresponds the the attribute in the Smartthings Capabilities list. For switch it would be 'switch'.
Example
Special note about ValvesSmarttings includes a valve which can be Open or Closed but openHAB does not include a Valve item type. Therefore, the valve is defined as a having an item type of String. And, therefore the item needs to be defined with an item type of string. It can be controlled in the sitemap by specifying the Element type of Switch and providing a mapping of: mappings=[open='Open', closed='Close']. Such as:
RGB Bulb exampleHere is a sample configuration for a RGB bulb, such as a Sengled model E11-N1EA bulb. Currently this binding does not have a RGB specific bulb therefore a Thing is required for each part of the bulb.
Example
things file
items file
sitemap file