Cannot connect to Powered Up Remote

[laurensvalk]

I'm using https://beta.pybricks.com/ and I've installed the (I assume) latest firmware though the interface.

When trying the Remote example code, the hub LED begins to pulse and the remote LED blinks white, but it doesn't appear to connect and then I get
Traceback (most recent call last): File "main.py", line 6, in OSError: [Errno 116] ETIMEDOUT

I'm using the City hub by the way

I press the "Download and run this program" button and the green button on my remote at the same time. The remote blinks white and the hub pulses but it doesn't appear to connect. The remote stops blinking roughly the same time as the timeout.

Originally posted by @pqhf5kd in #186 (comment)

[laurensvalk]

Could you share the script you used?

Can you also add the following to your code, and share the output?

from pybricks import version
print(version)

[pqhf5kd]

from pybricks.pupdevices import Remote
from pybricks.parameters import Button
from pybricks.tools import wait

# Connect to the remote.
my_remote = Remote()

while True:
    # Check which buttons are pressed.
    pressed = my_remote.buttons.pressed()

    # Show the result.
    print("pressed:", pressed)

    # Check a specific button.
    if Button.CENTER in pressed:
        print("You pressed the center button!")

    # Wait so we can see the result.
    wait(100)

[pqhf5kd]

('cityhub', '3.1.0a3', 'v3.1.0a3 on 2021-07-19')

[dlech]

It is working for me with the same firmware version. They only way I know to troubleshoot would be to connect the defective remote to a computer and log the Bluetooth packets. Maybe the remote has different firmware or something like that?

[dlech]

Also, try turning on the remote later after the program is already started instead of pressing the buttons at the same time.

[pqhf5kd]

I'm on a 2021 MacBook Air. The remote doesn't appear in the bluetooth list when in pairing mode, nor does it on iOS.
It does appear in the bluetooth list on iOS after connect through the PUP app. Is that normal?

It connects through the app quickly, without any issues.

[dlech]

You would need to use a program like pybricksdev that knows how to connect to the remote.

[laurensvalk]

Maybe the remote has different firmware or something like that?

Do you remember roughly when this remote was purchased? Was it purchased separately or as part of a train set?

[laurensvalk]

Someone on our Facebook page has reported a similar issue.

@dlech, if more people run into this, perhaps we can share a firmware zip here that prints out relevant debug info during the connection process, so people can try it without Pybricksdev.

[pqhf5kd]

Someone on our Facebook page has reported a similar issue.

@dlech, if more people run into this, perhaps we can share a firmware zip here that prints out relevant debug info during the connection process, so people can try it without Pybricksdev.

That was me on Facebook, sorry!

The remote came from a 60198 set that I purchased sealed, but from a private seller, in December 2020. I had a look on the box, but it doesn't look like there's a date code.

The remote has the following under the battery box:

• '25IO' in print

The following is moulded:

• 209-J00326
• HANDSET NO.2
• IC: 3072A-28739
• FCC ID: NPI 28739
• CMIT ID: 2018DJ5115

[dlech]

I just had another idea. If you have iOS or Android, you can install nRF Connect and sniff the adverting data from the remote.

We are looking for the raw advertising data like this: