This is strange because nothing should have changed in this regard between the previous version (4.2.9) and the current version (4.2.10). I've just tested this with 4.2.10 and can't see any problems, it just works for me.

The only thing I can think of that could cause this is if you have Schedule Overrides in place, that are overriding the schedules you are attempting to set via AppleScript. Try selecting "Clear All Schedule Overrides" from the Control menu in SecuritySpy, and then trying your scripts again.

If this doesn't resolve the problem, could you both please grab the previous version and compare them side by side to confirm that there is definitely a difference between versions? You can obtain it here: download SecuritySpy 4.2.9.

As for the camera numbers, you can get these from the Camera Info window. Click on the header bar (where the column header names are shown) to get a menu to add the relevant column. The camera names will not change between SecuritySpy updates.

Sometimes when there are two versions of an application installed, AppleScript gets confused about which one it should send commands to. Could this have been possible in your case - did you have two versions of SecuritySpy on your Mac? Ideally you should make sure there is just one version of SecuritySpy, in the Applications folder. I can't think of anything else that might have caused this problem.

Hello,

The same for me with the following script where only the shell script was working (Mac OS 10.13.6, camera D-Link dcs-5020L). it was running perfectly on version 4.2.9 that had been previously deleted:

property thePath : "http://*****:********@imac.local:8000/++camerasetup"

do shell script "curl -d " & "'cameraNum=1&transformationMenu=2&mcCaptureMovieCheck=1&frontCheck=1&resetTimeText=5&action=save' " & thePath

tell application "SecuritySpy"
ptz preset3 camera number 1
delay 7
set sensitivity 50 camera number 1
set schedule "Armed 24/7" camera number 1 mode Actions
end tell

No error message displayed.

Noting that the new version was not working properly, version 4.2.9 prefs files have been cleared (but I'm nor sure that all prefs files have been erased) and 4.2.10 reinstalled and configured identically but not working again.

So, I've downgraded (result all Ok) and reinstalled 4.2.10 and this time everything works. There may be something to see there...

I've been running 4.2.9 for over 24 hrs now and no issues with Applescript.

Ok

to complete the previous message: number -10006 from window 1

Just for MacOS reference, on the main SecuritySpy system I am running 10.13.6. On the view only system, 10.14.5. Both experience the same issue.

Any updates on this issue?

SS beta installed 5 minutes ago, for now everything works but I'm still waiting a few hours to restart the tests.
As for my window management script I simply exploited the dictionary of the application and did a little cooking with some information gleaned here and there and of course, I will try the new command.
Thank you

Great, thanks for reporting back!

Hello,
Re-reading my previous post proves that a vacation was well needed.
So we forget this model of nonsense and I make the thing clear in a future comment.
With apologies

The "soundMenu" and "scriptMenu" parameters require the whole file name of the sound/script, including the file extension, which you are omitting in your above script.

So, for example, if your sound is stored in the file "Hero.aiff" (which is the case for the macOS "Hero" sound that SecuritySpy makes available by default), then you will need to specify soundMenu=Hero.aiff as the parameter and value.

Likewise, the script file will normally have the extension ".scpt" so you will need to specify scriptMenu=Send_iMessage.scpt for that.