Request that ZooZ 4-in-1 Sensor be removed from compatibility list (warn users when they add these devices)

hate to say it but when i switched over from st to hubitat i tossed my two 4-1 along with std zwave switches.. even when it did work it chewed through a set of batteries in weeks..

1 Like

From what I've read, I'd put it in a secure lead-lined container with a large boulder on top of it.

:wink:

2 Likes

I have 2 4-in-1s on a C-7. I also have a C-5 that I have that is not currently in use. I'm not really having any problems at the moment. I was thinking about moving them from the C-7 to the C-5 and using Hub Mesh. Mostly as an experiment and as a way of learning and testing hub mess. Anybody see any problems?

1 Like

I recently bought a C7 and was going to do a full migration but after seeing this thread decided to do exactly what you are saying. I shared out my two 4-in-1s along with 2 switches that will remain with the C5 as repeaters then exported my RM rules to the C7. Two days in and running great.

1 Like

A second hub is a great way to isolate questionable devices. Hub mesh or HubConnect are both great options for linking the two. Hub Mesh is super simple to get setup and HubConnect is a little more customizable just depends on what you're going for.

1 Like

Shockingly simple. Setup Hub Mesh sharing out four devices, exported 3 rules, imported 3 rules changing devices to those I shared, disabled rules in original hub. 5 minutes max.

Yup, my only concern with it is that they just released it and it hasn't had much time to get all the kinks ironed out yet. It should be fine but I like to give stuff a while to prove its self out before giving out blanket recommendations for something.

1 Like

Was going to buy my dad a c-7 for christmas, but other than some switches i have given him in the past, he has two 4in1 and 2 schlage locks. He can just keep using the Vera i gave him years ago. :slight_smile:

1 Like

I moved both my 4-in-1 sensors to my C-5. I'm using Hub Mesh to link my C-5 and C-7. I can not say the C-7 is running better but the 4-in-1's seem to work very well in the new environment. Simple to implement.

Hello, I also own 4 of the Zooz 4-in-1 sensors and a C7 HE. I purchased these from The Smartest House about a week before this post went up and the item was flagged for incompatibility with C7.
I took suggestions here, setup a secondary controller, and included the sensors as forced insecure (using Z-Way and a rpi).
The devices appeared in HE, discovered as the correct Zooz device and loaded the correct driver. But the sensors just flood my network and donā€™t seem to respect the motion retrigger interval. Instead I get multiple copies of the same message in my HE logs every 11 seconds. At some point sensors just keep transmitting active messages even when the room is empty and still for hours. Then the inevitable Z-wave network crash.
Iā€™ve pulled batteries on the sensors for now. Iā€™m out of ideas. I like the design and array of sensors. But I am unable make these things work.

1 Like

If you read this thread, you know at this point the solution is to bind a secondary z-wave switch to hubitat and use it to pair without security then remove the stick to allow the sensor(s) to connect to the rest of the mesh. This will solve your issue

Maybe I wasnā€™t clear, but I built a secondary controller, included it to the C7 Z-wave network, and used it to include the Zooz 4-in-1 in a forced unsecured mode. Others may have had luck doing this, but I did not see any different results. The sensors continue to take down my Z-wave network despite no longer being S0 devices in Hubitat.

[EDIT: missed the first letter of the quoted text, and it just changes the entire context of what was said.]

Ahh, I got it now. Hmm... so its showing none in security and you don't have any ghosts? If thats the case, try shutting down the hub from the settings menu. Unplug the power for 5 mins (at the outlet not the usb port) Power back up and then run a z-wave repair and see if that helps.

Turning off S0 reduces the traffic of these by two thirds but if you have enough of them they can still cause problems.

I had 2 do that when added with the secondary. They also listed as having pending changes in the device properties. I was able to resolve by hitting the configure button in the device properties. I then pulled the battery and after replacing the configuration came down and resolved the issue. You may also need to move it closer to the hub to get it to take the update. You will know it worked when there is no longer any pending changes for teh device.

You may be on to something. I kept poking at this problem yesterday. The main offender has syncStatus reporting 1 pending change. Iā€™ve been trying to force the device to awaken with a single push of the tiny button. Logs show device sync when I push the button, but always 1 pending change when finished.

For testing I have this sensor located in the same room with the C7. I pulled the battery, hit configure on the device page, then replaced the battery.

With debug logging on, I can see the device synchronizing parameters. But the log still shows 1 pending change. So does the device details page.

C7 log during sensor wakeup sync

dev:4602020-12-28 01:16:18.139 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:16:18.135 pm debugNotificationReport(v1AlarmType:7, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:)

dev:4602020-12-28 01:16:18.129 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:16:18.123 pm debugBasicSet(value:255)

dev:4602020-12-28 01:16:15.510 pm infoGarage motion sensor: syncStatus is 1 Pending Change

dev:4602020-12-28 01:16:15.498 pm debugThe changes will be synced the next time the device wakes up. You can force the device to wake up immediately by using a paperclip to push the recessed button on the bottom of the device.

