See my other guides for SSL certificates on Pi-hole v6:
Pi-hole v6 introduces changes to its web server:
- Embedded Web Server – Pi-hole no longer relies on
lighttpd
.
See my other guides for SSL certificates on Pi-hole v6:
Pi-hole v6 introduces changes to its web server:
lighttpd
.pip install micropython-rp2-rpi_pico-stubs
to install Python type checking helpers.script: | |
todo_list_move_incomplete_items: | |
fields: | |
source_list: | |
description: "Source list to copy from" | |
dest_list: | |
description: "Destination list to copy to" | |
subtext: | |
description: "The non-title text to add to the items" | |
due_today: |
alias: Ashley’s Light Fader | |
description: > | |
Fades a lamp over time. If you have any questions or comments about this | |
script, feel free to tweet Ashley Bischoff at @FriendlyAshley. Released under | |
the Apache 2.0 license. (v2.0) | |
fields: | |
light: | |
name: 💡 Light | |
description: entity_id of the lamp. | |
selector: |
blueprint: | |
name: Report offline zigbee/zwave/battery/smart plug devices | |
description: Works with Smart Plugs, ZWave, Zigbee etc (Works with ZHA & Z2M) | |
#By Tahutipai 2024-02-21 | |
#Originally Based on the work of Sybx @ https://community.home-assistant.io/t/low-battery-level-detection-notification-for-all-battery-sensors/258664 | |
#Note: This has been upgraded to report only the Device that is offline, not multiple individual sensors within one Device | |
domain: automation | |
input: | |
time: | |
name: Time to test on |
blueprint: | |
name: Bathroom Humidity Exhaust Fan | |
description: > | |
# 🚿 Bathroom Humidity Exhaust Fan | |
**Version: 2.6** | |
Step into the future of freshness - customize it your way and experience the convenience of automated humidity control! 🌿🚿 | |
/*This is sketch for internal temperature sensor ESP32 CPU. | |
* The main ideas are: | |
* to ignore 53.3 (128 before converting to Celsius); | |
* WiFi must be connected, if else you'll get 53.3 (128) only. | |
* | |
* Tested in AI Thinker ESP32 Cam module. Can be add to standard camera example in Arduino. | |
* While ESP32 Cam module was idle - the temperature was around 47*C. | |
* While camera video stream was on - the temperature was rising to around 57*C. | |
* See temperature values in serial monitor at 115200. | |
* Best regards, Anton S |
blueprint: | |
name: Update notifications | |
description: Send notifications for new updates and install or skip on action | |
homeassistant: | |
min_version: '2022.4.0' | |
domain: automation | |
input: | |
update_entities: | |
name: Update entities | |
description: >- |
Think of all the arguments you've heard as to why static typing is desirable — every single one of those arguments applies equally well to using types to represent error conditions.
An odd thing I’ve observed about the Scala community is how many of its members believe that a) a language with a sophisticated static type system is very valuable; and b) that using types for error handling is basically a waste of time. If static types are useful—and if you like Scala, presumably you think they are—then using them to represent error conditions is also useful.
Here's a little secret of functional programming: errors aren't some special thing that operate under a different set of rules to everything else. Yes, there are a set of common patterns we group under the loose heading "error handling", but fundamentally we're just dealing with more values. Values that can have types associated with them. There's absolutely no reason why the benefits of static ty