![]() ![]() With Keyboard Maestro you can design or record your own macro shortcuts and activate them at any time, you can navigate through running applications and open windows, and you can work with an unlimited number of clipboards - all by pressing simple keystrokes. Keyboard Maestro will take your Macintosh experience to a new level in “Ease of Use”. Use Hot Keys to connect to SSH or FTP sites.Use Hot Keys to Open Financial Accounts.How do I configure the program switcher?.How do I Insert Styled/Colored Text or Images?.If I need something else tidied up regularly I can add it to that one Make scenario and voilà. It’s very simple, 3 actions, but it’s a great way to re-use that same automation as a component. If there were any events, it calls the webhook to run the tidy up. Instead of trying to set up multiple automations involving each of the 4 calendars I use for podcasting (one for each podcast, plus another for any podcasts I guest on), I turned to Pushcut.Įvery day at midnight Pushcut runs an action which gets my calendars events for the last day filtered to just those for calendars. But then I stumbled across another scenario: I wanted to run this automatically the day after I record any podcast. I can run the Make scenario through any other Make (or IFTTT/Zapier) automation through a simple HTTP request to that webhook. The solution to this was to use a webhook as the trigger. This is an automation which I wanted to integrate into a number of other automations, but also to be able to run it in an adhoc fashion. ![]() remove records which are no longer needed), delete/archive some Google Documents, and similar. One of the many things I do with Make is “clean up” a number of tables in various Airtable bases (i.e. I back everything up, and get it off the device, as well as another copy off my network: the 3-2-1 rule. The most important part of my system is backups though. I’ve just added another private git repo for my ESPHome configs, not that they need to be private, but if I screw up and put credentials into the YAML instead of secrets then it’s less worrisome □ I could reverse engineer folder structure from the compose files, but why bother? □ Install instructions are just a numbered list, with links out to relevant instruction pages/forum posts (which I do my best to remember to throw into when I add the link to my note so it should be there in the future).ĭocker compose files as well as related config for containers are all backed up to a private git repo, there’s a folder for each physical machine I use, and a readme with a note about the folder structure I’m using and anything important I might forget (such as why X container is using host networking). Plex is installed straight onto my Plex server). For more complex devices it also contains which OS is installed, and containers/services are running on the device as well as install instructions (e.g. The device notes contain the name, IP, MAC Address, approximate description (if needed) and so on. smart home devices that all show up on the router as Espressif will get noted so if I set my network config on fire then I don’t have to trial and error my way through setting it all up again). I only document ethernet devices and wifi devices that are “important” (e.g. The table is generated with Dataview from a subfolder of device notes. I use Obsidian to document setup/installation processes, my network, and similar.įor example, my network note has a Mermaid diagram for approximate layout (router, switches, and devices have their own shapes, lines connect ethernet devices, wifi devices aren’t on the diagram), and a table with names, MAC addresses and DHCP assigned IPs of devices as well as wifi vs ethernet. As I took a little bit of time to write up my response and include some links I thought it would be worth sharing! There was a post on the Home Assistant subreddit today asking how people document their smart homes.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |