Powerlinc 2413U will not connect my 2019 MacBook Pro

[marchioli]

Well worked for a few days and now same problem even though the device is there. It appears to be similar to some other postings where Apple has screwed with the USB devices.
Still working through the problem. I did find this universal Serial port driver that claims to support the FTDI and other serial devices.

https://www.decisivetactics.com/products/serial/

It didn't work for Indigo but did work for the terminal/device browser. I rebooted and no difference.

[matt (support)]

Sounds like you've tried everything, but just to make sure: you have tried different USB ports (including on USB hubs) as well as changing the USB cable? Also unplug all your USB devices except your keyboard/trackpad to rule out some type of conflict. Lastly, try using an extension cord to plug the 2413U into different outlets on different circuits (in different rooms). If there is a lot of power line (or RF) noise then the PowerLinc can get so confused the USB communication fails. Trying it in different locations can help rule that out.

All that said, it is likely it has just become marginal.

[marchioli]

Matt,
Thanks for chiming in.

I swapped out the 2413u v2.4 with my 2413U v1.7 which I had recapped. it again worked for about 2-4 days and then Indigo said it couldn't open the serial device.

I downloaded 'Serial' from https://www.decisivetactics.com/products/serial/ which did load fine and it sees the A60335J2 USB to serial port just fine. However, it also cannot open the serial port for writing and says it fails.
So, I shut down Indigo and was then able to open the USB Serial port just fine. So it IS something in Indigo that is blocking the USB Serial port once it is opened.

Here is 'Serial' app opening the USB port once Indigo has been shutdown

Screen Shot Serial opens USB port OK.png (13.67 KiB) Viewed 3039 times

'Serial' app could not open the USB serial port WHILE Indigo was running

Screen Shot USB FT232R Could Not Be Opened.png (66.31 KiB) Viewed 3039 times

I did find some blurb on the FTDI site about problems with multiple write to the devices from threads will block subsequent threads trying to write to the device if the first thread isn't finished (relinquished it). For instance, the FTDI driver doesn't by default support multithreading writes. They have some sort of helper program but I haven't tried it.

I'm wondering if that hasn't crept into the mix of things with the new python 3 upgrade . I don't have the time or bandwidth currently to go that deep into the device tree to see if it is blocked.

Also, I happen to think overnight (one of those sleeping thoughts) that all of this difficulty seemed to have started with the last release 2022.1.2 - it may be a coincidence but thought I would mention it because I'm not exactly sure what the difference in 2022.1.1 and 2022.1.2.

So, my 2413U works fine - it responds to resets and it open on the 'Serial' app just fine. It does not work fine with Indigo.

List of the Serial devices from the 'Serial' app

Screen Shot 2022-08-03 at 8.23.31 PM.png (35.49 KiB) Viewed 3039 times

For completeness, here's a list of the USB devices on my late 2014 Mac Mini running 12.5:
lsusb -v
2022-08-03 20:39:25.333 system_profiler[921:32202] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
2022-08-03 20:39:25.334 system_profiler[921:32202] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
USB:

USB 3.0 Bus:

Host Controller Driver: AppleUSBXHCILPT
PCI Device ID: 0x9c31
PCI Revision ID: 0x0004
PCI Vendor ID: 0x8086

USB Receiver:

Product ID: 0xc52b
Vendor ID: 0x046d (Logitech Inc.)
Version: 24.11
Speed: Up to 12 Mb/s
Manufacturer: Logitech
Location ID: 0x14700000 / 2
Current Available (mA): 500
Current Required (mA): 98
Extra Operating Current (mA): 0

IR Receiver:

Product ID: 0x8242
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.00
Speed: Up to 1.5 Mb/s
Manufacturer: Apple, Inc.
Location ID: 0x14400000 / 3
Current Available (mA): 500
Current Required (mA): 100
Extra Operating Current (mA): 0
Built-In: Yes

BRCM20702 Hub:

Product ID: 0x4500
Vendor ID: 0x0a5c (Broadcom Corp.)
Version: 1.00
Manufacturer: Apple Inc.
Location ID: 0x14300000

Bluetooth USB Host Controller:

Product ID: 0x8289
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.50
Manufacturer: Apple Inc.
Location ID: 0x14330000

Hub:

Product ID: 0x0237
Vendor ID: 0x050d (Belkin Corporation)
Version: 0.00
Speed: Up to 480 Mb/s
Location ID: 0x14200000 / 5
Current Available (mA): 500
Current Required (mA): 2
Extra Operating Current (mA): 0

CP2102 USB to UART Bridge Controller:

Product ID: 0xea60
Vendor ID: 0x10c4 (Silicon Laboratories, Inc.)
Version: 1.00
Serial Number: 0001
Speed: Up to 12 Mb/s
Manufacturer: Silicon Labs
Location ID: 0x14260000 / 10
Current Available (mA): 500
Current Required (mA): 100
Extra Operating Current (mA): 0

FT232R USB UART:

Product ID: 0x6001
Vendor ID: 0x0403 (Future Technology Devices International Limited)
Version: 6.00
Serial Number: A60335J2
Speed: Up to 12 Mb/s
Manufacturer: FTDI
Location ID: 0x14210000 / 8
Current Available (mA): 500
Current Required (mA): 90
Extra Operating Current (mA): 0

