I started receiving "invalid operand type" on "increased by over" and "decreased by over" triggers on a rule machine trigger. I haven't recently changed anything on the app, so not sure what's going on. I tried editing the trigger and re-saving, and that worked, so it's valid, but still receiving the error. I can delete and recreated the triggers, but I thought @bravenel might want to look at it before I do to see if it's a bug.
Are you on the latest hub platform version? This sounds like a previously discovered issue, though I can't recall if the last update was released before or after the fix was made (if not, should be the next one).
I was able to reproduce it just now in a new rule, using my EcoWitt weather station (I'm assuming not the same driver @brad is using). This rule is setup on a C-7 running 18.104.22.168. The windGust attribute in the driver is defined as a number.
I get the same behaviour using a virtual temperature sensor and triggering on the temperature attribute increasing by 1 or 1.5 (in case inclusion of a decimal place was important). Both scenarios with the temperature sensor produce the invalid operand error.
I also created a new virtual thermostat and rule to see if I could reproduce the behaviour there also same as @sburke781, and I was able. See that rule and logs below. It looks like the first event/trigger after the rule initilizes is fine, but subsequent ones don't work. I tried a number of varying triggers with decimals, numbers, variable instead of constants, different values... and they all fail after the first trigger. Of note, though, oddly 2 of the triggers are throwing 2 errors.