Hi, I've recently seen this error in my logs, I don't believe I used to see this, perhaps related to the upgrade to 2.3.6? [Invalid Operand Error] I have an app that sets the hub variable SumpHiPwrT1 to now in seconds. The variable is declared as type number. [Hub variable] The error seems to …

That's odd. I will look into this...

Was just looking at my logs and I am seeing the same error. It's occurring in two rules , both with a similar triger as OPs. In my case it's humidity sensor increase.

I am running .144 and problem still persists.

[image] user6909: problem still persists. Can you elaborate on this by including a screenshot of your rule, and a screenshot for the logs generated when the rule runs?

I am using latest Rule Machine app. Temperature sensors are: endpointId: 01 application: 05 manufacturer: LUMI model: lumi.weather modelType: Aqara WSDCGQ11LM Errors: app:7582023-10-17 12:32:08.660errorinvalid operand type for 20.95(number) decreased 20(number) app:7582023-10-17 12:32:08.…

I tested this with the same Aqara sensor and ended up with the error. It's weird that it works several times before getting the error. [BRDecreased] [BRTemp]

Just realized I am still getting this error as well. For me it is a Humidity increase. Just noticed mine is a bit different. As the final part in () says string? not number. [10-18-err] Rule trigger: [10-18-err2]

Error, invalid operand type

Get Help

JD0691 October 7, 2023, 5:29pm 5

@brad @bertabcd1234 The .144 update fixed my problem.

Receiving "invalid operand type" on "increased by over" and "decreased by over" triggers on a rule

Problem Rule temperature ¨Invalid Operand Type number¨