![]() ![]() Poll Interval (optional): How often in minutes to poll the sensor for updates. Name (optional) The friendly name for the entities associated with the zone. Sensor Type: The type of sensor connected to the zone - either dht or ds18b20. Commonly needed for normally open wired smoke alarm circuits. Invert the open/close state: Inverts the open/closed meaning of a binary sensor circuit. ![]() Name (optional) The friendly name for the entity associated with the zone. Binary Sensor:īinary Sensor Type: The type of sensor connected to the zone. The UI will reflect specific options available to each zone. Note some zones do not support all behaviors. Additional fields depend on how you configured the general behavior of the zone. After that, you’ll be prompted, for each zone that is not disabled, to configure details of the zones’ behavior. You need to specify Disabled, Binary Sensor, Digital Sensor, or Switchable Output for each zone. The settings UI starts by having you configure the general behavior of each zone. You can reconfigure these settings at any time and once completed the settings will be immediately applied. The settings for each panel can be accessed by selecting the entry in Settings -> Devices & Services -> Configured and then clicking on the gear icon in the upper right corner. Using Settings UI to Configure Zone Behavior If you imported settings from configuration.yaml you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you’ll need to utilize the settings UI to configure zone behavior. Once configuration is completed you’ll see a Konnected.io entry in Settings -> Devices & Services -> Configured. If you want to retain configuration.yaml and need to re-import any changes or updates you will need to delete the entry in Settings -> Devices & Services -> Configured and repeat the UI configuration for that device. ![]() Any future changes to settings should occur via the settings provided in the Home Assistant web interface. Once the import creates a Configured integration the Konnected section of the configuration.yaml is no longer used - it is recommended to remove the konnected section of configuration.yaml and after the import occurs. If you have an existing configuration.yaml completing the UI configuration will do a one time import of the settings contained in configuration.yaml. IP/Port info can be found using the Konnected mobile app. If the UI prompts you for IP/Port, you’ll need to enter it. If your panel was discovered via SSDP, you shouldn’t need any information to complete configuration - simply confirm that the information displayed is correct. Selecting one of these discovered panels will guide you through connecting and configuring the panel. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more Konnected.io entries appear in the Discovered integrations list. Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via Settings -> Devices & Services in the Home Assistant (web) frontend. Instead, use a proxy like NGINX or Caddy to serve SSL/TLS. This means that you should not use the http integration to serve SSL/TLS certificates. Konnected devices communicate with Home Assistant over your local LAN – there is no cloud component! For best performance we recommend allowing unsecured HTTP API traffic between Konnected devices and Home Assistant on your LAN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |