This object is in archive!
Send Message
Need Answer
I've been playing around with a simple rule that sends a message based on an action. I've added myself as a contact and tried to create the attached rule. Every time I hit save, I get this message:
rule2java: java.lang.IllegalStateException: Expected BOOLEAN but was NUMBER
Anyone know what's causing this problem?
Files:
Send Message.JPG
The same question 
No connection
Real-time notifications may not work
Hi,
can you please show us the configure Tab from the send Message block?
regards Helle
Hi,
can you please show us the configure Tab from the send Message block?
regards Helle
Absolutely. I tried both email and SMS and get the same message with each. I wasn't able to find anywhere to enter my SMTP server settings, so I'm guessing it gets sent by the Zipato servers, but I can't find much documentation on the messaging aspect.
Absolutely. I tried both email and SMS and get the same message with each. I wasn't able to find anywhere to enter my SMTP server settings, so I'm guessing it gets sent by the Zipato servers, but I can't find much documentation on the messaging aspect.
Hi Nathan,
to send SMS you need to buy some credits, because Zipato has to pay for sending sms.
Just try to send push messages.
http://zipabox.de/pushnachrichten-direkt-von-der-zipabox/
regards Helle
Hi Nathan,
to send SMS you need to buy some credits, because Zipato has to pay for sending sms.
Just try to send push messages.
http://zipabox.de/pushnachrichten-direkt-von-der-zipabox/
regards Helle
Thank you for the link. Is push free?
Where do I buy the credits? I was looking at what you can purchase through the web interface, like Advanced Rule Creator, Global Cache, etc. The only one I can find that would be close, would be the Messaging Pro, but that doesn't say anything about SMS messaging, only HTTP and Socket.
Thank you for the link. Is push free?
Where do I buy the credits? I was looking at what you can purchase through the web interface, like Advanced Rule Creator, Global Cache, etc. The only one I can find that would be close, would be the Messaging Pro, but that doesn't say anything about SMS messaging, only HTTP and Socket.
Just aks the Support for Credits.
The others things are free.
regards Helle
Just aks the Support for Credits.
The others things are free.
regards Helle
I can't seem to get Push or Email to work correctly either? Are you sure you don't have to pay for them as well? I keep getting the same error.
I can't seem to get Push or Email to work correctly either? Are you sure you don't have to pay for them as well? I keep getting the same error.
I found you have to be both a user and a contact for emails and sms to work. But SMS is a paid service now. Push should work fine. I have them all the time.
Not sure what the error message is, but you should lodge a ticket here for help http://support.zipato.com/index.php?/Tickets/Submit
I found you have to be both a user and a contact for emails and sms to work. But SMS is a paid service now. Push should work fine. I have them all the time.
Not sure what the error message is, but you should lodge a ticket here for help http://support.zipato.com/index.php?/Tickets/Submit
I have also seen the same error you mention and I think it is a bug in the rule generator.
I have found the following that seems to work:
a) Drag out the blue (SENSOR) puzzle piece back to the work surface
b) Re-apply the action (in your case "MOTION")
c) Drag the blue (SENSOR) puzzle piece back into the WHEN statement
d) Save the Rule
My assumption is that the SENSOR puzzle piece does not initialise correctly then incorrectly reports a NUMBER to the WHEN statement when it should be reporting a BOOLEAN.
As a faster workaround, I have found also that just resetting the action in the SENSOR piece (i.e. MOTION for you) will also work.
Best regards
/Marcus
I have also seen the same error you mention and I think it is a bug in the rule generator.
I have found the following that seems to work:
a) Drag out the blue (SENSOR) puzzle piece back to the work surface
b) Re-apply the action (in your case "MOTION")
c) Drag the blue (SENSOR) puzzle piece back into the WHEN statement
d) Save the Rule
My assumption is that the SENSOR puzzle piece does not initialise correctly then incorrectly reports a NUMBER to the WHEN statement when it should be reporting a BOOLEAN.
As a faster workaround, I have found also that just resetting the action in the SENSOR piece (i.e. MOTION for you) will also work.
Best regards
/Marcus
Thanks Marcus. That work around allowed me to create the rule. I'm at work now, so I'll have to wait until my wife walks in the closet to see if it works. But the rule no longer shows as "Invalid" when I look under "My Home Rules".
Does anyone know where you buy SMS credits?
Thanks Marcus. That work around allowed me to create the rule. I'm at work now, so I'll have to wait until my wife walks in the closet to see if it works. But the rule no longer shows as "Invalid" when I look under "My Home Rules".
Does anyone know where you buy SMS credits?
You purchase SMS credits on the Control Center. When the Control Center opens, click the icon on the left that looks like a wallet.
You then have a link to "BUY CREDITS"
you can buy credits in batches of 5, 25 or 100
Each credit is one US Dollar value
A single SMS message costs six hundredths of a Credit (0.06)
Have fun!
/Marcus
You purchase SMS credits on the Control Center. When the Control Center opens, click the icon on the left that looks like a wallet.
You then have a link to "BUY CREDITS"
you can buy credits in batches of 5, 25 or 100
Each credit is one US Dollar value
A single SMS message costs six hundredths of a Credit (0.06)
Have fun!
/Marcus
Replies have been locked on this page!