Sending example.com "firmware update" to devices

[Kasoo]

I notice upon connecting to the server my device says

Firmware update available! Starting now...

In the device logs it looks like inker is sending a fake firmware url down the device, i presume it shouldn't be doing this!

I: src/api-client/display.cpp [131]: Payload - {"status":0,"image_url":"https://INKER/assets/default-screen.png?t=1783168749190","filename":"default-screen-1783168749190.png","image_url_timeout":0,"firmware_url":"https://example.com/firmware/v1.0.0.bin","update_firmware":true,"refresh_rate":900,"reset_firmware":false,"special_function":"","temperature_profile":"default","maximum_compatibility":false,"battery":100,"wifi":-67}
I: src/bl.cpp [2257]: update_firmware: 1
I: src/bl.cpp [2260]: firmware_url: https://example.com/firmware/v1.0.0.bin

I see that example firmware url is in backend/prisma/seed.ts, but i don't understand the implications of this:

  // Create sample firmware
  const firmware = await prisma.firmware.upsert({
    where: { version: '1.0.0' },
    update: {},
    create: {
      version: '1.0.0',
      downloadUrl: 'https://example.com/firmware/v1.0.0.bin',
      releaseNotes: 'Initial stable release',
      isStable: true,
    },
  });

[wojo-o]

Thanks for flagging this. That example.com firmware entry comes from the default seed/dev data (backend/prisma/seed.ts) — it's placeholder sample data, not a real firmware target. I'll adjust this so the seed no longer sets update flags and devices won't pick it up. Will be sorted in the next release.

[wojo-o]

Hey I created beta version of 0.5.1, please try and give me feedback if everything works on your instance.

    docker run -d \
      --name inker \
      --restart unless-stopped \
      -p 80:80 \
      -v inker_postgres:/var/lib/postgresql/17/main \
      -v inker_uploads:/app/uploads \
      wojooo/inker:0.5.1-beta