Actions in rule not executing

wentzel · December 17, 2021, 10:46pm

Hi,

I've been trying to get started with my smart home for a while now. Most things used to work, but now things are going bonkers. E.g. I have a simple rule in Rule machine turning off a bunch of lights when I press a button on a key fob. However, it just turns off some of them. In the logs it says that the action is run, and I even broke out this specific plug (it's lights that are connected to a fibaro smart plug) to a an action of its own in case there were too many lights checked in the same action.

I really have no idea where to start looking for issues, so any pointers would be greatly appreciated

bravenel · December 17, 2021, 10:52pm

You are probably overloading your mesh network with too many commands all at once. Try this app:

github.com

hubitat/HubitatPublic/blob/master/example-apps/allOff.groovy

definition(
	name: "All Off",
	namespace: "hubitat",
	author: "Bruce Ravenel",
	description: "Turn Devices Off with Recheck",
	category: "Convenience",
	iconUrl: "",
	iconX2Url: ""
)

preferences {
	page(name: "mainPage")
}

Map mainPage() {
	dynamicPage(name: "mainPage", title: "All Off", uninstall: true, install: true) {
		section {
			input "appName", "text", title: "Name this instance of All Off", submitOnChange: true
			if(appName) app.updateLabel(appName)
			input "switches", "capability.switch", title: "Switches to turn off", multiple: true

This file has been truncated. show original

wentzel · December 17, 2021, 11:16pm

Thanks for your input!

So is your suggestion to use the action in Rule machine to call this app instead of using the action to turn off switches?

Is there no stacking of commands in Rule machine/Hubitat, making sure they will each be performed? If not, is there any instructions somewhere that lists the recommended number of simultaneous commands/actions?

bravenel · December 17, 2021, 11:17pm

No, to just use this app to turn off a bunch of devices. It will reveal to you in its logs which devices are having issues being turned off. And provide you a means of mitigating those issues, such as 'metering' (slowing down the commands). You could trigger it from RM if you want, perhaps with a virtual switch, turned on/off by a rule.

mark.cockcroft · December 17, 2021, 11:21pm

I have a basic rule which shuts down everything when away, I found it easier to just group them in lots of 10-15 with 5 seconds in-between to alow the mesh to quiet down,