Interface > control interface > Main interface. my vlc also keeps a console log open that i can only minimize. il try to get you some relevant config tbh i kind of hacked my way through vlc, turning this on off blah blah. The tricky part is setting up VLC properly so HASS can talk to it. If you dont then hass doesnt connect thats my biggest gripe. so if you close VLC by mistake, then re-open it and then restart hass. HASS has to be restarted for it to connect to the VLC. Like a virtual audio switch.ĮDIT : oops i mis read your question about automation. Supposedly exists a windows/linux/mac pulse audio client that installs “virtual sound card” which pipes audio over network to pulse audio daemon, the system speakers are physically connected to. I also hate to lose surround sound on my main windows workstation so im researching a feature in Pulse Audio that can be like a virtual sound card, so multiple devices can use the speaker. Im planning to dig into this annoyance very soon. I was hoped getting away from windows would help but it sounds like it’s on the component side since your pi does the same. First getting windows 10 to autostart vlc is tricky, and i cant figure out a way to keep it running in the background. I am switching VLC player from my main windows workstation to headless dedicated linux or pi. I dont recall the error but i would have to restart hass for it to reconnect to VLC. I have same problem if VLC is restarted (closed and reopen, or pc reboots) HA does not automatically connect and stops working. Nice! I dont use TTS but it seem worked when i goofed around with it. Special note: the vlc_telnet component only allows content_type music "media_content_id": " "media_content_type": "music" To test it you can use the services in dev tab.Įntity: media_player.HTPCvlc # here is JSON for service call: I choose to keep them on hass in the config for media_player:Īdd sound and config then reboot, you should see a new entity under media_player. Second, the sound files can be hosted anywhere. link on the component page for how to do so. On the page it calls the platform “vlc-telnet” when in fact it should be “vlc_telnet”įirst step is to configure VLC management interface to allow telnet. ![]() There is actually a component page that shows how to use it that unfortunately failed to show up on my many google searches for home assistant vlc remote. After hours of noobishly trying to get play_media service to work with a recent version of hass i almost gave up so I started browsing the gibhub built in components for ideas why the custom one wasn’t working and then I saw it, “vlc_telnet”. I dont see anyone using the vlc_telnet platform for media player component so wanted to share for anyone else.īefore i found vlc_telnet i found THIS post with a custom component to control VLC via http. ![]() This is not the vlc component integration to play audio on the home assistant machine, but to trigger home assistant to play audio on a remote vlc player (home theater pc suuuround sound) to play siren or warning when an alarm is triggered.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |