I’ve been looking at the forums and I’ve been searching the WIKI for over a week and I can’t find a "beginners tutorial anywhere.
I would like to learn how to :
have the motion sensor send me an email or text when I’m not there and it is tripped?
have a water sensor send me an email or test when it is tripped.
and most importantly run a test to see if it actually sends a text of email.
or where to find expanded screen shots of u12 screens that are set for the most basic functions as examples to follow and learn from.
(for example "here is a screen shot of a scene named xxxxx where the motion sensor sent to email when tripped…and here is what the email notification looks like in findvera
Everything I have is paired and working I just need to understand events scenes and commands so that I can teach myself the functions.
I realize that having something this flexible makes it more powerful but unless you can start somewhere it is impossible to grasp the basics.
Please help because I love the idea of this it is just really too hard to come in with no frame of reference and be very successful with the produce (particularly with all the interface discussions going on right now).
P.S>If the WIKI is suppose to be an online manual it either really suc?s or I don’t know how to use it.
Note: you must setup a user for Vera first. This is done from the Users tab on the UI. Enter a name and a password, then add an email and phone number.
Add a Scene, then add an event to it: select from the Device drop-down list the motion sensor, then select the event type “An armed sensor is tripped”, name the event and for the Tripped, select “Yes”. You must also check which user to send notifications to.
Thanks Mcvovidiu for replying and I have set the sensors in scenes as you suggest but your Test Sequence link makes no sense to me???
It appears to be setting up and programming a trial system. Then it offers web links for testing to a web sequence and I don’t understand where to input.
All you have to do it copy that link into your browser’s address bar, replace “ip” with the IP address of your Vera and hit enter. What you want to test is that the scene will respond to the sensor being tripped, clicking a button in the UI would only test that the scene runs when it is specifically told to run. Faking the sensor trip is a better test.
Thanks again for the reply…I’m remote from my vacation home and using findvera to program and look at my system…can I use the local ip address that is assigned by my home router? or do I have to wait until I am back at the home?
I am doing lots of reading but for a new user what may be obvious to me in a week or two is not now.
You guys have done an excellent job developing and constantly evolving this system so writing a user manual on the fly while you keep improving the system I understand is very tough…but for reference you could use some sample screen shots for basic training of common scenes and events and leave the “loop a doodle” and “Luup me up” stuff for an advanced section.
Seriously, we all can grasp that you have hundreds of spinning plates going, so don’t get discouraged you have a nice group of users both slow like me and advanced that see the promise in your system.
@Sball. On the test sequence page there are information how to control Vera through URLs through findvera.com also. You must put after https://ra1.findvera.com ( or ra2 ) the username/password and then the rest of command’s URL.
@shady. We had that available on UI2 but for the advanced usage, it doesn’t make a lot of sense, as you may want to copy/paste some Lua or URLs to test something.
@mcvovidiu Thanks, I never saw the videos in UI2, unless you are talking about the Lady in the corner of the screen. I was talking about maybe having some video screencasts of someone actually clicking through the steps in the actual UI. You’d still have the wiki page for copy/pasting of URLs and code.
I’m not sure where you’re stuck. I have my driveway motion sensor set to email me when it senses motion while it’s “armed” and it works consistently. See attached. You need to set up users in the Users section and enter their email addresses, but after that it’s easy to turn notifications on or off in the Scene.
Maybe you’ve done this and it’s really a matter of getting Vera to talk to MCV’s servers?
Thanks Rancho that is how my scene looks and all I’m trying to do is test the sensors email capability remotely…I have set up users and keep checking notifications in findvera after folowing the above advice: No luck
I have two devices I am trying to test and they are both paired and seem to be working as they should
A HSM 100 that reports to be device(when you open the + by the battery icon) #9 node id 5; the Motion part #10 id 1; Light sensitivity #11 id2; and temperature #12 id3
I also have a water freeze sensor that is working showing a temperature it is Device #4 and node # id 3.
I’ve tried many combinations with the URL provided by your support documents and emails and am now getting the 503 message…and I can’t find any explanation what that error means.
With my own username and password for the xxxxxx/yyyyy which works perfectly on findvera
Using the 3451 port as suggested seems to be communicating but FYI I have vera set as a switch getting it’s IP from a existing router. In the advanced network settings I chose “through a gateway on my network and vera is a switch” and DHCP and vera was assigned 192.168.1.7 would that matter on this test?
Or perhaps it is how the sensors are set wrong…they are both set for default behavior and report temp and light changes. I’m 1000 miles away from my home and unable to test them locally but love checking in on the temp and camera. I just would like to be confident that they will send me a notification if they are tripped.
Best Home Automation shopping experience. Shop at Ezlo!