Franck Nijhof c464056402
Making our website faster, cleaner and prettier (#9853)
* 🔥 Removes octopress.js

* 🔥 Removes use of root_url var

* 🔥 Removes Octopress generator reference from feed

* 🔥 Removes delicious support

* 🔥 Removes support for Pinboard

* 🔥 Removes support for Disqus

* 🔥 Removes support for Google Plus

* ↩️ Migrate custom after_footer to default template

* ↩️ Migrate custom footer to default template

* ↩️ Migrate custom header to default template

* 🔥 Removes unused template files

* 🚀 Places time to read directly in post template

* 🚀 Removes unneeded capture from archive_post.html template

* 🔥 🚀 Removes unused, but heaving sorting call in component page

* 🚀 Merged javascripts into a single file

* 🔥 Removes more uses of root_url

* 🚀 Removal of unneeded captures from head

* 🔥 🚀 Removal of expensive liquid HTML compressor

* 🔥 Removes unneeded templates

* 🚀 Replaces kramdown with GitHub's CommonMark 🚀

* 💄 Adds Prism code syntax highlighting

*  Adds support for redirect in Netlify

* ↩️ 🔥 Let Netlify handle all developer doc redirects

* ✏️ Fixes typo in redirects file: Netify -> Netlify

* 🔥 Removes unused .themes folder

* 🔥 Removes unused aside.html template

* 🔥 Removes Disqus config leftover

* 🔥 Removes rouge highlighter config

* 🔥 Removes Octopress 🎉

* 💄 Adjust code block font size and adds soft wraps

* 💄 Adds styling for inline code blocks

* 💄 Improve styling of note/warning/info boxes + div support

* 🔨 Rewrites all note/warning/info boxes
2019-07-15 22:17:54 +02:00

2.8 KiB

title description logo ha_category ha_release ha_iot_class redirect_from
Zabbix Instructions on how to integrate Zabbix into Home Assistant. zabbix.png
System Monitor
Sensor
0.37 Local Polling
/components/sensor.zabbix/

The zabbix integration is the main integration to connect to a Zabbix monitoring instance via the Zabbix API.

There is currently support for the following device types within Home Assistant:

Configuration

To set the Zabbix integration up, add the following information to your configuration.yaml file:

# Example configuration.yaml entry
zabbix:
  host: IP_ADDRESS

{% configuration %} host: description: Your Zabbix server. required: true type: string path: description: Path to your Zabbix install. required: false type: string default: "/zabbix/" ssl: description: Set to true if your Zabbix installation is using SSL. required: false type: boolean default: false username: description: Your Zabbix username. required: false type: string password: description: Your Zabbix password. required: false type: string {% endconfiguration %}

Full configuration

# Example configuration.yaml entry
zabbix:
  host: ZABBIX_HOST
  path: ZABBIX_PATH
  ssl: false
  username: USERNAME
  password: PASSWORD

Sensor

The zabbix sensor platform let you monitor the current count of active triggers for your Zabbix monitoring instance.

You must have the Zabbix component configured to use those sensors.

To set it up, add the following information to your configuration.yaml file:

# Example configuration.yaml entry
sensor:
  - platform: zabbix
    triggers:
      name: Important Hosts Trigger Count
      hostids: [10051,10081,10084]
      individual: true

{% configuration %} triggers: description: Specifies that this sensor is for Zabbix 'triggers'. In the future there will be other Zabbix sensors. required: true type: string name: description: Allows you to specify the name for the Sensor, otherwise the host name, as stored in Zabbix, is used. This is useful when you are specifying a list of hostids to monitor as a single count. required: false type: string hostids: description: This is a list of Zabbix hostids that we want to filter our count on. required: false type: string individual: description: A 'true'/'false' to specify whether we should show individual sensors when a list of hostids is provided. If false, the sensor state will be the count of all triggers for the specified hosts (or all hosts within the Zabbix instance, if hostids isn't provided). required: false type: boolean {% endconfiguration %}