I always use “Add Node Secure” even if it’s not a device that needs security. I also have 10+ mains powered devices to relay thru as well so there’s always a path.
Agreed 1 of 9. Even my light switches are secure added. Pointing it out for those that don’t know you can’t use security devices without.
Cheers!
2 Likes
regarding Security - please read this. https://github.com/home-assistant/architecture/issues/81#issuecomment-469692485
1 Like
@Fishwaldo are you able to confirm/unconfirm that even when initiating a “secure add” (encrypted node pairing) that if the device doesn’t need/support security (encryption) that the request will auto downgrade to a “regular add” (unencrypted pairing)?
Thanks.
If the device supports the Security CC, then it will do encrypted comms. There is no “concept” of need/dont need in Z-Wave, just supported/not supported. If you have it, its used. 
If you do Secure Add on a device that doesn’t have the Security CC, then there will be a small timeout during inclusion, but then will operate non-securely.
1 Like
Exactly the information I was looking for. Thanks.
So you did nothing extra to get the entity to appear? Mine was working and suddenly stopped responding so I ended up removing it, now when re-adding I do not get the “cover” entity. I have removed and secure added multiple times with no luck. This time I just brought the control within a few feet of my stick and still no luck. Any ideas anyone has would be appreciated.
Post the first 10 lines of your OZW_Log.txt
2019-07-25 13:56:09.193 Always, OpenZwave Version 1.4.3428 Starting Up
2019-07-25 13:56:34.070 Info, Setting Up Provided Network Key for Secure Communications
2019-07-25 13:56:34.070 Info, mgr, Added driver for controller /dev/ttyUSB0
2019-07-25 13:56:34.070 Info, Opening controller /dev/ttyUSB0
2019-07-25 13:56:34.070 Info, Trying to open serial port /dev/ttyUSB0 (attempt 1)
2019-07-25 13:56:34.073 Info, Serial port /dev/ttyUSB0 opened (attempt 1)
2019-07-25 13:56:34.073 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-07-25 13:56:34.073 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-07-25 13:56:34.073 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-07-25 13:56:34.073 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
and based on some of the other posts maybe you will want this…
home-assistant-frontend==20190721.1
homeassistant==0.96.4
homeassistant-pyozw==0.1.4
homekit==0.14.0
I am running Python 3.7 but that was done quite awhile ago, and it was working with 3.7.
I had been fighting with getting HomeKit to show my cover so at some point last night I did the install of python-openzwave as was mentioned above for another issue thinking it wasn’t being properly recognized. So I’m really not sure if that’s what broke it, or if it was already broken and that’s why it wasn’t appearing in HomeKit… but either way suddenly last night it went unavailable, so I thought for sure removing and re-adding would have taken care of it but I have had no luck.
Have you tried restarting HomeAssistant?
Check your log when you re-added the device.
I’ve heard stories that some devices would get hot enough to desolder some bits loose in the units as well.
Yeah I have done more restarts than I can count… even removed then restarted… re-added and restarted … it shows the “sensor entities” I’m just not getting the cover itself in HA … could that also be due to the hardware itself failing ?
Usually if the whole thing’s dead you don’t even get sensors.
Could the fact that’s it not seeing the tilt sensor at the moment (Because it’s in the house near the stick) be putting it in an “alarm state”? I know with wink I sometimes had to do a manual open close when first adding…
Not sure, I added mine already mounted in my garage.
As for the unknown part, that’s due to openzwave not finding your config_path where the device XMLs live.
Do you know how I could fix that ?
2019-07-25 16:37:31 ERROR (SyncWorker_4) [openzwave] Can't remove old config directory
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/openzwave/controller.py", line 1385, in update_ozw_config
shutil.rmtree(self.library_config_path)
File "/usr/local/lib/python3.7/shutil.py", line 491, in rmtree
_rmtree_safe_fd(fd, path, onerror)
File "/usr/local/lib/python3.7/shutil.py", line 429, in _rmtree_safe_fd
_rmtree_safe_fd(dirfd, fullname, onerror)
File "/usr/local/lib/python3.7/shutil.py", line 449, in _rmtree_safe_fd
onerror(os.unlink, fullname, sys.exc_info())
File "/usr/local/lib/python3.7/shutil.py", line 447, in _rmtree_safe_fd
os.unlink(entry.name, dir_fd=topfd)
PermissionError: [Errno 13] Permission denied: 'living.xml'
2019-07-25 16:37:31 ERROR (SyncWorker_4) [openzwave] Can't copy to /etc/openzwave/
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/openzwave/controller.py", line 1390, in update_ozw_config
shutil.copytree(os.path.join(dest, 'open-zwave-master', 'config'), self.library_config_path)
File "/usr/local/lib/python3.7/shutil.py", line 321, in copytree
os.makedirs(dst)
File "/usr/local/lib/python3.7/os.py", line 221, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/etc/openzwave/'
2019-07-25 16:37:31 ERROR (SyncWorker_4) [openzwave] Can't update /etc/openzwave/pyozw_config.version
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/openzwave/controller.py", line 1395, in update_ozw_config
with open(os.path.join(self.library_config_path, 'pyozw_config.version'), 'w') as f:
PermissionError: [Errno 13] Permission denied: '/etc/openzwave/pyozw_config.version'
2019-07-25 16:37:31 ERROR (SyncWorker_4) [openzwave] Can't create /etc/openzwave/__init__.py
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/openzwave/controller.py", line 1401, in update_ozw_config
with open(os.path.join(self.library_config_path, '__init__.py'), 'a') as f:
PermissionError: [Errno 13] Permission denied: '/etc/openzwave/__init__.py'
Tried zwave.update_config
I have mine configured as /srv/homeassistant/venv/lib/python3.7/site-packages/python-openzwave/config/ozw_config if i recall. I’d check your paths manually as my install isn’t exactly like yours.
Mine is the same minus the venv directory… how do i go about “setting” that?
Either via the integration in configuration menu or via configuration.yaml