Sorry for the delay - seems I shouldn't expect the forum to email me when someone replies to my posts.
Can you tell me which node corresponds to #2? Is that your HEM device? You can see the node ID at the bottom of the page when you click on a device.
This page lists some parmeter configuration values that can be setup for your device. It appears that it is only programmed to send updates when something "important" happens -- for example, when there's a major change in power consumption. There's also a few parameters you can adjust to make it send on a consistent interval. Note that the more often it sends, the less battery life your device will have.
beta z-wave driver
- 53 Views
- Last Post 04 December 2012
Axial-User
posted this
30 November 2012
Ryan-Scott
posted this
30 November 2012
The key problem seems to be that the security manager is busy (notice where it says "true" in the logs). That's interesting though - do you have a lock or some sort of device that requires beaming to communicate with?
Ryan-Scott
posted this
30 November 2012
I've added some additional logging to the beta driver as well as some logic that should take care of the endless queuing -- though I'd still like to understand what you have in your system that's triggering it.
In any case, you can download version 2.114 now.
Please let me know how it goes.
Axial-User
posted this
01 December 2012
installed 114
in waller dimmer and switch both now working reliably (yay). Getting results from The Aeon labs HEM(device 2) is still flakey and suspect it might be the problem child (note I haven't wired in the power adapter for it, so it currently runs off batteries - confirmed they are charged). Sometimes can get an update every few mins other times its over an hour.
apologies for the long post, just not sure how much of the log you want to see.
12/1/2012 7:26:48 PM: Properties requested for device 9dd522c1-1825-4425-b537-edba92a61be0
12/1/2012 7:26:48 PM: Found device: yes
12/1/2012 7:26:59 PM: SEC: SendDataSecure for 2
12/1/2012 7:27:00 PM: LogManager: 07:27:00.396: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 7:27:20 PM: LogManager: 07:27:20.400: SecurityManager.nonceRequestTimerElapsed
12/1/2012 7:27:59 PM: SEC: SendDataSecure for 2
12/1/2012 7:28:00 PM: LogManager: 07:28:00.457: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 7:28:20 PM: LogManager: 07:28:20.468: SecurityManager.nonceRequestTimerElapsed
above 3 lines repeat every few seconds
8:36 it receives an update from the HEM
12/1/2012 8:35:47 PM: LogManager: 08:35:47.219: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:03 PM: LogManager: 08:36:03.589: SecurityManager.nonceRequestTimerElapsed
12/1/2012 8:36:03 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:04 PM: LogManager: 08:36:04.933: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:07 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:08 PM: LogManager: 08:36:08.465: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:24 PM: LogManager: 08:36:24.925: SecurityManager.nonceRequestTimerElapsed
12/1/2012 8:36:24 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:26 PM: LogManager: 08:36:26.174: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:26 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:27 PM: LogManager: 08:36:27.588: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:28 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:29 PM: LogManager: 08:36:29.804: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:29 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:31 PM: LogManager: 08:36:31.109: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:46 PM: LogManager: 08:36:46.182: SecurityManager.nonceRequestTimerElapsed
12/1/2012 8:36:46 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:49 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:50 PM: LogManager: 08:36:50.215: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:51 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:52 PM: LogManager: 08:36:52.472: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:54 PM: SEC: SendDataSecure for 2
12/1/2012 8:36:55 PM: LogManager: 08:36:55.916: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:36:59 PM: SEC: SendDataSecure for 2
12/1/2012 8:37:00 PM: LogManager: 08:37:00.848: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:37:08 PM: SEC: SendDataSecure for 2
12/1/2012 8:37:10 PM: LogManager: 08:37:10.207: SecurityManager.nonceRequestTimerElapsed
12/1/2012 8:37:10 PM: SEC: SendDataSecure for 2
12/1/2012 8:37:11 PM: LogManager: 08:37:11.559: Nonce request timer started. NonceState:NonceGetSent
12/1/2012 8:37:12 PM: SEC: SendDataSecure for 2
12/1/2012 8:37:13 PM: LogManager: 08:37:13.787: Nonce request timer sta
Ryan-Scott
posted this
04 December 2012
Sorry for the delay - seems I shouldn't expect the forum to email me when someone replies to my posts.
Can you tell me which node corresponds to #2? Is that your HEM device? You can see the node ID at the bottom of the page when you click on a device.
This page lists some parmeter configuration values that can be setup for your device. It appears that it is only programmed to send updates when something "important" happens -- for example, when there's a major change in power consumption. There's also a few parameters you can adjust to make it send on a consistent interval. Note that the more often it sends, the less battery life your device will have.
