Zugg Software :: View topic

Posted: Mon Jan 19, 2015 9:45 am

When I input the following command, absolutely nothing happens. It is as though I didn't put anything through the command line. Any ideas?

#alarm {+1} {#ECHO HELLO}

Posted: Mon Jan 19, 2015 11:48 am

dont put the time parameter in brackets

Posted: Wed Jan 21, 2015 11:21 am

Interesting, I have always utilized the brackets when using #ALARM. Is this something that is incorrect with the documentation?

Posted: Wed Jan 21, 2015 11:30 am

its the only thing different from the syntax i use, other then making use of the id field

Apprentice Joined: 23 Aug 2013 Posts: 175

#ala "nameofalarm" {+1} {command(s)} {class|class|class|class|class}

works 100% of time... and thats for a one time alarm, for a permanent one, use {numberoftime} instead of {+numberoftime}

Novice Joined: 19 Nov 2006 Posts: 40

#ALARM {+@stunDelay} { #EXEC %db(@stunInfo, type) }

works for me in my stun loop triggers

I ran #alarm {+1} {#ECHO HELLO}

got the expected successful result.

In your debug, it appears you are running #alarm {+1.5} {#ECHO HELLO}

I don't think decimals are eligible numbers for the alarm time.

Posted: Wed Feb 25, 2015 12:09 pm

From the help files:

A normal alarm cannot match a time smaller than or equal to half a second, so the fastest-repeating alarm you could have would be #alarm 0.501 {commands}. These restrictions don't apply to one-time alarms. The smallest unit of time you can use is a millisecond.

So the decimal is not the issue.

Try creating the alarm in a blank package (just hit escape from the session selection window).
It won't save, but it will let you see if the issue is specific to the one package or not.
This will let us rule out a corrupted package file.

Otherwise... you may need to export to XML and start over with a fresh session.
Importing the XML on a new package file might be enough to fix it, but you may have to start over.