Skip to content
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

Thermo Sensor data not being sent from Tablet #30

Closed
sundogit opened this issue Apr 10, 2013 · 7 comments
Closed

Thermo Sensor data not being sent from Tablet #30

sundogit opened this issue Apr 10, 2013 · 7 comments

Comments

@sundogit
Copy link

So I have a new setup running and the flow meters and relays are all working as they should through the system. However, the thermo data isn't getting back to the server from the tablet.

On my first setup, the thermo sensors auto populated in the DB when the tablet was first setup and ran core... this time it didn't... I hooked the kegboard up to the server and ran pycore and saw all the thermo sensor data coming through so they're working... so then i manually created the Thermo sensors in the DB using the raw names I was seeing in the pycore monitoring (for example kegboard.thermo-da00000400dadc28), but I'm still not getting anything from the tablet running Core to the server. The Thermo logs are empty and obviously no temp is shown on the tablet or the server...

I've tried restarting everything, re-running the setup on the tablet, heck even removing the app completely from the tablet and re-downloading it from the Play store, but it just doesn't want to send the thermo data...

Not sure what to do next... here's the bug report from the Android App if it helps... I notice it's not listing the thermo device under the taps as it has them assigned in the DB, but maybe it's not supposed to... I guess I don't know much about the App.

Kegbot bugreport.

--- Kegbot core ---

Package info:

versionName=1.0 beta 29
versionCode=29
packageName=org.kegbot.app
installTime=Fri Mar 08 10:43:08 CST 2013
lastUpdateTime=Fri Mar 08 10:43:08 CST 2013
installerPackageName=com.android.vending
signature=06D936CB1BB9FB1A6BD4FC80105BDD79A5AF137F

Core info:

mStarted=true
deviceId=7B6D49007973F210
gcmId=
enableFlowAutoStart=true
allowManualLogin=true
allowRegistration=true
cacheCredentials=true

TapManager

numTaps=2 
mFocusedTap=[Tap meterName=kegboard.flow0 name=Left Tap mlPerTick=3.378570079803467]
All taps:

  meterName=kegboard.flow0 
  mlPerTick=3.378570079803467 
  relayName=kegboard.relay0

  meterName=kegboard.flow1 
  mlPerTick=3.378570079803467 
  relayName=kegboard.relay1

FlowManager

numActiveFlows=0 
totalFlowsProcessed=1
Recent flows:

  id=1 
  ticks=0 
  strval=Flow id=1 finished=true tap=[Tap meterName=kegboard.flow0 name=Left Tap mlPerTick=3.378570079803467] user=root ticks=0 volume_ml=0.0 
  timeSeries=0:0 2107:0

SyncManager

KegboardManager

HardwareManager

AuthenticationManager

ConfigurationManager

SoundManager

BluetoothManager

--- System logs ---

--- (end of bugreport) ---

mike
Mar 08, 2013 - 10:03 AM
Email the bugreport to bugreport@kegbot.org (which should be the default recipient, did you change it?)

sundogit
Mar 08, 2013 - 10:03 AM
I just sent the file over bluetooth to my machine so that I could see what it had in it in case I saw something that would help me figure it out. I'll send it.

mike
Mar 08, 2013 - 11:03 AM
Actually, is there nothing in "System logs"? If so, e-mail won't be any different..

I'll try to repro later today..

sundogit
Mar 08, 2013 - 11:03 AM
Hmm... what System Logs? As in on the server?

mike
Mar 08, 2013 - 11:03 AM
Hmm... what System Logs? As in on the server?
The "System logs" block of the text you pasted above. I assumed (wrongly) that you scrubbed it; it should have lots of data. Probably your device's version of android isn't making them available; sigh..

sundogit
Mar 08, 2013 - 11:03 AM
Ah I see now. Yep I'm dense.

I suppose a rooted Xoom might give those logs?

mike
Mar 08, 2013 - 11:03 AM
I suppose a rooted Xoom might give those logs?
Probably not worth the trouble..

In Android Settings, do you see a "Developer options" section, and within it, "Take Bugreport"? If so, please grab that and send it to the same address (after repo'ing the problem).

If you do not see "Developer options", try following these instructions to reveal it (groan): http://timgray.blogspot.com/2012/11/enable-developer-mode-on-your-jelly.html

If neither work, we can try something else.

Also, if you are running the kegbot server in the foreground (ie with runserver), there should be some logs for each http request, so we can see what's going on from that side. If you have those, send them along.

sundogit
Mar 08, 2013 - 12:03 PM
Nope don't have the option and the reveal didn't work either. It's running 4.0.4 and i don't think that the take bug report was put in until 4.1.x?

The server is normally running via supervisor but I'll fire it up in the foreground and capture what's going on.

sundogit
Mar 08, 2013 - 1:03 PM
Posting the errors here too in case anyone else would ever come across it.:

[08/Mar/2013 15:12:01] "POST /api/thermo-sensors/kegboard.thermo-da00000400dadc28 HTTP/1.0" 401 5739
[08/Mar/2013 15:12:02] "POST /api/thermo-sensors/kegboard.thermo-0900000400c37c28 HTTP/1.0" 401 5739
[08/Mar/2013 15:12:05] "POST /api/thermo-sensors/kegboard.thermo-2600000400922f28 HTTP/1.0" 401 5739
Is there a place to put in the API key that I missed?

mike
Mar 08, 2013 - 1:03 PM
What version of Django are you using (run kegbot-admin.py version)

If it's 1.5, can you please try: pip install Django==1.4.5?

sundogit
Mar 11, 2013 - 11:03 AM
(kb)root@keg:~# kegbot-admin.py version
1.4.4

sundogit
Mar 13, 2013 - 8:03 AM
So should I upgrade to 1.4.5? Or... is something else going on?

sundogit
Apr 10, 2013 - 12:04 PM
Mike?? Hello??? still having this problem...

mike
Apr 10, 2013 - 12:04 PM
The forum is not meant to be a bug tracker, and your last message would be a poor bug report.

Please open up an issue on github.com/Kegbot/kegbot .

Include the kegbot server and app versions you are using, which should be the latest.

sundogit
Apr 10, 2013 - 12:04 PM
OK I can do that - you were just responding to every post here with ideas and suggestions so I just thought you were going to continue doing that.

I'll copy everything that we've both said here and put it all into a new bug report.

And for the record, I did upgrade to 1.4.5.

@mik3y
Copy link
Member

mik3y commented Apr 10, 2013

So it still isn't clear:

  • Are you now running the latest Kegtab version (1.0.0b37)?
  • Have you upgraded your Kegbot server to version 0.9.8?

@sundogit
Copy link
Author

Yes we're on the latest Kegtab version

No we currently don't have 0.9.8 running - I just submitted another bug for what happening when we upgraded. Once we get it running, we'll see if the thermo's come through

@mik3y
Copy link
Member

mik3y commented Apr 12, 2013

I think this was resolved in Kegbot/kegbot-server#119. Please re-open if not.

@mik3y mik3y closed this as completed Apr 12, 2013
@sundogit
Copy link
Author

Negative ghostwriter. Thermo data still not showing on the tablet and not being stored in the DB.

@sundogit
Copy link
Author

And it doesn't look like i can re-open the issue... unless you meant make a new issue...

@mik3y
Copy link
Member

mik3y commented Apr 12, 2013

Ok, let's try again. Please provide:

  • Django request logs
  • Android bugreport

.. from a new, minimal reproduction of the problem.

For the sake of brevity in this report, you can e-mail both to bugreport@kegbot.org, and update here when done.

@mik3y mik3y reopened this Apr 12, 2013
@sundogit
Copy link
Author

Update: So I upgraded everything and wasn't getting the thermo data still. But, for a different issue i was having with Users not showing on the tablet, i re-ran the setup wizard and magically I get the thermo data again. I hadn't ran the setup wizard in a few months, so maybe with all these changes made in the background, something just needed to be kicked by the Android setup wizard.

So, in short, wahoo!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants