-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Lost Uptime #302
Labels
bug
Type - Confirmated Bug
Comments
Fixed in next release |
Great. Thanks :) |
arendst
added a commit
that referenced
this issue
Mar 29, 2017
4.1.1 20170329 * Fix default Telemetry for command Prefix3 * Fix webserver Module parameters for disabled select * Fix sensor status for enabled switches * Remove Light as alternative for Power (save code space) * Remove migration option from pre V3 (code cleanup) * Remove unofficial SPIFFS support (code cleanup) * Remove command list when unknown command is entered (save code space) * Rename Status11 json from StatusPWR to unique StatusSTS * Rename command Gateway to IPAddres2, Subnetmask to IPAddress3 and DnsServer to IPAddress4 (save code space) * Add Command MqttResponse to select either command or RESULT topic as response (#258) * Add command StateText1 to StateText3 to assign MQTT_STATUS_OFF, MQTT_STATUS_ON and MQTT_CMND_TOGGLE respectively (#286) * Remove restart after IPAddress changes (#292) * Add support for MAX31850 in xsns_ds18x20.ino (#295) * Fix possible uptime update misses (#302)
curzon01
pushed a commit
to curzon01/Tasmota
that referenced
this issue
Sep 6, 2018
4.1.1 20170329 * Fix default Telemetry for command Prefix3 * Fix webserver Module parameters for disabled select * Fix sensor status for enabled switches * Remove Light as alternative for Power (save code space) * Remove migration option from pre V3 (code cleanup) * Remove unofficial SPIFFS support (code cleanup) * Remove command list when unknown command is entered (save code space) * Rename Status11 json from StatusPWR to unique StatusSTS * Rename command Gateway to IPAddres2, Subnetmask to IPAddress3 and DnsServer to IPAddress4 (save code space) * Add Command MqttResponse to select either command or RESULT topic as response (arendst#258) * Add command StateText1 to StateText3 to assign MQTT_STATUS_OFF, MQTT_STATUS_ON and MQTT_CMND_TOGGLE respectively (arendst#286) * Remove restart after IPAddress changes (arendst#292) * Add support for MAX31850 in xsns_ds18x20.ino (arendst#295) * Fix possible uptime update misses (arendst#302)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Has anyone noticed "uptime" counter sometimes not updating ? I've simultaneously restarted all devices and from time to time different one is behind. FW version 4.0.7 but earlier versions had the same issue.
Mar 28 18:02:30 sonoff5-3250 ESP-MQTT: tele/sonoff5/UPTIME = {"Time":"2017-03-28T18:02:30", "Uptime":19}
Mar 28 18:37:35 sonoff5-3250 ESP-MQTT: tele/sonoff5/STATE = {"Time":"2017-03-28T18:37:34", "Uptime":19, "Vcc":2.673, "POWER1":"OFF", "POWER2":"OFF", "Wifi":{"AP":1, "SSID":"SW", "RSSI":24}}
Mar 28 19:02:31 sonoff5-3250 ESP-MQTT: tele/sonoff5/UPTIME = {"Time":"2017-03-28T19:02:30", "Uptime":20}
Mar 28 19:38:25 sonoff5-3250 ESP-MQTT: tele/sonoff5/STATE = {"Time":"2017-03-28T19:38:25", "Uptime":20, "Vcc":2.670, "POWER1":"OFF", "POWER2":"OFF", "Wifi":{"AP":1, "SSID":"SW", "RSSI":22}}
Mar 28 20:38:52 sonoff5-3250 ESP-MQTT: tele/sonoff5/STATE = {"Time":"2017-03-28T20:38:52", "Uptime":20, "Vcc":2.886, "POWER1":"OFF", "POWER2":"OFF", "Wifi":{"AP":1, "SSID":"SW", "RSSI":24}}
Mar 28 21:39:15 sonoff5-3250 ESP-MQTT: tele/sonoff5/STATE = {"Time":"2017-03-28T21:39:15", "Uptime":20, "Vcc":2.673, "POWER1":"OFF", "POWER2":"OFF", "Wifi":{"AP":1, "SSID":"SW", "RSSI":32}}
Mar 28 22:02:30 sonoff5-3250 ESP-MQTT: tele/sonoff5/UPTIME = {"Time":"2017-03-28T22:02:30", "Uptime":21}
Mar 28 22:39:46 sonoff5-3250 ESP-MQTT: tele/sonoff5/STATE = {"Time":"2017-03-28T22:39:45", "Uptime":21, "Vcc":2.889, "POWER1":"OFF", "POWER2":"OFF", "Wifi":{"AP":1, "SSID":"SW", "RSSI":32}}
The text was updated successfully, but these errors were encountered: