MRC Magnum floor heating device keeps getting discovered as cc_curtain

[CVD95]

Hello,

I've added 3 MRC devices successfully, of which one had the options for the floor heating and cc_curtain.
The 4th device, which was actually the first one I tried, keeps giving cc_curtain as only device type.

I've tried re-adding the device to the smart life app to get a new local key 3 times.
I also tried restarting the device manually twice (waiting 30 secs to turn them on).

When trying to add the device I've used the following parameters: device id (not uuid), Auto, local key, auto (and 3.3 sometimes).
I've tried adding the device a lot of times, just to see if the device type would change, but it wouldn't.

The device details JSONs are similar to each other. Here are some values of it:

• product_id: fy783e8g0n38ahlt
• product_name: MRC
• model: MRC-2
• sub: false
• category: wk

As reference, this is the commit which added the device: 80deb01

I hope you can help me with this.

Thanks in advance

Home assistant version: 2023.11.1
Tuya local version: 2023.10.0

Logs:
2023-11-09 21:58:26.196 WARNING (MainThread) [custom_components.tuya_local.config_flow] Report this to https://github.com/make-all/tuya-local/issues/
2023-11-09 22:00:28.269 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop by custom integration 'tuya_local' at custom_components/tuya_local/device.py, line 77: self.api = tinytuya.Device(dev_id, address, local_key), please create a bug report at https://github.com/make-all/tuya-local/issues
2023-11-09 22:00:31.601 WARNING (MainThread) [custom_components.tuya_local.config_flow] Device matches cc_curtain with quality of 10%. DPS: {"updated_at": 1699563628.4383764, "2": "MANUAL", "3": "warming", "16": 197, "24": 205, "101": "time_date_temp", "104": 0, "107": false, "108": false, "109": 0, "110": "2", "111": "2", "112": 0, "114": "0_5", "115": 5, "117": 30, "123": 7943, "124": "wood", "125": "12k", "126": true, "127": true}
2023-11-09 22:00:31.601 WARNING (MainThread) [custom_components.tuya_local.config_flow] Report this to https://github.com/make-all/tuya-local/issues/
2023-11-09 22:06:08.277 WARNING (MainThread) [homeassistant.util.async] Detected blocking call to sleep inside the event loop by custom integration 'tuya_local' at custom_components/tuya_local/device.py, line 77: self.api = tinytuya.Device(dev_id, address, local_key), please create a bug report at https://github.com/make-all/tuya-local/issues
2023-11-09 22:06:11.320 WARNING (MainThread) [custom_components.tuya_local.config_flow] Device matches cc_curtain with quality of 10%. DPS: {"updated_at": 1699563968.5547712, "2": "MANUAL", "3": "warming", "16": 197, "24": 205, "101": "time_date_temp", "104": 0, "107": false, "108": false, "109": 0, "110": "2", "111": "2", "112": 0, "114": "0_5", "115": 5, "117": 30, "123": 7943, "124": "wood", "125": "12k", "126": true, "127": true}
2023-11-09 22:06:11.320 WARNING (MainThread) [custom_components.tuya_local.config_flow] Report this to https://github.com/make-all/tuya-local/issues/
2023-11-09 22:15:59.617 WARNING (MainThread) [homeassistant.util.async] Detected blocking call to sleep inside the event loop by custom integration 'tuya_local' at custom_components/tuya_local/device.py, line 77: self._api = tinytuya.Device(dev_id, address, local_key), please create a bug report at https://github.com/make-all/tuya-local/issues
2023-11-09 22:16:02.502 WARNING (MainThread) [custom_components.tuya_local.config_flow] Device matches cc_curtain with quality of 10%. DPS: {"updated_at": 1699564559.7544446, "2": "MANUAL", "3": "warming", "16": 197, "24": 260, "101": "time_date_temp", "104": 0, "107": false, "108": false, "109": 0, "110": "2", "111": "2", "112": 0, "114": "0_5", "115": 5, "117": 30, "123": 7943, "124": "wood", "125": "12k", "126": true, "127": true}
2023-11-09 22:16:02.502 WARNING (MainThread) [custom_components.tuya_local.config_flow] Report this to https://github.com/make-all/tuya-local/issues/

[make-all]

The logs show that not all dps are being reported by this device. I don't know why this one device would be acting differently than the others, but I have marked the missing dps as optional to allow matching in this condition also.

[CVD95]

I've successfully added it to hass now with the new release. Thank you!