Its challenge, a puzzle, and an opportunity to learn more about battery devices and sensors in the process. It seems to work fine for the majority of people, especially on other hubs (others from Hubitat and other brands) which is interesting. It largely seems to be a problem with the C7 hub, possibly something with the 700 series Zwave radio / SDK.
This is only true if you ignore the post that I gave directly to you showing this issue was occurring 2 years ago before the C-7 was ever even thought of. I also had issues with this device on the Vera platform.
As for the "fine for the majority of the people" you might want to search the forum and see all the posts regarding the problems from this device first.
True. I have not be around that long, my first Hub is my C7 and it is less than a year old. I revisited that other thread and didn't see anywhere mentioned what hub it was on, or what firmware the devices were. Also did not see any mention of the chatty reporting causing any actual issues besides an annoyance in the logs, unless that was just not mentioned in that thread.
I saw one post where it appeared 6-8 events were being logged within the same second, so all from the same motion activation. I have not seen anything like this, at most I see two which can be expected depending on the param 8 setting. Currently I am only getting one report per event (approx every 7 seconds). So possibly the excessive reports was fixed in a firmware update. Current is 32.02.
If this were the case then this would not be on the compatibility list as zooz and the HE team regularly communicate with each other.
I believe that was added because so many people were reporting issues specifically just on the C7. Not denying people had issues on the C7, but it could be issues with just the 2 reports every 7 seconds. The issues you were having with 6-8 reports every 7 seconds have possibly been resolved.
If anyone wants to send me their "defective" ZSE40 units that are not being used I would be happy to keep trying to break my mesh. I would even pay for shipping.
1 Like
It was added because the only way these devices "somewhat" play nice with the mesh is by including them with NO security on the C-7, which is not possible on the C-7 by standard practice and only possible by using an external zwave stick (not included with C-7 purchase)
S0 devices produce 3x the amount of traffic on the mesh. This device has 4 attributes plus battery status it reports so that 15x the reporting when included as an S0 device.
The reason this didn't pose "as big" of an issue (still was when using multiple of them) on the C-5 was because the hub radio on the C-5 was default set to include all devices with NO security except locks and garage doors.
Lots of ZSE40’s out there, and lots of C7 hubs too. Compatibility would be ideal. I’m a fan of anyone giving it a shot, especially if there’s a learning opportunity in it. I certainly learned a lot by chasing this very problem.
There’s also the satisfaction of finally having a solid technical explanation of the problem between the C7 and the ZSE40. My perception is that both companies point at their Z-Wave certification, claim no-fault, and have no interest in resolving the matter. Which is fine I suppose as there are workarounds, and the sensors are a generation behind.
The sensors do perform very well on my C5, granted it’s just the 4 sensors and 2 repeaters on the mesh. They seem to be the fastest sensors in the house even with having to trigger the dimmers through hub mesh.
FWIW, I also tried adding these sensors without security using a secondary controller but that too caused mesh failures.
I would assume this is also why @jtp10181 has yet to experience much issues. The larger the mesh the more likely these devices will cause you problems. Mine was only around 50 devices and had 4 of these that continuously had problems, that went away after removing them.
FYI, If you think these are fast, you should try zigbee motion sensors.
1 Like
Exactly my experience on the C7 with about half the devices.
Need to try the Zigbee sensors. I’ve had good luck with that side of the C7. The RGBGenie controller is crazy fast compared to any Z-Wave controller in my setup.
1 Like
On a side note on the Zooz ZSE40. The overly chattiness is only one of the multitude of issues with these (imo junk) devices. Which are in no particular order.
- Overly chatty
- Unusable Illuminance reading (0-10 scale) is not useful in lighting automation
- Device will NOT report temp, humidity, or illuminance if motion is active, therefore is useless in automating a bathroom fan switch to come on when in the shower, as the motion is always active, so the device doesn't report humidity reading until several minutes of inactive.
- Battery life is sub par.
There are far better and even cheaper devices than these, best to choose them instead.
1 Like
I didn’t know about #3 that’s interesting.
No one in my house wanted them in the bathrooms because the lux sensor looks like a pinhole camera.
I have them in our bathrooms and we use them to detect humidity (on the C5 hub). Hasn’t been a problem for us… Though maybe another sensor would be better…
I just confirmed your #3 issue and sent to Zooz, will see what they say about it.
I have confirmed that the other sensors do not report changes when motion is active. Also when they do finally report it is very delayed. Going from bottom up on this log snip the last lux reading was 40 something and then I held the sensor with my finger over top of the lux sensor, you can see multiple motion active reports over a minute. I then pointed it at the wall in the dark and after about another minute it reported the 0 lux. Then I turned it around again towards me and pointed a light directly at the sensor from 3:33 - 3:37 (5 minutes), did not get any lux reports. So then I turned it at the wall again but this time pointed the light at the wall so it would pick up the light (last reading still showing 0). Once there was not any more motion it finally reported the change about 2 minutes later.
It was reported and they were informed over 2 years ago, I wouldn't hold my breath on fixing this defective device. As you will see from reading the thread below, Zooz's "remedy" is they created a new different device for you to purchase.
1 Like
The inovelli 4 in 1 is passable and they write their own drivers. Any suggestions on other brands of temp, humidity and motion sensor?
New ZSE40 driver which allows you to disable the double reports on the ZSE40 FW 32.x
This will cut the traffic every 7s in half (from 2 reports to 1). I have tested with one device going on C7 with no issues, will be testing with 3 in a couple of weeks.
1 Like
Hey Folks,
Is the ZSE40 - 700 Series problematic? I see two models, but unsure to which model has the issues even if there are still issues?
Check out this thread..
edit: to summarize I think it works for the most part but there may be some battery reporting issues and it's probably a good idea to pair with no security.
1 Like
Thanks @erktrek, yeah I think it's still not completely 100% ok and the names of the devices confuses me a little 500 vs. 500 V2 vs. 700 I join all my devices with security none to save the hassle down the road.
1 Like
It's the 500 that's problematic on the C7. It needs joined with no security. 700 series is fine (anything besides s0 is fine, but prefer to pair with no security)
2 Likes
