-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Make use of the button on Respeaker 2-Mics #149
Comments
+1 to this. Button is unused, i'd like to put some load on it. |
I'm also running a wyoming satellite on a pi zero2w with a Respeaker 2-Mic hat and would like this feature to be added. |
I'd love more details on how you achieved this please? Any chance of a write up somewhere perhaps? |
I will try |
Here is a quick and dirty explanation of what I did to make the mute button work on my Wyoming-satellite.
sensor:
n.b. the name, id, and state topic can be anything you want. The state_topic must match
alias: Jarvis3 Mute
n.b. the name of the entity_id must be the entity name of the mute switch in your Wyoming protocol service for your Wyoming satellite in HA. On the Wyoming-satellite:
Edit the 2 subprocess lines to match the topic name you have chosen, change the IP address to that of your HA, and the user name and password you setup in the MQTT integration. Rename to .py n.b. you can run and test the script by navigating into the wyoming-satellite/examples folder and with the command python3 mute_button.py
sudo systemctl edit --force --full mute_button.service Paste the following and change the /home/pi to match your setup: [Unit] [Service] [Install]
basically to import the PauseSatellite from wyoming.satellite (line 16) and to flash the leds RED (lines 130-136) |
I'm running my wyoming satellite on pi zero 2w and a ReSpeaker 2-Mics, which has a physical button.
Can it be possible to assign a feature to it, or at least expose it as an button entity? For example, I would love to assign the mute switch to it - muting is something every smart speaker has, and it's very inconvenient to activate it by going into Home Assistant settings.
Maybe, LED service could even be triggered to light up with red (if it supports that color?) when the button is activated, to indicate the mute functionality was activated.
The text was updated successfully, but these errors were encountered: