I just checked. The two roast I did today were not deducted from inventory in RW, although the roasts themselves show up correctly. I manually adjusted them.
-
Enter beans into RW including initial weightâŚwhether 1KG or otherwise
-
Initiate the roast in RT
-
edit the roast profile by entering the green bean weightâŚfor example 454gm. I may edit this weight at the beginning of the roast when the temperature is just coming up, or I may enter the green bean weight after the roast has completed. Doesnât seem to matter, and i cannot imagine why it would ( but I guess it could).
4)The green bean weight appears in RW, but the green bean weight has not been subtracted from the initial weight.
Question:
Must I be logged in to RW WHILE I am roasting?
And does RW need to be open WHILE I am roasting?
1 Like
Canât answer you directly but what I do is keep myself logged into both R.W & RT3 while Iâm roasting or editing roast data or edit/creating Recipes. I just never log out of either.
Bruce
Still continues to happen to me as well. Every once in a while the stock declines as it should from a roast of that bean, but 90% of the time, it isnât working. Although it is adding up the roasted weight and roast count for each bean. This is using the latest from Matthew. Again, as Bruce suggests, I am always logged into RW when using RT.
Bob and lanai, Iâd say my process and experience matches yours. I just canât figure it out.
Billy
Yeah. It really needs serious attention to just get it done. I know itâs been looked at and believed fixed prior, but obviously thereâs something more going on here
I roasted two batches of Columbian today. I was logged in to RW at the time and it was running in the background. Again, RW shows that I conducted the roasts but RW failed to deduct the grams of green beans used in the roast from my bean inventory. But, there is another interesting thing I noticed and I am including picturesâŚat least I hope I am.
Here is a pic of RW. It is clear to see that I am logged in:
This is a screen shot from the My Beans area with my Columbian bean selected and on the screen:
The upper right corner shows the three roasts that Iâve made with this bean. Two from todayâŚone from a few months ago. Notice that the user is shown as â@unknown Ownerâ. Maybe Iâm missing something here, but this seems unusual to me. Should it not indicate that I am the owner and show â@lanaiguycoffeeâ?
So the problem persists. Sure would like to get this resolved!
Could there, perhaps, be a relational database problem that is causing confusion with the inventory ownership and roast ownership??
Iâll speculate there are several suppliers in the database listed as Burman Coffee Traders. If you created your own version of that supplier I wonder if, when you created the inventory entry, you got the same vendor but a version created by someone else⌠?? Thereâs really no way to be sure who created what, and more importantly it ought not make a difference, but maybe thatâs the flaw. Again⌠just speculating.
Bruce
Hi everyone, sorry for the late reply here. Iâve been really busy recently with my Masterâs thesis.
To answer a few of the questions you guys have:
- You do not need to be logged into roast world and Roastime in order for the inventory feature to âworkâ.
- I donât think itâs an relational database issue problem (we actually use a nosql database provided by Firebase) since my tests on roast world for inventory updates works okay for me.
- I think this might be an issue specifically with RT and when roasts are created (Iâm not 100% sure). I asked Matthew to double check if he can recreate the inventory issues. Unfortunately I donât have a roaster with me and so I cannot create roasts.
- @lanaiguycoffeeâs âUnknown Ownerâ issue seems to be a bug and I will get that fixed asap.
- @lanaiguycoffee for the roast and weight process, at what point do you assign the bean to the roast? Do you assign the green weight and the bean at the same time? Or do is one added before the other? (Order shouldnât matter but it might help to recreate this issue)
I reported the same thing either in another post called,â 1st Roast after Seasoning (Brazil Santos)â with the @unknown User. This accounts for a ton of unviewable roasts and I mentioned the liklikood of relational database issues. Itâs definitely happening and itâs a big problem in terms of the result to the community
Hi, I wrote in that thread that I manage to deploy a quick fix for this.
1 Like
derrick, I normally enter my green bean name and amount while the roasts is preheatingâŚbetween preheat and charge. However, that is not a firmly established habit. I think Iâve probably done it differently from time to time.
I have the same workflow. I enter bean information and weight during preheating. It does not seem to deduct properly.
Thanks for the reply, Derrick.
Just an updateâŚnone of my 3 roasts yesterday âdeducted correctlyâ from RW inventory. Iâm using the process that lanaiguy and bob outlined a couple of weeks ago.
Just did 3 roasts this past weekend and my inventory on RW deducted properly (except for rounding errors which is to be expected).
This past weekend I roasted with RT v3.1.9 offline (i.e. my laptop wasnât connected to the internet) because I didnât want to pick up RT 3.2.3 right away. So in effect I wasnât âlogged inâ to RW since Iâm offline. Roasting went fine. But for me to edit the roast in RT to identify the bean in my inventory I have to go back online, and then my inventory on RW reflects the amount I roasted. I was fine to let RT update when I went back online after I was done with my 3 roasts (I didnât want to troubleshoot anything if something was to go wrong).
Hi everyone,
Iâm writing here to let you guys know that we tracks down the bug that was causing this issue and will have it fixed soon.
If you guys are available, please let me know if it works on your end. You donât need to do anything on your next roast but include your green weight information.
Iâm having this issue and itâs really causing problems for us. Itâs caused quite a bit of confusion about what inventory we currently have to the point that weâve had to re-weigh every bean we have. A majority of which had incorrect information in RW.
This has been fixed and will be released along with the next version of RoasTime. Weâve been testing various release candidates (weâre on rc-7 which is probably going to be the last rc) for RT 3.4.0. If youâd like to get early access to this you can join the slack group here for instructions on how to try this out: Slack
1 Like
This has been fixed with the new release of RT v3.4.0. Please see Forced RoasTime update, migration to new Bean Inventory system today (3/7) - #37.
If you still experience this issue after upgrading to RT v3.4.0, please open another issue.