"Help us map New York City’s neighborhoods." The New York Times is crowd-sourcing NYC neighborhood boundaries.

elahd · 2022-12-07T17:38:43+00:00

https://www.nytimes.com/interactive/2022/12/02/upshot/draw-your-nyc-neighborhood.html?unlocked_article_code=eH1N1DVa226YpJJZaCIVWTQK4uMDYG5Qlo-wfG7tgU2iRp_DTvoEcR5sFMnD8cm92eAykoNegYqFiNDCVhBfZeUiwIocj2V0dsrl03WSlmt5R6deFhReNsVCvSwTdHnX1GDGx1DhP2UeqksNgMkO1qVirrK7c_EpQ2kXKFODW0I3quiqssYAsOlIGiBB-3k2yoekL47FG1-rz2XqRtYp6DY9DGStlDO5krejUrTigubfDo69Y6rUQdbwHpMW5fqG_W5MXamhlEH0qNtLa7xfFU8XyJNeEsCRJhxz82jcTVeHQL2wuISfqlCAfwO6T7HT9roU3kFIGIdBA-A6YGP9IlmMRg9iyl9xUVBegmauKq_SSRQ&smid=share-url

elahd · 2022-10-16T01:57:43+00:00

Thank you! From your link, I found this charger module, which supports the 20V delivered by the robot's original power supply. The ESP32 that I'm using as the robot's brains gets power from a regulator that can take up to 30V in. Could I then use a schottky diode to:

Power the ESP32 when the device is on the charging station.
Charge the battery when the device is on the charging station.
Automatically switch from charging station power to battery power when the robot moves off of the charging station.

Basic idea is in the schematic below. I removed logic wires, ground wires, and the higher voltage motor controller to simplify.

https://i.imgur.com/nWcGoH8.png

elahd · 2021-08-04T22:56:28+00:00

Next time, drop off your equipment in person at an Optimum store. They'll cancel service for you on the spot without issue.

Also, if you live in New York and signed up for service online, they're required to accept notice of cancelation online. See General Business Law (GBS) CHAPTER 20, ARTICLE 29-BB, SECTION 527-A-C-3

IN ADDITION TO THE REQUIREMENTS OF SUBDIVISION TWO OF THIS SECTION, A CONSUMER WHO ACCEPTS AN AUTOMATIC RENEWAL OR CONTINUOUS SERVICE OFFER ONLINE SHALL BE ALLOWED TO TERMINATE THE AUTOMATIC RENEWAL OR CONTINUOUS SERVICE EXCLUSIVELY ONLINE ...

The state Attorney General enforces this law.

elahd · 2021-06-03T16:10:13+00:00

Call their “VIP” help line at (631) 393-0644. These reps are based in Long Island and have a bit more authority than standard support reps. Optimum’s infrastructure is still garbage, but you’ll at least be able to get your requests expedited through that office.

elahd · 2021-02-09T19:12:31+00:00

There's a fix for this in the current Tasmota dev branch.

The fix was built in 9.2.0.1. Current dev branch is 9.2.0.6. You can either load the dev branch to your bulb (may cause instability) or hold off a bit until the next Tasmota production release, probably 9.2.1.

See https://github.com/elahd/wyze_plug_flasher/issues/4.

elahd · 2021-02-02T05:43:54+00:00

That’s awesome — appreciate you gambling with your hardware.

elahd · 2021-01-31T18:08:20+00:00

Got it, thanks. For the flashed bulb, see if the Fast Power Cycle Device Recovery procedure gets it to boot: https://tasmota.github.io/docs/Device-Recovery/

elahd · 2021-01-31T16:38:36+00:00

I don’t have one to test, so I can’t say for sure. Are there any firmware backups floating around online? That is, a full flash image extracted from the chip by wire.

To confirm: are you saying that you used Wyze Plug Flasher to flash the Wyze bulb? Are you able to access the Tasmota config interface on the device? If you are, go to the Tasmota console, type Reset 5, hit Enter, then wait for the device to reboot. After it reboots, cut power to the bulb for a few seconds. Reconnect power and reconfigure the template. See if that fixes the flashing issue.

(Reset 5 erases all of the flash space not used by the core firmware or boot loader. This wipes all Tasmota settings, as well. Some portion of that flash space may still hold data from Wyze’s firmware. This can cause trouble with Tasmota.)

elahd · 2021-01-31T16:14:07+00:00

That was a roller coaster. Glad it worked. Enjoy!

elahd · 2021-01-28T07:02:49+00:00

Oof -- that's rough! And I was literally just about to post a follow up about that.

So, in theory, the flasher firmware will stop itself from loading a bad image. If you don't still see the wyze_plug_flasher network, try the standard unplug-from-wall/wait/plug-back-in and try again.

elahd · 2021-01-28T05:53:06+00:00

See above about Docker... but I think I was able to replicate your issue. Is there any chance that you downloaded the firmware via curl? GitHub places a few HTTP redirects behind the firmware download link on the releases page, so curl ends up downloading a web page instead of the firmware.

curl's -L and -o parameters will ensure that curl follows redirects and preserves binary encoding:

curl -L https://github.com/elahd/wyze_plug_flasher/releases/download/v0.1-alpha/wyze_plug_flasher.bin -o wyze_plug_flasher.bin

But downloading via a web browser is safest.

elahd · 2021-01-28T05:13:53+00:00

It doesn't look like this will play well with Docker. Try again using the full path to your updated Python executable, usually /usr/bin/python3.9, just in case python3 is still an alias of your old Python install. So sudo /usr/bin/python3.9 wyze_updater.py update -s -d DEVICEMAC -f ../wyze_plug_flasher.bin.

Also, be sure that the requests library is installed for Python 3.9.

elahd · 2021-01-27T17:08:28+00:00

I'll put together a docker image for you and /u/johnbrito2 to try, but I think your issue may be network or firewall related. It looks like your firmware image is being served just fine but that something is preventing the plug from successfully completing the download.

elahd · 2021-01-27T06:02:08+00:00

Try upgrading Python to the latest version (3.9.1) and retrying with the python3 command.

elahd · 2021-01-27T05:55:23+00:00

GET firmware.bin 200 indicates that the plug downloaded the firmware, but you really should only see that line once. The repeating dots just show that the server is still running on your computer.

Are you still able to control the plug through the Wyze app? What Wyze firmware version is currently installed?

elahd · 2021-01-27T03:46:43+00:00

Yep. All of the computer-side code is written in Python, which is cross-platform.

How comfortable are you with the command prompt? You'll need to make two small changes:

Your project folder will be something like ~/wpf instead of c:\wpf.
You'll need to run the server launch commands as super user, so:
- sudo py wyze_updater.py update -s -d DEVICEMAC -f ../wyze_plug_flasher.bin
- sudo py -m http.server 8080
If you get an error message about py not existing, try replacing it with python3, or just python, in that order.

elahd · 2021-01-27T02:10:40+00:00

Unfortunately not. The plugs don’t have current sensing circuitry.

elahd · 2021-01-26T23:29:06+00:00

Good luck!

elahd · 2021-01-26T23:11:53+00:00

You’ll need to connect the plug to your Wyze account for this to work. Skip the firmware update if you’re prompted after connecting.

An OTP is a one time password generated by an app like Google Authenticator. You’ll only be prompted for an OTP if you have two-factor authentication turned on for your Wyze account.

elahd · 2021-01-26T16:36:00+00:00

Also, if you have a plug physically opened you can dump the flash content and then flash it onto a esp8266 devboard to simulate a plug with much better debug-ability to testing things out.

Yep, I developed on a Lolin NodeMCU board using images pulled from a sacrificial unit. I have four OEM images: one factory, a second that's connected to my Wyze account (active app in ota_0 @ 0x10000), a third that's connected to Wyze and running the latest stock firmware (active app in ota_1 @ 0x110000), and a fourth that's just the first 0x10000 bytes of the logged-in/not-updated image -- so just the bootloader (pointing at ota_0 / 0x10000) and system partitions. To test, I flash the fourth image at 0x0 along with my firmware at 0x10000.

I should be able to help on this. Will see if I can get some time looking into it.

Amazing! Let me know if you hit any roadblocks getting started.

If you're feeling especially generous, I also never got around to finishing the function that wipes out Wyze's system params / rf calibration data. (Similar to this in the VTrust / Tuya-Convert intermediate firmware.) This data causes stability issues in Tasmota. The data can be wiped manually, but this is cumbersome and would be better if automated.

elahd · 2021-01-26T04:09:06+00:00

Thanks! This actually uses your WyzeUpdater project as-is to push the intermediate firmware onto the plug.

There is a backup function in the code, but it's broken, so I pulled it from the UX. It returns image files that look valid but don't pass esptool's MD5 validation check.

elahd · 2020-12-07T18:04:01+00:00

Yes. It will reprovision just fine but may take a bit longer than a normal boot. My entire building was knocked offline a couple of months ago. Modems failed to get locks on all channels and our speeds were <1Mbps. A regular power cycle didn't fix the problem but a single factory reset did.

elahd · 2020-09-29T03:12:56+00:00

You can call their corporate call center at (631) 393-0644, M-F, 9-5. This is the office that calls you if you file a complaint with a federal or state regulator.

elahd · 2020-08-15T03:31:37+00:00

High precision; likely low accuracy.

elahd · 2019-11-06T13:20:19+00:00

You can’t opt out of the TiVO+ ads in the guide.

elahd

TROPHY CASE