Add discussion link
All checks were successful
Build release image / build (push) Successful in 1m26s
All checks were successful
Build release image / build (push) Successful in 1m26s
This commit is contained in:
yehor
@@ -116,4 +116,6 @@ binary_sensor:
|
||||
pin:
|
||||
number: D5
|
||||
mode: INPUT
|
||||
```
|
||||
```
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -49,4 +49,6 @@ Now we need to create a handler of the Aqara button in `automations.yaml`:
|
||||
- data:
|
||||
message: "Someone near your front door"
|
||||
service: notify.push
|
||||
```
|
||||
```
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -134,4 +134,6 @@ Now we can rely on that group’s state to check if there is nobody home. I’ve
|
||||
service: notify.push
|
||||
```
|
||||
|
||||
That is all for now. Thanks for reading.
|
||||
That is all for now. Thanks for reading.
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -208,4 +208,6 @@ Also, this automation should be able to run in parallel to make it possible to h
|
||||
```yaml
|
||||
mode: parallel
|
||||
max: 10
|
||||
```
|
||||
```
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -40,4 +40,6 @@ binary_sensor:
|
||||
friendly_name: "Bed occupancy"
|
||||
device_class: occupancy
|
||||
value_template: "{{is_state('binary_sensor.bed_occupancy_door_side', 'off') or is_state('binary_sensor.bed_occupancy_window_side', 'off')}}"
|
||||
```
|
||||
```
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -42,4 +42,6 @@ action:
|
||||
|
||||
|
||||
|
||||
Here we are checking for the `engine is off` text in incoming SMS to perform some action. For example, to set the value of some `input_boolean`.
|
||||
Here we are checking for the `engine is off` text in incoming SMS to perform some action. For example, to set the value of some `input_boolean`.
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -105,3 +105,5 @@ switch:
|
||||
```
|
||||
|
||||
That’s it for today. Thanks for reading.
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -237,4 +237,6 @@ Before placing our power supply inside the TV we need to make sure it is isolate
|
||||
|
||||
So the overall picture is looking like this:
|
||||
|
||||
|
||||
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -85,4 +85,6 @@ Compile, flash, open logs and start firing into our device with your IR remote.
|
||||
[17:34:51][D][remote.samsung:055]: Received Samsung: data=0xE0E020DF
|
||||
```
|
||||
|
||||
You can now use this data with the ESPHome [Remote Transmitter](https://esphome.io/components/remote_transmitter.html) component to build, for example, something like [this](/2021-01-13-building-wifi-ir-remote-control-for-any-tv-with-esp8266-wemos-d1-mini-and-esphome/index.md).
|
||||
You can now use this data with the ESPHome [Remote Transmitter](https://esphome.io/components/remote_transmitter.html) component to build, for example, something like [this](/2021-01-13-building-wifi-ir-remote-control-for-any-tv-with-esp8266-wemos-d1-mini-and-esphome/index.md).
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -120,4 +120,6 @@ Decreasing the volume action is the same, but with negative `target`:
|
||||
service: esphome.amplifier_set_volume
|
||||
data:
|
||||
target: -50
|
||||
```
|
||||
```
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -119,4 +119,6 @@ You'll get an email notification on the address added here when there will be ti
|
||||
|
||||
After certificate generation, we should open Settings on the same Certificates tab, find our domain service, and choose the newly generated certificate for it.
|
||||
|
||||
That's it!
|
||||
That's it!
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -43,4 +43,6 @@ In your Home Assistant go to _Settings -> Devices & services_ and click the _"Ad
|
||||
|
||||
In the configuration window that appeared you need to set your NAS's local IP address as a _Host_ and leave the _Port_ number unchanged.
|
||||
|
||||
Hit _Submit_ and you are done.
|
||||
Hit _Submit_ and you are done.
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -54,4 +54,6 @@ The authorization header should have the next format: `PVEAPIToken=<proxmox user
|
||||
|
||||
You can use `shutdown` or `reboot` as a `command`.
|
||||
|
||||
After restarting Home Assistant you will have a new service available. In our example, it would be `rest_command.spacedock_one_shutdown`. Calling it will do the trick.
|
||||
After restarting Home Assistant you will have a new service available. In our example, it would be `rest_command.spacedock_one_shutdown`. Calling it will do the trick.
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -105,4 +105,6 @@ And up it back with a system service, also enabling it:
|
||||
sudo systemctl start wg-quick@wg0 && sudo systemctl enable wg-quick@wg0
|
||||
```
|
||||
|
||||
Further interface control should be performed through `systemctl` as well like `systemctrl stop`, `systemctl restart` or `systemctl status`.
|
||||
Further interface control should be performed through `systemctl` as well like `systemctrl stop`, `systemctl restart` or `systemctl status`.
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -98,4 +98,6 @@ Cron job line to add:
|
||||
|
||||
```
|
||||
@reboot sleep 30s && /usr/sbin/etherwake -i vmbr0 <mac_address>
|
||||
```
|
||||
```
|
||||
|
||||
<BlogDiscussions/>
|
||||
@@ -184,4 +184,4 @@ Have no idea why everyone wants to write a conclusion for each post nowadays. It
|
||||
|
||||
Have a nice tinkering.
|
||||
|
||||
import BrowserWindow from '@site/src/components/BlogDiscussions';
|
||||
<BlogDiscussions/>
|
||||
Reference in New Issue
Block a user