-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After a firmware update "tasmota/discovery/..../sensors" sends an incomplete data set (ESP8285N08) #22730
Comments
I can confirm this issue with Shelly 2.5 and Shelly 2pm. Position, Target, Tilt and Direction are missing unter 14.4.1 I can't read any hint in the changelogs and/ore as breaking changed. Please can somebody support it. TIA! |
See cause and solution #22353 @stefanbode pls revisit. |
Happy new year and thx for bringing it up. We did some changes in the way rules work with shutters. Interestingly I operate my shutters also with HA and did not see an issue. Mine still work fine. Anyhow the discovery message is wrong. Lets fix it.... Hmm, on a shelly 2.5PM with 14.3 I have a complete sensor discovery. will update to latest to see if there is a change. ok, here I do see the same problem. In discovery the the shutter is now missing. @arendst : Any changes recently on the discovery? as said. 14.3.0.7 was still working with the discovery. |
Ah I think I know the cause of the issue. I changed the init order delaying shutter init. This may be too late for discovery. I’ll take a look how to fix this without reverting the delay (as I did it for some reason I’ve already dorgotten) |
I can also make a fix. I do see that TasmotaGlobal.tele_period does not count anymore from 0...teleperiod. The 0 is still working. In all other cases I got a 2. And I do see that on discovery I get a 5. Maybe something I can rely on and just add the sensors also on TasmotaGlobal.tele_period==5. In my test this recovers the issue The GetNextSensor is setting this to 2 and currently I assume If I do not send something if the shutter is not moving and the tele_period == 2 seems to be a good idea. |
in the esp32 line 2386 to recovers it on my side. would do similar on esp8266 |
Thx. I'll make the change in both files now and push to dev branch. |
PROBLEM DESCRIPTION
After a firmware update "tasmota/discovery/..../sensors" sends an incomplete data set
I use a "Nous L12T WiFi Smart Curtain Module with Tasmota" with ESP8285N08 and firmware version 13.2.0. Everything works great.
I use it in "MQT: stat/tasmota_8F447F/RESULT = {"ShutterMode":1}"
Then I do an OTA update to the current version firmware 14.4.1.
The update runs without errors. Then I see that the position of the roller shutter is no longer displayed in % in the Home Assistant. This and other sensors are no longer defined and should no longer exist!
These sensors are missing in "tasmota/discovery/..../sensors" after the update:
"Position"
"Direction"
"Target"
"Tilt"
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:TO REPRODUCE
Steps to reproduce the behavior:
I try to see if it has something to do with SetOption19 or a retain. I check and compare the entire configuration. I can't find an explanation here. Luckily I use three of these devices and two still have the old version installed. I install the mqtt explorer to compare the telegrams. I notice that the two firmware versions respond differently to "discovery":
I can't find any other solution than downgrading to the old firmware version. Then it worked as usual again!
EXPECTED BEHAVIOUR
I would like the sensors to be available again like they were in the old version.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
Firmware Version 14.4.1
Firmware Version 13.2.0
ADDITIONAL CONTEXT
I can't find any other solution than downgrading to the old firmware version. Then it worked as usual again! I won't update until there is a solution
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: