#Hammerspoon hit enter every x seconds generator#
#Hammerspoon hit enter every x seconds software#
#Hammerspoon hit enter every x seconds free#

It's a great chance to try programming in a space I am less familiar with. I love working on recreational programming projects during a vacation.

#Hammerspoon hit enter every x seconds generator#

The generator is available on my website here. Thanks for reading! PokГ©mon Map Generator Febru

#Hammerspoon hit enter every x seconds free#

Please feel free to drop me a line if you have any feedback on this post. These sensors are also really easy to debug - you can view them in the History section of Home Assistant. I tried keeping the lights on during severe weather (I have since removed this), and it only took one change to the 'should be' sensor for the patio lights. I like how well this addresses the edge case described above, and how easy it is to experiment with new states driving the 'should be' sensors. I also prefer it over Node-RED, although I still use Node-RED for some tasks in my home (this may be a subject of a future post). I think this is easier to understand and extend than the classic way of doing Home Assistant automations. Target_entity: switch.patio_shelly_channel_1 Source_sensor: binary_sensor.patio_lights_should_be_on This makes the patio lights automation very simple: automation: Here's the one for my patio lights: template: I define these 'should be' states with simple boolean logic in a template binary sensor.

If the patio lights should be on, then turn them on.

The patio light automation has just one rule: In my smart home, I take all this input state and derive a 'should be' state out of it. But what if we add another rule? For example: if the back camera detects a person or dog, turn the lights on for three minutes.ДЄdding additional 'what am I doing' state makes the complexity explode for state bookkeeping. You might add a 'lights on due to time' and 'lights on due to door opening' state to bookkeep when to perform actions of the automation. You could solve this by introducing more state.

Door opens at 8:59PM, and the lights turn on.

Imagine I'm letting the dogs out at 8:59PM. While these rules sound simple, they have edge cases that will bite you when the cases fight each other.

if the back door opens while the sun is below the horizon, turn the lights on for 3 minutes.

if it's after sunset but before 9:00PM, turn the lights on.

If you did an 'if-this-then-that' approach, you might have rules like:

the patio door was opened within the last 3 minutes at night (if I'm going outside, or letting the dogs out).

In this post, I'll talk about how I'm automating my home declaratively rather than using an 'if-this-then-that' approach.

#Hammerspoon hit enter every x seconds software#

My home is powered by Home Assistant, which is a great software package for running a smart home. I agree - I recommend you go play with it! Declarative Home Automation May 21, 2022 You've never seen anything like TiddlyWiki I think this site might eventually become a TiddlyWiki. I found this software a few days ago, and I've already become enamored with it. If you want something new in the view for each tiddler, tag it with $:/tags/ViewTemplate. If you want a new item in the sidebar, just tag it with $:/tags/SideBarSegment. This lets you put things into the system easily. Much of this UI comes from use of tags, which is just another field on a tiddler.

keyboard shortcuts, including the ability to make your own.

plugins, which can contain JavaScript, CSS, and tiddlers.

the state of the wiki, like open tiddlers.

the user settings (metrics, themes, behaviors).

To help you wrap your mind around this concept, here are things that are just tiddlers in TiddlyWiki:

TiddlyWiki supports key-value storage (called 'fields') on tiddlers, enabling you to make your own taxonomy and relationships. This can be done with the embedded powerful template language. For example, I added an Emoji picker and indicator to all my Tiddlers in a few minutes. This makes it very easy to add new functionality to these views. The sidebar menu, the story list of tiddlers, the editor toolbar, all of this is represented as Tiddlers. Besides a small kernel of core functionality, the rest of the system is represented as 'tiddlers' - individual notes / files. It is a tool that is built inside of itself. I can make copies of to back it up or try new things. I can sync one file to copy my entire database, viewing experience and all. This is very novel - it's the ultimate portability. It has everything in it - the editor, the viewer, a filesystem implementation, but it's all saved to one HTML file. TiddlyWiki is a self-contained HTML file. But I'd need a way to view and edit those files.

If I were using vimwiki (which I used to, heavily!), I'd store all my files on my computer (like in ~/.vimwiki, which I had symlinked to my NextCloud instance). There are two components of it that I find so intriguing. But TiddlyWiki has some special tricks up its sleeve that I think put it into a league of its own. There are lots of these 'second brain' pieces of software - Notion, Obsidian, vimwiki. It's wiki software that you run on your computer. The Recursive Power of TiddlyWiki June 2, 2022