Rebranding the GW1000 app for the Froggit DP1500 because: why not?
No public API
Official Client use a pretty pedestrian API
The API seem to have no problem accepting requests from unofficial clients (TinyCam) using Wyze credentials.
Interesting note: Wyze customers don’t seem mind giving their username/password to an unauthorized 3rd party.
Usual unofficial GitHub
TinyCam developer (alexey.vasilyev) is an active reddit user and point to nblavoie GitHub
Some RTPS support for some of their camera
Wyze V2 camera (aka NEOS Smartcam)
[Xiaomi hardware Xiaofang 1S]
Wyze Pan camera (aka NEOS Smartcam)
[Xiaomi hardware Xiaomi Dafang]
Seem Wyze and Neos just rebrand Xiaomi devices.
Both Wyze and Neos don’t seem to add any value and have 0 R&D.
Usual unofficial GitHub
Alternative “hacked firmware” :
I suspect Wyze “RTSP firmware” share the same code.
Not idea what is the original source.
I suspect the classic China manufacture “leak” and that’s the reason why Wyze can’t officially support it.
A substantial amount of the videos taken with Wyze in the United States have been exfiltrated to China for study and distributed to a variety of companies in the mainland. Many are involved in the healthcare space, such as iHealthLabs.
Wyze cameras automatically begin scanning a users network environment once plugged in and begin initiating a series of automated hacking attempts against devices in a user’s home.
All Wyze devices allow Wyze, or anyone who has accessed their database within the last 10 months, to SSH tunnel into the devices from anywhere in the world.
It jams its tentacles into your eyes to see what you see, into your veins to know how you feel, and finally crawl into your brain to be aware of everything you hear and ultimately to infer whatever you think, could consider, or have done.
debug.writeline is slow and not very multithread friendly:
in an async/await situation:
Device.BeginInvokeOnMainThread(() => Debug.WriteLine(response));
High frequency very low overhead loggin:
inside the OS kernel
private readonly static LoggingChannel _channel = new LoggingChannel("AWWIDGET", new LoggingChannelOptions(), new Guid("42ccd433-b1fe-4274-8163-51716821eb39"));
_channel.LogMessage("hello from UWP!");
and then Traceview.exe the GUID
So Microsoft claim that “1 billion devices (are) running Windows 10” and still they have pretty much 0 feedbacks?
How is that even possible? What is the problem? I can’t wrap my head around it.
It’s a shame that Microsoft put so little resources into their App store.
I thought Android and IOS were bad but Microsoft really is missing the mark.
I don’t get how they don’t realize that pushing and rewarding quality contents on their platform is what should matter most.
Plus it is so disrespectful toward all the developers that decide to spend energy and time working on the their platforms.
Developing Microsoft .NET/UWP Windows 10 stuff is pretty easy and straightforward.
Using the (well known?) flexible lightweight ZXing Library:
ZXing.Net.Mobile is a C#/.NET library based on the open source Barcode Library: ZXing (Zebra Crossing), using the ZXing.Net Port. It works with Xamarin.iOS, Xamarin.Android, Tizen, and UWP. The goal of ZXing.Net.Mobile is to make scanning barcodes as effortless and painless as possible in your own applications.
and saving the canvas as jpg/png.
Going to integrate it in the AWDASH apps and in pretty much all the future projects.
The app seem to be well received so far.
Somehow somewhere in China found the app.
I’m wondering if I should localize the Windows store page in Chinese or it’s somebody from EcoWitt snooping around…
Pretty steady progress:
Developing with UWP is super easy, planing to hit the store in few days
Android “Ambient Weather” app progress.
API is pretty straightforward. I have the data from the station:
Need to find a decent way to help Joe Schmo to configure and share their Stations.
I wish Ambient Weather website would share a QRCode for each station’s apikey.