If you’re currently running Android beta 3.1.0.b535, it’s a 2-step process. The Play Store will 1st update your app to production 3.0.0.519, then you’ll need to recheck the Play Store for an update and Android beta RC 3.1.0.b560 will show up.
It seems the only difference is you can now set a schedule for what hours of the day the warning is active? I don’t think that was there before this update.
I am on 3.0.5 558, still no 3.1 for me.
FLP firmware changer my recording warning from a melodic tone sequence to the voice saying you are being recorded.
No way to change it from one sound to another now, just on or off.
That bites a bit. In a neighborhood where neighbors walk by, the time in not too offensive, but the lil ole ladies don’t like the voice when they walk their own neighborhood, and I understand.
Trying to access my cams on two different devices (iPhone, iPad) this morning. The v4s are throwing a “Request Failed” and when I try to refresh the cam list I get “oops, try again” message. Tried on my second device that wasn’t setup for the latest app and after authenticating, it won’t pull the list of devices or favorites. Automations are there.
Also noted the v4s are generating events even though I can’t click on the devices without a request error.
Anyone else seeing odd things? Me thinks something is going on on the service side once again…
UPDATE: reverted both apps to non-beta version and problem goes away. Re-installed 3.1.0(5) and the problem returns
I went through all of my cams on the beta app and I have a third, a V3 is also doing it. Rebooting cams have no effect. They still produce events but cannot go live. Again, reverting to release version works.