Caine Nielsen avatar image
Caine Nielsen asked

Is PowerLevelController broken? Overruled by brightness?

After attempting to add the powerLevel controller to our Alexa smart-home skill, I have found that I am unable to trigger a powerLevel command. I am not seeing a powerLevel controller visual interface in the Alexa mobile app (Android, iOS), and when attempting to adjust the device powerLevel Alexa simply responds "Ok" without making any requests. (We are not receiving request to our back end.)

I am following the docs, and our discovery and stateReport objects include the powerLevel controller and look to be formatted correctly. All other controllers are working fine, toggles, brightness, etc.

I have seen other posts here on the forum regarding the powerLevel controller not working, I will list those below. Some mention that the powerLevelController is sometimes overwritten or covered up by the normal powerController or the brightnessController interfaces. Our skill is using both as well.

Anyone who can help would be much appreciated. I may end up switching to a rangeController since we have seen success with those for our devices, but if at all possible, I would like to avoid that.

Is this a bug? Is this expected functionality? Does powerLevel not have a visual interface? Let me know.


alexa smart homeapppowercontroller
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

KatC@Amazon avatar image
KatC@Amazon answered

Hi there,

I know we've talked to you via our Contact Us page, but I wanted to add an answer here in the forums as well for others. What you're describing is considered expected behavior by our engineering team, as certain interfaces interfere with the functionality of others, such as the BrightnessController and PowerLevelController. The recommended utterances for triggering them are the same, and so the controllers don't always behave as expected when used together (although I know this is not always explicitly mentioned in our documentation).

The recommended workaround continues to be the use of primitives/generic controller interfaces instead of the powerLevelController, such as the rangeController you mentioned. Information on generic controllers can be found here:

There is no plan to change this functionality, but if anyone has a specific case where the rangeController can't be utilized, I would be happy to bring your situation to our engineers and request their feedback. Please use the Contact Us page in the Developer Console to open a case with our Developer Advocacy team so that we can pull up your skill information and help you with your specific case.

10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.