-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merkury wifi bulbs #133
Comments
@kueblc - will the newer process (smart-link-py) maybe have different results? |
It may, |
Same steps as original project? @kueblc |
Yes |
@kueblc - I do have the Vtrust recovery AP and I can get to the device info page. I understand this is a good finding. However, I couldn't get the curl command to complete the flash, nor would (re)running the ./start_flash make any difference. In both cases, I attempted flash3 without certainty it is correct. From the info page, I read that available storage was 512K, not 1MB. Does this impact which method? Should my next step be flash method other than 3, or possible the smart-link-py branch? |
No progress with the smart-link-py on the previous attempted bulb, or a fresh one. The fresh one has this info available...... Wifi firmware version 1.1.0. MCU module firmware version 1.1.0 |
Yes, if it pairs it will stop blinking. Feel free to share your logs for additional feedback. Check if your wifi log shows the device's mac address connecting. This would indicate the pairing was successful. Check also to see if the web log shows any activity. If it does, please share. If it doesn't, see if you can capture what's happening on the network with |
Info page from device: VTRUST-FLASH 1.0 READ FLASH: http://10.42.42.42/get?read=HEX-ADDRESS |
This is great, you've successfully loaded the flash stub. You can now backup your firmware and replace it with your choice of alternatives. Please let us know what trouble you experienced and how you resolved it for future reference. |
wlan0: STA 5c:cf:7f:7e:b8:41 IEEE 802.11: associated |
Traceback (most recent call last): |
I haven't been able to do anything even though I have the recovery AP. The logs above are from me attaching my computer to the recovery ap, and attempting the curl command to flash. It says it will flash and restart, but when it restarts, it is still in recovery mode, and not flashed. |
Is
Is this everything that was in the web log?
Are you still running |
Yes. |
|
I cleared all logs so I knew what was from today's attempts. I attempted to run ./fake-registration-server to no avail. OK. No new logs to delete. I ran ./start-flash. I did not connect another device first. ./start-flash recognized the bulb online and appeared to be attempting to do something. Previous attempts informed me it wouldn't be any different. As I walked out of the room I accidentally hit the light switch. $@#@^^%#@@...... Turned it back on and BAM..... I see the backup lines flying by. About 15-20 seconds later the message to flash and have fun. I flashed it. It rebooted and is now online with tasmota running. |
@kueblc - Colin. Before I attempt the second bulb from the pack, what can I do to help? If it is real complex I need detailed instructions. Or have I provided enough for you to pin point what's going on? If need be, I can hold off on the second bulb so I can test any update you may make? Just let me know. |
You'd need to be running the AP So just try running |
Yes. I do have a grasp. However, others have reported very similar struggles. I will proceed with second bulb and see how it goes. |
The process is rather amazing. Some devices start faster than others. I have stopped the flashing process about 8 times during the process of reading, or paused, and I have easily recovered from each and every time. Even when I rebooted the device (mid process) and had no lights and responses- it worked perfectly (and instantly as the device was already waiting for firmware). |
Second bulb flashed successfully.....
|
so, now using this version of TUYA-CONVERT https://github.com/kueblc/tuya-convertit's possibile to flash via OTA also when installed TUYA firmware is v.1.0.5? |
I have since learned each device's FIRMWARE revision is different. The only way to know is to try. |
Using a dedicated (to tuya-convert) SD Card and a RPI3b I have successfully flashed eight Gosund plugs.
All moving parts worked in other words.
When attempting to flash the Merkury 9W white wifi bulb, the process just hangs at dots going across the screen while waiting for the device to connect / appear.
I have confirmed that the Tuya Smart app can connect and control the bulbs.
I will continue trying some of the notes / misc ways people are reporting success after work today.
The text was updated successfully, but these errors were encountered: