Skip to content

Update http.markdown #38626

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 19, 2025
Merged

Update http.markdown #38626

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions source/_integrations/http.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ server_host:
type: [list, string]
default: "0.0.0.0, ::"
server_port:
description: Let you set a port to use.
description: Allows you to specify which port Home Assistant should listen on.
required: false
type: integer
default: 8123
Expand Down Expand Up @@ -75,7 +75,7 @@ ip_ban_enabled:
type: boolean
default: true
login_attempts_threshold:
description: "Number of failed login attempt from single IP after which it will be automatically banned if `ip_ban_enabled` is `true`. When set to -1 no new automatic bans will be added."
description: "Number of failed login attempts from a single IP after which it will be automatically banned if `ip_ban_enabled` is `true`. When set to -1 no new automatic bans will be added."
required: false
type: integer
default: -1
Expand Down Expand Up @@ -129,7 +129,7 @@ The `http` platforms are not real platforms within the meaning of the terminolog

To use those kind of [sensors](#sensor) or [binary sensors](#binary-sensor) in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived.

If you want to use HTTP sensors, create a [Long-Lived Access Tokens](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token) in the Home Assistant UI in the **Security** section of your {% my profile title="**User profile**" %} page.
If you want to use an HTTP sensor, create a [Long-Lived Access Token](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token) in the Home Assistant UI in the **Security** section of your {% my profile title="**User profile**" %} page.

All [requests](https://developers.home-assistant.io/docs/api/rest#post-apistatesentity_id) need to be sent to the endpoint of the device and must be **POST**.

Expand All @@ -142,7 +142,14 @@ If you want to apply additional IP filtering, and automatically ban brute force
banned_at: "2016-11-16T19:20:03"
```

After a ban is added a Persistent Notification is populated to the Home Assistant frontend.
After a ban is added a Persistent Notification will appear in the Home Assistant frontend.

To clear an IP ban, you can either:

- Remove the specific IP entry from `ip_bans.yaml`, or
- Delete the entire `ip_bans.yaml` file. It will be recreated automatically the next time a ban occurs.

After making changes, restart Home Assistant to apply them.

## Hosting files

Expand Down