jay (support) wrote:jeff-4 wrote:I just installed 10.11.2 and can no longer connect to my Insteon PowerLinc Modem. I am pretty unhappy with the situation, since everything was working up this most recent upgrade. I know most of the blame goes to Apple, but I purchased Indigo because of its promised compatibility with the Mac and now it isn't.
It's frustrating for us too since we have no control over the USB/driver issues that many new OS releases introduce. Having said that, I just upgraded my development Mac to 10.11.2 and the PowerLinc connected just fine (the jury's still out if it will continue to work since the bug I filed with Apple takes a day or two to trigger on this Mac). Try the following and let us know the answer to each:
- Does the PowerLinc show up in the System Information app when you select USB under Hardware? It should show up as FT232R USB UART
- In the Insteon config dialog, is it showing a serial port named something like "usbserial-XXXXXXXX" (make sure that it's not saying "port not found"?
- Is the PowerLinc plugged directly into a USB port on your Mac and not a hub (or a USB port on a keyboard)?
- If the answer to the first one is no, try another USB cable/port.
simdude wrote:jeff-4 wrote:I just installed 10.11.2 and can no longer connect to my Insteon PowerLinc Modem. I am pretty unhappy with the situation, since everything was working up this most recent upgrade. I know most of the blame goes to Apple, but I purchased Indigo because of its promised compatibility with the Mac and now it isn't.
One of the best tips I could give you for home automation using any computer is wait to do upgrades. This can be hard if you are multi-purposing your main computer but upgrades can break things. You'll notice many people buy an older mac just to handle the home automation. Probably not an expense you want to hear but an option. I'm using my main computer for now but wait as long as possible to upgrade. Matt and Jay are great at working with Apple and getting things worked out but it will take some time.
In the meantime, try some troubleshooting. Switch USB ports. Reboot with and without the modem plugged in. If you boot without it plugged it, plug it in after you're up and running. Also, try plugging into a hub. While plugging directly into the mac is preferred, oddly, sometimes the hub works better. Any information you can provide with help narrow down the problem. I will also check my OS version and modem at home and see if I have a similar configuration and help if I can.
Mark
jeff-4 wrote:
I've tried all of these things except the hub (don't have one). What happens is that the modem comes back and is recognized in Indigo. But then the connection breaks when I ask Indigo to actively do something, like turn on a light, add a device, etc. Weird thing is that eventually the PowerLinc comes back on and Indigo carries out my scheduled events without problems. See also my response to Jay. ANy help would be great;y appreciated!
simdude wrote:
I ended up doing an inadvertent update to 10.11.2. I say inadvertent because I had to do a reboot and it auto-installed. I must have a setting for updates to be automatically applied. In any case, I am now updated. I'm running Indigo 6.1.4 with the PowerLinc 2413U and the Aeon Gen5 Z-wave stick. My house is Z-wave however. I bought the 2413U anticipating I may move back to Insteon. For now, I only use it to control X10 Christmas lights. That being said, it has worked fine for the X10 stuff. I'm not seeing any lockups or other issues. Is there any chance the issue is only present when communicating with Insteon devices?
As far as your modem failing, I believe they have a 2 year warranty. I would inquire about a replacement.
jeff-4 wrote:2. When I try to issue a command form the Indigo window, to turn on a light for example, I see the acticvity registering on the status bas (lower lef) for the PowerLinc modem, but then nothing happens (the light does not light) and the PowerLinc 2413U letters are redlined. When I look at the log, there is a VERY long list of lines reading
Error resending previous command (busy or unexpected command)
durosity wrote:Perhaps worth posting this as a sticky somewhere?
Users browsing this forum: No registered users and 23 guests