@ericm I looked at the placement of hubitatPublish() again, and I really can't see a cleaner way than placing it here, there's too many different routes into MqttPublishDirect() from all over the code.
1 Like
Ahh. So I tried that, increased it by 1, but it didn't save my wifi info or Hubitat settings (i.e. had to setup via sonoff SSID). Appears it took my override settings (see below), but had to set up from sonoff SSID. Then tried to restore back to sonoff-minimal.bin so I could reflash to -1 and the device never came back (looks like a blue light inside my plug is blinking constantly). Oh well.
file included from tasmota/my_user_config.h:610:0, from /workspace/Tasmota-Hubitat/tasmota/tasmota.ino:32: tasmota/user_config_override.h:24:2: warning: #warning **** user_config_override.h: Using Settings from this File **** [-Wcpp]
Do make sure you have "#undef" before each #define in user_config_override.h, like this:
// -- Setup your own Wifi settings ---------------
#undef STA_SSID1
#define STA_SSID1 "YourSSID" // [Ssid1] Wifi SSID
#undef STA_PASS1
#define STA_PASS1 "YourWifiPassword" // [Password1] Wifi password
Do you mean that you now neither get your device back on your wifi nor have it start as an AP?
Correct. It appears bricked after downgrading from 7.1 (with increased CFG #) to tasmota minimal.
There's a lot of changes to the saved config part of the code and many additions to the structure. A word of caution to others, stick to the minimal build generated from the same code base and the same compiler. It is the same cautioning ericm has at the top of the first post in this thread.
Unfortunately the way to solve it now would be through TTL, if you need any help with that, please don't hesitate to ask.
1 Like
Thanks. I’ve done it before using this guide [Release] HubDuino v1.1.7 - Hubitat to Arduino / ESP8266 / ESP32 / ThingShield Integration (ST_Anything). Let’s see if I can do it again.
Ok, good luck! At least it looks easier than what I dealt with the other day:
I’ve also seen some 3d printable tools for flashing ESP32 and TYWE3S and similar ones. Just insert some pogopins in the 3D printed model and it’s easy... I don’t have a 3D printer though...
Ha not much better here. Can you point me to the tools to 3D print? Any advice on what I should flash to it? I’m using esptool.
Since I haven’t got a 3D printer I haven’t looked looked very closely at this, but this is what I have in my bookmarks:
https://m.yeggi.com/q/esp+pogo/
Yes, very similar, I’m happy I don’t have to solder as much, I’m really not very good at that...
I would clear the flash and put my version of Tasmota 7.1 on it, I’ve put it on a Sonoff Mini that was a bit glitchy with the previous version, the last 24 hours it’s been rock solid. But I guess more time is needed to really know. I’ll be running this on 30 devices as soon as I have the time to write the drivers missing for some of them.
I’ve also flashed back and forth OTA between my version and Tasmota Minimal from the same codebase, and no issues.
Finally got it. Bizarre I can’t flash it at 3.3v, had to go to 5. Never could get it to run any flash when not connected to the socket; just but Eric’s original firmware on it and will let it be.
Hi
@markus and @brianwilson I have about 14 Sonoff devices and TX light switches running in Hubitat I am using @ericm 's pre complied Sonoff.ino.generic.bin (6.6.0) do you guys have the complied bin file that would take ericm's version to 7.1 or are you still working on this? Also if I upgrade the devices to the 7.1 would the drivers in Hubitat still work 100%.
Great to hear you got it to work again, with it being this hard to resurrect, if it is stable on 6.6, maybe best to keep it there? I do appreciate you testing my firmware though, important to know it works for others. Thank you for trying!
I will release this version in binary form soon, but want to wait for the official Tasmota version to release their final version of 7.1 first.
With that said, everything is very stable for me, but will continue to run it to make sure. If your devices are stable on 6.6 and you’re not missing any functionality, then don’t upgrade, at least not yet. If you want to help testing this new version I would appreciate the help, but as you can see above, you may end up having to resurrect the device through TTL.
As for driver compatibility it should be 100%, the communication code is exactly the same as in 6.6 except what has been changed by the original author of Tasmota, but the API remains the same. I’m currently writing new drivers for TuyaMCU based devices, but the Sonoff ones stay the same.
I need help. I don't know if I've missed a step or just confused.
Updating the Sonoff TH with new firmware went fine. Upon download the module did broadcast an SSID but now it's gone! I've tried shutting everything off, reflashing, etc. - Nothing seems to be working now... Any ideas??
As you used the new firmware you maybe able to try the fast power recovery.
1 Like
Had this happen to me, how did you flash? OTA or using the pins on the board? What I did was reflash the device using the pins again, then connect to Sonoff wifi and setup my wifi details. Also once I have setup my wifi details, I power off the device and then power on again.
Did you solve this? I'm running this on 12+ devices now on the firmware I released, some of them Sonoff, though none Sonoff TH. If you need any further assistance, please just ask
I tried the suggestion of power cycling it four times but that didn’t work.
I’m not sure what else to try.
If the Power Cycle reset truly doesn't work, the other option would be to flash it again through TTL, a guide can be found here:
It can also be done without soldering, but that requires some pogopins to be reliable.
Hello, I'm using several basics and minis without any issue (thanks Ericm!), but got tons of lines from my devices in my log. I have tried to disable them in Hubitat and in the webui, but I still get lots of them. Is there a way to completely disable logs?
