No video :(

Create a MOTION Activated Music Automation!

Подписаться 818

Просмотров 3,9 тыс.

50% 1

Let's create an automation that allows your music to follow you around the home. So no matter which room you are in, you will always have your current playlist.
Want to create your ideal smart home?
Contact Us: www.luxeia.co....
Never miss an update by following our socials!
▶ Facebook: / luxeialtd
▶ Instagram: / luxeialtd
▶ LinkedIn: / 74410440
#smarthomes #smarthouses #homeassistant #homeautomation #technology

Опубликовано:

26 авг 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 14

@luisinigo5572 6 месяцев назад

Cool automation and very well explained!

@xbox360benji 6 месяцев назад

Yeah just found you matey going back through your uploads thanks for sharing...this one will also help me figure how to set alarmo to know when I or my girlfreind is at work or home without arming..I think lol

@MarkGhali 6 месяцев назад

Great Video! Subbed and liked! great video

@calamityairlines9762 6 месяцев назад

Good job dude. Thanks for making this

@formatBCE 3 месяца назад

No need to complicate conditions adding ANO - they're AND by default. Also, won't work if you left the room for a snack, and came back in within sensor cooldown period. Music will be playing in the kitchen...

@LuxeiaLtd 3 месяца назад

That is true, I don't technically need the AND, but that's how I do it. I feel like it keeps things tidy, haha. The sensors I use have no cooldown period. They activate immediately after no motion. I haven't encountered any issues, but your mileage may vary!

@formatBCE 3 месяца назад

@@LuxeiaLtd every PIR sensor has inbound cooldown, when they don't register motion. Mostly it's 30s to 1m. Mmwave also have it, otherwise the light would be turning off on you. :)

@LuxeiaLtd 3 месяца назад

@@formatBCE I thought you were talking about the cooldown after motion was no longer detected. The inbound cooldown is too short to cause issues like that in my particular setup, but I can see how this could impact others.

@PatrickBulteel 5 месяцев назад

Nice automation. Two things though to improve your videos. 1. You need a better microphone as it's hard to hear you. 2. The resolution you're using is too high and it's hard to view the automations you're building clearly. If you either increase the size (ctrl-+) you'd have better views of the workflow you're building. Otherwise, great content! FYI - I have a github repo with multiple examples (search home-assistant-examples in github), if you have one, I'd like to point it to your repo, otherwise, I might just create the automation and paste it as yaml with a link to this video.

@LuxeiaLtd 5 месяцев назад

Thank you the suggestions. 1. A new microphone has been on the list for a while, but I keep buying new smart home gadgets instead! 2. I will take this into consideration for my next video and pull focus onto the automation builder, as there is certainly a lot of dead space. I don't have a github repo unfortunately.

@PatrickBulteel 5 месяцев назад

Also FYI - your demo isn't working. No DNS resolution.

@LuxeiaLtd 5 месяцев назад

Yeah, it hasn't worked for over a year. I need to fix the demo server or just remove the link. One of those jobs I keep forgetting about!

@VincenzoCasini 5 месяцев назад

do you know if it works with google speakers as well? I'm testing it right now with the developer tools console, just calling service: media_player.select_source target: entity_id: media_player.spotify_vince_dx data: source: Office speaker but it looks like it doesn't switch on this speaker

@LuxeiaLtd 5 месяцев назад

Unfortunately I don't have any google speakers to test this with, so I am unable to confirm this for you. One thing to check would be the source name. In the Spotify app you can choose which device you want to cast to. This list of devices should include your Google or Alexa speakers. Make sure you are setting the source using the name as it appears in this list. Hope that makes sense!