These replies are not always tagging. I must be hitting the wrong reply button.
As I mentioned above, if convenient, would be interesting to see what might happen if you roast offline.
These replies are not always tagging. I must be hitting the wrong reply button.
As I mentioned above, if convenient, would be interesting to see what might happen if you roast offline.
I don’t want to be online because of bug issues like this.
Syncing online is not a good solution, but it might help in finding the issue.
edit, actually, no they do not save randomly. None of the roasts edited after the fact save.
Original text:
never mind, one of my edited roasts hasn’t erased yet. So the whole thing is not consistent.
This is probably a syncing with the cloud issue, like they can’t just leave us offline people alone, and have to force us into some weird moving of files any time we do a fw update or software upgrade.
Tech companies just cannot resist all that free data and they’ll lose a few customers just to keep everyone else sort of on a more automated semi forced system.
They could just add a toggle to “auto sync or no” and leave us alone.
I don’t have plans to roast for a few weeks while since I just roasted 8kg last week. Maybe someone else can try an offline roast to see if they have similar issues as you do with the syncing.
I have not tried to roast offline since RT 3.x back when there was more issues with the software syncing with RW. For my workflow, the 8kg last week on the latest RT was pretty stable for what I do. I never attempt to edit any or my previous roasts while I’m roasting because I’m a manual roaster (i.e. I don’t use playback or recipes which means I have to watch what’s happening and press the buttons) and I also roast back-to-back 3 to 4 kgs per session.
I only edit my roasts to input information like beans, etc., after I’ve shut down and cleaned up my roaster, and I sit down at a desk and then edit in RT.
The way I check if the data is synced while I’m roasting is use my ipad to check RW while my laptop is logging the roast in progress.
Maybe make sure you’re using the latest software. I mentioned what I was using in an earlier post. This past week was the first time I roasted in since May 2023 so I made sure I downloaded the latest client software from their website and did the necessary client, proxy, comms updates (I don’t update my f/w). And I’m using a Win10 old Surface Pro (gen 2) laptop.
Thanks. I did update to the latest software about a week or so ago when this all happened.
That said, I think the issue is when things are NOT in sync. Could be anything from a corrupt file, to a duplicate file, etc. If everything is good, then I think you will have a difficult time replicating it, like aillio tech support is having.
Bab mentioned the issue “fixing” itself, and I noticed I had no issues once I did a sync.
However, when I copied old files onto the files that were in sync, that is when the issue happened, so I got rid of the sync’ed files and just used my old files, and things started to work again while offline.
Can you also try the above and see if it fixes the issue for you?
I tried deleting files and such, but what seemed to do it, was doind a clean install, deleting all files, signing in and syncing, then deleting my sync’ed roasts.
But I wonder if it would work if you just go rid of the synced roasts?
I think I found a way to get it to work.
What caused the issue, is unknown, but I tried deleting all the roast time files, and then syncing, and then adding my old roasts back into the roasts folder. Nothing fixed the issue
However, when I deleted the roasts after syncing, and then added my old roasts without syncing again, suddenly everything started working again.
Guessing the why that worked, is probably a stupid idea, but I’m not that smart, so I’ll do it anyway. Assuming duplicate roasts or something get added when using backup files and sync’ed roasts. Could cause the app to mess up? And either deleting the duplicate or syncing fixes the issue?
Ignore my assumption, but after backing things up, give it a try.
On a Mac the two folders to backup are:
Library>Application Support> RoasTime
and
Library>Application Support> roast-time
When you uninstall RT, these files are not erased, so if you reinstall, they will still be there, and if you are trying to avoid uploading your work to the A.I. copy server, by uninstalling and reinstalling, that doesn’t do it, and when you reinstall, all your work automatically uploads when you reinstall RT and sign in.
Good idea not to edit while roasting. I find with all the extra things one has to juggle roasting on the Bullet, that can be distracting. Most production roasters will make some simple automatic title generator, but go more in depth later on. But a production roaster can time things so that when one batch ends, there is minimal to no preheat for the next roast charge. I do not find that to be the case with the Bullet, and I generally have at least 1 minute to make a title between batches, as I do not like making note during the roast either. I might forget to check to see if the USB fan is going, or open the info box, or change out the chaff basket, or check the chaff plug or chute plug, or all these little extra things that add up, the multitasking on a Bullet is pretty intense.
What I like to do, is edit the previous roast during the back to back preheat. Even if it is just the name. And then edit the roast again after cupping.
So, being able to edit after the roast is complete and not have days or weeks of work completely erased, is probably preferable.
I’m with you on the edit stuff
…gotta say, it is nice to open RT4 and see roast titles.
….whelp, I spoke too soon. Started messing up again, and titles and files are back to untitled. Lost another day of work in a sense.
Very frustrating.
Not to mention the drum is now stalling or slipping. So, may need to tighten some screw or belt or something.
It sounds like the guys in Thailand were able to recreate this happening. We are working on a potential fix.
Thanks. That is great news!
*Drum was an easy fix, was a loose couple screws on a motor gear. Was just bad timing, is all.
So, we believe we have fixed this in Proxy v1.43.1
. Please let us know if you are on this version and still encounter this issue!
Good news!
Once it has been tested will reply here.
Hi, just looked up my proxy, and it is v1.31.10
How do I update?
I got the download from the website which bumped me up to proxy v1.42.2
But how do I get the recommended proxy version?
Still have the issue.
New update worked at first, and then things went bad again. In about a 24hr span.
Anyone else get it working yet?
It has been 1 week, have you guys had any chance to get feedback on the fix?
Hey @jimmybulletroaster - just to confirm you did get the latest version? It should auto update when connected to the network.
We have no heard any feedback - still have the ticket open waiting for it. We are no longer able to recreate the issue. Happy to connect with someone on a screenshare if it is reproducible for anyone.