chore(suite): unreadable device tips improvements

[mroz22]

addressing #14284

todos:

• do we have a knowledge base article addressing old hid devices fw update issues?
• do we wan't to include button to switch to using old bridge (desktop only)

cc @MiroslavProchazka

resolve #14284

[MiroslavProchazka]

I would not lead them to KB article as there is a significant chance they will brick the device. I would just lead them directly to write tech support

[MiroslavProchazka]

Regarding the button switch, @Hannsek and @Hermez-cz shall decide. I would be personakls up for adding it there.

[Hannsek]

If we can target the specific firmwares then yes, let's do it. I had it in the design suggestion somewhere.

But if it is just ~ 10 users, we shouldn't spend time on this.

[Hannsek]

We have this on KB:

[mroz22]

I would do something like this (for desktop)

and this for web

explanation why I believe it makes sense as suggested here https://github.com/trezor/trezor-suite/pull/14637/files#diff-4f4ba83e95f4c0800b23ced0ac2643abf14ea387d3de6e91d0ac38b47113e2bfR123

cc @Hannsek please check on it and please give me the KB link.

Also connect-device troubleshooting probably should be revisited as well.

[Hannsek]

It seems fine to me. The KB article is here.

@Hermez-cz please check it as well.

[Hermez-cz]

Hi, I didn't catch if we can recognize affected devices. Is that possible please?

The bridge toggle might be puzzling minds of all users with connection issues and there's no way they'll understand what it's about. They have no idea what bridge is, what might be an alternative implementation, what does the 3.0.0-bundled.24.10.0 mean etc. All feels very non-transparent and anyone might just feel forced to give it a blind shot.

Also old Trezor model vs. firmware version sounds fuzzy like this. Should we refer only to firmware / device software perhaps? Because it doesn't mean a thing if my Model One would be very old if I'd keep it up to date.

The URLs are the most prominent thing in the whole page, more prominent than those bullet point titles, is that intentional?

[Hannsek]

Please do some adjustments:

• display this 4 points error only for HID devices
• other devices should see only first and fourth point (is there another troubleshooting step that may help core devices?)
• adjust second point so that after clicking on the link, a bridge modal would appear where the toggle to switch to old bridge will be present

[mroz22]

no changes here. sorry for diff

[martykan]

Looks good 👍

Only thing I noticed when testing is when toggling bridge implementations the error changes into "App can't communicate with device" momentarily. But that's probably not important

[Hannsek]

@evgenysl Once you'll be testing that, please post here screenshots of how does it look now. 🙏🏻

[bosomt]

This is what i see on 24.11.2 when i connect 1.3.3 device

Info:

• Suite version: web 24.11.2 (b44a924)
• Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
• OS: MacIntel
• Screen: 1512x982
• Device:
• Transport: WebUsbTransport

[bosomt]

This is Node bridge and app with same device

Info:

• Suite version: desktop 24.11.2 (b44a924)
• Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) TrezorSuite/24.11.2 Chrome/128.0.6613.162 Electron/32.1.2 Safari/537.36
• OS: MacIntel
• Screen: 1512x982
• Device:
• Transport: BridgeTransport 3.0.0-bundled.24.11.2

[mroz22]

Hmm I think it should have displayed something different. Could you please also post old bridge status page with that device?

[bosomt]

Same device with old bridge running