[matt (support)]

I did find some blurb on the FTDI site about problems with multiple write to the devices from threads will block subsequent threads trying to write to the device if the first thread isn't finished (relinquished it). For instance, the FTDI driver doesn't by default support multithreading writes.

When Indigo tries to open the serial port it does so with the exclusive access flag, which will block any other applications (like the Serial utility app you found) from being able to open a connection. Multiple apps trying to communicate with the same PowerLinc won't work given how its communication protocol works. So the behavior you described (of having to shutdown Indigo Server first) is to be expected and not an error or related to the problem.

I'm confident this isn't related to the Indigo upgrade at all (the problem started without you having recently upgraded Indigo which points towards a hardware malfunction, noise issue, or the chipset vs. driver problem), but you are welcome to revert Indigo back to an older version. Just choose the Indigo->Stop Server menu item, then Indigo->Quit menu item, then you can relaunch an older version of Indigo. Note there have been no changes to Indigo over the last few years in how it handles USB/serial communication in general, or specifically with the PowerLinc. Also note Indigos PowerLinc communication isn't built on Python so the python3 changes aren't going to be the culprit.

Note just because the Serial app can connect to it doesn't mean the PowerLinc is working. Indigo will report an error (please copy/paste the error you are seeing) if the PowerLinc isn't responding correctly to the initializing commands. That is, the process is much more complicated than just the serial connection being opened.

Regarding drivers, the CP2102 driver won't help (but shouldn't hurt either). That driver is for a different chipset than the FTDI. Apple's build-in FTDI should work (I think called AppleUSBFTDI), so the best place to start is with only it installed. Sometimes installing the independent FTDI driver (not Apple's version) can help (if PowerLinc rev is 2.4 or older), but for most folks the Apple included driver works.

Not sure if any of this will help much. My guess is still on it being marginal hardware (even though it is 2 different PowerLincs) or you are running into the older FTDI chipset problem that some users have found in PowerLinc versions 2.4 and older (2.5 seems to work better). It appears to be a problem with driver compatibility and the chipset based on the evidence we've heard of so far.

[marchioli]

Ok, so spent some time to try to remove any and everything that might be conflicting with the FTDI driver - I basically followed their uninstalling and VCP guidelines for Apple supplied USB FTDI device drivers.

I then removed the kernel extensions that were there for USBFTDI and shutdown and powered off.

I copied the newest FTDI driver download (1.5) to the applications folder and ran it - allowing security firewall exceptions for the downloaded program. It flashed 'Success'.

I then reset the PLM (hold down button unplugged for 15+ seconds, plug in with button held down while it beeps and once it stops beeping release button).

I started Indigo, disabled the Insteon device, and then plugged in the PLM. I went to Indigo to configure the device to the new driver (USBSerial_xxxx). Then, Insteon -> Enable. It prompted for new PLM and to resynch all devices which I clicked ok.

So, back up and running for a while. We'll see if it holds for more than a day or two.

[marchioli]

Still up and running

[uniball]

I'm now experiencing this issue. Going to read through the post and see what I can do.

I am on a 2017 iMac that is now running iOS Ventura.

[uniball]

I'm now experiencing this issue. Going to read through the post and see what I can do.

I am on a 2017 iMac that is now running iOS Ventura.

I wasn't able to remove the FTDI driver since I couldn't find the file that was referenced on the FTDI website. I performed the reset of the PLM and it worked for a short time. PLM had a green light and Indigo was able to sync. After a bit the light on the device went out and it no longer syncs.

Any guidance would be greatly appreciated.

[jay (support)]

If the light is going out completely, unfortunately that means that the PLM is failing.

[uniball]

If the light is going out completely, unfortunately that means that the PLM is failing.

That is what I was suspecting. The lights have been acting quite odd lately. For a while it was always red but it was still working. I had the device unplugged for a day and it helped for a moment but then lost connection. Insteon says they are having chip issues so new inventory is pushed out until 1st quarter next year.

[mvignola29]

Just started to have a similar problem. Where the PowerLic 2413 indicates a power failure and where there is not one. I have tried my backup 2413, changed the cable and used another outlet plug. My system was working properly for the last few days this just occurred. I am running Ventura

[jay (support)]

Just started to have a similar problem. Where the PowerLic 2413 indicates a power failure and where there is not one. I have tried my backup 2413, changed the cable and used another outlet plug. My system was working properly for the last few days this just occurred. I am running Ventura

It might be a Ventura issue (it wouldn't be the first time Apple has broken certain aspects of USB). This is why we recommend that you avoid doing macOS upgrades until a few dot releases in.

[mvignola29]

I deactivate my License on my Imac24 and Installed Indigo7 on my notebook which is also running Ventura and and after activating now all is working properly. There must be some setting on my imac24 which is causing this power connect failure to the USB port, I did try other ports on the Imac24 but still had the same problem, Not sure what to do next, I was wondering if I could get a second temporary licenses so that I can try to troubleshoot this issue using my back up Powelinc 2413U. and Indigo application

[matt (support)]

Try this link to create a Trial License. If it fails because you already have one then email us your username and we'll add one to your account.

[mvignola29]

Yes it did fail since I already have a email with you