No Connection, Please Help!

Hi, I frequently run into this issue, and what frustrates me the most is when it happens while a roast is in progress
and I have to restart the app just to monitor the roasting process again; I’ve tried swapping cables, but that didn’t solve it.
Has anyone else experienced this? Did you find a solution?
Hopefully, the Aillio team has a fix for this.

I’m using a Mac Mini M4 with a USB Type-A to Type-C adapter.

@jedsadazisz may you help me? i dont know what must to do

Hi @jadingopi

If you are using a Bullet R1, you may try updating to the latest firmware version using the link below:

Bullet R1 Web Updater
Please make sure to close RoasTime before connecting, as RoasTime uses the same USB port.

You will need to contact the Aillio Support Team to get the password required to access the web updater. They can also help check the issue, as it might be related to the hardware or USB port.

[email protected]

Thanks!

Also having this issue on a Mac using an adapter, however on an allio bullet r2 pro.

I’m having the same on-going issue. The SW team has been helpful but I’m still having issues. I run on a windows machine. Very frustrating. It started when I upgraded to V4.14.3.

I can’t use roastime on my windows machine either, V4.14.3, no reply to my request for access to the updated firmware.

Last roast was 10/7, had to do it blind. Still no fix.

Is there a way to get access to the previous roast time version that wasn’t broken?

Hi @retsofekaj6pa9 . Could you please open Device Manager and check if the Aillio Bullet Roaster appears under Ports (COM & LPT) or Universal Serial Bus controllers?

  • If it’s under Ports: In RoasTime, open the status dropdown, click Use next to Serial, and restart RoasTime.
  • If it’s under Universal Serial Bus controllers: Click Use next to libusb in the RoasTime status dropdown, then restart RoasTime.

If it still doesn’t work, please try this:

  1. Open PowerShell.
  2. Copy and paste the following command, then press Enter:
Remove-Item "$env:TEMP\roastime-comms\driver" -Force
  1. Restart RoasTime and check again.

Please let us know if this fixes the issue. Thanks!