I installed the garage door cam kit. I mounted the camera on the ceiling behind the opener. I set the unit to close the garage door at 10 pm each night. A couple of times the door didn’t close. I rescanned the QR code and that seemed to fix it. Now last night and tonight the door didn’t close at 10. Any ideas on what could be causing this .
Rules/automations won’t run reliably if the wifi signal is weak. Does the cam have a good signal?
The automations are stored in the cloud and sent to the camera/controller at the given time, if there is a communication issue at that time, it won’t happen. It would be nice if Wyze would work on some sort of confirmation that the rule actually ran, and if not, try again, but that doesn’t currently seem to be the case. Try repositioning your router or tweaking your wifi to try and get a better signal to the cam.
I have a mesh system and one of the repeaters is near the door to the garage. The signal seems to be fairly strong at the camera. I had to camera on the opener but moved it to the ceiling to be sure it didn’t lose the qr code from vibration. Would it help to increase the size of the qr code?
If there is a node near the camera, the camera will see a good signal. The question is how is the signal between the node and the main mesh router?
Increasing the size of the QR code won’t do anything, that is only used when you add the camera to your account and it sounds like that is working fine.
I don’t think that’s accurate. I believe @vstensland is asking about the QR code sticker included with the Garage Door Controller:
Why is there a QR code sticker in the materials?
Your Wyze Cam v3 uses the QR code sticker and AI technology to detect the open/closed status of your garage door. This allows us to provide features like garage door notifications, door event history, scheduling, etc.
This is not the same as the QR code generated by the app when setting up/adding some Wyze camera models to an account. Wyze even sells replacement stickers.
I don’t have any direct experience with the Garage Door Controller, but my understanding is that the camera’s ability to view and read the QR code sticker is more for generating status (open/closed) notifications than for initiating actions (though you’d think that the system might be smart enough to do a check—“Can I see the QR code now, before I execute this command that’s been requested at this time?”—instead of running on a “dumb” schedule, but I don’t have any insight into the logic used by that process), so I wouldn’t necessarily expect the size of the sticker to be an issue.
I’m in the same camp of wondering about the signal getting all the way from the cloud to the camera and controller at the time the Automation is supposed to run. I also wonder about the status of the firmware on both the Garage Door Controller module and the Cam v3 that’s being used in this installation. I’d be inclined to check/update those, schedule tests at different times, and then submit a log (followed by a Support ticket that includes the Log ID) whenever the issue can be replicated.
Ah, my bad. In that case, maybe it would help, but I also don’t know what process all the systems involved use to verify the action has completed (if it has).
However I’d think if the door hasn’t closed, it wouldn’t see the QR code anyway so the size wouldn’t matter? I guess maybe in the meantime @vstensland could set it to close it at 10PM and 10:05PM, if it sees the code it won’t run the second one since it knows the door is closed? That assumes there is some sort of logic in it to know if it is already closed or not.
I like the idea of this sort of test, because then @vstensland could check the Automation History to get an idea of what happens when the later “close” Schedule is supposed to run. I’d be checking the Automation History anyway, because that should give an indication of success or failure, but scheduling two “close” operations back-to-back has the potential to provide more data points.
I check the history back to installation. It says closing was successful each night. There have been probably 4 times it didn’t close . Also It doesn’t appear to allow me to add another close command at 10:05. Not sure where to go from here. The google mesh repeater is about 25 ft from the main one and probably 25 ft to the camera from the repeater. Would think that would be close enough. My house is not very big.
1 Like
That’s a bummer, but since I don’t know where in the app these are set for the Garage Door Controller, I’m not sure what else to specifically advise. If you can set up the “close” operations using Schedule type Automations, then I wouldn’t expect that to have any sort of restriction at all, but I don’t have hands-on experience with this product.
I guess where I was going with my thinking before is scheduling some “close” operations at other times—morning, afternoon, whenever you have some time and proximity to your garage door—just to see if you can replicate the failure, and then I’d do the log and ticket immediately after that, trying to give the engineers a reliable point in time to look at for troubleshooting the problem.