Ok, maybe this, on your scheduled "check if the door is unlocked", work in a refresh before you check it.
For the door auto lock, I use a contact sensor on my doors and send a delayed lock command off of the contact close event, this prevents the door from locking itself when open in addition to not needing to know what the state of the lock is.
Anything you can do to reduce the amount of polling on your network will contribute to increased responsiveness and reliability.
Hi @mike.maxwell - Thanks for the suggestions. There is something about the state of my lock being out of sync that leaves me uncomfortable. I can live with lots of other devices not updating properly. I want to know if that door is locked or not. It would be nice if another solution came up besides refreshing it, this is the only way I have come up with to keep it reliably locked.
I do have a contact sensor here. It will not solve the problem all of the time though. Say someone unlocks the door but does not open it? Or a false presence event unlocks it while everyone is asleep.
Maybe I am being to OCD about it.
any rule or automation capable of doing this should be mode restricted.
There are very, very few automations that I allow to run when the house is in mode "sleeping"
I found this thread while trying to figure out why my switch status wasn’t updating in the iOS Home app (I’m using homebridge) if I physically interacted with the switch. I created a rule machine rule to refresh my z-wave devices (I have 12) every minute. Am I going to run into any performance or stability issues by having this rule run every minute? In a perfect world I’d like it to update faster than every minute, but I want to balance having up-to-date info in the app without sacrificing performance and/or stability of my mesh network.
Some users poll every 10 seconds. Only poll the ones where it is important. This should not cause performance issues, or z-wave mesh issues. Hitting the mesh harder than that might. You can fine tune this. The less you do it, the better.
I had 20 second polling on devices I needed near instant status on that had automations set. I also had 3 minute and 4 minute polling on other switches, the 4 minute was triggered by the 3 minute so they wouldn’t overlap. I experienced lag from time to time with my closet lights that are triggered by Motion, expected them to turn on near instantly but sometimes it would take 20-30 seconds.
I ended up changing out all the switches I was polling 20 seconds with Zwave plus switches since they report physical events which helped a lot. I also installed the zone motion app and use it to trigger refresh so I am only refreshing those devices when someone has been in an area vs all the time. This has also helped.
Hopefully these ideas will provide some help as I have tons of older GE switches that require refresh, over 50 of them. I have a string mesh but the frequent refresh was straining it from time to time.
Yesterday one of my new GE Z-Wave Plus in-wall Smart Switches (model 14291) stopped reporting physical switch presses; it had reliably done so ever since i installed it about 6 weeks ago. Odd, since it is not one of those which require polling to keep their switch state in sync with digital events. So I rebooted the hub (made no difference) and also initiated a Z-Wave repair as well just in case some routing table had gone pork-- also ineffective. Still no physical event reporting, even though it functioned and indicated its status normally when commands were issued by HE.
As a last resort before adding the switch to my list of non-reporting Z-Wave switches handled by my RM periodic refresh app, I pulled the 'air gap' on the switch for a few seconds. Success-- it started generating physical switch events again. Apparently the air gap reset was enough to 'reboot' its Z-Wave module and get it working properly again. I haven't read of this scenario before; hopefully its not a frequent issue with these devices.
Nor have I, not having a love affair with GE/Jsco devices to be honest...
I was thinking physical events not logging was another issue of the firmware, I did a rule in RM to refresh some of my switches and dimmers every 10 seconds and everything looks fine now, I almost complain why they worked in ST, I learned that ST was refreshing all devices every 10 seconds so doing the same in HE for just 2 devices(those 2 we use them physically a lot) will not make a issue(like eating the CPU). Thanks for the info.
any luck with these switches? i added one over the weekend and cant seem to get any physical event reporting.
thank you.
what switches, specifically?
GE zwave switch … heres the data from the driver:
Data * deviceType: 18770
that doesn't help, what's the model number?, and how old is it?
model # on box 12722. newly installed but purchased maybe 6 months ago.
there's no hope for these, they are rubbish.
great!
how about 45856GE?
yeah, those are fine, they pair as generic zigbee switch, no idea how well the router works with off brand quasi compliant sensors though...
ok have one those will replace this one.
dont need the routing … the xbees seem to be doing a fine job there.
thank you.
got the 45856GE hooked up … all seems to be good.
since these are power monitoring … is there a way to see the power data? changing to zigbee power outlet and hitting configure would that do the trick?
thank you.
Question Bruce, is it only the smart Z wave devices that supports push updates? Would it make sense to modify the generic the way dimmer and generic z wave switch (Because there are generic Z wave smart switch and generic Z wave smart dimmer) to allow us to configure a polling intervals? This way we do not me I’m all encompassing will manager role and we can have her device refreshing Intervals define
Download the Hubitat app
