Go ping on the v2 PM. Same problem exists on the older cams. See my previous thread from a month ago.
Great, thanks. I had to downgrade a week ago to get the person detect to work
Looking good on my end! Thanks.
thank you for the update.
Not a beta tester, so no access to the new firmware, but will definitively be looking forward to it.
Glad to hear it’s going well.
DNS is still acting up. One cam is behaving ok-ish but the other is still screaming into the void. Please see my writeup in the Beta section and alert the v2 PM, please.
Also, the release notes for 4.36.0.252 don’t mention any DNS fixes.
My V3s have been behaving fine after the upgrade, only see request to api.wyzecam.com when I open the app. Not sure if this firmware was supposed to address this issue on the V2s as well.
So when is 4.36.0.252 going to be released to non beta testers?
How do I update to the new firmware?
Until it’s released to the general public - it looks like you’d need to be a beta tester:
Looks like 4.36.0.252 was just released per:
4.36.0.252 (February 17, 2021)
- Improved the recognition rate for microSD cards
- Added a turn off function for microSD cards
- Added an independent update function for the Spotlight
- Fixed a bug when switching Spotlights
- Fixed a Spotlight authentication failure bug
- Fixed an excessive DNS lookup issue
Thanks.
I have to thermostats but I am afraid to use them. …Had enough of amateur hour. I know the stuff is dirt cheap but I did not want another hobby of trying to keep Wyse crap running. Doesn’t work / intermittently works / used to work / reports to the chi-coms….geesh
Awe come on; misery loves company. LOL There’s no way I would use any WYZE product that is associated with or connected to a utility, such as heat, air conditioning, water, etc…
Issues with CAMs, sensors, fans, weather monitoring systems, maybe even a vacuum isn’t that bad (unless it catches on fire of course). The bulbs and plugs are iffy for me, but I couldn’t resist and broke down yesterday to order the new color bulbs. They look like a fun/cool toy!
Like I said, anything that could literally cost you WAY more $$ due to WYZE hiccups (using nice words here), I’m going to take a hard pass on all of it and advise my friends and family to do the same.
Ah but will you put the new smart switches in your walls? For me, if they’re not UL listed, no way. (Most all the cheap brands aren’t.)
Hmm, I’m not privy to the new smart switches. In my mind these will fall into that iffy category along with the plugs and bulbs. You have an excellent point. If they are not UL certified I don’t think I would take the risk of having that fire hazard inside of my walls!
For those who aren’t familiar with UL, check out their website:
UL Product Certification
No details yet…
My Wyze Cam v2 is doing something similar, but going to different sites.
*.kinesisvideo.us-west-2.amazonaws.com
kinesisvideo.us-west-2.amazonaws.com
aws-iot.wyzecam.com
*.iot.us-west-2.amazonaws.com
You can clearly see when I reboot the device and when it starts up again. I have tried reverting to older firmware, but that did not help
Yikes… that’s a ton of lookups. You’d expect the camera to pull the DNS lookup, cache it, and then respect the time-to-live (TTL) setting for the DNS entry.
kinesisvideo.us-west-2.amazonaws.com
origin = ns-1472.awsdns-56.org
mail addr = awsdns-hostmaster.amazon.com
serial = 1
refresh = 7200
retry = 900
expire = 1209600
minimum = 86400
Name: kinesisvideo.us-west-2.amazonaws.com
Address: 35.161.88.185
kinesisvideo.us-west-2.amazonaws.com nameserver = ns-1559.awsdns-02.co.uk.
kinesisvideo.us-west-2.amazonaws.com nameserver = ns-73.awsdns-09.com.
kinesisvideo.us-west-2.amazonaws.com nameserver = ns-601.awsdns-11.net.
kinesisvideo.us-west-2.amazonaws.com nameserver = ns-1472.awsdns-56.org.
aws-iot.wyzecam.com canonical name = a24rq1e5m4mtei.iot.us-west-2.amazonaws.com.
iot.us-west-2.amazonaws.com
origin = ns-407.awsdns-50.com
mail addr = awsdns-hostmaster.amazon.com
serial = 1
refresh = 7200
retry = 900
expire = 1209600
minimum = 60
a24rq1e5m4mtei.iot.us-west-2.amazonaws.com has AAAA address 2620:108:700f::3423:d8f9
a24rq1e5m4mtei.iot.us-west-2.amazonaws.com has AAAA address 2620:108:700f::36bb:2ef2
a24rq1e5m4mtei.iot.us-west-2.amazonaws.com has AAAA address 2620:108:700f::22d8:c791
a24rq1e5m4mtei.iot.us-west-2.amazonaws.com has AAAA address 2620:108:700f::23a5:d887
a24rq1e5m4mtei.iot.us-west-2.amazonaws.com has AAAA address 2620:108:700f::2ceb:ba17
a24rq1e5m4mtei.iot.us-west-2.amazonaws.com has AAAA address 2620:108:700f::2cef:8e68
a24rq1e5m4mtei.iot.us-west-2.amazonaws.com has AAAA address 2620:108:700f::2cf0:11c4
a24rq1e5m4mtei.iot.us-west-2.amazonaws.com has AAAA address 2620:108:700f::3423:4ff4
Name: a24rq1e5m4mtei.iot.us-west-2.amazonaws.com
Address: 54.148.175.241
Name: a24rq1e5m4mtei.iot.us-west-2.amazonaws.com
Address: 54.184.105.247
Name: a24rq1e5m4mtei.iot.us-west-2.amazonaws.com
Address: 54.191.177.212
Name: a24rq1e5m4mtei.iot.us-west-2.amazonaws.com
Address: 34.216.199.145
Name: a24rq1e5m4mtei.iot.us-west-2.amazonaws.com
Address: 44.224.13.135
Name: a24rq1e5m4mtei.iot.us-west-2.amazonaws.com
Address: 44.238.197.163
Name: a24rq1e5m4mtei.iot.us-west-2.amazonaws.com
Address: 52.34.105.245
Name: a24rq1e5m4mtei.iot.us-west-2.amazonaws.com
Address: 52.34.228.92
I’d have to agree - that behavior seems a bit aberrant.
I thought they said they fixed this with the last firmware update…???
I believe that firmware was for the v3 camera. I am using the v2 camera and I don’t believe there is any new firmware for it. If fact, I think they stopped people from using the version that was released back in Nov, due to a different issue.