Page 1 of 1

7.1.1 stopped Z-wave from working - fixed

PostPosted: Sun Dec 31, 2017 7:25 am
by rijdat
I have just upgraded to 7.1.1 from an earl;ier version of 7, running on Sierra. When Indigo starts up it tries to start the Z-Wave interface but stops it. Restarting the Mac did not help. This is in the log:

31 Dec 2017, 13:11:18
Reloading interface "Z-Wave 2.0.111"
Starting interface "Z-Wave 2.0.111" (pid 658)
Z-Wave Error Error in plugin execution InitializeMain:

Traceback (most recent call last):
File "<string>", line 1, in <module>
File "plugin.py", line 50, in __init__
File "/Library/Application Support/Perceptive Automation/Indigo 7/IndigoPluginHost.app/Contents/PlugIns/plugin_base.py", line 256, in __init__
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/handlers.py", line 171, in __init__
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/handlers.py", line 64, in __init__
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py", line 911, in __init__
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py", line 941, in _open
IOError: (13, 'Permission denied', u'/Library/Application Support/Perceptive Automation/Indigo 7/Logs/indigoplugin.zwave/plugin.log')

Stopping interface "Z-Wave 2.0.111" (pid 658)
Stopped interface "Z-Wave 2.0.111"

The Admin permissions on the plugin.log file and the indigoplugin.zwave folder were both Read Only. After a couple of attempts I reset them to Read and Write and Z-Wave started working again.

Cheers, Richard

Re: 7.1.1 stopped Z-wave from working - fixed

PostPosted: Sun Dec 31, 2017 1:03 pm
by matt (support)
Keep an eye out for other permission problems (ex: when Indigo is trying to save its database file, create a new event log file, etc). When this has happened in the past it is because another installer (not Indigo) had messed up the permissions on the entire Application Support folder.