Page 3 of 3

Re: New Mac Mini

PostPosted: Thu Nov 15, 2018 5:50 pm
by jay (support)
blysik wrote:
Do we know if the new Mac Minis will have the same USB driver problem?


[MODERATOR NOTE] I deleted a couple of posts that linked to another post about the new mini. The problem is that the post linked to implied that it the new mini didn't work. If you continued to read down through the thread then you would have found out that his issues were not related to the driver issue. But I'm still not clear if the FTDI issue is a problem or not since it's unclear if the user in that post performed the workaround in the OS install in his new mini or not.

Also, while we appreciate the feedback, @matt's reply doesn't answer the question because his interface doesn't use the FTDI driver.

So - can anyone with a new mini confirm that it does work correctly with FTDI-based devices without the workaround. The community would be very appreciative for a firm answer.

Re: New Mac Mini

PostPosted: Thu Nov 15, 2018 6:03 pm
by mat
if anyone has an old working v2 stick, I'll happy to try and return - my v2 bit the dust years ago.

Re: New Mac Mini

PostPosted: Thu Nov 15, 2018 11:38 pm
by kwijibo007
I have an Aussie 921.4 v2. Z-stick but that’s probably not going help.

Re: New Mac Mini

PostPosted: Fri Nov 16, 2018 4:57 am
by mat
kwijibo007 wrote:
I have an Aussie 921.4 v2. Z-stick but that’s probably not going help.


No would probably be cheaper to buy one, than post both her and back hahaha

New Mac Mini

PostPosted: Sun Nov 18, 2018 3:32 am
by gillekes
Just found the time to move to the new mini. Still had a v2 stick laying around, but as I’m not using it any more there are no zwave modules asociated to it. Plugged it in mini, but Indigio could not find it in the modemlist... back to the gen5 and popped up on the list.
The switching part:
The old mini was running Sierra.
I installed the mini as a new mac, then I used the migration assistant and imported the apps and docs.
Connected the gen5, went to the config tab, selected the modem and there you go... smooth as butter!
Evereything worked from the first second!
And the mini is fast!!!
To have an idea, on the old mini (mid 2011) converting 4k movies to be able to play on the apple tv would take 16h. With the new 1,5h!!!
I use to iPad pro with wifi screen sharing from the mini to do some light programming in indigo and this used to have an awfull lag. Now it is 100 times faster. I would say it usable now!

Gilles


Sent from my iPad using Tapatalk

Re: New Mac Mini

PostPosted: Sun Nov 18, 2018 7:47 am
by CliveS
gillekes wrote:
Just found the time to move to the new mini. Still had a v2 stick laying around, but as I’m not using it any more there are no zwave modules asociated to it. Plugged it in mini, but Indigio could not find it in the modemlist..
Sent from my iPad using Tapatalk


From the Wiki
"The Aeotec Z-Stick Series 2 interface requires that you install the Silicon Labs VCP Driver Kit for Mac OS X. Make sure you have restarted after the installation process. If you reinstall your OS, then you will need to rerun the driver installer. Warning: Before upgrading macOS to the next major revision, please visit the Announcements section of our forums to see if there are potential issues with the OS update (drivers, particularly in macOS High Sierra, are somewhat buggy)."

Re: New Mac Mini

PostPosted: Sun Nov 18, 2018 10:43 am
by jay (support)
Yes, the driver issue is limited to devices requiring the FTDI driver ( PowerLinc, RFXtrx/rec433, etc).

Re: New Mac Mini & W800RF32

PostPosted: Sun Nov 18, 2018 2:04 pm
by dscottbuch
I just moved everything over to the new Mini and Mojave. Overall only some minor pains. I had to remove and re-install the Homekit-Bridge Plugin due to 'some corruption' from the Time Machin restore and this resulted in rebuilding the entire house.

My question, though, is that I can't get Indigo to see the W800RF32 interface. I've installed the newest Prolific driver and System Report show it clearly attaching, property but there is no serial interface shown in the "Manage Interface..." configuration.

Any ideas, things to try. I've re-installed Indigo (7.1.1 btw) and Prolific with multiple reboots to no avail.

BTW the reboot on the new mini is amazingly fast (coming from a 2011 iMac).

Thanks,

Scott

Re: New Mac Mini

PostPosted: Sun Nov 18, 2018 3:53 pm
by jay (support)
Did you approve the driver in the System Preferences -> Security & Privacy window after you installed it?

Does it show up when you open a terminal window and past in:

Code: Select all
ls /dev/

Re: New Mac Mini

PostPosted: Sun Nov 18, 2018 7:28 pm
by dscottbuch
I had done the approval, but apparently on the wrong 'Prolific' choice. I re-installed and approved everything pending and it's working now.

Thanks,

Re: New Mac Mini

PostPosted: Sun Nov 18, 2018 7:31 pm
by dscottbuch
So, now, after approving all the pending approvals, including 'Legacy: Perceptiveautomation' the USB 'Bug' is back and it's not connecting to the PowerLinc. This was working fine before I did this, through multiple reboots. Do you know how to 'unapprove' these system extensions?

Thanks,
Scott

Re: New Mac Mini

PostPosted: Mon Nov 19, 2018 10:20 am
by jay (support)
dscottbuch wrote:
So, now, after approving all the pending approvals, including 'Legacy: Perceptiveautomation' the USB 'Bug' is back and it's not connecting to the PowerLinc. This was working fine before I did this, through multiple reboots. Do you know how to 'unapprove' these system extensions?


I don't know how to unapprove any other than just uninstalling them. I think you have to approve them any time you install them.

What are the exact errors you're getting? Let's just make sure that it is the driver bug issue.

Re: New Mac Mini

PostPosted: Mon Nov 19, 2018 1:27 pm
by dscottbuch
After a reboot the 2413U does not reconnect. I have unplug and then plug in the USB, which, when plugging it back in sometimes reboots the computer again. This was the problem on my iMac. Also, before approving all of these items in the Security->General panel was NOT happening. I could reboot and the 2413U would reconnect when the server started.