Steam Deck Controller ID Lacks Any Letter Code

Thank you for the comment. I input the line into the Konsole and found results for two different Steam Controllers (but I'm assuming both are the same), and I'm guessing the 'Uniq' line refers to the ID? If so, I'm more puzzled as both read out as '123456789ABCDEF', which while more descriptive, still doesn't match what iFixit has on their site.

Yey you should see the same number but correct, 123456789ABCDEF is not correct. Try the jupiter-update-controller command. If you get Python errors, specifically related to JSON, run

steamos-readonly disable

, then in the usr/share/jupiter_controller_update location change:

In

/usr/share/jupiter_controller_fw_updater/d20bootloader.py

json.dumps(devs)

to:

json.dumps(devs, default=str)

and in /usr/share/jupiter_controller_fw_updater/d21bootloader16.py

json.dumps(devs)

to:

json.dumps(devs, default=str)

and also:

'path': item['path'].decode('utf-8'),

to:

'path': item['path'].decode('utf-8') if isinstance(item['path'], (bytes, bytearray)) else str(item['path']),

(Do it with sudo i.e. sudo nano /usr/share/jupiter_controller_fw_updater/d20bootloader.py)

After these changes, jupiter-controller-update started working again. You can also after that do:

systemctl restart jupiter-controller-update

systemctl status jupiter-controller-update

Check it and verify the ID one more time.

Also you can try developer mode enable and set

beta channel

and

beta update.

I wrote about this problem to support and now works for me. I see correct ID controller.

P.S.

It has to be the beta channel and beta software. Earlier I tried the stable channel with beta software, and it didn’t work.

Later, I deleted the directories:

.steam/steam/config

and

.steam/steam/userdata

After restarting and logging back in, I still had 12345678. Then I tried switching to the beta channel and updating to the beta version. After that, the ID was displayed correctly.

I opened a support ticket on Steam about this problem, and it was escalated to the development team yesterday. I think I'll risk trying the procedures you suggested.