Iris Pusbutton Webcore vs Rule machine


I have added a Hubitat Hub in my shop which has mostly Iris V1 devices. I have been using something else but its development is moving to slow so I have started to move over to Hubitat.

I wanted to try and use Rule Machine as much as possible as that runs locally as I understand it. So I have a relatively simple task of wanting to have a Iris V1 pusbutton turn on a bank of 5 switches. These 5 switches turn on several banks of lights on my shop floor.

I got it to work but it does it too quickly, at least that is what seems to be happening. I press the button and it will fly through the 5 switches but about every other push one of the switches will not get toggled. Then they are out of sync. I see no way to slow it down and I would like to check the status of the lights and if only one or two banks are on then I don’t want it to toggle I want it to turn them off. So I I decided I needed to move to Webcore.

My problem here is I have the Push button added but when I select the push button attribute I only get one trigger ‘gets’ but the only value I can assign to it is an integer. See below. I will not be able to test it until tomorrow and sorry if there is a thread somewhere about this, but I couldn’t find it if there was. Does 1 mean one push?

Should I use string variable set to ‘pushed’ and compare to that?


Do note that webCoRE on HE runs locally on HE…

  • there is a lot of mis-information on webCoRE on HE, such as webCoRE causes crashes (proven to not be true) or rule machine is faster (no data ever presented to prove this claim in last 6+ months, and webCoRE is the only app that provides tracing information)

Hubitat buttons work slightly differently than smart things.

the attributes are pushed, held, etc, and the value is which button was pushed.

You can see the attribute values your device provides by looking at the device handler ‘events’ for the device in question as you push or hold different buttons.

See specifically the section

  • Buttons operate differently in HE than ST, so when importing pistons from ST, these portions will need to be adjusted to the HE button devices and attributes.
    • Hubitat’s button implementation
      • This is a simple edit to use holdablebutton, pushablebutton as the attribute vs. button after import.
    • Some users have found they needed to recreate the if statement for a button if ST import brought in a device subIndex.


Okay so that is the button that is pushed so since these are a one button device I should be good.


This was about to drive me crazy. I spent way to long on getting this to work. I was just about to report there was a problem with Webcore or Hubitat. My piston would work whenever the lights were all on or off, but if I manually turned one or more banks off, the lights would toggle state. I had gone through I don’t how many logs and had come to the conclusion that Hubitat was saying it wasn’t changing the light but it was.

It finally dawned on me that I had forgotten my quick try with Rule machine. Webcore was turning things off and on but then my rule machine action would trigger and screw things up.