Can you post your latest log again?
The log might be similar or the same since I removed and added the lock multiple time before you had messaged me.
Itâs getting the correct data from the lock:
2018-11-17 17:52:28.538 Detail, Node009, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-11-17 17:52:28.538 Detail, Node009, Queuing (Send) DoorLockCmd_Get (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x62, 0x02, 0x25, 0x12, 0xb9
2018-11-17 17:52:28.538 Detail, Node009, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_ALARM
2018-11-17 17:52:28.539 Detail, Node009, Queuing (Send) AlarmCmd_Get (Node=9): 0x01, 0x0c, 0x00, 0x13, 0x09, 0x05, 0x71, 0x04, 0x00, 0x06, 0x01, 0x25, 0x13, 0xa8
2018-11-17 17:52:28.539 Detail, Node009, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_ALARM
2018-11-17 17:52:28.539 Detail, Node009, Queuing (Send) AlarmCmd_Get (Node=9): 0x01, 0x0c, 0x00, 0x13, 0x09, 0x05, 0x71, 0x04, 0x00, 0x08, 0x01, 0x25, 0x14, 0xa1
2018-11-17 17:52:28.539 Detail, Node009, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_BATTERY
2018-11-17 17:52:28.539 Detail, Node009, Queuing (Send) BatteryCmd_Get (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x80, 0x02, 0x25, 0x15, 0x5c
Any errors showing up in the HomeAssistant log?
Here is the log
2018-11-17 17:52:23 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 192.168.1.156
2018-11-17 17:52:23 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 192.168.1.156. Retrying in 2 seconds
2018-11-17 17:52:26 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File â/usr/local/lib/python3.6/site-packages/homeassistant/components/zwave/init.pyâ, line 949, in discover_device
self._zwave_config)
File â/usr/local/lib/python3.6/site-packages/homeassistant/helpers/discovery.pyâ, line 151, in async_load_platform
assert hass_config, âYou need to pass in the real hass configâ
AssertionError: You need to pass in the real hass config
2018-11-17 17:52:37 ERROR (MainThread) [homeassistant.components.light.hue] Unable to reach bridge 192.168.1.156 ()
2018-11-17 17:52:50 ERROR (SyncWorker_14) [homeassistant.components.light.nanoleaf_aurora] Could not generate the auth token, did you press and hold the power button on Light-Panels-53-50-eb.local.for 5-7 seconds?
Some kinda zwave config error there.
AssertionError: You need to pass in the real hass config
Might need to pop on discord and ask about that one never seen it before.
1 Like
Thank you so much for your help. I was able to figure it out. I reinstalled HASSIO and it works now. Thank you so much.
I have the same situation. You state that you âfigured it outâ, but then say that you just reinstalled. So what exactly was figured out?
What made you decide to reinstall? Iâm hesitant to reinstall and have to set everything else up from scratch again.
What exact problem are you facing ?
Like I said, I have exactly the same situation that you described above. Various kwikset items in the overview but nothing that actually give me control over the lock and codes. No lock.device. An error in the logs that states âAssertionError: You need to pass in the real hass configâ.
I didnât want to repeat it all, but there you go.
So what exactly fixed it? Did you really reinstall everything? In that case it seems like you just got lucky rather than figuring anything out. I have no confidence that it would work better this time. Seems like Iâd be lucky to get everything set up again as well as I have it. There are also issues with network keys, apparently you donât have to configure them explicitly anymore, but wonât I have to have it to reconnect?
I can tell you few things I did and I had done a lot of trial and error since this was my first z wave device, in fact it was the first device I added to HA. I had got the network keys wrong initially but the lock showed up as lock.lockname but I didnât have the option to control it. Next I removed my lock from HA using remove node option and then did a heal network. After that I reinstalled HASSIO followed by adding the zwave integration using the integration menu rather than configuration.yaml but this time the lock didnât have the lock.lockname option so I again repeated the above step and reinstalled HASSIO. Now the third time I added z wave using configuration.yaml and got the correct network keys and it worked. So I removed it again and installed HASSIO again and tried to integrate using the zwave integration menu but again it gave me the same error which you are getting, so I removed it again and installed HASSIO and used the configuration.yaml and used manual network keys and now it works fine. Hope this helps.
Thanks Ravious. I too am at this point with a Schlage lock. Its my eighth node though. Sounds like Iâm starting over and adding them all again using the older configuration.yaml method.
1 Like
I hope it does the trick.
Thank you. My take away is that the network key is required in the yaml even though there are docs saying that it is not.
Why reinstall between each config change (5 times)?
I have a thermostat that I added and works great. But this is my first secure device to add.
How did you get the network key wrong? Donât you generate it from scratch? There isnât anything to find or match up according to the docs.
I added the zwave section to the yaml with a usb path that I found in the UI and a network key that I generated. Then I did the âadd securelyâ action in the z wave integration in the UI, then pressed the A button on the lock, then a heal network. Now I see a widget in HA that allows me to lock and unlock. Yay!
But I donât see a way to add passcodes to the lock via HA.
Add pass codes from the Zwave option in the configuration menu:
Or use @ptdalenâs package for a UI to configure it.
1 Like
Same problem, locks are paired, but I cannot control them.
Mac OSX
HA 90.2
OZW Log
2019-04-18 17:28:34.111 Info, Node009, Sending (Send) message (Callback ID=0x44, Expected Reply=0x04) - DoorLockCmd_Get (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x62, 0x02, 0x25, 0x44, 0xef
2019-04-18 17:28:34.119 Detail, Node009, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-04-18 17:28:34.119 Detail, Node009, ZW_SEND_DATA delivered to Z-Wave stack
2019-04-18 17:28:35.400 Detail, Node009, Received: 0x01, 0x07, 0x00, 0x13, 0x44, 0x00, 0x00, 0x80, 0x2f
2019-04-18 17:28:35.400 Detail, Node009, ZW_SEND_DATA Request with callback ID 0x44 received (expected 0x44)
2019-04-18 17:28:35.400 Info, Node009, Request RTT 1289 Average Request RTT 1278
2019-04-18 17:28:35.400 Detail, Expected callbackId was received
2019-04-18 17:28:44.116 Error, Node009, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-04-18 17:28:44.116 Detail, Node009, Removing current message
2019-04-18 17:28:44.116 Detail, Node009, Notification: Notification - TimeOut
2019-04-18 17:28:44.117 Detail,
2019-04-18 17:28:44.117 Info, Node010, Sending (Send) message (Callback ID=0x45, Expected Reply=0x04) - DoorLockCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x62, 0x01, 0xff, 0x25, 0x45, 0x13
2019-04-18 17:28:44.126 Detail, Node010, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-04-18 17:28:44.126 Detail, Node010, ZW_SEND_DATA delivered to Z-Wave stack
2019-04-18 17:28:45.363 Detail, Node010, Received: 0x01, 0x07, 0x00, 0x13, 0x45, 0x00, 0x00, 0x7d, 0xd3
2019-04-18 17:28:45.363 Detail, Node010, ZW_SEND_DATA Request with callback ID 0x45 received (expected 0x45)
2019-04-18 17:28:45.363 Info, Node010, Request RTT 1245 Average Request RTT 1271
2019-04-18 17:28:45.363 Detail, Expected callbackId was received
2019-04-18 17:28:54.121 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-04-18 17:28:54.121 Detail, Node010, Removing current message
2019-04-18 17:28:54.121 Detail, Node010, Notification: Notification - TimeOut
Two nodes, 9 and 10, both returning the same error: ERROR: Dropping command, expected response not received after 1 attempt(s)
All help appreciated!
Did you pair the locks securely?
Do you have a network key set?
Yes, locks paired securely.
I added the network key, restarted HA and still having the same error. Both doors are locked, physically, but both components show them as unlocked.
Iâm not seeing the detail someone else posted above that includes âlock_status:â Iâll try removing and re-pairing again but each time it skips nodes. 6 was one door, 7 failed, 8 was another door. I removed them all, or so I thought (7 came back unknown node) and now the doors are 9 and 10 with no nodes at 6 and 8.
You are pairing them but clicking the Add Secure Node button in Home Assistant correct?