Page 2 of 2

Re: Where to start

PostPosted: Mon Jul 30, 2018 1:41 pm
by siclark
You should be good on high Sierra with an aeotec zwave stick. The issues are on usb but I don't believe impact that stock. I, and many others are fine on high Sierra. Possibly a problem if you use insteon bit doesn't sound like you do.


Sent from my iPhone using Tapatalk

Re: Where to start

PostPosted: Mon Jul 30, 2018 6:34 pm
by Different Computers
I've been running 10.13.6 for quite a while now, and have not had any USB issues with Z-wave or Insteon.

How long?

Code: Select all
Indigo:~ me$ uptime
20:33  up 17 days,  6:14, 2 users, load averages: 2.83 2.96 3.12


Last reboot was when I upgraded.

Re: Where to start

PostPosted: Tue Jul 31, 2018 9:35 am
by jay (support)
Different Computers wrote:
I've been running 10.13.6 for quite a while now, and have not had any USB issues with Z-wave or Insteon.

How long?

Code: Select all
Indigo:~ me$ uptime
20:33  up 17 days,  6:14, 2 users, load averages: 2.83 2.96 3.12


Last reboot was when I upgraded.


What Mac model are you using?

Re: Where to start

PostPosted: Tue Jul 31, 2018 2:10 pm
by Different Computers
It’s the same i5 as my sig, just updated to 10.13.6. A retina MacBook pro

Re: Where to start

PostPosted: Tue Jul 31, 2018 2:40 pm
by jay (support)
Different Computers wrote:
It’s the same i5 as my sig, just updated to 10.13.6. A retina MacBook pro


Exact model please. Trying to figure out it's approximate age.

Re: Where to start

PostPosted: Tue Jul 31, 2018 3:10 pm
by howartp
Different Computers wrote:
No submit button. Z-wave Scene Controller either doesn't catch the double tap, or I have no idea how to use ZWSC.

Turn on plugin debugging and it will log any incoming button or scene commands.

Post them here and we’ll see what’s happening.

(If it doesn’t, then grab the Zwave Watcher plugin as that logs all activity from a device, not just anticipated button/scene commands)

Peter


Sent from my iPhone using Tapatalk Pro

Re: Where to start

PostPosted: Tue Jul 31, 2018 5:23 pm
by Different Computers
Sorry for being vague. Retina, 13 inch, Late 2013

Model Identifier: MacBookPro11,1
Processor Name: Intel Core i5
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 4 GB
Boot ROM Version: MBP111.0146.B00
SMC Version (system): 2.16f68

I don't think it has been restarted since the 10.13.6 update. So maybe the problem that appears on reboots hasn't happened yet? I'm sure you can understand why I'm not thrilled at giving it a try.

Also, the screen is severely cracked, but I doubt that makes a difference!

Re: Where to start

PostPosted: Wed Aug 01, 2018 3:51 pm
by jay (support)
Different Computers wrote:
Sorry for being vague. Retina, 13 inch, Late 2013

Model Identifier: MacBookPro11,1
Processor Name: Intel Core i5
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 4 GB
Boot ROM Version: MBP111.0146.B00
SMC Version (system): 2.16f68

I don't think it has been restarted since the 10.13.6 update. So maybe the problem that appears on reboots hasn't happened yet? I'm sure you can understand why I'm not thrilled at giving it a try.

Also, the screen is severely cracked, but I doubt that makes a difference!


We've never seen it randomly fail - it either always fails or it never fails (you never saw a failure, right?), so I think you're safe. Thanks for the information, it's another data point. I have an even older MacBook Pro 13" (Mid 2010) which does fail consistently.