If inovelli driver is used (wich i am using.) . I dont need a handler?
I opened up a brand new sensor and updated the firmware to 2.5, but I am so far unable to put it in listening/repeater mode.
A few observations:
- Device reports that it is not a listening node regardless of whether I include it with 1x or 5x button presses
- Pressing the button seems to manually wake the device AND put it in exclusion mode, regardless of how many times you press the button (I tried 1x, 2x, 3x, 4x and 5x). I tried pressing the button 5x really fast as well, but it didnt seem to make a difference.
- Perhaps it is not properly seeing the number of button presses?
(device reports the same capabilities when included with 1x or 5x button presses)
hey guys, soo i need some helpā¦ currently on hubitatā¦ ive got a inovelli switch in the bathroom along with a 4 in 1 sensor, I have a motion rule set up for the witch to turn on on motion then turn of a minute later after no motion as been detected. I have turned off the 700ms delay and all. there is still a couple seconds delay before the lights come onā¦ is there some sort of way to speed this up a bit?.. i looked into associating the sensor with the switch but canāt seem to figure it out. any help or small tutorial would be apreciated
While I am not able to help you with the automation or association portion (I am not familiar with Hubitat), I just wanted to let you know that the 700ms delay setting would have no effect on what you are trying to do. The 700ms delay is for pressing buttons on the physical switch. It used to determine the ādouble-clickā speed when pressing the buttons multiple times to trigger scenes, but has a side-effect of causing delays on a single-press because the device is waiting to see if you are going to push the button again.
As far as the delay though, I think the first step is to determine where the delay is occurring. The LED light on the sensor will flash when it first sees motion. Are you able to see how long after the LED flashes before the lights turn on? That will help you determine if the delay is at the sensor detecting motion (you might need to change the sensitivity settings or orientation of the sensor), or a delay with your automations.
1 Like
I cannot help you with Hubitat either, as Iām not familiar with it. But in addition to what @jtronicus suggested, I would look at both of the devices and see how many hops it takes to get to the hub. If the devices are not both connected directly to the hub, it may be worth doing a Z-Wave repair.
Are you using the hub or association?
A few things to consider:
- Minimum level. Do you have the switch set to a low ight at 1% via minimum level increase? It can sometimes take up to 40% of the ramp just to turn the light on, which can be perceived as a slow response.
- Ramp rate. Set this at 0 for z-wave and see if results are faster for you. This will go from 0% to 100% immediately instead of the 3s it is set at by default. I keep the local ramp rate at 1 personally.
- Association. You donāt actually have to use the hub to control motion based switching. If you associate these properly you can turn on directly from the sensor.
In addition to the other questions regarding identifying where the delay comes from -
- Are you using the Motion Lighting rules or Rule Machine to handle the āif motion, then onā logic?
- If you use the Hub to turn on and off that light over zwave, is that instant?
Despite my version 2.5 sensor reporting not listening, it still responds to commands pretty quickly (seemingly not waiting for a wakeup interval to pass before getting the command, or maybe just a really really short interval).
Unfortunately, I donāt know how to tell if any traffic is actually getting routed by a device, only that itās reporting capable of routing.
Iād look at the route to the hub for devices around it. If you see one connecting through it, then you know itās routing. If you donāt, unfortunately, then you donāt know for sure.
Itās not very clear in zwavejs2mqttās network map. There are neighbors of the LZW60 that canāt see the controller directly, but those devices always have other neighbors they could route through as well. Iām not sure which route traffic is actually taking.
Just for clarity, do you mean you have the battery in, or did you convert it to be wired?
Thereās no battery. Itās powered by a USB cable.
If itās plugged in, it canāt have a battery inserted because of how itās cabled. Itās one or the other. I think what @krisk is saying that when itās powered by USB, itās still reporting a dead battery and in a perfect world, it wouldnāt report dead when plugged in.
Did you have to alter it to get it powered by USB, or where am I supposed to be able to plug into?
Oh I get that, Iām just wondering what I missed when I set mine up the other day and left it on battery. If I can easily change these to cabled w/ USB, that would be ideal.
No alteration. Just pull out the battery and thereās a micro USB jack.
2 Likes
Well sweet, thanks 
You can be fancy and 3D print a new back door with a circle or groove cutout. STL models are here:
2 Likes
Thatās what I believe I am trying to do but donāt know how to go about itā¦ Using the association tool.
I am testing this and with 5x click inclusion it is showing a role type of āSLAVE_ALWAYS_ONā and the check box is showing that it is a listening node. Also, it responds to commands instantly and they are not queued like they typically are with battery devices.
On the other hand a 1x inclusion shows the device as a āSLAVE_SLEEPING_REPORTINGā and does not have the check box to indicate it is a listening node.
1 Like
Hmmmā¦ maybe I didnāt quintuple-click fast enough?