Keep in mind that this implementation requires an api for fetching data, and assumes the following response schema:
{
"perPageOptions": [
15, 50, 100
],
"actions": [
"Delete all", "Publish All", "Unpublish All"
],| blueprint: | |
| name: Sensor Light | |
| description: > | |
| # 💡 Sensor Light | |
| **Version: 8.5** | |
| Your lighting experience, your way - take control and customize it to perfection! 💡✨ |
| # Add to your .env.example and .env files | |
| CSP_ENABLED=true | |
| CSP_REPORT_ONLY=true |
| blueprint: | |
| name: Low battery level detection & notification for all battery sensors | |
| description: Regularly test all sensors with 'battery' device-class for crossing | |
| a certain battery level threshold and if so execute an action. | |
| domain: automation | |
| input: | |
| threshold: | |
| name: Battery warning level threshold | |
| description: Battery sensors below threshold are assumed to be low-battery (as | |
| well as binary battery sensors with value 'on'). |
| blueprint: | |
| name: Wake-up light alarm with sunrise effect | |
| description: 'A wake-up light alarm with a brightness and color temperature sunrise | |
| effect. Note: Requires date_time_iso sensor in configuration, not manually executable!' | |
| domain: automation | |
| input: | |
| light_entity: | |
| name: Wake-up light entity | |
| description: The light to control. Turning it off during the sunrise will keep | |
| it off. Color temperature range is auto-detected. |
Keep in mind that this implementation requires an api for fetching data, and assumes the following response schema:
{
"perPageOptions": [
15, 50, 100
],
"actions": [
"Delete all", "Publish All", "Unpublish All"
],| <?php | |
| use PhpCsFixer\Config; | |
| use PhpCsFixer\Finder; | |
| $rules = [ | |
| 'array_indentation' => true, | |
| 'array_syntax' => ['syntax' => 'short'], | |
| 'binary_operator_spaces' => [ | |
| 'default' => 'single_space', |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"