This is a know issue, we already fixed it in the next Homey Firmware version (it is caused by a “bug” in Homey core)
