that is correct
Sorry I was away for couple hours. I changed drivers like you suggested, but no response. Iāll try re-adding device and maybe driver too
I had to re-add device to start working again. However there is no Firmware and Association Group info
Otherwise device is responsive
Spoke too soon. Driver freezes and stop reporting all capabilities. Even CLI does not report any logs. It just state Connectedā¦
Swithcing to different Zooz driver from @philh30 brings device back to life and starts reporting to CLI.
This driver is not responding at all:
From CLI:
43 af6a9a6b-063e-440b-92ea-91289b740455 Zooz Multisensor
āāāāāāāāāāāāāāāāāā
? Select a driver. 43
connecting... connected
No logs are registred at all
I have v2 hub. Previously i had your driver working fine
Iām going to troubleshoot the ZSE11 / ZSE40 issues with users in a private PM since this doesnāt impact any of the other devicesā¦
1 Like
Will the multi-sensor driver work with an older Monoprice 4-in-1 sensor?
Iām currently using erocm123ās zooZ 4-in-1 Sensor (Advanced) DTH.
It doesnāt currently, but at some point (probably not before 10/15) Iāll be adding support for the settings that are different in the 16.9 firmware so Iāll check with Zooz to see if they also want me to add the original modelās generic fingerprint to itā¦
1 Like
I am in the same situation. Hope they can add the zen2x fingerprints to the zen7x fingerprints so we can get the same functionality. I know @krlaframboise is working hard to get everything done.
2 Likes
I think that stock z-wave driver supports 4 in 1 sensor, but without settings.
Bottom one is sensor from Monoprice yhat looks identical like Zooz 4 in 1
1 Like
My ZSE18 works fine with the new driver - but it [still] reports battery 1% and doesnāt recognize that itās on USB power ā and so triggers low battery warnings. Can Battery/USB be a manual setting? Firmware 1.03
Thanks for the great work! All my Zooz devices are fully functional on Edgeā¦ except for ZEN31 and ZEN51.
Any update on these? Thanks
This is really sad. 2,500 views and only 18 people have clicked the like button, for a developer that has created a multitude of excellent drivers, that many thousands have benefited from.
I hope we can do better
2 Likes
Could you add updated ETAs on the ZSE43, ZEN16 and ZEN17 to the main post?
Also, what are the various deadlines (Sep 30, 2022? Oct 31, 2022? Dec 31, 2022?) and what do people need to do before each date?
This post explains the dates (as they currently stand):
If youāve never installed a custom DTH for the device, you shouldnāt need to do anything.
If you are using a custom handler (from Kevin or from elsewhere), sometime in the next 2 weeks:
-
Subscribe to the driver channel via the link at the top of this page.
-
Click the links from the subscription page to enroll drivers for any Zooz devices you want to use them for. These custom drivers will give you access to the advanced features of the devices; note that many devices will likely retain basic functionality with a āstockā driver from Samsung.
Then you have two choices:
A) Wait for the ST migration beginning 9/30 and see what happens. Single-endpoint devices (e.g. switches, sensors) āshouldā translate seamlessly and, if there is a fingerprint match, will automatically select the custom driver you had installed ahead of time. If they select a stock driver instead, or you didnāt install the custom driver, or you want to switch to a different driver, you can choose a new driver from the deviceās āsettingsā button in the app.
B) You can self-migrate by excluding and re-adding the device. After excluding the device, youāll need to remove the custom DTH from your hub (if youāre using one); otherwise, the device will use that DTH again when you re-add (if you have multiple of the same device and you want to test with just one, Iām not sure if thereās a way to do that). Note that this option requires you to rebuild all associated automations; it may be helpful to create a dummy virtual device and use it to replace the device in all automations, then you can swap the device back in after itās paired and working.
If you have devices currently using a handler that creates child devices (anything labeled as āmultichannel switchā above), itās not clear how the ST migration will manage them - Iāve asked in the main thread and didnāt get a clear answer. I suspect all the child devices will disappear, the parent device may transition smoothly, and youāll be in the same position as if youād chosen option B.
Hi @krlaframboise any chance of including the Zen06 in the Zen15 driver? It looks like both my Zen06 and Zen15 are using the same DTH of yours, but I donāt see any mention of it in this thread, so I thought Iād ask. Thanks for all your great work!
As I noted, Iām not seeing drivers for several of the Zooz devices yet. So what is going to happen if those arenāt ready in the next 2 weeks?
@krlaframboise, any update on Zen15 support. Thanks.
2 Likes
ZSE43 and ZSE44 either today or tomorrow and then Iāll be working on the ZEN17 and ZEN16.
ZEN15 is next after that and I can include the ZEN06ās fingerprint.
ZEN51 and ZEN52 will be after the ZEN15 and I believe those are the only remaining drivers for devices still being sold.
The 500 series in-wall dimmers/switches might be after that.
3 Likes
Can someone check their ZSE11, ZSE18, ZSE29, or ZSE40 and let me know if the label of the Firmware tile changed back to āUntitledā?
Nevermind, ST broke the time consuming workaround that they forced all the developers to do when they broke it the first timeā¦