Today, we have an update for Wyze Wi-Fi Chime. Firmware version 1.0.043 adjusts the default volume and brings a few bug fixes.
Read our Release Notes
https://go.wyze.com/releasenotes
Today, we have an update for Wyze Wi-Fi Chime. Firmware version 1.0.043 adjusts the default volume and brings a few bug fixes.
Read our Release Notes
https://go.wyze.com/releasenotes
I’m curious what these 2 updates are (copied from the release notes page):
- Increased the number of cloud command records to 30.
- Set the maximum number of OTA retry attempts to 10.
The first one, is that a rate limit? Like 30 commands per x amount of time? Like is that a limit of 30 times per day? 30 times per hour? If there are more than 30 commands, the device just refuses to chime or run the automation?
Just trying to understand. While I realize that it’s unlikely someone is having their doorbell button pressed 30 times in a day, people also use these for other detections too. For example, if you have it make a sound every time it detects a package, but you’re not home, and the wind instigates a new event every 2-5 minutes from waving branches, it could detect the package 30 times in an hour, and then you won’t get any more sounds for the rest of the day (assuming this is a daily rate limit). Or, I have my DCDB cause this to chime with a bird sound anytime my cats are on my porch, so if my cat sits on the porch for a couple of hours, it’s possible to drain my entire rate limit for the day now? Do I understand that correctly?
If so, does that mean if I block the firmware update that I won’t be subject to that new unwelcome rate limit?
I’m just speculating here—and I absolutely agree that definitive detail directly from Wyze would be appreciated—but I interpret “cloud command records” as the number of entries a user would see in the app when navigating to Automations ➜ Automation History. Maybe prior to this update there was a limit to how many Automations Actions or Triggers involving the Wi-Fi Chime were actually stored and could be retrieved for review by users checking their Automations logs for troubleshooting? That’s what I infer from the Release Notes, anyway, particularly with respect to “records”. Like I said, though, I’m just guessing here.
That makes sense. I suspect and hope you are correct. there is no need to store more than the last 30 commands in the records (needlessly wasting AWS storage costs for something that has no income to offset it). Still would be nice to have that clarified. ![]()
Oh, yeah, for sure I’m always in favor of more clarification and better details in the communication from Wyze. I’m just wondering if maybe they had the Wi-Fi Chime purging older Automations log entries at an artificially low limit and decided to raise that with this firmware. ![]()