Its not just on boot - it can also occur after the DHCP lease expires.
This is common on ESP8266 and many other IoT devices. As @teredactle stated, and I agree, it’s poorly written firmware that causes this type of issue.
I understand why Wyze does it. I agree that they should do it. I don’t agree that it’s acceptable or that they implemented it correctly. It’s poor coding and can easily be fixed by a knowledgeable developer on this topic.
I really hope this is the case (upgraded memory) and agree that it should not be a forked firmware that never gets updated. I tried the v2 but can really only run one camera because the connection becomes unreliable with more than one unit.
Under the heading of “some folks are never satisfied”…
Not only do I want RTSP support (for which I have cast my vote) on the V3 (of which I just ordered 2 for testing) I would also like to have ftp support for bulk copies of the SD card (as I would prefer to avoid fetching the camera to remove the SD card).
@StopICU33 thanks, any chance you have any timeline on rtsp FW on v3? Additionally, any chance there is some work done at supporting a usb RJ45 dongle via the USB-A port? You guys have created firmware to make v2 into a webcam, why not add support for an ethernet dongle, that would be simply amazing.
@WyzeGwendolyn any chance there is a timeframe when v3 will be able to be ordered from Canada?
No, not POE. The USB port used to connect the wyze as a webcam, can be used (with the right coding) to allow the use of a USB to RJ45 dongle/adapter. Camera would still be powered via the power plug. This is the same as many Android media boxes can do, firetv stick etc. Not the same as the POE feature, although that would be nice to have too but I don’t think it will happen as that would required hardware changes where the adapter via the USB port would require only SW changes (code).