pybricks/util_pb/pb_device_stm32: fix pb_device_set_power_supply port offset

This was using the I/O port offset instead of using the motor port
offset. Since it controls the motors, it needs to use the motor port
numbering.

This was only noticed on move hub since it is the only hub where there
are motor ports without I/O ports.

Fixes: pybricks/support#913

Author: dlech

CHANGELOG.md

@@ -6,9 +6,13 @@
 
 ### Added
 - Added `close()` method to `DCMotor` and `Motor` so they can be closed and
-  re-initialized later.
+  re-initialized later ([support#904]).
+
+### Fixed
+- Fixed `Light` controlling wrong ports on Move hub ([support#913]).
 
 [support#904]: https://github.com/pybricks/support/issues/904
+[support#913]: https://github.com/pybricks/support/issues/913
 
 ## [3.2.2] - 2023-01-06
 

pybricks/util_pb/pb_device_stm32.c

@@ -201,9 +201,9 @@ void pb_device_set_power_supply(pb_device_t *pbdev, int32_t duty) {
     // is only valid on Powered Up platforms and it assumes that motor driver
     // id corresponds to the port.
 
-    #ifdef PBDRV_CONFIG_IOPORT_LPF2_FIRST_PORT
+    #ifdef PBDRV_CONFIG_FIRST_MOTOR_PORT
     pbdrv_motor_driver_dev_t *motor_driver;
-    pb_assert(pbdrv_motor_driver_get_dev(pbdev->iodev.port - PBDRV_CONFIG_IOPORT_LPF2_FIRST_PORT, &motor_driver));
+    pb_assert(pbdrv_motor_driver_get_dev(pbdev->iodev.port - PBDRV_CONFIG_FIRST_MOTOR_PORT, &motor_driver));
 
     // Apply duty cycle in reverse to activate power
     pb_assert(pbdrv_motor_driver_set_duty_cycle(motor_driver, -PBDRV_MOTOR_DRIVER_MAX_DUTY * duty / 100));