@bobbyD@bcopeland
Hub is C8 running latest 2.3.5.141 platform.
I bought few ZEN51 and one ZEN54 Zooz devices just in case because they are on sale.
I cannot include any of these new toys no matter what I tried (bring close to the hub,
factory reset, etc.) For sanity check I was able to include/exclude couple older spare
devices without any problems. So this inclusion problem is not global failure.
And I already have one ZEN51 associated with C8. But I do not remember was it included
directly to C8 or came from C7 with migration.
Have you done an Exclude first? If you've done a bunch of failed Includes, you'll be creating ghosts each fail, usually.
The Exclude has to do 80% of the same work as an Include but because it doesn't allocate a node number, there's nothing in the process that can cause more work later (ie. ghost eradication.)
You should expect to see "unknown device excluded" which is 100% ideal. It tells you the hub and device are communicating. This eliminates a lot of uncertainty. If it doesn't exclude then you can conclude that the communication is wonky and focus on that alone. In other words, the experimenting close, far, high, upside down and backwards can be eliminated because once you get the "unknown device excluded" you know that communication is possible at that spot.
Well, with these two devices (ZEN51 and ZEN54) attempts to start Inclusion and/or Exclusion
did absolutely nothing. There was not any messages at all. Therefore there was not any failed
inclusions. As I mentioned and to check if this problem is global I tried to include few
different ZWave devices. Everything was OK. So, the problem is not global (I think and I hope)
but somehow related only to these two new Zooz devices. And I tried factory reset few times
on both these new toys. This did not fix a problem.
I am 99.9%+ sure something is wrong with these devices, not hub.
It could be a wrong ZWave frequency but box said "US".
I will contact Zooz about this problem and see what they will say.
I am not sure if LED should have a different blinking pattern when device is in Inclusion mode.
The LED on these two devices always slowly blinks green and this pattern is not changing
when I tried to initiate Inclusion and/or Exclusion modes by pressing a button.
BTW,
I do have a ZWave Sniffer but I am not sure what to look for.
Should I try sniffer?
Sniffer could be configured for like 11 different frequencies.
Question:
If device is not Included and I press a button on the device will it send
any messages out?
If yes, I can try a different frequencies and see if the device is sending out something.
And for the correct frequency what I should look for in the sniffer log for not included
device (if anything at all)?
OK, In order to minimize traffic on the US frequency I temporary shutdown C8.
Than I went through all 11 frequency choices but have not seen anything while
pressing the device button. Of course it was some minimal traffic on the US
frequency but I did not spot something eye catching (frankly, I have no idea
what I should look for in this case).
So, is all these new Zooz toys are sort of DOA?
it is hard to believe they are all somehow defective.
Just in case, I tried Z stick with PC Controller (for this test I did not pair Z stick with HE).
Again, I was able to include/exclude few older spare devices (sanity check) but these
new Zooz toys simply are not responding at all.
I will contact Zooz and ask then to replace all these devices (5 total).
It looks like something is not right with the firmware,
Zooz has always been helpful but they will put you through the wringer with trouble shooting. I had a Zen 32 that never went in to pairing mode. It acted like the initial firmware was never loaded. I eventually sent them a short video of me pressing the button 3 times and they sent me a new one. Send them a detailed email up front maybe with a video of the constant slow blinking.
The clicking speed must be extremely fast!
The device better to be placed on a solid surface and most likely few attempts maybe required.
The setup button is very small and recessed. This makes it very hard for fast clicking.
I contacted Zooz and suggested them to revise this extremely user unfriendly requirement
for very fast button clicking.
If you use Smart Start it does not require the button clicking.
Also says in the manual to press it QUICKLY. In the online instructions via the QR code it says "as quickly as possible". Also in both instructions it says that the LED will flash. So if the LED does not flash after the 3x button press then you did not start inclusion mode.
First thing I was trying of course was a Smart Start. It did not work.
So, I started the inclusion process by clicking a setup button.
With whatever firmware was loaded the entire series of 3 clicks must be done
within a second or less. This is "very nice" feature taking in account very small
recessed button paired with not extremely fat but big enough finger(s).
BTW,
I tried your custom driver for ZEN54 0-10V Dimmer. It works but the delay
for the OFF command is noticeable and takes about 2-3 seconds.
I guess, this is not a big deal but I wonder why is such a delay for the OFF command.
ON command is near instant. All preliminary testing was done from the Device page.
I just tested mine, I do not have a light connected but I can hear the device click the instant I press the off button. Check your ramp rate settings, if you have that set for Off, it may be slowly ramping down before going off. I just tested it and set mine to 2 seconds for the Ramp rate off and it delayed the audible click I can here when it fully shuts off. You need to be on firmware 1.30 to see all the ramp rate settings since they added new ones recently.
I have been using the Smart Start on all the Zooz devices recently, never had an issue with it. Just add the code to the mobile app, adjust security settings if desired, then power up the device.
Since I don't have an immediate use for this toy I already excluded it from C8 ZWave mesh.
I am sure, this delay is/was related to the ramp setting for the OFF command but I forgot
what it was. For the test I did not modified any parameters, everything was jus default settings.
can be eliminated because once you get the "unknown device excluded" you know that communication is possible at that spot.
