/Library/Application Support/Perceptive Automation/Indigo 2021.2/
Skill Builder wrote:
You cannot change the invocation name for a live skill. Error code: InvalidStageInvocationNameChange
/Library/Application Support/Perceptive Automation/Indigo 2021.1/
/Library/Application Support/Perceptive Automation/Indigo 7.5/
import logging
indigo.server.log("message here", level=logging.WARNING)
System software from developer 'Legacy Developer:Perceptiveautomation' was blocked from loading.
sharedProps = dev.sharedProps
sharedProps["sqlLoggerIgnoreStates"] = "brightnesslevel, onoffstate"
dev.replaceSharedPropsOnServer(sharedProps)
sharedProps = var.sharedProps
sharedProps["sqlLoggerIgnoreChanges"] = "true"
var.replaceSharedPropsOnServer(sharedProps)
/Library/Application Support/Perceptive Automation/Indigo 7.4/
/Library/Application Support/Perceptive Automation/Indigo 7.3/
/Library/Application Support/Perceptive Automation/Indigo 7.2/
/Applications/Indigo 7.2
jalves wrote:
Another data point: I just updated my Indigo machine to 10.13.3 and after the restart i had to do the unplug/replug routine for the Insteon and RFXCom devices. Once I did that everything worked just fine. FWIW, the Insteon interface is plugged directly into the Mini, while the RFX device is plugged into a USB hub.
jalves wrote:
I was on 10.13.2 before the upgrade. That's the only thing I changed - (the upgrade to .3). I've experienced the same issue at times using 10.13.1 & .2. Just to further muddy the waters, there have been some restarts than didn't require the unplug/replug exercise.
sarahcat wrote:
“After a couple of possible security exploits, I upgraded to High Sierra for my Mini running Indigo. The Gen5 Z-Wave interface initializes perfectly, but my Insteon Dual Band MODEM now requires the USB connection to be physically unplugged and ‘re-plugged’ when I restart the Mini, after the High Sierra MacOS install.
The behavior appears consistent and repeatable, so far. I’m using Jay and Matt’s favorite USB2 hub.
Updated to MacOS 10.13.2 and USB Serial Issues started immediately.
Reverting the MacOS did address the USB Serial failures, so 10.13.2 is clearly broken.
Error resending previous command (failure response)
Error unknown command bytes received 0E 01 (ignoring)
Error resending previous command (busy or unexpected command)
Error resending previous command (failure response)
Error unknown command bytes received 0E 01 (ignoring)
Error resending previous command (busy or unexpected command)
Error resending previous command (failure response)
Error unknown command bytes received 0E 01 (ignoring)
Error resending previous command (busy or unexpected command)
Error resending previous command (failure response)
Error unknown command bytes received 0E 01 (ignoring)
Error resending previous command (busy or unexpected command)
Error resending previous command (failure response)
Error unknown command bytes received 0E 01 (ignoring)
Error resending previous command (busy or unexpected command)
Error resending previous command (failure response)
Error unknown command bytes received 0E 01 (ignoring)
Error resending previous command (busy or unexpected command)
PeteVis wrote:
Over at the SecuritySpy forum, users are warning about High Sierra.
Apparantly when locking the screen (as you would with i.e. a headless mac mini server where Indigo runs), High Sierra stops processing apps that are running in the foreground or background.
Maybe it's a bug, or maybe a feature... but it could be a big problem for users like me who have Indigo on a seperate Mac tucked away in the closet...
MFi (and HomeKit) remains a hardware accessory program, and software authentication is merely an alternative to existing hardware authentication mechanism ("authentication coprocessor") that's presently required within a HomeKit-enabled hardware accessory. Software authentication doesn't expand HomeKit beyond the hardware accessory realm.