Settle on a common prefix to ESP-specific entities

esp is often used as a bridge to other device, e.g. a lock,
an AC, a siren, power switch etc. It helps to distinguish esp chip
sensor readings from that of the target device

templates/esp32-poe.yaml

@@ -16,9 +16,9 @@ ethernet:
 text_sensor:
 - platform: ethernet_info
   ip_address:
-    name: "Device IP (Ethernet)"
+    name: "ESP chip IP (Ethernet)"
   mac_address:
-    name: "Device MAC (Ethernet)"
+    name: "ESP chip MAC (Ethernet)"
 
 logger:
 

templates/esp8266-vcc.yaml

@@ -3,5 +3,5 @@
 sensor:
 - platform: adc
   pin: VCC
-  name: "VCC Voltage"
+  name: "ESP chip VCC Voltage"
   entity_category: diagnostic

templates/nuki.yaml

@@ -15,7 +15,7 @@ packages:
 
 button:
   - platform: factory_reset
-    name: Forget the lock and restart
+    name: "Forget the lock and restart"
     disabled_by_default: true
 
 time:

templates/time.yaml

@@ -1,6 +1,6 @@
 binary_sensor:
 - platform: template
-  name: "Device clock invalid"
+  name: "ESP chip clock invalid"
   lambda: 'return !id(sntp_time).now().is_valid();'
   entity_category: diagnostic
   device_class: problem

templates/uptime.yaml

@@ -1,3 +1,3 @@
 sensor:
 - platform: uptime
-  name: "Uptime"
+  name: "ESP chip uptime"

templates/wifi.yaml

@@ -1,15 +1,15 @@
 sensor:
 - platform: wifi_signal
-  name: "WiFi signal"
+  name: "ESP chip WiFi signal"
 
 text_sensor:
 - platform: wifi_info
   mac_address:
-    name: "Device MAC"
+    name: "ESP chip MAC"
   ip_address:
-    name: "Device IP"
+    name: "ESP chip IP"
   bssid:
-    name: "Connected to BSSID"
+    name: "ESP chip connected to BSSID"
     filters:
     - to_upper
     - substitute: !secret wifi_ap_lookup