-
-
Notifications
You must be signed in to change notification settings - Fork 323
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
6.0.x quits after 2-4 days / 5.9.1 shows never changing temp readings #222
Comments
first approach is always to open the console, and possible post the output here, then I can help. |
Device #3, on version 5.9.1 constantly reports 21.56 as temperature, no changes ever. This firmware continued to provide readings for at least 8 days. Interval was set to 3 seconds for collecting output readings. Normal operation is set at 900seconds WM: Connection result: a: 1832 16122 152 absTilt: 83.81 T: 27.09 V: 3.39 owT: 21.56 Gravity: 30.45 calling HTTP Final-sleep: 1s; RT:71650 ▒l{ےgc parsed json a: 1824 16144 162 absTilt: 83.79 T: 27.01 V: 3.39 owT: 21.56 Gravity: 30.44 calling HTTP Final-sleep: 5s; RT:4703 parsed json a: 1808 16114 168 absTilt: 83.81 T: 26.96 V: 3.39 owT: 21.56 Gravity: 30.45 calling HTTP Final-sleep: 5s; RT:4742 parsed json a: 1828 16130 174 absTilt: 83.80 T: 26.97 V: 3.39 owT: 21.56 Gravity: 30.44 calling HTTP Final-sleep: 5s; RT:4704 parsed json a: 1814 16136 148 absTilt: 83.80 T: 26.95 V: 3.39 owT: 21.56 Gravity: 30.45 calling HTTP Final-sleep: 5s; RT:4766 parsed json a: 1808 16124 162 absTilt: 83.77 T: 26.94 V: 3.39 owT: 21.56 Gravity: 30.43 calling HTTP Final-sleep: 5s; RT:4800 parsed json a: 1806 16108 160 absTilt: 83.79 T: 26.93 V: 3.39 owT: 21.56 Gravity: 30.44 calling HTTP Final-sleep: 5s; RT:4697 ▒l▒ parsed json a: 1814 16124 184 absTilt: 83.81 T: 26.91 V: 3.39 owT: 21.56 Gravity: 30.45 calling HTTP Final-sleep: 5s; RT:4948 parsed json a: 1818 16134 180 absTilt: 83.74 T: 26.92 V: 3.40 owT: 21.56 Gravity: 30.41 calling HTTP Final-sleep: 5s; RT:4684 parsed json a: 1802 16122 168 absTilt: 83.79 T: 26.92 V: 3.39 owT: 21.56 Gravity: 30.44 calling HTTP Final-sleep: 5s; RT:4261 parsed json a: 1832 16154 176 absTilt: 83.76 T: 26.92 V: 3.39 owT: 21.56 Gravity: 30.43 calling HTTP Final-sleep: 5s; RT:4797 parsed json a: 1806 16130 178 absTilt: 83.82 T: 26.93 V: 3.39 owT: 21.56 Gravity: 30.46 calling HTTP Final-sleep: 5s; RT:5896 |
Device #3, on version 6.0.0 (strange, I downloaded 6.0.1 https://github.com/universam1/iSpindel/releases/download/6.0.1/firmware.bin), has changing temps. As noted before, 6.0.0 seemed to last only a few days before quitting (it did not hit the 8minute mark). I will reset the interval to 900 seconds now and report back when I do not receive new readings any more. calling HTTP Final-sleep: 5s; RT: 8535 woken from deepsleep, normal mode calling HTTP Final-sleep: 5s; RT: 4246 woken from deepsleep, normal mode calling HTTP Final-sleep: 5s; RT: 4342 woken from deepsleep, normal mode calling HTTP Final-sleep: 5s; RT: 4246 woken from deepsleep, normal mode calling HTTP Final-sleep: 5s; RT: 4347 woken from deepsleep, normal mode calling HTTP Final-sleep: 5s; RT: 4301 woken from deepsleep, normal mode calling HTTP Final-sleep: 5s; RT: 4291 woken from deepsleep, normal mode calling HTTP Final-sleep: 5s; RT: 4815 woken from deepsleep, normal mode calling HTTP Final-sleep: 5s; RT: 4313 |
If you have that low intervals the device will heat up itself a lot. The same is while charging. But that has been discussed already a lot of times. Check the FAQ |
Please reopen. As you can see on the earlier pictures the issue also occurs with 15 min intervals. |
If so, how is that related to the software? Rules out to the hardware then. |
6.0.0 has right fluctuating temps (=ok) 5.9.1 has never changing temps (=not ok, not hardware related because hardware works on 6.0.0) |
5.9 is buggy that’s why I deleted these releases. On the 6.x version you can see scanning actions for the DS, means you have hardware issues as it can’t read it. |
Thank you for your reply. I am not sure I understand though. 6.x results in a working ispindel for me (pin 12 reports a good temp) only the ispindel reports for <4 days (with 900second intervals). I understand you are trying to say reverting back is not an option. Would you like me to run a new trial with my 7 spindels on 6.x for duration to see if the problem for me on 6.x persists? |
Exactly. See you have the scanning for DS in your log, means you either did not save your settings or the DS cannot be found reliable |
Ok. I will update my spindels to 6.x and report back next week if they are still sending data every 900 seconds. If they discontinue before that time will notify you and ask where to go from there. |
Sorry to be back, but all of the ispindels have failed in the last few days on 6.0.1. Not a single one out of 7 reports back to me anymore: please see the statistics below: #1: 14 oct 15:36: flashed to 6.0.1: Last reading 17 okt 21:43 (lasted 3 days on 6.x) last battery state: 3.01 Please note how on 5.9.1 (flatlines) the temperature was not accurate, but the ispindels were able to last more than 3 days. I would like the stability of 5.9.1 (prolonged output: multipledays) with the sensor accuracy of 6.0.1. |
Something is terribly wrong with your setups or your iSpindels, i have never seen battery emptied within 3 days! Normally they last 3 months for me. |
I would suggest you do stress-testing on the newest software version i have asked many Brewfather users to revert to old firmware because the logging was not stable. @universam1 |
Anyone else aside of Brewfather users having this problem? |
@Gkire I like to see the battery graphs |
On it! They are fully charged and logging now. Will report back in a few days. @tgangso, can you make a graph available in the chart for battery indication? |
you might try the new 6.0.2 using the new SDK |
Thanks for the 6.0.2. Howeverthe problem seems to persist on occasion: Current time is 07:00am For #3 and #7 I wasn't able to get the putty results, it went straight to config. Putty on Ispindel #4 reported back on reset::
3.0.0-dev(c0f7b44) woken from deepsleep, normal mode Final-sleep: 900s; RT: 7278 |
Current time 07:49 The #8 reports: woken from deepsleep, normal mode Final-sleep: 900s; RT: 6401 |
See the RT: output, anything above 3000ms means you got WiFi issues connecting to your Access Point. |
Hi there,
All of my 8 ispindels on software 6.0.x (downloaded 6.0.1, was reported as 6.0.0 in the information menu) started with a full charge on 1 october for a test run on duration. The blue outlined ones in the picture below stopped working due to reasons unknown relatively quickly. On october 4th all black outlined ones also stopped working all around 1800 hours and despite enough battery charge remaining. I use Brewfather as an endpoint, Brewfather confirmed the server was up and running, not a error on that end.
Fix as suggested by other users was reverting back to 5.9.1 which I did on October 5th. Momentarily 6/8 ispindels are still up and running, so definetely an improvement there. However, the temperature reading is too constant that it is simply unbelievable. This was not the case on 6.0.x. Please advise on how to debug from here.
First 2 pictures are on 6.0.x, showing the status on October 5th. Quits between 2 and 4 days after commencing.
Next 2 pictures 5.9.1 (see temperaturenot changing and reporting discrepancy)
Still works when reset on 5 october (3 days encounting).
See that the ispindels are so close a discrepancy of 4 degrees Celsius should not be possible.
The text was updated successfully, but these errors were encountered: