A Binary Sensor entity will be created for each attribute (below) supported by the device. The SmartThings Binary Sensor platform lets you view devices that have binary sensor-related capabilities. Support for additional platforms will be added in the future. A single device may be represented by one or more platforms. SmartThings represents devices as a set of capabilities and the SmartThings integration maps those to entity platforms in Home Assistant. The name given to the device in SmartThings.Įvent data payloads are logged at the debug level, see debugging for more information. See the button capability reference for a list of possible values (not all are supported by every device). This can be found in the configuration entry registry or in the SmartThings Developer Workspace.ĭescribes the action taken on the button. The unique id of the location the device is part of. This can be located in the Home Assistant device registry or in the SmartThings Developer Workspace. The unique id of the device in SmartThings. The device handler installed on SmartThings must be able to create those child components. For multi-button devices, the current SmartThings API will no longer pass the ButtonNumber but use a child component_id for each button. For devices with child-devices, this attribute identifies the child that raised the event. Attributeĭescribes which integration of the device triggered the event.
#SMARTTHINGS CT100 SMARTAPP UPDATE#
If the URL is not correct, update your Home Assistant configuration, restart, and try again. If using Home Assistant Cloud it will start with.
#SMARTTHINGS CT100 SMARTAPP PLUS#
Click the plus icon and type/select ‘SmartThings’. From Home Assistant, navigate to ‘Configuration’ then ‘Integrations’.Set the external URL in the Home Assistant configuration to the URL that Home Assistant is available on the internet (this must start with If you do not use Nabu Casa you must configure your network to allow TCP traffic from the internet to reach the IP address and port of the device running Home Assistant.Īfter completing the prerequisite steps above you are ready to setup the integration! See troubleshooting if you are having issues setting up the integration.Self-signed SSL certificates are not supported by the SmartThings Cloud API. Setup remote access via a domain name secured with SSL.Alternatively, you will have to configure and setup an internet accessible webhook in Home Assistant as described below: The preferred approach is to subscribe to Home Assistant Cloud (Nabu Casa) and the integration will configure and use a cloudhook automatically. This integration requires an internet accessible incoming webhook to receive push updates from SmartThings. When the token is displayed copy and save it somewhere safe (such as your keystore) as you will not be able to retrieve it again. Enter a token name (can be whatever you want), for example, ‘Home Assistant’ and select the following authorized scopes:.Log into the personal access tokens page and click ‘ Generate new token’.The PAT is used to create a Home Assistant SmartApp in your SmartThings account during setup of the integration. An internet accessible incoming webhook or active Home Assistant Cloud subscription.No brokers, bridges, or additional dependencies.Support for multiple SmartThings accounts and locations with each represented as an integration instance in Home Assistant.Entities automatically synchronized upon restart of Home Assistant when changed in SmartThings.Controlling SmartThings devices as Home Assistant entities ( see platforms for supported devices and capabilities).The features of this integration include: SmartThings is integrated into Home Assistant through the SmartThings Cloud API.
0 kommentar(er)
