Closed stephan1980 closed 5 years ago
Use latest dev build from http://thehackbox.org/tasmota/sonoff-sensors.bin There where problems with WDT resets (introduced with 6.4.1.16). Solved in 6.4.1.18
Thank you, I have uploaded the latest bin. If everything is working fine I will give you feedback!
Hi,
Any news on this?
Unfortunately the same problem with 6.4.1.19. After uploading everything worked fine for some hours. This morning at 10:30am the devices made a restart because of a blocked loop and again lost all GPIO configuration
Let's try something else. Try to do a reset 5 in the Tasmota console. That will erase all settings but will leave the wifi credentials.
If that does not solve your issue, try erase all flash with esptool.py as explained in the wiki and flash again with the precompiled bins from development branch.
I am currently not at home. I am able to try after coming weekend.
Is it related to this issue? https://github.com/arendst/Sonoff-Tasmota/issues/5323#issuecomment-468575163
Back home I tried both: Reset 5 and complete flash erasing. Only erasing the complete flash worked for me.
Unfortunately the same problem with 6.4.1.19. After uploading everything worked fine for some hours. This morning at 10:30am the devices made a restart because of a blocked loop and again lost all GPIO configuration
I'm pretty sure that this behaviour is related to the TSL2561. I can reproduce it a 100%.
If lux goes any higher about ~30000 (this was the highest value i've mesured so far and i have no idea how i could get the actual value. It's for sure that it must be a sunny day;)) the device(webinterface/teleperiod/..) freezes immediatly and as soon i put the sensor to shadow it starts reporting again. If it's too long exposed to values > 30000 you get blocked loop with all configuration deleted
Tested with Wemos D1-Mini & Sonoff Basic 6.5.0 and 6.4.x (2.5.0 and 2.3.0)
This happened with my tsl2561 lib version 2.0.7 It was fixed with 2.0.8. Current version is 2.0.10.
Sounds like tasmota still uses the old version.
I'll update to 2.0.10 now
Library updated. Should be in Hackbox after two hours.
17:26:50 MQT: stat/Uvlux/STATUS10 = {"StatusSNS":{"Time":"2019-04-18T17:26:50","VEML6070":{"UvLevel":1968,"UvIndex":2.63,"UvIndexText":"Niedrig","UvPower":0.066},"TSL2561":{"Illuminance":114500.000}}}
114500 Lux i will report tomorrow if it's stable
thx
09:48:57 MQT: tele/Uvlux/STATE = {"Time":"2019-04-19T09:48:57","Uptime":"0T16:24:42","Vcc":2.993,"SleepMode":"Dynamic","Sleep":250,"LoadAvg":19,"Wifi":{"AP":1,"SSId":"KBW1HAB","BSSId":"44:4E:6D:0F:B7:F5","Channel":11,"RSSI":54,"LinkCount":13,"Downtime":"0T00:00:53"}}
09:48:57 MQT: tele/Uvlux/SENSOR = {"Time":"2019-04-19T09:48:57","VEML6070":{"UvLevel":642,"UvIndex":0.86,"UvIndexText":"Niedrig","UvPower":0.021},"TSL2561":{"Illuminance":118300.000}}
thumbs up
I'm pretty sure that this behaviour is related to the TSL2561.
Nope, unfortunately its not only related to the TSL2561 Happened to me today after a power outage. Device type has than changed from "generic" to "sonoff-basic" and all gpio mappings (SCL/SDA) were gone. My sensor is a SHT31-D. Lolin V3, Firmware Tasmota 6.5.0.9, SDK 2.3.0
IMPORTANT NOTICE If you do not complete the template below it is likely that your issue will not be addressed. When providing information about your issue please be as extensive as possible so that it can be solved by as little as possible responses.
FAILURE TO COMPLETE THE REQUESTED INFORMATION WILL RESULT IN YOUR ISSUE BEING CLOSED
Make sure these boxes are checked [x] before submitting your issue - Thank you!
status 0
:My weather sensor including both a TSL2561 and a BME280 is working fine until the device somehow performs a restart. I am using a precompiled binary (sonoff-sensors.bin). After the restart all sensor configuration is gone (GPIO mapping for SDA and SCL). Funnily enough the device seems to do the restart every morning at around 10:20am. That is what I get in the logfile after the restart:
I am totally confused because the devices worked for some days without any restart.... The problem occurred suddenly.
After reconfiguring the device I get what I want to get:
Maybe someone could give me a hint?!