Hi,Thanks. just the standard temp from the Show 5 clock overlay.
WORD TO THE WYZE: Some (perhaps many) of us out here in the wild place higher emphasis on developing the app along these lines & existing feature set rather than adding things like person detection - the firmware for which didn’t (and still doesn’t) seem ready for primetime.
Slow it down, get it right. Why all the hustle?
Most likely app development and hardware development are separate teams. They can be worked at the same time.
True. However, person detection is also part of the app. I’d wager that they wouldn’t want to work too many angles of the app at once either for stability concerns.
Not fully understanding why the person detection was so highly prioritized and fast-tracked. I understand its potential value, but it feels a little more like gravy than substance vs beefing-up the shortcut options.
And if both can be worked at once, why has this languished with such an extensive list of very useful suggestions? I feel like many of them are low-hanging fruit & easy adds since the base features, themselves, already exist within the app. Additions outlined in these wishlists would truly be force multipliers to make Wyze much more powerful overall.
Of the suggested additions, these are of the most interest to me:
- Turn Motion Tracking on/off
- Detection zone on/off
- Pan Cam: move to a specific camera memorized position or waypoint
- Toggle notifications for Wyze Sense sensors (by sensor and event type)
- Toggle Sensor Video recording for Wyze Sense sensors (by event type) [by sensor implemented]
- Disable/Enable Person Detection
#3 is actually mine and would free-up manual intervention considerably for me!
I would like to add one more - Record a video to the SD card (like and event when recording events only).
I added it to the list at the top.
Loki, what about the ability to nest shortcuts as well?
I can see the concept of very simple shortcuts embedded within more complex ones… would eliminate the need to duplicate steps.
I think hierarchical or nested shortcuts would be a new/different topic for the #wishlist. If you wouldn’t mind writing that up, including a detailed example, and submitting it, we will probably accept it as a new #wishlist item.
I’m the proud owner of a set of wyze cams, sensors and bulbs. I want to use these as both automation and security products (I’m aware of the security disclaimer).
It would be ideal if we could have profiles for changing the settings of all these products at once with a click of a button (not only the cameras). Example of 2 profiles:
- Away profile (security functions important): a) bulbs vacation mode on, b) sensor triggers notifications + all lights to switch on + all cameras to start recording, c) smart plugs off or on, etc.
- Home profile (focus on automation, not security): sensors trigger lights to switch on but don’t trigger the cameras to switch on and start recording or send notifications, etc.
All you need to do is to add profiles buttons in the home screen to switch easily from one to another as well as the option of allocating a shortcut to one or more profiles.
You can already do this. What you are calling a profile is called a shortcut button. Create one for Home and one for Away. I think what’s either missing currently or from the proposed list at the top of this topic is the ability to enable/disable other shortcuts based on the button. I’ll add that to the list at the top now.
Thanks @Loki. Currently actions can only be triggered by one event per shortcut. If you want another event to trigger the same or another action you need to set another shortcut. What I suggest is that a set of shortcuts can be grouped into a profile (or whatever you want to call it). This way you can activate/deactivate a group of shortcuts with a click of a button.
This one please.
I’m still a bit confused about what you’re asking for. It’s true that only one event can trigger a shortcut. But you are not talking about event-triggered shortcuts. You’re talking about button triggered shortcuts, and these can have multiple actions associated with them. So one button for Home could trigger one bunch of actions and another button for Away could trigger a different set of actions.
I feel like I’m still missing something. What is it?
As we know Wyze cams are sensible to bugs, so personnally I am lowering the sensibily of the cams on the evening and increasing it the morning. This prevent me from having too much “flies&bugs” alerts. As I don’t want to only rely on the “person” algorythm because it is not 100% reliable (cars,animals,etc) to filter the notifications, I found out this was the best in my case. It would be amazing if the rules would exist in the app, allowing to set the sensibility in regards of the time. What do you think?
Holding off on further input here with the advent of the scheduler. Quite likely that things I’ve had in mind to nest will come to fruition by other means.
Would it be possible within the device trigger rule for actions to add a call to an html/https address with various optional parameters. This would allow for greater flexibility to control other non-Wyze devices, better reporting and a great deal of flexibility for the future.
I have added this request to the list at the top of this topic.