Difficulty controlling Zooz Zen17 Relay child device

🛎️ Get Help Devices
1

I have a Zooz Zen17 Relay (which has 2 child devices - one is unwired/unused). The child device that is wired controls a fan.

I have the fan child device as a Switch on one of my dashboards. On my phone, when I press the dashboard switch to either turn on or turn off the fan, the color of the switch changes, but the fan does not turn on or off. Let's use Turning Off as our example for now.

If the fan is truly on (motor running, making noise) and the dashboard switch shows it on with a yellow tile, if I press the button on the dashboard, the tile turns from yellow back to dark gray/black, as if it was off. But the fan remains on (motor running, making noise).

When I check the Device Details > Events, I can see a "command-off" entry at the time I pressed the switch on the dashboard. However, there is no "Switch Off" entry in the Events, nor in the Logs (next tab over).

Now, if I go to a computer and open the same dashboard (local, not cloud) I will find that the dashboard tile for the device still shows yellow/On. There I can turn the dashboard switch off, and the fan device actually turns off (no motor running, no noise) and the dashboard switch becomes dark gray/black, just like it did on my phone.

Again, when I check the Device Details > Events, I can see a "command-off" entry at the time I pressed the switch on the dashboard. However, there is no "Switch Off" entry in the Events, nor in the Logs (next tab over).

The only way for the "Switch Off" entry to show in the Events/Logs is for me to go into the Device>Commands> and manually click Refresh - then the state shows as Off and the Events/Logs tabs correctly show that the device is now off.

So I guess my issue is a bit complicated...
Firstly why is my phone unable to control the switch, even though the dashboard says I have turned it on/off?

Secondly, why is my computer able to control the switch correctly, using the same dashboard (albeit without reporting correctly in the Events/Logs)?

Thirdly, why does the device not report it's status in the Events/Logs tab until I click on the "Refresh" button within the device page?

Thanks

2
  • What model hub?
  • What platform version is the hub running 2.4.?.???
  • If you have a C8 Pro hub, on Zwave details there is a Switch to... button what does it say?
  • What driver are you using for the device (shown as type in device list or details page).

Depending on what you say to the above, this driver might fix it. [DRIVER] Zooz Relays Advanced (ZEN16, ZEN17, ZEN51, ZEN52)

3

Apologies -

C-8 Pro
2.4.2.157
Switch to ZWaveJS
Zooz Zen17 Universal Relay

4

Update your hub, the last 3 updates you are missing are related to dashboard issues.

If that does not help try my custom driver I linked to above.

Oh also, do you know what firmware your ZEN17 has? It might be listed in on the device page > Device Info tab (my driver for sure saves it there), if not you can check the actual device label which tells you at least the base firmware rev for your hardware.

5

Ok will do and report back to you.

It says Firmware 2.0 if that helps.

6

Ok so now if I go to the dashboard on my PC, click to turn off the fan, the switch turns dark gray, but the fan continues to run. So I have to press the green check mark at the top right of the dashboard to do a kind of "refresh", then the switch appears on/yellow again. Clicking it this time will turn off the fan instantly and the switch will turn dark gray again. The device info tab will also correctly report it as being off.

Is there any way to get it so I don't have to do the process twice, using the green check mark refresh button?

Thank you!

7

What have you changed? Just updating? Or did you try the other driver?

You will need to turn on debug logging on the parent device, then reproduce again. Show a screenshot of the logs and the events (from device page).

8

Thank you for the suggestions. I've done more testing and found that this is essentially happening with all of my devices. At least any of the switches (lights, relays, outlets).

Dashboard> press tile and one of three things happens:

  1. tile acts like it has been pressed, lights up accordingly, but device never turns on. Hubitat logs show that a command was received, but nothing was actuated for some reason.
    OR 2) tile shows no change, but device turns on/off immediately, but tile never changes color.
    OR 3) tile shows no change, device turns on/off after 30 seconds to 1 minute delay or so, and tile never changes color, unless the dashboard is refreshed.
    Sometimes this refresh will "wake" the dashboard, and subsequent commands are immediate and work fine, and sometimes the devices will only switch on/off if the dashboard is refreshed, then the command seems to make it through to the device.
    Checking the logs shows the commands are received by the hub at the time I press the tile... but nothing happens - at least sometimes not immediately.
9

Then it’s not a dashboard issue.
Are all the impacted devices zwave? Sounds like a zwave mesh issue if so.

1 Like
10

I've tried repairing my mesh a few times, but it doesn't make any difference. Unless there are other tips I should try? I don't have any ghost devices.

