![]() alias: "Turn light off 10 minutes after door closed" We don’t need to worry about the sun state for this one, or even checking to see if the light is already on – it doesn’t matter if it’s already off: I needed to turn the light off when I was done and why do that manually every day? Since the idea is to have the light on while you get in, let’s just have the light on for a short period of time – enough time to get in, take your coat and shoes off, and move through to the rest of the house.įor this we can add a second automation that fires when the door has been closed for a period of time. ![]() I had something similar set up with SmartThings and it had a limitation. Now we can add our action, which is really simple: I went down a bit of a blind alley with the sun component at this point, focussing on the sunrise and sunset events, until I realised that there’s a “below_horizon” state for the sun component which covers the period. We only want it to run after dark – let’s say between sunrise and sunset. ![]() So far so good, but this will turn the light on at any time of day. The first step is to trigger the automation based on the state change of the sensor: I’ll assume you have a door sensor that reacts to the door opening – in my case it’s my existing SmartThings sensor that I’ve linked to HomeAssistant using the bridge. I don’t want to be reaching for my phone every time I want to turn a light off, so in this post I’ll be showing you my thought processes behind creating a simple automation.Īutomations need a bit of thought, and you’ll probably end up tweaking them as you realise the logic you need is a bit more complex than you may have first thought.įor example, let’s say we want to turn the entrance hall light on when we open the door after dark, so that we can see what we’re doing when we get in or there’s someone at the door. While it offers a great web frontend to manage everything from a single place, the true value is in automation. Svrooij node-sonos-ts for the excellent API.Now that I’ve got my devices into HomeAssistant, it’s time to get the most out of it by using automations. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. Install directly from your Node-RED's setting palette. Open a GitHub issue (preferred method) or send an email to (German/English). Prefix: nrcsp: and available keywords: universal|mysonos|config|commands|extensions|helper|discovery. Set the ENV variable DEBUG for debugging (example DEBUG=nrcsp:universal). There is a Quickstart guide in the Wiki and example flows in Node-RED Import - Examples. New commands, , (removing surroundsystem commands) Group commands automatically address the coordinator in that groupĭNS names are supported in config node (ipv4 address should still work)Įxplore the full scope in the Wiki. Group players by using their SONOS-Playernames. My Sonos, Music-Library (NAS shares), SONOS-Playlists and SONOS-Queue are supported.Ĭontrol your player: play, stop, pause - modify the SONOS queue.Ĭhange player setting such as volume, mute state, alarms, loudness, treble, bass, the LED and more. Play your track, album, playlist, station from Spotify, Napster, Amazon, Deezer and other music content provider. This package is in no way connected to or supported by Sonos Inc. Works well with Home Assistant (see example) and with its sister package node-red-contrib-sonos-events, handling SONOS events / subscriptions. A set of Node-RED nodes to control SONOS player in your local network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |