From 206d6006404426d85bfa3e852e4ac142f1235516 Mon Sep 17 00:00:00 2001
From: Fredrik <944065+fohlsso2@users.noreply.github.com>
Date: Sun, 15 Dec 2019 08:00:03 +0100
Subject: [PATCH] Update proxmoxve.markdown (#11457)

* Update proxmoxve.markdown

that are the two things I stumbled on when trying out this new integration. Didn't expect it to spew loads of ssl errors in the logfile, and when that was fixed I went looking for a sensor called proxmox which wasn't there.

* Minor changes
---
 source/_integrations/proxmoxve.markdown | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/source/_integrations/proxmoxve.markdown b/source/_integrations/proxmoxve.markdown
index 209a9099f08..5cec938598b 100644
--- a/source/_integrations/proxmoxve.markdown
+++ b/source/_integrations/proxmoxve.markdown
@@ -45,7 +45,7 @@ port:
   default: 8006
   type: integer
 verify_ssl:
-  description: Whether to do strict validation on SSL certificates.
+  description: Whether to do strict validation on SSL certificates. If you use a self signed SSL certificate you need to set this to false.
   required: false
   default: true
   type: boolean
@@ -97,4 +97,6 @@ proxmoxve:
 
 ## Binary Sensor
 
-The integration will automatically create a binary sensor for each tracked VM or container, the binary sensor will either be on if the VM's state is running or off if the VM's state is different.
+The integration will automatically create a binary sensor for each tracked virtual machone or container. The binary sensor will either be on if the VM's state is running or off if the VM's state is different.
+
+The created sensor will be called `binary_sensor.NODE_NAME_VMNAME_running`.