I have a rule that activates the siren, my understanding is the siren plays for about 30 seconds and then quits. I’d like to have another automation kicked off after the 30 seconds so I can do it again.
Can that be done and how do I do that
Thanks for the help
i did an alternating bulb flash with two lights event driven. four automations
if !a then b
if !b then !a
if a then !b
if b then a
if a turns off turn on b. if b turns off turn off a . if a turns on then turn off b. if b turns on the turn on a.
It works for a while, but the bulbs can lose commands in my experience…
so - chain them with events maybe that can work, maybe not…
That was a pretty smart idea!
I wanted to do something similar (continually change light colors during the holidays), so I just integrated my Wyze bulbs into Home Assistant. But you thought up a really cool workaround just within the Wyze App. I like it.
Do what again, exactly?
The one thing that occurs to me is adding a Wyze Plug essentially as a logical switch (acting in a Device & Service Trigger Automation). This is what I use to get doorbell button press announcements to trigger a Google Home routine. Whatever your Automation triggers, one of your “DO” items could be using a Plug’s “Turn on for” Action. You have have the Plug “Turn on for” 30 seconds. Then you have a second Automation that’s a Device & Service Trigger, and its “IF” is Plug “Turns Off”. Then that kicks off whatever you want to happen next.
Does that make sense or seem like it would work for what you’re trying to accomplish? I’m not sure I fully understand the request.
There’s another type automation chaining that could be useful; it’s a “broadcast” type instead of “sequential”. A good example would be, when a camera detects a person, turn on all the floodlights for xx minutes.
I imagine a sequential chain is just a linked list of individual rules, instead of a single rule.
Is it safe to assume you are using HMS? Or which siren are you activating?
I am asking because when you go to Home / Away settings, you can set the duration of the Siren. Mine is 4 minutes
Because the topic and initial post were originally tagged with a couple of different camera models (IIRC), I responded with the belief that @Aggrevated was using an Automation Action like “Turn on the siren” (like what I see as an available Action choice for Cam v4, for instance).
it works until one of the bulbs loses something… here’s some speculation on event chaning like i described. first - consider where the automation lives… in the case i described, the source of the event likely has a look up list associated with that event ( light off) - it likely has a list of targets to send the event notification to, and since that’s network based from a name eg ‘a’ notifies ‘b’. ‘a’ must resolve ‘b’ into a reachable network address. if that lookup fails - ‘b’ wont get notified - so my sequential blink routine eventually fails. now - if ‘a’ realized that failed, then it could retry - which is where there is probably some missing or damaged code in the Wyze software. also another thing to consider - there maybe a maximum number of devices to notify on event… probably a binary number and likely less than 255 is my guess… after all, it’s a lightbulb, not a supercomputer. in some ways - wyze did a good job with the automation in that you can address a group and if you change the name of a device in the group, then that appears to be communicated appropriately… the problem with putting in a loop in the automation logic for any of the devices lies in how and where the automations function takes place. in the OP here, the writer probably wanted a do loop to resend the command to sound the siren multiple times - and that isnt in the wyze function. maybe an external automation could do that - but where is that automation running? on alexa? does it have a ‘wait’ or a timeout? idk… I’m pretty sure that just stacking 5 ‘turn on sirens’ to a camera without waiting would probably not work… just my thoughts… The suggestion to use the home monitoring function where the siren length can be set seems to be the answer that the OP was looking for.
Lots of choices, I’ll have to work through them
To clear up one question the cameras are all Pan Cam V3
Sorry, no idea what HMS is? The siren is in the camera
I can see how this might work, the turn on period is in minutes so there may be some quiet spots but I could live with that
I’ll get back to you after I test it
I am using the Automation Action, just trying to work around the current limitations of what the Automation is set up to do
If you’re using a Plug, you can use seconds as the increment.2024-12-28T20:20:05Z Edit: I immediately see my error, but I’ll leave the rest of this intact in case it’s useful for someone. You’re correct that the “Turn on for” increment is in minutes only; “Has been on for” and “Has been off for” can be defined with Hours:Minutes:Seconds. I’ve used a Wyze Plug to power-cycle a connected appliance by having a Device & Service Trigger Automation that does this:
My Wyze account is linked to Google Home, which means that I can tell a nearby smart speaker to turn the Plug off, and then 20 seconds later it will turn on again.
HMS = Home Monitoring System