openmiko VS ExtPay

Have a Wyze Cam V2 running openmiko. I can pull the feed via the camera's IP, but Klipper (Fluidd, Mainsail on BTT CB1) shows like below. Additionally, moonraker-timelapse throws an error. This was working fine until I tried Hyperlapse. Now I can't wrap my head around this

I'm running MainsailOS, and a Wyze cam v2 running openmiko. I have Tailscale installed on the Pi for remote access. In Mainsail config, I have the camera configured via private IP. When I access the web control panel externally, I do not get video output. Is there a way to get this to work? I do not think there's a way to connect the Wyze cam to my tailnet.If it's not possible, have any good recommendations for a good, cheap, wide-angle (110 degrees FOV or better) camera I can purchase? I wouldn't want to spend more than $25 for one. Quick search yielded this one, but don't know if there's a Klipper-community recommended one that everyone uses.

you wish lol. the mod allows you to get highest possible resolution video out of it without all the compression pixelation. its super easy to install. but it does take a little bit of linux knowledge to edit config files and stuff. heres the link if interested: https://github.com/openmiko/openmiko

I bought a used Wyze Cam V2 relatively cheap and installed OpenMiko on it for example.

I have a WyzeCamV2 running OpenMiko firmware, which supports (and I have configured for) H264 RTSP streaming. I can view the video stream through VLC with the url rtsp://192.168.1.199:8554/video3_unicast. I am executing the command docker run -p 8081:80 --name mycamera -e AGENT_CAPTURE_IPCAMERA_RTSP="rtsp://192.168.1.199:8554/video3_unicast" kerberos/agent:latest on my host. The agent seems to run fine and I can connect via browser. With our without AGENT_CAPTURE_IPCAMERA_RTSP... set, I cannot add the RTSP stream; no cameras show attached and when I try to connect one via dashboard->settings, it just spins. The logs aren't really helpful (see below).

OpenMiko is one example.

That's why I only use cameras flashed with open firmware: https://github.com/openmiko/openmiko

If all else fails, you can flash different firmware and use them locally. I'm using [OpenMiko](https://github.com/openmiko/openmiko) on my Wyze Cam v1 (I'd assume there's a similar open-source project for the v3), and Wyze themselves publishes an RTSP firmware. Without a bit of technical know-how and some supporting hardware (namely a router than supports OpenVPN) you won't have access to the stream off your local network, but you can stream locally with VLC Player.

I've been using SQLite/Litestream for https://extensionpay.com for about 3 years now! Serves about 120m requests per month (most of those are cached and don't hit the db), but it's been great!

I was convinced that SQLite could be a viable db option from this great post about it called Consider SQLite: https://blog.wesleyac.com/posts/consider-sqlite

Using SQLite with Litestream helped me to launch the site quickly without having to pay for or configure/manage a db server, especially when I didn't know if the site would make any money and didn't have any personal experience with running production databases. Litestream streams to blackblaze b2 for literally $0 per month which is great. I already had a backblaze account for personal backups and it was easy to just add b2 storage. I've never had to restore from backup so far.

There's a pleasing operational simplicity in this setup — one $14 DigitalOcean droplet serves my entire app (single-threaded still!) and it's been easy to scale vertically by just upgrading the server to the next tier when I started pushing the limits of a droplet (or doing some obvious SQLite config optimizations). DigitalOcean's "premium" intel and amd droplets use NVMe drives which seem to be especially good with SQLite.

One downside of using SQLite is that there's just not as much community knowledge about using and tuning it for web applications. For example, I'm using it with SvelteKit and there's not much written online about deploying multi-threaded SvelteKit apps with SQLite. Also, not many example configs to learn from. By far the biggest performance improvement I found was turning on memory mapping for SQLite.

I made a couple browser extensions that make over $500/month each. The key seems to be naming your extension after high-volume search terms and getting good reviews on the chrome store (and obviously having an extension that works well and solve a common problem on major websites). I monetized them with my own service, https://extensionpay.com. Feels so good to eat your own dog food :)

Neat! I'm serving around 120m requests per month for https://extensionpay.com from a 2GB VPS running a single-threaded nodejs process and SQLite as the db. Most of the requests are cached, but still, it's amazing how far you can get with cheap hardware.

I use SQLite/Litestream for https://extensionpay.com! Serves about 120m requests per month (most of those are cached and don't hit the db), but it's been great!

I have no affiliation with Litestream but I was convinced that SQLite could be a viable db option from this great post about it called Consider SQLite: https://blog.wesleyac.com/posts/consider-sqlite

Using SQLite with Litestream helped me to launch the site quickly without having to pay for or configure/manage a db server, especially when I didn't know if the site would make any money and didn't have any personal experience with running production databases. Litestream streams to blackblaze b2 for literally $0 per month which is great. I already had a backblaze account for personal backups and it was easy to just add b2 storage. I've never had to restore from backup so far.

There's a pleasing operational simplicity in this setup — one $14 DigitalOcean droplet serves my entire app (single-threaded still!) and it's been easy to scale vertically by just upgrading the server to the next tier when I started pushing the limits of a droplet. DigitalOcean's "premium" intel and amd droplets use NVMe drives which seem to be especially good with SQLite.

One downside of using SQLite is that there's just not as much community knowledge about using and tuning it for web applications. For example, I'm using it with SvelteKit and there's not much written online about deploying multi-threaded SvelteKit apps with SQLite. Also, not many example configs to learn from. By far the biggest performance improvement I found was turning on memory mapping for SQLite.

Happy to answer any questions you might have!

I made https://extensionpay.com to monetize my own browser extensions and between that and free distribution on the extension stores it’s really easy to try making extensions that make money. So far devs have made over $300k with ExtensionPay. That said, it still take some skill to find a niche that works.

Just want to put a plug in for https://extensionpay.com/ - I've used it in extensions in the past. It takes away the headache of setting up a backend for payment. They do take an extra 5%, but it's worth it especially. for smaller projects

Have a go at looking at this: https://extensionpay.com,

That's fair. Right now my payment processor (ExtensionPay) doesn't support multiple pricing tiers. However, in the future I'm considering rolling out my own logic so that I can provide a lifetime license option for some users.

Oh nice! Maybe you'd be interested in the tool I built to take payments in extensions: https://extensionpay.com

If your concern is about security of the extension, you may right click on top of the extension's icon and select "Inspect popup". Select the "Network" tab and type CTRL-R to force a reload of the extension. Verify there are no external network requests (except to extensionpay.com for paid features).