The release notes should’ve mentioned that 2.40 FINALLY has HMS status as trigger rules!!!
That’s even cooler than the extra pins (which I also like). I kind of wish we could have rules depending on what pin is entered. For example, if I change our PIN numbers for the HMS and someone tries to use the old PIN, or a neighbor or someone tries to use a temp pin you gave them months ago while you were on vacation to take care of your pets…but then their kid tries to use it months later or something, It would be nice to have it set off different rules. Just saying…
Also, now we need some new Rule Template suggestions/presets:
If HMS detects an alarm, Turn on siren on ALL CAMERAS too
If Cancels an Alarm (or switches to Disarmed mode), Turn off siren on ALL CAMERAS too
Those are things lots of people will want, so they should be ready made templates. Especially for those of us with dozens of cameras who don’t want to have to do it all manually.
In fact, I just barely went through and set it up so that canceling the HMS alarm or switching to disarmed mode always turns off all sirens. Then no matter why a siren is going off, anyone in my family can just go to the keypad or their phone and know exactly how to turn off all sirens. This is very useful just for that. (I have been using a dedicated contact sensor that will shut off all sirens, but I like these HMS rules better because I can require a pin).
I’m sorry but I don’t see the improvement. Can someone enlighten me, please?
From 39 to 40, I don’t see any improvements. For example, group view in iOS, both iPhone and iPad go to sleep/lock screen mode. That wasn’t fixed and quite a few people were asking for that to be fixed.
Again, in group view mode, the top two views are 100% but the bottom two rows are at 75%. Haphazard programming.
I’m giving up, I’m stuck with Wyze echo system for now and I’ll put up with whatever they shove down my throat. The question remains, how long?
Yeah, I was a beta tester for Adobe Illustrator from 1988 till 1996, and I never saw such a programming incompetence. Adobe took our feedback seriously. Looks like Wyze doesn’t give a hoot to our feedback. I have been reporting the same issue via the app over and over, and all is moot from Wyze. Why even have a beta program if they don’t listen to us. Wait, I know. They dump it on the user and see what happens.
I love Wyze cameras, that’s all I have and I’ll be damned if I go beyond that until they clear their act.
I’m seeing the app mis label the time of event videos. I’ll have events labeled 5 minutes in length in the events list but when I tap that event, it’ll only be 14 seconds for example. I tested this alongside the public app and it doesn’t seem to affect that one.
I use the beta Android app. Up until last week, I have always had to manually update to the new version of the Wyze app. And now, for the last 2 app rollouts, the last PROD update and this beta update, the app was auto-updated without my permission.
I would prefer to control when apps get updated. I thought I had that feature disabled and now I can’t find the setting on my phone.
Can anyone offer suggestions on why this auto-update suddenly started occurring?
THANKS! There must have been an Android update that reset those settings. It has been so long that I disabled the Auto-update feature, that I forgot where to find it. I was getting ready to do a search for that setting, so thanks for helping me out.
Another issue in the Beta App as it applies to the Rules building UI & Actions for the Thermostat:
When selecting the Thermostat for Actions, if I choose Turn On Heat Mode, the Turn On Off Mode becomes unselectable. This is good.
However, Turn On Heat Mode does not deactivate Turn On Cool Mode. Both can be selected.
In fact, if I toggle the three, I can get any two to be selected at any given time.
I can’t really think of any situation why two conflicting commands should be allowed to be sent at the same time.
Additionally, the Set to Home, Away, and Sleep can all be selected simultaneously. The app should not be allowed to program multiple conflicting commands. Once one is selected, the other two should deactivate.
The only set that does work right is the Notifications On\Off.