Recovering a Tasmota smart globe?
Hi, I have a "Brilliant" smart globe on which I used tuya-convert to install Tasmotat 8.1.0.2. It worked fine for a month. It has since stopped working. Now, when I switch the globe on it broadcasts an open SSID "ESP-B2CDB3" - where B2CDB3 is the second half of the globe's MAC address. Connecting to the SSID reveals the globe using 192.168.4.1 is running a DHCP server which gives out 192.168.4.2 to me when I connect. 192.168.4.1 does not have any open TCP ports (as confirmed by nmap). As port 80 (and 443) are both closed browsing to http://192.168.4.1/ fails, and I can find no way to do anything beyond getting an IP via DHCP with the globe. Does anyone have any suggestions as to how I could recover this globe? Regards, Kim
I have no (specific) idea but it sounds like the dhcp service is working but the http service is not and presuming there is no other service present on the wireless interface (ssh for example) it sounds like the only option is to attempt to re-flash the firmware - presuming there is a method available for debricking these... I wonder if there is a physical terminal connection present on the control board - or even a test-bus (JTAG?) On Wed, 16 Sep 2020 at 21:41, Kim Oldfield via luv-talk <luv-talk@luv.asn.au> wrote:
Hi,
I have a "Brilliant" smart globe on which I used tuya-convert to install Tasmotat 8.1.0.2. It worked fine for a month.
It has since stopped working. Now, when I switch the globe on it broadcasts an open SSID "ESP-B2CDB3" - where B2CDB3 is the second half of the globe's MAC address. Connecting to the SSID reveals the globe using 192.168.4.1 is running a DHCP server which gives out 192.168.4.2 to me when I connect.
192.168.4.1 does not have any open TCP ports (as confirmed by nmap). As port 80 (and 443) are both closed browsing to http://192.168.4.1/ fails, and I can find no way to do anything beyond getting an IP via DHCP with the globe.
Does anyone have any suggestions as to how I could recover this globe?
Regards, Kim _______________________________________________ luv-talk mailing list luv-talk@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-talk
-- Dr Paul van den Bergen
Hi Paul, On 17/9/20 9:26 am, Paul van den Bergen wrote:
I have no (specific) idea but it sounds like the dhcp service is working but the http service is not and presuming there is no other service present on the wireless interface (ssh for example) it sounds like the only option is to attempt to re-flash the firmware - presuming there is a method available for debricking these...
One recovery method has some SSID hacks (for misconfigured device wireless), and then open a web browser to update the settings. These instructions don't say what to do if it isn't listening on port 80. I haven't found any mention of Tasmota firmware broadcasting SSID ESP-<MAC> - so I don't know what state it is in, or how to recover from this SSID. Another recovery method involves power cycling 5 times to get it into fast flash recovery mode. With my attempts at power cycling this globe I haven't been able to invoke recovery mode.
I wonder if there is a physical terminal connection present on the control board - or even a test-bus (JTAG?)
It's a sealed light globe which plugs into a 240V socket so I'd rather not have to take it apart - but I may yet be left with no other option.
On Wed, 16 Sep 2020 at 21:41, Kim Oldfield via luv-talk <luv-talk@luv.asn.au <mailto:luv-talk@luv.asn.au>> wrote:
Hi,
I have a "Brilliant" smart globe on which I used tuya-convert to install Tasmotat 8.1.0.2. It worked fine for a month.
It has since stopped working. Now, when I switch the globe on it broadcasts an open SSID "ESP-B2CDB3" - where B2CDB3 is the second half of the globe's MAC address. Connecting to the SSID reveals the globe using 192.168.4.1 is running a DHCP server which gives out 192.168.4.2 to me when I connect.
192.168.4.1 does not have any open TCP ports (as confirmed by nmap). As port 80 (and 443) are both closed browsing to http://192.168.4.1/ fails, and I can find no way to do anything beyond getting an IP via DHCP with the globe.
Does anyone have any suggestions as to how I could recover this globe?
Regards, Kim _______________________________________________ luv-talk mailing list luv-talk@luv.asn.au <mailto:luv-talk@luv.asn.au> https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-talk
-- Dr Paul van den Bergen
Hello Kim, On 9/16/20, Kim Oldfield via luv-talk <luv-talk@luv.asn.au> wrote:
Hi,
I have a "Brilliant" smart globe on which I used tuya-convert to install Tasmotat 8.1.0.2. It worked fine for a month.
Tasmota comes up in a Google search, along with the ESP8266 chip, which is a wi-fi IOT chipset. There are security questions about the widespread use of it. If you can get wired access, there are ways to reflash, but if sealed in with the only access by wi-fi, then probably just e-waste.
It has since stopped working. Now, when I switch the globe on it broadcasts an open SSID "ESP-B2CDB3" - where B2CDB3 is the second half of the globe's MAC address. Connecting to the SSID reveals the globe using 192.168.4.1 is running a DHCP server which gives out 192.168.4.2 to me when I connect.
192.168.4.1 does not have any open TCP ports (as confirmed by nmap). As port 80 (and 443) are both closed browsing to http://192.168.4.1/ fails, and I can find no way to do anything beyond getting an IP via DHCP with the globe.
Does anyone have any suggestions as to how I could recover this globe?
From my reading, briefly, I think you need to physical access to the circuit board, and that may be not possible in a nondestructive fashion. Best of luck.
Regards, Kim
Regards, Mark Trickett
participants (3)
-
Kim Oldfield -
Mark Trickett -
Paul van den Bergen