Theo's Tasmota Tips and new release v6.1.0

[GasTurbineMan]

Again, and first of all - Tasmota is a great product for the Sonoff devices. Great work by Theo.

I see where v6.1.0 as an official release and no longer in development mode. Glad to see continued updates to the software.

Will "Theo's Tips" be updated as well? I have read "20180523 - Relation Tasmota and ESP8266/Arduino core version" a few weeks ago, but quite frankly, I could not understand how to implement the workarounds needed for core version 2.4.1, so I am still using core 2.3.0

If "workarounds" are still needed to run v6.1.0 with core 2.4.1; would it be possible to provide some clarification on how to install the needed code mods?

Thank you.

[arendst]

I guess you refer to the Hue workaround as the other 2.4.1 workarounds are served by Tasmota. They are independent from Tasmota versions as they are introduced by the underlying core versions. I keep these workarounds in Tasmota as long as the current core versions are present.

Follow the link in the Hue item and read the issue log regarding where to fix the webserver problem in 2.4.1 core. You'll need some background knowledge to handle this or just refrain from 2.4.1 and keep using the released 2.3.0

[GasTurbineMan]

I followed link and understood the workaround for the Hue issue – and was able to make the needed change. The one I could not understand was the memory leak issue. I followed the provided link – but it appeared to me there were 2 or maybe 3 different opinions on how to resolve the issue. And none of them provided any specific instructions on what to change. Was the memory leak issue on 2.4.1 resolved with v6.1.0? From: Theo Arends <notifications@github.com> Sent: Saturday, July 7, 2018 10:20 AM To: arendst/Sonoff-Tasmota <Sonoff-Tasmota@noreply.github.com> Cc: GasTurbineMan <rglokey@gmail.com>; Author <author@noreply.github.com> Subject: Re: [arendst/Sonoff-Tasmota] Theo's Tasmota Tips and new release v6.1.0 (#3156) I guess you refer to the Hue workaround as the other 2.4.1 workarounds are served by Tasmota. They are independent from Tasmota versions as they are introduced by the underlying core versions. I keep these workarounds in Tasmota as long as the current core versions are present. Follow the link in the Hue item and read the issue log regarding where to fix the webserver problem in 2.4.1 core. You'll need some background knowledge to handle this or just refrain from 2.4.1 and keep using the released 2.3.0 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3156 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AlsMjKl-ixQzFOy5PrP4j8TOIwqf8VoHks5uENGqgaJpZM4VGZDZ> . <https://github.com/notifications/beacon/AlsMjBquy_JhzrTskddhtOG7RUsuTq6Rks5uENGqgaJpZM4VGZDZ.gif>

[arendst]

As I said before. The workarounds are needed BECAUSE THE UNDERLYING CORE LIBRARY contains errors like indeed memory leaks.

As no new core library has been released the errors are still there and the workarounds are ALSO STILL PRESENT in Tasmota. No need for a user to change anything as the workarounds are in Tasmota.

[reloxx13]

Note: dont forget that 2.4.1 still cannot sleep the wifi connection, which results in a higher power consumption.
If you care about your electricity bill, stay on 2.3.0.

Sleep is bugged in the Core, which lays even UNDER the UNDERLYING CORE LIBRARY of tasmota.

The core is managed by the chinese as much as i know. I expect a fix for this in a few months, since they changed alot api calls including the sleep api in the past months. Thats why i hope the sleep bug will be the next step. The latest released core with the api changes got already included in the latest arduino lib.

Tasmota -> Arduino ESP library -> ESP Core

so, yes, those are even two other layers tasmota depends on.
and to avoid confusing, theo means the Arduino ESP Lib as core.

Some sources:
Arduino ESP Lib Github (check releases page, its still 2.4.1 as theo mentioned):
https://github.com/esp8266/Arduino
Latest CORE Include in Arduino ESP Lib
esp8266/Arduino#4853
The still open Fix PullRequest for the Alexa Bug in Ardunio ESP Lib
esp8266/Arduino#4235
Bug Report for Sleep Bug in Arduino ESP Lib (their are more, search for sleep in the issue list)
esp8266/Arduino#4658
Energy saving:
https://github.com/arendst/Sonoff-Tasmota/wiki/Energy-Saving

[GasTurbineMan]

OK, so you say "no need for user to change anything . . .". I downloaded v6.1.0a and set PlatformIO.ini to use core 2.4.1 and set user_config.h for hue emulation. Flashed Sonoff Basic and while Alexa discovers the new device, when I try and get Alexa to turn device on/off, I get the "device is unresponsive".

I went back with 2.3.0 and Alexa / Hue are working again. I will stick with 2.3.0 for now until the core library errors are corrected.

Just now starting to work with temperature sensors. Tasmota rocks!!

[reloxx13]

If you build it yourself, you HAVE TO insert the HUE Workaround local on your system. As said, it cannot be fixed in the tasmota sourcecode.

I dont think theo meant the dev build with "no need for user to change anything", but i dont know if theo included the hue fix in the ready to use bins.

The bugged code is automatic downloaded by your platformIO software as underlaying library and does not lie inside your tasmota directory.

only for theo:
The only way to let it be fixed for all in tasmota , would be to

• fork the platformIO adapter for Arduino ESP,
• fork the Arduino ESP lib,
• fix the bug in the Arduino ESP Fork,
• change the url inside the platformIO adapter to the forked Arduino ESP lib,
• use the github url of the forked platformIO adapter inside platformio.ini

[arendst]

@reloxx13 thx. will add it to my release task list which already takes me half a day ...

[reloxx13]

thats why i did not mention it before, took to much time for bugs which are not your fault.
and i dont know how it works in arduino ide, i just hate this ide so much 👎

i dont know what takes it so long for you.

