[Bug] Undefined Pybricks Code state after hub.system.reset(1)

[laurensvalk]

Describe the bug
The run button can get stuck, after hub.system.reset(1), and stay that way even if you reconnect.

This test was done on the Technic Hub

Pybricks Code (Beta) v1.1.0-beta.1
Version 91.0.4472.101 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit)

To reproduce

First run the script, then click play again.

from pybricks.hubs import ThisHub
from pybricks.tools import wait

hub = ThisHub()

print(hub.system.reset_reason())

hub.system.reset(1)

And this isn't too bad.

But it remains stuck after you reconnect, so a hard refresh is required.

Expected behavior
Disconnect as during a regular power-off.

[laurensvalk]

Actually, the real cause is one step back. Even though the Bluetooth button correctly shows the disconnected state, the run button becomes enabled again.

So if this button were not enabled, the problem documented in the first post couldn't even occur.

[dlech]

Fix is committed.