| use AppleScript version "2.4" -- Yosemite (10.10) or later | |
| use scripting additions | |
| (* | |
| Original script: John Gruber (https://daringfireball.net/linked/2023/12/05/an-applescript-for-safari-split-tabs-to-new-window) | |
| Much more elegant version: Leon Cowle (https://github.com/leoncowle) | |
| Even more elegant version: https://stackoverflow.com/questions/54066100/applescript-to-split-safari-tabs-into-new-window/54089865#54089865 | |
| Worth a warning: "moving" tabs with this script doesn't actually move them like | |
| drag-and-drop does. The tabs "moved" by this script will reload in the new window, |
Beelink GTR5 + Proxmox VE + Windows Guest using the Vega8 Graphics Card
I've seen several posts on Reddit and other forums that say "oh you can use a grandstream phone with UniFi Talk and it's flawless". Unfortunately, I am not a VoIP engineer so it was not intuitive to me, but I got it to work. Here's how.
For this writeup, I'm using a Grandstream DP750 DECT base with a DP720 DECT wireless handset. I really wanted a wireless phone for general use in my house, but Ubiquiti doesn't make one, so I wanted to find a way. My goal is to setup UniFi Talk for my home phone solution and share a single phone number with a UniFi wired phone that sits on my office desk. As far as I know, you have to get a UniFi phone to do the initial Talk setup (though, in my tinkering, I noticed it's using a PostgreSQL database, you could probably bypass the initial setup if you knew what you were doing). I'm also using a UDM-Pro for my gateway.
Assuming your UDM-Pro management interface is on 192.168.1.1, your base station should be assigned an IP on a VL
| 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'). |
| fan: | |
| - platform: mqtt | |
| name: "Diffuser" | |
| availability_topic: "tele/diffuser/LWT" | |
| payload_available: "Online" | |
| payload_not_available: "Offline" | |
| state_topic: "stat/diffuser/POWER1" | |
| command_topic: "cmnd/diffuser/POWER1" | |
| speed_state_topic: "stat/diffuser/FAN" | |
| payload_low_speed: low |
This information is depricated in favor of a Synology package, official support thread is here: https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559
There is an active PR to merge the package into https://synocommunity.com/.
| This will allow several functions including a persistent pop-up notification on your HA front end, a notification to whichever notify service you use (I’m using Pushbullet in this example), and, if you use another custom component (https://community.home-assistant.io/t/echo-devices-alexa-as-media-player-testers-needed/58639), it will also trigger an announcement to all of your Echo devices. | |
| This integration uses a custom sensor. | |
| you can find the code and the instructions for use at the following location: | |
| https://github.com/eracknaphobia/nws_custom_component | |
| NOTE: you will need to change the name of the file dep[ending on the version of ha you are installing it in. The instructions in that repo makes a note of that. |
