Can anyone explain this for me and how to change it. I have the fade set to 60sec
What is the actual goal? This built-in variable is set when the rule is triggered. That was the description text property for the event last time that happened (though this also looks like a pretty odd event...). It doesn't necessarily tell you anything about the current state of a device.
1 Like
The goal is to see if the fade time is working correctly. The device shows active and I sometimes have to save preferences to get it to change.
I've looked at the specs for this sensor and it said it works with zigbee 3.0. Why isn't there a Sonoff device driver in the driver list?
There are only device specific drivers for devices that do not work with the generic drivers.
What fade time? If that's some setting on the device, it's not clear how looking at any app -- such as the rule in your screenshot -- is going to help. If you need help with the rule instead, you'll need to share the rule itself and ideally logs from at least one execution that demonstrate the problem.
If you're concerned about the time a mmWave sensor takes to report motion inactive, keep in mind that they are very sensitive and sensitive to different things compared to the more common PIR sensors, so that could also be worth looking into.
There is no generic driver for presence sensor mmwave. Not that I can find. Only tuya mmwave that was coded.
I know how the rule works. And the device works fine for a couple of days then stops. I was wondering if it keep Accumulating the time, or keep add the 60 seconds each time it's activated.
It is still not clear to me how the screenshot (from a rule) in your first question relates to what it is you're asking.
Are you dealing with a Zigbee network problem, perhaps?
What is "it"?
2 Likes
The fade time
It's a screenshot from the device not a rule
OK, but then now we're back to this question. 
Is this a preference in your driver? If so, if it's a custom driver, asking the driver author how that preference is supposed to work (developers typically create a topic in the forum that is a good place for discussion of that particular app or driver) may work best. Otherwise, at least sharing information that would be helpful for others to understand, including the specific driver that you're using, would be a good start.
(For clarification, the only context in which I have seen this phrase typically used is as an alternative to "transition time," something you can specify when dimming or sometimes turning on or off a device such as a dimmer or bulb -- not related to any sensors you might be using in an automation with [or without] it.)
No, that is a screenshot from the "Local Variables" table in a Rule 5.1 rule, and:
2 Likes
Seconding what @bertabcd1234 said.
The partial screenshot in the OP is from a rule machine rule.
If you need help with a device, please start by posting screenshots of the device settings page and then please explain what the problem is.
At this point, whatever role this rule is playing in terms of how you’re attempting to troubleshoot the device just makes things here incomprehensible.
2 Likes
Here is the device page. The problem is the device works (follows the rule) only sometimes.
In the morning it works well untill it's run a few hours the it doesn't react to movement.
I can hit the " save preferences" on the device page and it will work again.
I tried adding a "setPar('parameter: 'fading time, '120' to the rule and it worked for a while.
So the underlying problem is your device becomes unresponsive?
Yes
Does it always show motion is active while in this unresponsive state?
Or sometimes when motion is inactive too?
I can't tell right now the device is working. But I believe it shows active and the light doesn't turn on.
The fade time on all of these cheapish chinese mmW sensors is frustratingly erratic -- if set at 15", sometimes it's 15", sometimes a minute, sometimes an hour (or much more).
I don't haver this particular model, but many of us have found that putting these sensors on a smart plug and having it cycle off-pause-on once a week or so does seem to help keep the sensor's parameters from wandering as much.
1 Like
