LZW31-SN Lag with Hue Motion

Using the Inovelli LZW31-SN Dimmer, with Hue Motion sensor. I also have (2) of the GE Enbrighten (46199) switches on this switch circuit.

I feel there is quite a bit of lag between motion sensor action to trigger the switch. I can walk around the room for a few seconds before the switch is triggered on.

Any suggestions on what to change in the configs?

Basic Rule

Motion Sensor:

Dimmer Switch variables:

Logs:
app:7292021-08-15 08:39:06.034 am infoevt: Mudroom - Motion inactive, wait for 5 minutes …

dev:6572021-08-15 08:39:05.946 am infoMudroom - Motion is inactive

dev:5892021-08-15 08:39:00.273 am debugMudroom - Dimmer: MeterReport(meterType: 1, precision: 1, scale: 2, size: 4, meterValue: [0, 0, 1, 172], rateType: 1, deltaTime: 0, previousMeterValue: [])

dev:5892021-08-15 08:38:54.327 am debugMudroom - Dimmer: BasicReport(value:99)

app:7292021-08-15 08:38:51.049 am infoact: Wait Until Mudroom - Motion motion stays inactive for 5 minutes

app:7292021-08-15 08:38:50.974 am infoact: Turn on Mudroom - Dimmer

app:7292021-08-15 08:38:50.969 am infoevt: Mudroom - Motion motion active

dev:6572021-08-15 08:38:50.917 am infoMudroom - Motion is active

From the logs, it appears the "turn on" action with the dimmer is happening almost immediately after the "motion active" event from your sensor. So, it seems unlikely that the automation is the problem, more likely something with the device. I see that the dimmer is taking a bit over 3 seconds to report that it's on to 99% after that.

Here's my guess: the default ramp rate on the Inovelli dimmers is 3 seconds. You can see if this is the issue by just using the "On" and "Off" commands on the Inovelli device page directly to see how it responds. My guess is you'll also see it be similarly slow. There are multiple possible problems and solutions here. One possibility is just that this ramp rate is too slow, and you might find that decreasing it works better. Another possibility is that a level of 1% with this dimmer rand your bulbs is actually too low to turn them on, in which case adjusting the minimum level parameter may help once you figure out what that is. It could also be a combination of these things. It could also be something else entirely, but something on the device side seems the most likely to me given your logs.