Globe R01 Firmware Download

[Barton Ostby]

Sameissue, just 1 out of 3 bulbs is having an issue, mainly because my third one is new, and i already had the other 2 updated. The 3rd fails over and over and over. Is there any word on when a patch for this update will release? This is pretty infuriating at this point.

@chaz76vette @jcwking2010

If you are still experiencing this issue can you try turning off the bulb in the app and then trying again. You should be able to turn it off from the main page before going in and being prompted for the update.

@ytsejam777 Thanks for the reply. This worked for me, though I did need to disconnect power to the bulbs first, plug back in, then turn them off in the app, then attempt the update. They are updated now!

So I gave it try, I was not able to click the power button in the control area of the bulb due to the firmware overlay, but conveniently there is an on/off button on the list of devices. Once the bulb was off, I then went into the control area and ran the firmware update as normal. The firmware update went through without a hitch. I hope this post not only entertained, but may also be informative for the next unsuspecting purchaser of the Wyze Color Bulb.

Tried using three different phones, made sure my phones OS are updated to latest version, deleted Wyze and reinstalled, cleared cache, reset router, did all the turn the bulb off and on steps that everyone else said worked. Nothing worked. Still stuck with not being able to update.

"Cant open device for writing" I think it was a low memory state. Anyway I hosted them on TFTP as per the current instructions to install OpenWRT. Power on then hold the reset button with paperclip why until both files have downloaded.

Can you explain how you got around the line2: $'\r': command not found error? I used Notepad++ to create a new shell file, saved it as a Unix shell file, but I still get this error. It's driving me crazy; any help you can give would be greatly appreciated!

I also can't get to the router after installing the ...factory.bin OpenWRT firmware, and I have no idea why not. I have an old WD03 that I tested the install procedure on first and got it working just fine. Now, all I can do is access the recovery mode indicated by the globe as in the instructions for installing the firmware, and can get to 10.10.10.128 when I do, but all I can upload is the OpenWRT firmware again. I'll see the globe light shut off, then the wifi light comes on, but the device doesn't hand out DHCP addresses, and manually setting my address to a 192.168.1.xxx and the gateway to 192.168.1.1 does NOT let me get to a login page at 192.168.1.1.

I tried uploading the extracted firmware files provided by Resonate and putting them in the root of my TFTP server, but I also can't get the WD009 to connect to that TFTP server (10.10.10.254) like I could with the WD03. So I don't seem to have any way of installing the original firmware back on the router. Right now, I have an essentially useless device; I can get to a recovery page, but that's it. Can anyone provide any assistance?

So here's my story, I bought this W009 a few years ago for backing up images while traveling. I just pulled it out this past week. It had the OEM firmware on it. I didn't remember the WiFi password, so figured I'd just slap on OpenWRT and call it good. I didn't research much other than there was an image for it. And that is how I successfully bricked it.

I have followed the directions above as best as I can. I have the 2 files on my TFTP server. I have tried the server being on 10.10.10.1 and 10.10.10 254. It doesn't connect when I put it in the "globe" recovery mode. I have tried to select each of the rootfs and kernel, but no change.

I have also tried to SSH to the .128 address, but it fails to connect. I'll also admit that I'm not that familiar with Linux, so may have been doing something wrong. I have the unit connected via ethernet and when not in recovery, the only thing it will do is show 5G. There is no SSID being broadcast to connect via wireless.

After flashing to the firmware listed on -wd009 (23.05.0), my device rebooted and all I have are the WiFi, 5g and battery lights on. No actual wifi is exposed (which would be nice, but wasn't expected).

I have attempted to connect over ethernet directly, either dhcp or static, but wasn't able to ssh to 192.168.1.1. I also attempted to hook it up to my existing network to see if it would pull an IP, and it did not.

I encountered only having 5G and battery leds turn on after flashing the snapshot with the recovery web page at 10.10.10.128, using the hold reset button then power on and keep holding the reset button until the globe led lights up.

If you went directly to the snapshot or any 23.xx Openwrt builds, then try downloading the past releases, I started wwith the last 21.02.7 release factory image with the recovery page, then upgraded using sysupgrade images of 22.03.6 then finally 23.05.2, after that you may build your own snapshot or use the latest snapshot builds. This is what I did for it to work, you may need some patience waiting after the initial 21.07 flash. If your goal is to go back to the original firmware, then you may do the steps already posted in the forums right after 21.07 flash (get kernel and rootfs extracted from the original firmware file, scp them to your running openwrt and mtd write them respectively)

RavPower pulled the last/latest firmware off their page for the RP-WD03. I'm lucky to have it but my point is If you are going to flash the RP-WD009 it would be a good idea to archive the firmware locally, before they stop supporting it.

To everyone else, please note that when it rebooted finally, I thought I was left in the same state (Globe and Battery indicator only). I left my computer connected via ethernet and disabled the static (10.10.10.1) address. My computer immediately picked up a DHCP address from the device and I was able to successfully log into and start configuring the wifi and reassigning the ethernet port to wan.

And I now realize I'm going to need some help getting this configured as a travel router. Playing around with settings but not 100% sure I understand the terminology. But first, as @Lambda said, upgrading. Need to get the eth0 to be dhcp client so I can get it online.

Any pointers to setting up this device as a travel router would be helpful. It is a little weird because it has only one ethernet port. That defaults to a LAN port. To make this device a useful travel router, I'd want that to be a WAN port. But first I need to get the WLAN up and going with access to luci so I can move the ETH0 in to the WAN firewall zone. So far, I've managed to lock my self out of the device a half dozen times, lol.

By default Globe will ask you to use their own app. I realized that I could just use Tuya instead. And coupled with Localtuya, I wouId not need any cloud service. I followed the guide from the localTuya integrations and after a few tries, I am now able to completely control my color bulbs and smart plugs.

Hi All

@chamdemars

Is there still a way to get the Globe bulbs to work with HA?

I saw the fix about with the yaml but it looks like that file, localtuya.yaml has been superseded

Please let me know if there is a way to get these devices on HA.

Thanks

Simply cannot get it to work in Config/yaml file as per the below. I MUST be doing something wrong.

Your assistance will be greatly appreciated as I have some of these Globe devices that I want to use, but cannot get them into HA. The work fin in the app.

Morning

Could you perhaps just send me (blanked out of course) your yaml file that you placed in the config.yaml?

I am really struggling here and ready to give up. When I copy and paste, of course changing the information, the yaml gives me errors and I cant seem to get it working.

Thanks for your time

The APK he uses in the example is the Smart Living application which is from Tuya. The version he used is 3 .6 .1 which was uploaded on November 23, 2018. I found a version of the Globe Suite, 1.0.4, that was uploaded around the same site on the apkpure site. This version had the preferences file for localkeys that are referenced in the video.

It is possible to change the firmware in the current Globe devices which no longer use esp8266 chips but BEKEN chips (bk7231). Use CLOUDCUTTER to run ESPhome firmware and get full integration with home assistant with no cloud, no Tuya. How To

Should I be concerned about this?[quote="tom.guelker, post:47, topic:127191, full:true"]

The firmware update completed with an error but it appears that the firmware WAS updated from 22009631 to 24040011

All of my open/close remotes are happy now (Man, the WAF of having 14 of those things from blinds now available to work around the house....), also updated the E1810, about a dozen Fyrtur blinds (a couple left to go, doing them 2 or 3 at a time), all of my repeaters, and 2 of the 30W LED drivers. No problems with anything so far, other than the listed Fyrtur blinds now reporting battery in 200% scale.

Hello everybody im POME a music producer from the Uk, ive just received EMO amd tryed update his firmware. It did a template of emo on the screen then explanation marks, does anyone know what this means. Any help would be appreciated.

Sorry we have no proper info at the moment, The latest information from Living.ai, is that EMO PET APP is not scheduled for an update at this time.

I can only assure you both that we will pass this request on to them.

For the past two days, when I wake up in the morning and go into my home office, the globe icon on my XR1000 is flashing Red/Green. The internet and wifi is working with great upload and download speeds, but it is bothering me that the router is doing this. It has never done this before and that light has always been white. I will unplug the router and reboot it and the light will return to white, but overnight, it will go back to Red/Green flashing.

I checked the logs and I see a bunch of [DoS attack: RST Scan], [DoS attack: Fraggle Attack], [DHCP IP: (192.168.1.7)] to MAC address ]. etc. and other things but I'm just not experienced enough to know if these are normal or not.

3a8082e126