I am not sure if the following is a driver or Hub issue. Every time I run my Rule Machine App or command to play a sound on the device details screen, the Hubitat Hub logs the requested sound output twice in very quick succession. Sometimes I hear a brief break or distortion at the start of chime sound on the device.
I would think that I should only see one log message to play a sound.
The following are the Rule Machine App actions programed to run:
I am using the built in Zooz ZSE50 Siren & Chime driver with the latest firmware version 1.20.
I contacted Zooz and performed a number of actions they requested. The end result was the following comment from Zooz; "If the duplicate commands persist with the device freshly included, at default settings, and not tied to any apps or rules, that would indicate the hub or driver layer is issuing the command twice and would need to be investigated on the Hubitat side."
The Zooz team indicated the tested the ZSE50 with a Hubitat and were not able to replicate the behavior.
I have tried a soft reset, device factory reset, exclude and re-include the device, used the generic driver and no help. I have not factory re-set the Hubitat Hub because I am tring to avoid the long process of excluding and re-including all my devices.
I did find some past postings of other users having the same issue, but no resolutions. Does anyone have any ideal what is causing the problem and how to fix it?
Yes, all of my ZSE50 chimes have the same issue. As far as Legacy (ZIP) or JS for z-wave, I don't know. I checked Hub Details and Z-wave Details and did not see any information regarding ZIP or JS for z-wave. Is there an easy way to find out?
I have attached another screen capture with debug enabled. This is what was logged when playing a sound from the Device Details Commands screen.
I have also attached a couple of screen shots of the Hubitat Phone Application. I noticed that all the Chime devices show up in pink with a sad emoji. The details indicate missing attributes, but in the Hubitat Hub the everything looks fine. I tried "Configure" and "Refresh" on the Hub Device page but that did not change the status in the Phone App.
It also seems that, at least the driver level, it's not sending the command more than once.. There is no code on the hub side that will re-transmit a command. the only place that could happen is in Zipgateway (or ZWave-JS), but that is normal re-transmit when no ack is received..
Thank you for you feedback! It seems odd to me why only my Z-wave chimes would have consistent no ack issues, especially since one of them is 6 feet from the hub. Maybe it the newer devices need ZWave-JS for better compatibility and stable operation.
I found in the How To Remove Ghost Devices using hub tools or a UZB Stick - Get Help - Hubitat posting that I can enable ZWave-JS through using endpoints in my browser for my C8 hub. I changed over to ZWave-JS and now all my chime devices work as they should, only one sound message logged per request. So you were right on the mark that the problem was occurring in the Zipgateway.
UPDATE: After switching my C-8 hub to use Z-Wave JS my ZSE 50 Chime double logging issues were resolved. However, I noticed that all my other Z-wave devices are now generating three redundant log entries. If I switch back to ZipGateway, all of these devices return to normal logging and the ZSE 50 Chimes go back to double log entries.
I decided to do another test using the Z-Wave JS configuration. I tried using some Zooz community drivers (Advanced Drivers by Jeff Page) in place of the Hubitat hub drivers and voila…. the triple logging stopped on all the devices that I could find a driver for. Returning the same devices to the built-in hub drivers caused multiple logs to reappear.
Needless to say, I am back to using ZipGateway since it is the lessor offender in clogging up my log files with redundant messages.
Hopefully at some point Hubitat can find a resolution to this Z-Wave logging issue. Especially, when using Z-Wave JS with older drivers / devices.
Get Help - Hubitat
