the device id is not particularly new user friendly as it is a long hex string that you need to find in HA. Not easy for a lot of people.
My thought was that the event trigger would include the friendly name of the koala player, ie the event would be esphome.[friendly_name]_alarm_ringing.
Would make it easier to set up automations.
I don’t know what to do…
I’m really into abstract automations now. Basically for me it would be like this:
- trigger: event “alarm ringing”
- action: play music and open blinds (if any) in area (by device id from event) - i have scripts ready to do that.
In your case i would need to create several automations, or at least several triggers, and update that automation every time i change something.
While in my automation i just add new satellite to area, and it works automatically.
I’m standing on the point, that if user is using automation, he is able to get data from event.
I can add device friendly name as data field in the event. Would it work?
Upon further reflection, I think you are right. Leave it as it is. As you say, the automations are more generalized.
The user can always get the friendly name from the trigger id or the data field.
Ie: state_attr(trigger.entity_id, ‘friendly_name’)
1 Like
Thank you for support!
One minor glitch you might want to fix.
If alarm is turned on for a device that has yet to have an alarm time set, the device will crash and reboot.
Huh, thanks! I might know what’s going on.
I will apologize in advance as I am pretty sure this is offtopic to the thread. However in my defense Seeed seem to have named all these things very similarly, so I am having a really hard time even identifying this device (which I bought several years ago) so I can even begin to try and get it working:
I want to say it was called the Respeaker 4 mic USB something-or-other. Anyway I came across this thread while searching around for information, so I hope you guys don’t mind my interjection too much. 
Hi @TRS-80 !
Yeah, i guess your device is simple 4-mic hat (similar to one used in famous Wyoming-satellite build on Pi-Zero-2W, but with 4 microphones).
It doesn’t have any dedicated chips for microphones audio pre-processing, so unfortunately this software won’t work for you… 
It uses XMOS XVF-3000, I doubt there is an esphome library for it
1 Like
Oh, so it does have XMOS chip!
Sorry for not paying attention, i should’ve dug deeper.
Well, in this case there should be some special firmware for the chip, to expose its functionality through i2c - that would at least make possible ESPHome communication.
P.S. checked the Seeed docs - seems to be pretty good device, but not for ESPHome definitely. Might work with Pi Wyoming satellite.
Thanks Guise for the replies.
Yes this thing connects via USB (and/or microphone plug). I think it is supposed to be more of a complete, external device rather than something you would interface with an ESP via I2C or something like that (although yes, somewhat similar hardware to that older 4-mic HAT internally, I think).
I will look more into the resources provided, in the past when I tried I seemed to have trouble finding them.
If I need to connect to an RPi as Wyoming satellite than so be it. In fact this sounds vaguely familiar, I think I tried starting down this path in the past.
At one point (years ago) I did have it working (I was pleasantly surprised how well, in fact!) with Rhasspy, connected to my Linux desktop so I am pretty sure it should be possible!
BTW, that was several years ago now. So many of us have had dreams of F/LOSSH voice assistant for such a long time now, as I am sure you are well aware. It has been very exciting to see all these resources and development efforts being poured into these things the last few years, and now starting to bear fruit finally! Keep up the great work! 
1 Like
i am using mic lite
i have 2 issues.
- i am using it with pi zero 2w, at first everything is fine, but then mic and speaker not working, it seems like pi and mic lite lost connection, i restart pi then everything works fine. But after a while it fails again.
this issue is mentioned here
ReSpeaker Lite Stability Issue · Issue #8 · respeaker/ReSpeaker_Lite · GitHub
and here
Respeaker Lite USB connections issues, stops working after couple of minutes - ReSpeaker - Seeed Studio Forum
and still no reply from you - i am on FW USB v2.0.7 and i am stuck here. i cant flash other FWs.
C:\Users\MINHTIEP PC>dfu-util -R -e -a 1 -D D:\Downloads\respeaker_lite_i2s_dfu_firmware_v1.0.7.bin
dfu-util 0.11
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util / Tickets
Warning: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device…
Device ID 2886:0019
Run-Time device DFU version 0101
Claiming USB DFU Interface…
Setting Alternate Interface #1 …
Determining device status…
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0101
Device returned transfer size 4096
Copying data from PC to DFU device
Download [=========================] 100% 270336 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
Resetting USB to switch back to Run-Time mode
C:\Users\MINHTIEP PC>dfu-util -l
dfu-util 0.11
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util / Tickets
Found DFU: [2886:0019] ver=0207, devnum=18, cfg=1, intf=3, path=“1-6”, alt=2, name=“DFU DATAPARTITION”, serial=“0000000001”
Found DFU: [2886:0019] ver=0207, devnum=18, cfg=1, intf=3, path=“1-6”, alt=1, name=“DFU UPGRADE”, serial=“0000000001”
Found DFU: [2886:0019] ver=0207, devnum=18, cfg=1, intf=3, path=“1-6”, alt=0, name=“DFU FACTORY”, serial=“0000000001”
this issue is also mentioned here, and also did not receive your explanation
