You might be seeing that behavior, but if you change that setting to 15 then the driver sends the value 15 to the device so the issue has nothing to do with it being labeled wrong…
Change the setting to 20 and then force the device to wake up by pushing the recessed button with the paperclip.
What firmware version do you have and is this the first time you’ve ever changed that setting?
Tried that still same behavior persists. Firmware version 16.09. I believe this started after switching to edge driver but figured it out now as to why some motion based routines were not triggered all the time .
The ZSE 40 sensor i have is Version 1 which takes input in minutes only so it is behaving correctly as it is expecting value in minutes vs seconds that the driver is sending. If the driver can be modified so that user can select whether minutes or seconds to be set for “Motion Clear Time” where on selecting minutes input of 1 minute and up should be allowed.
The driver sends the value and the device interprets the value as either minutes or seconds based on the device’s firmware so there’s no way to force it to use a specific unit.
The profile for the 16.09 firmware should allow the range 1-255 so why can’t you just set yours to 1 minute?
Sorry, was only trying to help. Deleted the post, no worries.
It doesn’t take input lower than 15 and expects input b/w 15-255 only.
At the bottom of the settings screen, what do you see next to “Profile”?
Are you sure the “Firmware” tile on the device details screen shows 16.09?
That’s weird, the profile should have changed when the device was added.
If you enable the “Large View” setting it should force the profile to change and hopefully it will change to the correct profile for that firmware. You might need to reopen the mobile app after changing that setting to see the new profile.
If that works and you don’t like the large view you can disable that setting and it should still get assigned the correct profile for that firmware instead of profile 3.
Actually, the problem I was having with ZSE40 and long motion clearing time is now fixed. I changed the 15 to 1 and my device is now clearing motion after a minute. I tested this and went to 10 and 15 and sure enough, it cleared at 10 minutes and 15 minutes. I switched to philip30 driver(for example) and that setting won’t even allow me to enter anything less then 15. HOWEVER, it clears the motion at 15 minutes. I had to use Simple Device Viewer to change the setting to 1 for philip30 driver.
Something strange is going on. And NOW, when I switched back to this driver, I have no settings option. Tried to switch to other drivers for the ZSE40 and can’t get settings to come back for this device. But it seems to be working correctly.
That driver only supports firmware 17.09 and above which is why the minimum value is 15.
I have no clue why the settings aren’t displayed at all for you anymore, but if you’re seeing that with all drivers you’re trying then you’ll probably have to remove the device and join it again.
Zooz Multisensor Update - 12/16/2022
I just posted a new version with the changes below which should solve the problems users have been running into with the ZSE40.
Changed the ZSE40 default profile to the one for the 16.09 firmware to prevent the motion clear time setting of devices with that firmware from getting changed from 1 to 15 when the device is added.
Made it check to see if the correct profile is assigned every time a setting is changed which should ensure that the assigned profile always matches the device’s firmware. The driver now does this for all supported devices, but it shouldn’t cause any problems.
The ZSE40’s firmware version jumps from 32.32 to 1.10 for the 700 series model so made devices with firmware below 16.9 or above 24.15 get assigned the same profile which has the latest settings.
Zooz ZEN30 Double Switch Update - 12/16/2022
I just released a new version that includes the “switch” capability in the conditions and actions sections of Automations and that will hopefully solve the problem with the device not appearing in the new Smart Lighting app.
@krlaframboise Thank you. i can confirm that is showing up in new Smart lightning
Thank you for confirming that the change fixed the problem.
I just double checked the switchLevel capability isn’t listed for the Relay component in the Profile or Presentation so that must be a bug in the new Smart Lighting…
Thank you for the great work on this! My devices did not appear in Smart lighting after edge driver updated. I renamed one device and it magically appeared in Smart lighting. Renamed the other and it also appeared. Not sure how or why they change worked, but happy it did.
So, silly me I removed the DTH for Zooz ZEN27 so I could migrate to Edge driver only to find out there is no driver yet. Any idea on timeline? Sine Groovy won’t let me add the DTH back in am I just out of luck?
These work with the stock z-wave switch driver and the z-wave switch with child mc driver but do not have multitap functions.
@krlaframboise said hopefully this weekend the 500 series drive would be released.
This is correct however it doesn’t offer the scene controls.
I’m testing the changes for the (6) 500 series models now so assuming I don’t run into any major problems I’ll have the driver posted tonight…
That being said, it’s designed for the latest firmware and there’s only 1 profile for the switches and 1 for the dimmers so some of the settings displayed might not apply to your device.
