Automatic reconnect

I’ve got a number of Zooz devices connected to by Z-Box Hub. Occasionally, a device will fail communication and get marked as “Disconnected”. The only remedy I’m aware of is to log in to the UI an click to reconnect. This almost always succeeds.

Questions:

  1. Is there any way to get notified when a device disconnects?
  2. Some devices are only used via scenes, and the scene seems to happily run without errors, even though the underlying device is disconnected. There should be active error notification when a scene is attempting to use a device in such a state.
  3. Can Z-Box automatically attempt to reconnect a few times before calling it dead? I find this is usually a transient problem, often related to a power glitch. Rarely is it really a problem with the device that needs more attention

Thanks

-- Chris

There is a Notification setting for ‘Unavailable’ for a couple sensors I checked…

In your case, is the device in question battery operated? In the past, I’ve seen some hubs can miss the wake-up message and sometimes it’s almost a day before the device awakens again on its own.

Although I’ve never tried it, perhaps @Sara could confirm this notificaiton would be useful in this case?

Could also turn off the mark dead device:

But I know it is possible to do a scene that runs once an hour to “Wake dead devices”
But dont remember what it is atm :smiley:
But it is on the fibaro forum somewhere :slight_smile:

But this works only for non-battery devices, right?

I think you are right here, but I havent tested it to be honest :thinking:

Also better to find the reason why they go dead sometimes.

1 Like

This is good info, I didn’t think to look at notifications per device. It will work, but does mean a lot of clicking to get me there :wink: . I have very few battery operated devices.

The problem that really led me here today was a power glitch over the weekend (well, actually 3 over the course of the day) that seemed to leave my network (wifi and zwave) struggling to recover. I have a powered Titan valve actuator that disconnected and failed to reconnect, which meant I lost visibility and control. In particular I was running a scene which opens the valve, and it appeared to work, but in reality did nothing because the underlying device was not connected.

So, you’ve helped me cover the notification. I’ll look for the Fibaro “wake dead devices” (or I may drive this from my HA setup). The last piece, which is really a feature request for @Sara , is to improve ZBox Hub to produce feedback when a scene runs and tries to interact with a device that is not functional.

1 Like

If you don’t mind accepting some help from me and my friend Ms. ChatGPT, she and I just whipped up this Lua code that will set the notification on each device for you.

Change the variables at the top to set the following:

local DRY_RUN = true
True will only show you the changes it will make in the log.
False to actually apply the change to each device.

local ADMIN_USERNAME = "admin"
Set this to the username that should receive the notification. It defaults to an interval of “once” and channel of “email + push”

1 Like

Sweet, I know Ms. ChatGPT, she’s written some Lua for me as well! I’ll take a look, thanks!

1 Like

I had a similar problem with some low voltage Zooz relays I was using for irrigation control and found by adding a ZAC 38 range extender midway between hub and relays handled the problem. I also have my hub on a Battery back-up so it rarely shuts down except in an extended power outage.

1 Like