update

hass/homeassistant/automations.yaml

@@ -532,3 +532,19 @@
     entity_id: 2a315e13dac7a4d0e3a5331216e79a5b
     domain: switch
   mode: single
+- id: '1743200211639'
+  alias: Keller Fernbedienung an
+  description: ''
+  triggers:
+  - domain: mqtt
+    device_id: 4a84d5b803f02e7e8b28609f429b2585
+    type: action
+    subtype: 'on'
+    trigger: device
+  conditions: []
+  actions:
+  - type: turn_on
+    device_id: 8124b41a35198e5fce97345753af25a2
+    entity_id: c6e2dd01af76651db7bd1720f95768f9
+    domain: switch
+  mode: single

hass/homeassistant/configuration.yaml

@@ -110,8 +110,8 @@ recorder:
 http:
   # For extra security set this to only accept connections on localhost if NGINX is on the same machine
   # Uncommenting this will mean that you can only reach Home Assistant using the proxy, not directly via IP from other client
-  ip_ban_enabled: true
-  login_attempts_threshold: 10
+  ip_ban_enabled: false
+  login_attempts_threshold: 100
   use_x_forwarded_for: true
   # You must set the trusted proxy IP address so that Home Assistant will properly accept connections
   # Set this to your NGINX machine IP, or localhost if hosted on the same machine.
@@ -122,7 +122,7 @@ auth_header:
     # Optionally set this if you're not using authentik proxy or oauth2_proxy
     # username_header: X-Forwarded-Preferred-Username
     # Optionally set this if you don't want to bypass the login prompt
-    # allow_bypass_login: false
+    #allow_bypass_login: false
     # Optionally enable debug mode to see the headers Home-Assistant gets
   debug: true
 # Optionally, if something is not working right, add this block below to get more information