dev:4602020-12-28 01:16:07.469 pm debugMotion Sensitivity (Param #6) = 3

dev:4602020-12-28 01:16:07.427 pm infoGarage motion sensor: syncStatus is Syncing...

dev:4602020-12-28 01:16:07.423 pm debugConfigurationReport(configurationValue:[3], parameterNumber:6, size:1) scaledConfigurationValue: 3

dev:4602020-12-28 01:16:07.379 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:16:07.375 pm debugNotificationReport(v1AlarmType:7, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:)

dev:4602020-12-28 01:16:07.370 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:16:07.365 pm debugBasicSet(value:255)

dev:4602020-12-28 01:15:37.628 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:15:37.624 pm debugNotificationReport(v1AlarmType:7, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:)

dev:4602020-12-28 01:15:37.596 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:15:37.591 pm debugBasicSet(value:255)

dev:4602020-12-28 01:15:15.200 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:15:15.195 pm debugNotificationReport(v1AlarmType:7, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:)

dev:4602020-12-28 01:15:15.180 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:15:15.176 pm debugBasicSet(value:255)

dev:4602020-12-28 01:15:06.443 pm infoGarage motion sensor: tamper is clear

dev:4602020-12-28 01:15:06.439 pm debugNotificationReport(v1AlarmType:7, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:0, sequence:false, eventParametersLength:1, eventParameter:[3])

dev:4602020-12-28 01:15:05.309 pm debugChanging LED Indicator Mode (Param #7) to "1" (Temperature Off / Motion Off)

dev:4602020-12-28 01:15:05.304 pm debugChanging Light Change Trigger (Param #4) to "10" (10%)

dev:4602020-12-28 01:15:05.300 pm debugChanging Humidity Change Trigger (Param #3) to "10" (10%)

dev:4602020-12-28 01:15:05.296 pm debugChanging Temperature Change Trigger (Param #2) to "10" (1.0Ā°C / 1.8Ā°F)

dev:4602020-12-28 01:15:05.292 pm debugChanging Motion Sensitivity (Param #6) to "3" (3)

dev:4602020-12-28 01:15:05.254 pm debugChanging Motion Retrigger Interval (Param #5) to "60" (60 Seconds(Firmware 17.9) / 60 Minutes (Firmware 5.9 & 16.9))

dev:4602020-12-28 01:15:05.204 pm debugChanging Wake Up Interval to 43200 Seconds

dev:4602020-12-28 01:15:05.092 pm debugsyncDevice()...

dev:4602020-12-28 01:15:04.913 pm infoGarage motion sensor: temperature is 71.78Ā°F

dev:4602020-12-28 01:15:04.909 pm debugSensorMultilevelReport(precision:2, scale:1, sensorType:1, sensorValue:[28, 10], size:2, scaledSensorValue:71.78)

dev:4602020-12-28 01:14:57.072 pm warnAll the settings will be sent to the device the next time it wakes up.

dev:4602020-12-28 01:14:57.068 pm infoGarage motion sensor: syncStatus is Resync All

dev:4602020-12-28 01:14:57.054 pm warnconfigure...

dev:4602020-12-28 01:14:55.562 pm infoGarage motion sensor: tamper is detected

dev:4602020-12-28 01:14:55.558 pm debugNotificationReport(v1AlarmType:7, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:3, sequence:false, eventParametersLength:0, eventParameter:)

dev:4602020-12-28 01:14:49.250 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:14:49.247 pm debugNotificationReport(v1AlarmType:7, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:)

dev:4602020-12-28 01:14:49.218 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:14:49.214 pm debugBasicSet(value:255)

dev:4602020-12-28 01:14:38.909 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:14:38.905 pm debugNotificationReport(v1AlarmType:7, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:)

dev:4602020-12-28 01:14:38.865 pm infoGarage motion sensor: motion is active

dev:4602020-12-28 01:14:38.859 pm debugBasicSet(value:255)

dev:4602020-12-28 01:13:53.701 pm debugThe changes will be synced the next time the device wakes up. You can force the device to wake up immediately by using a paperclip to push the recessed button on the bottom of the device.

dev:4602020-12-28 01:13:49.608 pm warndescription logging is: true

dev:4602020-12-28 01:13:49.604 pm warndebug logging is: true

dev:4602020-12-28 01:13:49.600 pm infoupdated...

dev:4602020-12-28 01:12:54.446 pm debugThe changes will be synced the next time the device wakes up. You can force the device to wake up immediately by using a paperclip to push the recessed button on the bottom of the device.

dev:4602020-12-28 01:12:50.314 pm warndescription logging is: true

dev:4602020-12-28 01:12:50.310 pm warndebug logging is: true

dev:4602020-12-28 01:12:50.307 pm infoupdated...

Can you confirm z wave stick still works? Everyoneā€™s saying ā€œso far so goodā€ after couple days. I ordered aeotec stick. Iā€™m seeing this z wave stick can be used for many purposes- ota updates, adding excluding, ghost nodes etc.. And which one did you purchase?

I have 8 zooz 4 in 1 motion sensors! Replaced with a mix of fibaro and eco, I need humidity readings for some of my automations.

Even with the no security stick inclusion you will have issues with that many sensors. Probably anymore then 2 and you'll start seeing problems.

Anyone think this new one is worth a try?

Even with adding them with no security and setting reporting to the minimum 24h I was still having occasions where my Zwave switches would stop responding for several minutes. I suspected it was the 4 in 1 sensors so I swapped them out for Zigbee motion sensors and have not had the unresponsive switch problem since.

I would say these 4 in 1 sensors are just not compatible with the C7 hub. I would not recommend using them even without security set.

1 Like