Another attempt at replacing the Wyze camera firmware went much more smoothly, producing a pair of small cameras with better network manners:
That’s a VLC screen capture from the RTSP stream; obviously, I must up my clutter control game.
I resized the partition to 32 GB, installed the firmware (per the FAQ) into the root directory, tweaked the configuration files to match my situation, popped it in the camera, plugged the power cable, and It Just Worked™.
Herewith, a checklist of
config directory files requiring tweakage:
wpa_supplicant– WiFi SSID and password
timezone.conf– America/New_York for us
osd.conf– can be tweaked through the Web interface
staticip.conf– 192.168.1.11x, as you like
resolve.conf– pihole or router IP, as needed
defaultgw.conf– router IP
rtspserver.conf– different ports for additional cameras
It would be possible to have the pihole’s DHCP server assign a fixed IP address to each camera, based on its MAC address, but this way the camera knows who it is right from the start and what it’s supposed to be doing.
The router isn’t bright enough to route different port numbers on its Internet side to different LAN IP addresses with the same port address, so each camera must stream from a different port number. I don’t plan many world-available video streams, but a friend does enjoy watching the birds during feeder season.
With the RTSP stream up & running, I flashed the U-Boot bootloader (again, minus drama) and tweaked its
uEnv.txt configuration file:
- Change the memory layout to allow 1920×1080 video
- ethaddr – set to match hardware MAC address
- gateway – router IP
- ipaddr – match the staticip.conf value
- serverip – router IP (unclear what this does)
The cameras now produce no objectionable network activity, dramatically down from the Wyze firmware’s desperate attempts to contact various servers, every five minutes, around the clock. I have no way of tracking connections made with direct dotted-quad IP addresses, rather than through the pihole, but … this is a distinct improvement.