It's just weird that sometimes they dashboard will work, sometimes it will show the device as being on even when the Hub device details show it as off, or vice versa. Like the dashboard is not properly communicating with the hub. Sometimes it will control the device as I want it to, but only after using the green check mark or refreshing the page and trying again...

11

The dashboard reads the attributes directly from the device page. The only way it could be out of sync is if the page stops refreshing.

You need to test the devices from the device page itself. This will determine if it’s a device issue or not. If the devices work fine then you can move on to troubleshooting the dashboard.

See this post ‼ READ FIRST - Before Posting in Get Help for info and tips on zwave problems. Provide all the info requested there if you need help with the zwave mesh.

1 Like
12

Ok so for instance, I press Dashboard tile to turn ON fan. The tile still shows it as OFF. The fan actually turns ON. I go to the Device page, and it says Current State>Switch is OFF. I check the Events part tab of the device page, and it clearly shows a "Command called: on()"

Date/Time:
Name: command-on
Description: Command called: on()
State change: false
Physical: false
Digital: false
Value:
Unit:
Source: DEVICE
Type: command
Device id: 13
Device name:
Produced by: Fans
Triggered apps:

If I control the device from the device page itself, each "Command called:" is accompanied by it's respective Switch>on or off entry in the Event table and the fan itself turns on or off appropriately.

13

The device did not respond back to the hub that it turned off. That is when the state would change. The dashboard is working as designed.

Both the dashboard and the device page run the exact same command. The hub does not care where the on command of run from. Any differences like this are coincidental.

14

Ok thank you for your continued support, I can see that I likely have multiple simultaneous issues.

  1. Devices receiving and enacting On/Off commands, but not responding back to the hub appropriately that they have turned On/Off.
  2. ZWave Latency?
  3. But this one stumps me the most - why when I press to turn a device On or Off on my Dashboard tile, nothing happens? If I go in to the Device page itself to turn it On/Off, it functions as expected. Only then after manually using the Device page, am I able to control the device from it's Dashboard tile.
15

What does nothing happens mean exactly?
The device doesn't respond I assume? But Is there an event listed showing the dashboard called the appropriate command?

All the dashboard does when you use it is run the command. It is the EXACT SAME as clicking the command on the device page with one extra layer on top. The only way it could be an issue with the dashboard itself is if the command is not even being run.

If the command was called but the device did not react at all, then again, this points to zwave mesh / latency issues.

1 Like
16

Ok so if I understand, the "command* is being issued to the device, but it is not receiving a reply. So the "command" entry in the log is from the Hubitat itself, and there simply never returns a reply from the device?

I'm not sure what I can do to deal with the ZWave problems short of removing every device and hard resetting my Hubitat. I've tried the ZWave repair function but it has made no difference. I've tried putting a device right next to the Hubitat and it still gets ~30sec to 1 minute latency in response.

But what I am still unclear on is why, for instance with a door lock, is the Device page able to see instantly when I physically lock/unlock the lock, but when I send a lock/unlock command, it is delayed by 30s-1min sometimes even 2 minutes.

And separately, why do I need to refresh the Dashboard web page to get updated status tiles? For instance if I physically turn on a light, and check the Dashboard any number of minutes or hours later, the tile still shows the light as off, unless I press F5 or refresh the browser somehow (the green check mark sometimes).

Thank you!

17

Check your refresh intervals for the dashboards

image
image1289×288 23.5 KB

For zwave issues see this post:

18

Thank you. My refresh intervals are set to 2 seconds. But I can wait much longer than that and nothing loads. Manually refreshing is often the only way.

For instance, if I had a tab open on one of my dashboards, and then I navigate to that tab, it goes through the first couple of "Loading XX" but stops at "Loading Devices..." until I manually refresh the browser. This happens on our phones as well as PC. Likewise, if I am on one main dashboard and try to navigate to a dashboard linked there, it will do the same... I think the order is "Loading Layout", "Loading Variables", then "Loading Devices..." and "Loading Devices..." is where it stops every time. (until I manually refresh).

19

Try this, go to Apps > Hubitat Dashboard, expand it out and open one of your problem dashboards. This opens the underlying "app" itself, not the visual dashboard.

Under the Choose devices, make sure only the devices you need on that dashboard are selected. If you just select all devices it causes that dashboard app to try and subscribe to all those devices which can break it. If only the devices being used are select that maximizes the dashboard performance.

This would only help with your dashboard issue, not the Zwave issue. You likely have two separate issues going on.