The default PIR timeout (time the sensor will wait when no longer seeing motion to issue a clear) for a MultiSensor 6 is supposed to be 4 minutes (240 seconds), and it is on the old Vera controllers. However, on the Ezlo Plus, this PIR time gets set to 20 seconds. Any idea why this is? It can be reset back to 240 seconds, but we shouldn’t have to do that.
Its easy enough to set this back to 240. Just go in ezlogic.mios.com /Settings/Devices/Settings(for the Aeotec 6) and in the pull down select the timeout parameter and set it to what you like.
1 Like
Hello @richK
@curiousB is correct, the sensor manual mentions this:
Give it a try and let us know your results and comments, please.
As I said: “It can be reset back to 240 seconds, but we shouldn’t have to do that.” You are not telling me anything I don’t already know.
As the manual also says, “The default PIR time is 4 minutes”. On the Vera Plus it was 4 minutes, on the Ezlo Plus for some reason it is being set to 20 seconds. My question is about why is the Ezlo Plus changing this value to 20 seconds? Having to reset it back to 4 minutes, especially when doing multiple installations is a real pain, and is a problem for us.
As I said: “It can be reset back to 240 seconds, but we shouldn’t have to do that.” You are not telling me anything I don’t already know.
I understood what you said. I was merely underscoring your disproportionate outrage to a very minor problem.
Jonathan,
Thanks for reply. We use these sensors at scale and need to rely upon their documented values. Manual changes are only acceptable for diagnosis. We have already confirmed that we can restore the default 240 seconds for parameter 3 manually.
Can you confirm whether Ezlo has done anything to generally modify this setting from its factory default. We’ve checked with Aeotec and they assert that 240 sec remains the default.
If this setting has become unreliable we will have to arrange to modify it programmatically.
Please also note that the ezlogic site does not appear to have predefined parameters for the MultiSensor 6.
Thanks in advance for your help.
Lee
Hello @Lee
Thank you for your response and details.
The Z-Wave default parameters are part of the integration process, so we’ll check with the development department if there is something wrong and will solve it as soon as possible.
We appreciate your patience and understanding.
@JonathanB Any update on this?
I just checked for you, this is the custom setup the ezlo performs on the multisensor 6:
Parameter 5 is set to 2
Parameter 3 is set to 20 ← this is the PIR timeout!
Parameter 40 is set to 1
If you want, you can probably override this in the ezlo firmware itself, but that’s even more of a hassle than the UI, as the parameters will be reset on each update. Unless you’re deploying these sensor at scale on a single gateway, than it can be worth it to change the ezlo firmware.
To me it makes no sense why Ezlo is changing the defaults with these settings, without showing it in any way to the user. There are actually 137 different zwave devices where Ezlo overrides the default device settings during the inclusion proces. A lot of them at least populate the ‘Z-Wave parameter’ list with correct descriptions, so that’s a nice bonus.
Thank you, Jouked!
While some kinds of help we can to without, yours is precious.
We do deploy these at scale. We install our own custom plugin on the controllers we deploy to make up for certain shortcomings of Ezlo vs Vera already.
Would you kindly flesh out a couple things from your not to make us more capable?
- Where did you find this info so we can do it for ourselves in future?
- What’s your meaning when you say “change the Ezlo firmware”? Are you talking about using the plugin ZWave module, for example, to query and change settings? we could do that if we could make sense of the docs! Do you of examples or better docs?
Thanks and all the best!
Lee
Hi Lee,
You can find this info in /opt/firmware/plugins/zwave/configs/device_setting.json
In here, you’ll find this bit:
"134_2562_100": {
"configurations": [
{
"number": 5,
"size": 1,
"value": 2
},
{
"number": 3,
"size": 2,
"value": 20
},
{
"number": 40,
"size": 1,
"value": 1
}
]
}
134_2562_100 refers to the zwave manufacturer and device identifier. Luckily, the zwave-js project has a rather complete database of all these identities online, so you can find the right device with relative ease:
‘change the firmware’ would indeed mean changing bits in here. I’ve not tried manually changing the device_setting.json file. As there is also a (binary?) lua file in the same directory, with references to the same device identifiers in there, it could be that a change in just this json would not suffice. However, it might just as well just work.
I would grab an up-to-date ezlo hub, change this json, include the multisensor and see what you end up with.
Otherwise, you should be able to either fix this at scale with a custom plugin or a lua script. It seems this is possible from lua, which would set the right PIR timeout on zwave node 1:
require "zwave"
node_id = 1
param_number = 3
param_size = 2
value = 240
zwave.set_configuration_value( node_id, param_number, param_size, value )
If this works, you can wrap this in a bit of code using
get_all_nodes_ids() ← get a list of all zwave nodes
get_node_info() ← returns the manufacturer and device id’s for a specific device
If you match this for the multisensor devices, you can overwrite the right settings for all multisensors from lua. This bit of code can either run in a custom plugin or a simple bit of lua code, running from a meshbot.