Don’t forget to scroll down and specify how many rulesets you want to enable. Once that is done make sure you also click the option to setup the ruleset values.
Now fill out the values as shown in this example. This is the configuration for the first ruleset on my mode for Armed/stay. It uses the camera for motion and audio detection. It records on the same camera for 120 seconds
Some very minor updates were posted today.
- Found a value that was incorrect as part of ruleset 5 that would prevent notifications from working. That has been corrected.
- Added logging to help identify what rule sets are active in live logging.
1 Like
Just FYI Guys. It appears that there is some kind of SSL Handshake problem going on with the Arlo cloud right now with partner integrators. As of around 3:50am est this morning i stopped getting recordings into my library due to the issue. I have added this to a ticket with Smartthings and am going to expand my thread on arlo’s website there shortly. But this will prevent any recordings from being triggered.
This also impacts the Health check Smartapp as well. All of mine have be failing since that time as well.
The issue seems to have been resolved.
@Mavrrick58 - why is the IFTTT fix required to execute the camera ready check? I can’t save without inputting a value but I don’t use IFTTT…so maybe this won’t work?
It is required because it was one of the integrations I know of that can trigger arlo recordings externally. The IFTTT integration is what corrects the camera state once it gets messed up. Otherwise it would just tell you when it happens and then you would have to corrects it manually.
For all practical purposes it is just a virtual switch/button that is activated when the problem occurs. It doesn’t have to link to IFTTT as long as you link it to a service that can trigger a recording to the arlo cloud outside of Smartthings.
One note about your image. The check time value is the amount of time passed before validating the camera returns to a good state. I believe based on what you entered above you are thinking time of day. So you generally want that value to be just a bit longer then you have the length of your camera set to record. I have my cameras set to record for 120 seconds when an event is triggered. I have that value set to 130 and then i have the lower value which is just a validation that it was actually set to 30 seconds The idea being giving IFTTT enough time to actually fix it.
Okay, gave it a try and still no luck with actual recording.
Setup two (wireless) cameras and three different ST modes. Went to Arlo, switched to the “Smartthings” Arlo mode. Both cameras were set to do nothing when motion was detected. Not possible to uncheck all notification boxes per the Wiki instructions. So, I checked push notification and used settings to block them on my phone.
First Mode Away, (ST Away, not SHM) Activate Both Cameras, Triggers were Away Mode, motion on either of the cameras, opening one of the door contact sensors, or motion on one of several sensors. I have it set to activate several lights and a switch that plays a message so I know it has run. Action is to record and selected both cameras. I did not check general rule. Do not know if this worked as I had no events in away mode.
Second Mode Home, Deactivate both cameras. Only trigger is Home Mode. No actions. This appeared to work as both cameras were indeed off when I was at home.
Last mode Night. Activate outside camera, inactivate inside camera. Triggers are Night mode, same other triggers and actions as away mode (but I removed the inside camera as a trigger and only record on the outside)
Night mode appears to have turned off inside camera, and left outside camera on. I received the alert message that I had set on the switch telling me that activity was being recorded. However, when I went into Arlo - No recording.
All of the modes were listed as 1 ruleset. Keeping it simple as I can until this gets up and running.
Also have the keep alive time set at ten seconds longer than recording times(record at 120, keep alive at 130), and the refresh at 15 seconds.
I had to delete the automation and revert back to using my IFTTT integration that was at least arming and disarming. I will just have to deal with the not being able to exclude the inside cameras at night until the bugs get picked out of this app.
I will try your exact scenario in a bit.
When I have been doing my testing with what defines the mode all of my initial testing has been with the Smartthings location Mode. So that should be triggering fine and seems to be since you indicate it did trigger for the other two modes fine.
The lack of recording could be based on the specific camera’s you have as I only have two different models to test with. Which specific cameras and base do you have. The recording routine has been very well validated as I have had it much longer then Arlo Assistant has existed.
To validate this suspicion though I would need log information from someone with the other cameras. If you could create a rule, test it while collecting live logging from the IDE and then share that with me I should get a better feel for what is going on.
My Arlo Pro 2 and Arlo Q cameras record all day long with Arlo Assistant driving the recordings. So there is no doubt it does work. I just know I can’t test every condition. If you can give me that logging information hopefully I can fix it in short order or atleast provide a reason for why it isn’t working if I can’t.
I had something similar happen. I had Arlo Assistant turning off and on different cameras for different modes but was not getting any recordings except for two cameras. I finally discovered that the Mode that SmartThings created in the Arlo App only had 2 cameras in it. I setup the other cameras and all is well now.
Not the issue here. I double checked that when I verified that the cameras were set per the wiki (Kinda anal with my checklists) The cameras are all in my mode, and all are set to detect motion, do nothing, and push notify as you have to chose at least one notification option.
Will give that another try as soon as I get the chance. I have family coming in this weekend for an even, so may not be for a week or two.
For the record, I have a virtual switch that triggers the cameras to record through IFTTT. THAT works. I may just use that switch to use your app and trigger recordings.
Which arlo cameras do you have. There are 7 different wireless cameras. The original Arlo, Arlo wire free, Arlo Pro, Arlo Pro 2, Arlo Q, the ARLO Q + and the newest Arlo Ultra. I know not all functions are avaliable on all cameras. Also what base do you have.
FYI
Not really related to your smart app, but I had an issue with my Arlo mode changing by itself. From armed to to disarmed (or vice versa. ) I fixed it by getting rid of my official Arlo integration with Smartthings.
Hello, I try to run since launch but I need help. I have 2x Arlo Pro configured in the Arlo app to detect motions, do nothing and send me an email to a fake address. I created some modes and I receive SMS when there are movements… However, nothing is recorded …
I have the following log:
debug Sending SMS to ***********
debug Alarm Notification., ‘Mouvements Cabanon’
debug 197137
debug Sat Jun 22 03:02:07 UTC 2019
debug Camera is active and recording can not be submitted.
debug Ruleset 1 event
I created my fix with IFTTT because I already had problems but now I am running out of solution. I also have an Arlo Q but I have not tested it yet.
What can I do more?
Thanks
The line below indicates where the issue is.
That line means the camera method has identified that the camera status is still in initiated state and so it will not submit another recording. This is by design because until the camera is back in Completed status new requets to record will be ignored by the device handler in Smartthings. So there are 2 possibilities.
- It is valid and you should be able to look further down in the live logging and see a message like “Camera is not recording. Submitting clip to record.” It will also be followed by “Sending cameras message to record with xxx second capture”
- The other option is the camera clipStatus state is bad as it didn’t update after a recording back to completed. This happens far too often in my opinion, but it is what it is. The Camera health fix app is intended to correct this automatically once you got everything setup.
You can confirm if it is a bad state or not by opening up the device from the IDE and then reviewing the status of the camera. The steps would be once in the IDE Click on “My Devices” across the top. Scroll down the list and select the camera you are wanting to check. Then scroll down the page until you can review the “Current States” section. The last state in the list will be clipStatus. Click on that and it will show you how it has been changing recently. If everything is good you will see where it cycles between “Initiated” and “Completed”. If the last entry is “Initiated” and it is more then a few min ago then it is in a bad state.
You can fix that by either flipping the switch/button for the Camera Health Check, or by going into the arlo app and doing a manual recording. It may take more the one time to fix it as well. If you are using a switch instead of momentary button, make sure you set something up to flip the switch back off.
Thanks but I don’t hate the clipStatus State 
I use the default Arlo Pro Camera DTH
The Health check seems to work because when I activate it, it activates the movement on my camera and triggers the mode. I receive the SMS and IFTTT makes a recording of 10 seconds.
That is interesting.
Here is what I see when looking at the current status’s for my Arlo Pro 2’s
And this is what I see on my Arlo Q cameras.
Both of the have them have status’s for the clip. I also looked at the option for DTH for the cameras and there is no Arlo Pro 2 device handler. Just Arlo Pro which is what I am using. I will do a test with the original Arlo Pro Device Handler to see if it shows difference.
I have added a line to the program to add additional logging around the clip status check. I would expect the program to fail completely if that value was completely missing. Please check the live logging again and let me know what it shows for the current Clipstatus when it runs. I wonder if it is returning a default value somehow even though the state isn’t present. Once i have that info I will see about coding around it. I may need you to help me validate as you can see in my previous post I don’t have this condition with my cameras.
debug Not enogh time has passed. No notification is sent
debug 47208
debug Sat Jun 22 15:25:18 UTC 2019
Camera is active and recording can not be submitted.
debug Camera Status is null
debug Ruleset2 event
Do you use or have custom DTH?
FYI… No clipStatus on my Arlo Q too 