jeshab
December 3, 2019, 8:02pm
917
m4rk:
Commands such as Raise, Lower, Increase, Decrease all work but Raise and Lower actually move the blinds in the opposite direction to expected. 100 = Close. So, ‘Raising’ the number moves the blinds down.
Amazon recently introduced the ability to use open, close, raise and lower commands for the mode, range and toggle controllers via semantic extensions. This support still needs to be implemented in the skill. So, for the time being, the recommended solution is to setup Alexa routines as a workaround.
opened 01:51AM - 04 Oct 19 UTC
closed 06:30PM - 15 Dec 19 UTC
enhancement
Amazon just [announced](https://developer.amazon.com/blogs/alexa/post/49eff766-5… d95-4faf-9205-2ab52ae8a437/announcing-updated-smart-home-building-block-apis-non-controllable-device-states-semantic-extensions-and-expanded-international-support) support for open, close, raise and lower commands via sementic extensions using mode, range and toggle controllers.
It seems Amazon is focusing on improving these controllers instead of creating specific ones that would have limited purposes. This means that we should probably start creating metadata labels for generic device using these controllers. For example, part of this enhancement, a blind-specific label should be included.
