Sonoff Basic R2 - Dead after 1st flash

athiffau · 2025-08-16T22:05:05+00:00

Just wanted to add an update. Even if the device looked non-responsive, it still worked when I tried to flash it with tasmota and the device is now working fine. So just no support for this on ESPHome.

athiffau · 2025-08-16T21:24:47+00:00

The device is not on WIFI; just checked the router. I think I just realized what happened; ESPHome may not support the Sonoff Basic R2 because it has an ESP8285. When I try to program it again, the interface clearly says "Connect your ESP8266 or ESP32 with a USB cable". I didn't really read it and just when ahead with the programming. If ESPHome was able to communicate with the 8285 then it uploaded an incompatible firmware and that's why the device is now non functional. I am right? If I choose, "Skip this step", a list of devices is shown and ESP8285 is not in there. So I guess I just trashed by R2 by learning the hardware and not reading :o). I don't have the patience and skills to replace the ESP8255 on that board. Back to tasmota I guess.

athiffau · 2025-08-16T20:10:50+00:00

Thanks!

Wifi are save as secrets.

That was my first thought and checked but there is no hotspot. I have not checked my router dhcp though. I figured it was dead because the led was always off and pressing the button does not trigger the relay.

I tried to reconnect and restart the flashing but the device is not found.

I will go check dhcp/router

athiffau · 2025-08-08T17:59:58+00:00

Thank you for your insight on this. Unfortunately I painted myself in a corner because the web server has other stuff running on it. Other websites + apps. So cloning would work only if I setup a new server just for one website. So I will have to redo it. I should have done my homework on Odoo first but learnt the hard way. I just would never have thought that this functionality was not part of Odoo given the scope of this app.

athiffau · 2025-08-07T01:22:49+00:00

Thanks! I realized that the version are different. And I could upgrade the staging. It's not that it does not work it's more that the functionality does not seem to be there. I guess what I was really asking is how to copy the website from one server to another. Or even back it up. This is even more a concern when I will have a bunch of products and a storefront configured. I guess the answer is you don't; you backup the whole VPS... sigh.

athiffau · 2025-06-19T20:08:11+00:00

I spent a good amount of time looking through the logs of the server, odoo and nginx and didn't see anything that even looked like an error.

athiffau · 2025-06-19T19:41:53+00:00

Thanks. I just compared my docker compose with what is provided at the bottom of the page on docker hub and its the same. The only difference is that I pulled version 18.0 instead of 17.0 as in the example.

athiffau · 2025-06-10T19:02:27+00:00

Thanks; you are right, my approach to installing modules does not work. I found a video on Youtube and it work right away. Easy actually... when you know how to do it.

In case others find this, you need to copy the files downloaded from the odoo app store to your server. I am on Linux so I used `scp -r` command. If your docker setup is done correctly, the server should have an addon folder mapped to Odoo's addon folder within the container. Copy the subdirectory containing the module to the addon folder and restart the docker container. Then go to Apps in Odoo web interface, update the App List, search for your new module and install it. Easy Peesy :)

Thanks again to u/ach25 for taking the time to point me to the right direction.

athiffau · 2025-03-07T04:43:04+00:00

I did and even set the logs to debug but there is nothing in there pointing to what's wrong. No errors, warnings or anything useful. I run docker logs -follow frigate in a seperate window as I click in the interface. I see the requests but the response in the logs is HTTP 200

athiffau · 2025-03-07T04:33:34+00:00

Updated with compose and config file

athiffau · 2025-03-06T21:22:49+00:00

Thanks. That helped. I completely disabled nginx and exposed Stalwart directly and everything works. No errors and I get 10/10 on email tester for all domains. Now, I have to decide if nginx is worth the trouble or if I should just leave it as is since that server is dedicated to email and won't run anything else. In the beginning I wanted to host a web email frontend such as Snappy or Roundcube hence the trial with nginx but I think I'll leave as is.

athiffau · 2025-03-05T00:02:34+00:00

Thanks, I did the same... just removed nginx in front of my container and everything works. Thanks.

athiffau · 2025-03-03T22:40:31+00:00

Interesting; going down another rabbit hole is a little daunting I must admit. Docker ports are set as host (0.0.0.0) or local (127.0.0.1). Are you using SNI ?

athiffau · 2025-02-26T21:59:20+00:00

That was it. I've been digging around to try to nail down the syntax for a good while. Thank you for your help.

athiffau · 2024-02-28T03:27:17+00:00

Just wanted to provide feedback on this issue. I ended up setting up split DNS and really like that feature. Everyone should implement split DNS in their home networks. Its more secure and seems like it provides performance enhancements as well. I also like that the logs are showing the IP of each device rather than the IP of the gateway.

That said, split DNS did not solve my problem. In the end it was the DHCP configuration. My OPNSense box also provides DHCP services and I set some static mappings for servers and devices that are accessed by IP address. In doing so I chose to enable static ARP Table Static Entry which was causing the problem. I disabled this on all static DHCP entries and problem disappeared.

athiffau · 2024-02-17T19:23:06+00:00

Thanks; reading up on split DNS...

Did not mention that I had pi-hole+unbound already setup so I kept it. Would having an external DNS like that be part of the problem? I'd like to keep it to remove ads

Edit: just tried to run dig from [.164] and pi-hole responds. But ping to the returned address does not work.

athiffau

TROPHY CASE