mundmc wrote:Great Control Page and great implementation!
Group Trigger and Group Change Listener are great. It seeeems like you might benefit from Timed Devices but I’m not entirely sure you need it given your current script.
howartp wrote:
There’s also the Group Trigger plugin that may help.
Sent from my iPhone using Tapatalk Pro
SearchCz wrote:
I run a script every minute to see how long every device has been left on, and almost every device has a maximum amount of time in t is “allowed” to remain on. Near the end of that time, display a kind of “time is running out” graphic near that device’s graphic.
When time runs out, the device is switched off AND the countdown graphic is removed.
The problem is, if there is time remaining and somebody switches the device off …. that countdown graphic persists until the next t8me I run that scheduled script that checks on devices that might need to be turned off. But if. Could run that script immediately on any change of state, I would recognize that the device is now off and it no longer needs that countdown indicator.jay (support) wrote:SearchCz wrote:It looks like the only way I can specify a trigger on “any device”, is if it is based on a command being received rather than a device state changing. So the trigger I was attempting was on any command to any device. I’m seeing the Insteon command in my log file, but my triggered action doesn’t seem to be firing off.
That won't work - that trigger only fires when an Insteon device sends out a command. Changing the state of an Insteon device via Indigo won't trigger that.
What is the scenario for needing an action group to fire every time any device changes? Perhaps there's a different approach.
jay (support) wrote:SearchCz wrote:It looks like the only way I can specify a trigger on “any device”, is if it is based on a command being received rather than a device state changing. So the trigger I was attempting was on any command to any device. I’m seeing the Insteon command in my log file, but my triggered action doesn’t seem to be firing off.
That won't work - that trigger only fires when an Insteon device sends out a command. Changing the state of an Insteon device via Indigo won't trigger that.
What is the scenario for needing an action group to fire every time any device changes? Perhaps there's a different approach.
petematheson wrote:Nope, and even more annoyingly - the latest FW update to Protect (via the UDM Pro) has even broken the workaround.
It's been fixed in the next version, but that's yet to make its way to the UDM Pro version of Protect...
mundmc wrote:
Here’s some home theater pR0n; just finished my riser step lights:
mundmc wrote:This has inspired me. Here are some images from the 7” Fire Tablet in my kitchen:
mundmc wrote:This has inspired me. Here are some images from the 7” Fire Tablet in my kitchen:
durosity wrote:
Looks great! Just need to change Whiskey to Whisky.. don’t want that inferior non Scottish stuff in your automation system*
*I’m not a fan of whisky/whiskey.. but if it ain’t Scottish it’s crap [emoji23]