Galaxy Lamp master switch

[GTunney]

Does the master switch being part of the configuration and not controls within home assistant effect its functionality at all?

I expose all my devices to Alexa but it will not discover the master switch. It will discover the background and laser entities. I have numerous other switch devices which are also discovered. Just not the master switch.

It is also not possible to turn on or off the switch when doing by area. Using dev tools I can’t run the action switch.turnon and switch.turnoff based on area.

[make-all]

Exposure to voice assistants by default is one of the things that category tags affect. I think it can be manually exposed, but this is beyond the scope of this integration so you'll have to check the HA docs for how to do that.

[GTunney]

Thanks, any idea on why it won’t work turning on or off by area?

[make-all]

No idea. Is the entity in the Area? Maybe entities marked as config are not added by default when the device is added to the area, same as what happens on the UI and voice assistants.

[GTunney]

Yup it's in the area.

Is there a reason why the master switch was chosen to be added as a config and not a control by TuyaLocal?

Could this behaviour be changed so it can be added as a control?

[GTunney]

I have managed to resolve this by removing the category: config from the master switch within devices/moes_star_projector.yaml

This now allows me to control the star lamp via area and is also now discoverable within Alexa.

I'm not sure why the decision was made to have the master switch as a config category. It makes more sense to me to have it as a control given that's what it is doing, controlling the the overall projector.

[make-all]

Probably the decision had something to do with this comment on the original request:
#821 (comment)

Though having a master switch could sort of be redundant as dashboard entries have a master (screenshot 1).

I will change the config, since I'm also not sure it makes sense to not have it as a primary control.

[GTunney]

Probably the decision had something to do with this comment on the original request: #821 (comment)

Though having a master switch could sort of be redundant as dashboard entries have a master (screenshot 1).

I will change the config, since I'm also not sure it makes sense to not have it as a primary control.

Did this change get missed in the latest update I'm guessing?

Just updated and it's reverted master switch back to a config not control item.