Same here got 3.2.3 after someone mentioned/ had the 3.5.0 update that is supposed to fix things, why on earth push out updates that don't help is beyond me?Tha_Matt_Man wrote: ↑09 Nov 2021, 15:03 Just now one of my 4 camera's got an update. Version 3.2.3 now.
Why not 3.5.0 as with the persons above... No idea...
Lousy detection after firmware update (3.2.0)
Re: Lousy detection after firmware update (3.2.0)
Re: Lousy detection after firmware update (3.2.0)
Interesting, I have Google nest WiFi mesh. Also in contact with Support. I have 3.5.0 on both cameras, but that has not solved the problem. HomeKit still doesn’t work for me
Re: Lousy detection after firmware update (3.2.0)
I guess they push firmwares for people who contacted their support line. Everyone else (the non-complaining standard user - who might not even be aware of such issues) will get updated on the main update cycle.
Re: Lousy detection after firmware update (3.2.0)
In my case, I can confirm this assumption. My support request from two weeks ago has led to the update of my camera to 3.5.0. The feedback was in general, that firmware updates are deployed differently to customers to address the specific issue. Depends on what the initial support request stated as the problem.
I also received the info that preventing automatic updates is not possible, as the camera establishes a VPN connection to the servers. The VPN connection has some kind of dependency to the firmware, which from my understanding seems to be by design / on purpose.
V3.5.0 does not seem to have anything to do with the issues of HomeKit Secure Video.
Re: Lousy detection after firmware update (3.2.0)
Not that a proof is needed, since so many users complains. But nevertheless here is one.
I have a screen with live streams from all of my cameras. So I can see if something is moving.
This evening UPS came. I saw the driver on both cameras which are installed in the entrance area (blue and green frame).
But on the app the driver appears out of nowhere in front of the doorbell (red frame).
Between 17:41 and 17:45 none of the cameras reports the arrival of the UPS driver. The person (17:41) in the blue frame is my wife and my dog.
At least one of the cameras (green frame, 17:45) detect him leaving.
The person in the yellow frame (17:46) is me after the UPS driver has gone.
I have a screen with live streams from all of my cameras. So I can see if something is moving.
This evening UPS came. I saw the driver on both cameras which are installed in the entrance area (blue and green frame).
But on the app the driver appears out of nowhere in front of the doorbell (red frame).
Between 17:41 and 17:45 none of the cameras reports the arrival of the UPS driver. The person (17:41) in the blue frame is my wife and my dog.
At least one of the cameras (green frame, 17:45) detect him leaving.
The person in the yellow frame (17:46) is me after the UPS driver has gone.
-
- Posts: 25
- Joined: 16 May 2019, 09:59
Re: Lousy detection after firmware update (3.2.0)
Confirmed, the one camera that's already on 3.2.3 fixes nothing at night...
Let my dog out en walked myself in front of the camera. Floodlight went on but NO recordings. Nothing at all...
Still useless on 3.2.3..
EDIT: also contacted Netatmo support now
Let my dog out en walked myself in front of the camera. Floodlight went on but NO recordings. Nothing at all...
Still useless on 3.2.3..
EDIT: also contacted Netatmo support now
Re: Lousy detection after firmware update (3.2.0)
After update 3.2.0 only detetection of animals at night. They updatet my camera to 3.2.3 and now after darkno detections at all. What are they doing by Netatmo?
Re: Lousy detection after firmware update (3.2.0)
Firmware 3.3.5 reverts the camera to what it was before 3.2.0.
-
- Posts: 25
- Joined: 16 May 2019, 09:59
Re: Lousy detection after firmware update (3.2.0)
I'm still on 3.2.0, despite contacting Netatmo a week ago. Somewhat frustrating.