Hours lag in executing commands

[emekahansel]

I just got the C8 pro elevation. I basically got it to control my Airbnb location so guests can do self check in. I have Alarm.com hubs across all my locations but would love to replace it all with hubitat.

My locks are all Weiser 10 keypad zwave plus locks. I did factory reset on the lock before adding. My issue is that commands sent from the app take forever in some cases 4 hour to execute. And new user and codes constantly fail to add.

Is this a design flaw or am I doing something wrong?

[neonturbo]

That is not normal. Any command, even remote, should be near instantaneous.

How are you setting codes, in person? Hubitat remote access service? VPN? Please describe your steps here.

Are you using the Hubitat Lock Code Manager?

Do the lock codes populate quickly if you are on site?

[emekahansel]

The codes were add via Hubitat Lock Code Manager to add the codes. No VPN. I have a test lock installed in a piece of wood. The lock, Hub( hardwired and computer are all set on a table.

1. Exclude device( happens instantly)
2. Include device (takes forever and most times it times out)
3. Adding name, room and save.

The codes would go from pending to failed. When I click retry the same happens. I'll delete it reset the lock and try again.

[neonturbo]

Edited to add: inclusion should be near instant, or maybe 10 seconds at worst. If it is longer than this, something is wrong somehow.

The below would be a good start. I suspect that you have ghosts or other basic Z-wave issues.

READ FIRST - Before Posting in Get Help

Welcome to the Hubitat Community. You are probably reading this because you are about to ask for help, or you already did but did not provide enough information and were sent here! If you are new and need to post screenshots (or links), manually join the owners group: -> Hub owners - Hubitat TIP: When posting logs, screenshots are much easier to read. Any instructions are assumed to be for current platform version. Handy Links Diagnostic Tool Docs: Hubitat Diagnostic Tool | Hubitat Documen…

What info to provide for troubleshooting assistance:

• How is Hub being powered? Supplied power block or other (explain)
  • PoE power (with splitter) is known to cause major Z-Wave issues on the C-8 hub.
  • See this post for detailed write up on PoE testing: PoE and the C8
• Provide screenshots showing entire Z-Wave details Page
  • Hub should be running for at least 12hrs without reboot, and state how long in your post (you can find uptime on Logs > Device Stats)
  • Click the Refresh Statistics button, wait 10 seconds, then Refresh the page
• Provide screenshot of Z-Wave Topology Map (red/blue squares)
  [/quote]

Also, are you on Z-wave JS? Look at the top left of the Z-wave page, and see if there is a button to (paraphrasing) to revert to ZIP gateway.

[aaiyar]

Also - which specific model of Weiser lock and Hubitat hub are you working with? I will also reiterate @neonturbo's suggestion to use legacy z-wave for now, instead of ZWaveJS.

[emekahansel]

I'm using Wieser 620