i dont get it why you dont use the merge from dev to master, i always see the master line get never a merge, all files in the master looking like they are getting updated by your hand.

also if you need it, i have a small bash script to get the binaries ordered, i dunno if i mentioned it before, i think i did somewhere. but still, you need to update the version number by hand:

folder "releases"
inside a releases.bat

gitignore
releases/*
!releases/releases.bat

set version=6.1.0a

mkdir %version%

copy ..\.pioenvs\sonoff\firmware.bin %version%\EN-firmware-%version%.bin
copy ..\.pioenvs\sonoff-BG\firmware.bin %version%\BG-firmware-%version%.bin
copy ..\.pioenvs\sonoff-BR\firmware.bin %version%\BR-firmware-%version%.bin
copy ..\.pioenvs\sonoff-CN\firmware.bin %version%\CN-firmware-%version%.bin
copy ..\.pioenvs\sonoff-CZ\firmware.bin %version%\CZ-firmware-%version%.bin
copy ..\.pioenvs\sonoff-DE\firmware.bin %version%\DE-firmware-%version%.bin
copy ..\.pioenvs\sonoff-ES\firmware.bin %version%\ES-firmware-%version%.bin
copy ..\.pioenvs\sonoff-FR\firmware.bin %version%\FR-firmware-%version%.bin
copy ..\.pioenvs\sonoff-GR\firmware.bin %version%\GR-firmware-%version%.bin
copy ..\.pioenvs\sonoff-HU\firmware.bin %version%\HU-firmware-%version%.bin
copy ..\.pioenvs\sonoff-IT\firmware.bin %version%\IT-firmware-%version%.bin
copy ..\.pioenvs\sonoff-NL\firmware.bin %version%\NL-firmware-%version%.bin
copy ..\.pioenvs\sonoff-PL\firmware.bin %version%\PL-firmware-%version%.bin
copy ..\.pioenvs\sonoff-PT\firmware.bin %version%\PT-firmware-%version%.bin
copy ..\.pioenvs\sonoff-RU\firmware.bin %version%\RU-firmware-%version%.bin
copy ..\.pioenvs\sonoff-UK\firmware.bin %version%\UK-firmware-%version%.bin
copy ..\.pioenvs\sonoff-TW\firmware.bin %version%\TW-firmware-%version%.bin

copy ..\.pioenvs\sonoff-minimal\firmware.bin %version%\MINIMAL-firmware-%version%.bin
copy ..\.pioenvs\sonoff-classic\firmware.bin %version%\CLASSIC-firmware-%version%.bin
copy ..\.pioenvs\sonoff-knx\firmware.bin %version%\KNX-firmware-%version%.bin
copy ..\.pioenvs\sonoff-allsensors\firmware.bin %version%\ALL_SENSORS-firmware-%version%.bin


copy ..\.pioenvs\sonoff-DE-4MB\firmware.bin %version%\4MB-DE-firmware-%version%.bin

[arendst]

That's right. In my understanding I cannot merge dev to master because:

• readme is different
• platformio.ini is different
• some features in dev are not ready for master like display and/or sensor drivers
• I do not want debug file in master

If there is a way to merge while keeping the above in mind let me know...

[reloxx13]

yup, the keyword is gitattributes

git config --global merge.ours.driver true

echo README.md merge=ours' >> .gitattributes
echo platformio.ini merge=ours' >> .gitattributes

this ways, on a merge always the files of the merged to branch gets used

but if you made changes to those files in dev, you need to make them manual in master

the features needs to be as a feature branch (git flow), their will no other way around i think
steps than woud be:

• normal dev in dev branch,
• now work on the new sensor:
  • commit everything in the dev branch or create a patch file if you dont want to commit it now
  • change to feature branch "new sensor"
  • merge latest dev into feature
  • dev now on feature branch
  • commit if done to feature branch
• if new sensor is done, merge into dev

if you are looking for a good windows/mac git gui, try sourcetree (Free) or tower (pay).
those support git flow and easy merging. i use sourcetree.

im not sure about the debug file, this should be tested.
echo debugfile merge=ours' >> .gitattributes
that way, it should not get created in teh master if the master dont has it, but as said, im not sure.

maybe @ascillato or @RaymondMouthaan have also some tips 👍

but everything mentioned here should be tested on a new test github project.

something to read: https://medium.com/@porteneuve/how-to-make-git-preserve-specific-files-while-merging-18c92343826b

[GasTurbineMan]

OK, it is making sense to me now. When Theo says tasmota includes the workarounds, he means on his prebuilt BIN files. Sorry, I did not make it clear that I am downloading the .zip from git and building my own bins with PlatformIO. No worries, I will stick with 2.3.0 for now. From: reloxx13 <notifications@github.com> Sent: Saturday, July 7, 2018 3:10 PM To: arendst/Sonoff-Tasmota <Sonoff-Tasmota@noreply.github.com> Cc: GasTurbineMan <rglokey@gmail.com>; Author <author@noreply.github.com> Subject: Re: [arendst/Sonoff-Tasmota] Theo's Tasmota Tips and new release v6.1.0 (#3156) If you build it yourself, you HAVE TO insert the HUE Workaround local on your system. As said, it cannot be fixed in the tasmota sourcecode. The bugged code is automatic downloaded by your platformIO software as underlaying library and does not lie inside your tasmota directory. Note: i dont know if theo included the hue fix in the ready to use bins. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3156 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AlsMjDXSm_X_9va0AMffhfcKxsNmzGAkks5uERV6gaJpZM4VGZDZ> . <https://github.com/notifications/beacon/AlsMjAjWcbWG-ZYZZiIIfg8umPubtZV1ks5uERV6gaJpZM4VGZDZ.gif>

[ascillato2]

Hi,

If your question is addressed, please, close this issue. Thanks 👍