Based on the docs for State-o-matic, it looks like it gets the values from the Items linked to your z-wave device. That gives you some options.
-
Change your first state to “Reading over X for Y seconds” which will ignore those momentary spikes reported by the sensor, assuming the reading remains high for Y seconds. You might need to lower X a bit.
-
Use the following: Filter Profile (Note, when OH 4.2 is released OH core will support Marketplace transformations. Assuming MainUI get’s updated too this will be one of the first transformations I publish to the marketplace). This will filter out those spikes completely so they never reach the Item and threrefor the state machine.
-
Use a rule and a proxy Item. The rule only updates the proxy Item if the new reading is reasonable (by what ever criteria of reasonableness you want to apply).