msl320m - Unable to Save Scenes with White LED/Temperature Settings

[patrickblackjr]

Describe the bug A clear and concise description of what the bug is.

Your environment

System Health

version	core-2021.12.7
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.9.7
os_name	Linux
os_version	5.10.83
arch	x86_64
timezone	America/Chicago

Home Assistant Community Store

GitHub API | ok -- | -- Github API Calls Remaining | 4914 Installed Version | 1.18.0 Stage | running Available Repositories | 991 Installed Repositories | 7

Home Assistant Supervisor

host_os | Home Assistant OS 7.0 -- | -- update_channel | stable supervisor_version | supervisor-2021.12.2 docker_version | 20.10.9 disk_total | 31.3 GB disk_used | 3.0 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | File editor (5.3.3), Let's Encrypt (4.12.0)

Logs taken when the issue happened

2021-12-30 01:56:09 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration meross_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-12-30 01:56:09 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration grocy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-12-30 01:56:09 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-12-30 01:56:13 WARNING (MainThread) [custom_components.meross_cloud] Skip MQTT cert validation option set to: True
2021-12-30 01:56:15 WARNING (MainThread) [custom_components.meross_cloud]
===============================
Meross Cloud Custom component
Developed by Alberto Geniola
Low level library version: 0.4.2.2
-------------------------------
This custom component is under development and not yet ready for production use.
In case of errors/misbehave, please report it here:
https://github.com/albertogeniola/meross-homeassistant/issues
If you like this extension and you want to support it, please consider donating.
-------------------------------
List of devices reported by HTTP API:
- Kitchen Lights (msl320m) - OnlineStatus.ONLINE
===============================
2021-12-30 01:56:15 WARNING (MainThread) [meross_iot.manager] Found a new device Kitchen Lights (msl320m, HW 2.0.0, FW 2.1.2, class: msl320m:2.0.0:2.1.2) that has become online while we were offline.
2021-12-30 01:56:18 WARNING (MainThread) [homeassistant.components.vizio.media_player] Lost connection to 192.168.1.71:7345

This screenshot shows where according to the icon color the lights should be blue. The only way to get the lights to "true white" (activating the W LED) is to move the temperature slider. The primary way this presents itself is when saving a scene. It will always default back to the color that is selected, regardless of the temperature setting.

Let me know if I can provide additional information that will assist.

I'm not sure if this is just a bug in the way the sync occurs, or a limitation with the API provided by the vendor.

[barbatrukko]

any news here? I have the same problem. Also i tryed to manually edit scene... but not work

msl120b, core-2021.12.10, supervisor-2022.01.1, Home Assistant OS 7.2, integration v1.2.1

[tyrobi]

Not sure if anyone is still encountering this, but I just got it resolved on my end.

In the scene.yaml file, update this device's color_mode value to be color_temp rather than hs, then add a property below it for color_temp: <temperature (int, 100-500ish?)> and another under that as color_temp_kelvin: <temperature (int, in range 2801 - 6500)>

That seems to be running fine for me now, not sure why white mode is being saved as hs (hue-saturation)..