Differences

This shows you the differences between two versions of the page.

--- dictionary:unitcontrol:turnon [2019/06/09 13:38] – [Color Support] fixed for new plugin color handling James Sentman
+++ dictionary:unitcontrol:turnon [2023/02/13 14:52] (current) – external edit 127.0.0.1
@@ Line 27: / Line 27: @@
   * **xvalue/yvalue** (numbers) Another alternative way to specify the color for a device. You must specify both the **xvalue** and **yvalue** the z value or brightness is taken from the current brightness level of the device.
-===Color Handling===
-If you are using a color capable device keep in mind that the level that the lamp displays the color at is separate from the brightness of the color that you are passing. For example, dimming a lamp to 10% with an rgb color of “FF0000” would result in a color at the lamp that is really “190000” So if you wish a dimmer red, you can just pass the full on along with a lower dim level. Color presets are handled in the same way. This can be a little confusing when just reading about it, but it does seem to make the most sense when actually using the lamp. You have your lamp at a specific color and you wish to change it to another color, you don’t wish the level to change dramatically along with that color preset change. This is how the Phillips Hue bulbs handle color changes natively and how XTension handles the RGB pseudo internally.
-Since the phillips hue bulbs are always treated as simulated including a color setting in the ON command will return the bulb to the last level with that level altering the color that you are passing to be the proper brightness.
-RGB colors on the computer screen do not correspond perfectly to the color displayed by the bulb. A lot of work was done to support the specific transforms necessary for the Phillips hue bulbs and as long as you are choosing a color that the bulb can actually generate the color display is pretty close. For RGB Pseudo devices there could be considerable differences between what is displayed on your screen and what is shown at the lamp. Many less expensive devices seem to have an underpowered red channel and so you may have to boost the red above what you need to see the proper color on the screen in order to see the proper color on the lamp itself.
 ===Examples:===
@@ Line 41: / Line 36: @@
 <code>
---create a scheduled event that will turn on the light in 30 minutes
+--create a scheduled event that will turn on the light immediately and then return it to it’s current state, which may or may not be Off, in 30 minutes.
 turnon "Kitchen Overhead" for (30 * minutes)
+</code>
+<code>
+--to guarantee that a light turns back off after a specific time you need to verify the current state. The “for” switch
+-- returns a light to the state it was at when the command is executed. If the light can be turned on or off by other scripts or
+-- people use 2 commands to specifically generate the command you want.
+turnon “Kitchen Overhead”
+turnoff “Kitchen Overhead” in 30 * minutes
 </code>
 <code>
 --create a scheduled event to turn on the light in 90 seconds
---and another event in 20 minutes and 90 seconds that will turn it back off again.
+--and another event in 20 minutes and 90 seconds that will return it to it’s current state.
 turnon "Kitchen Overhead" in 90 for (20 * minutes)
 </code>
@@ Line 53: / Line 56: @@
 <code>
 -- turn on the light at 8pm and off at 10pm that day
+-- note that the until switch is the same as the for switch above. The light will
+-- return to it’s current state which is not necessarily off.
 turnon “outside light” at date (“8:00pm”) until date (“10:00pm”)
 </code>
@@ Line 66: / Line 71: @@
 </code>
+<code>
+-- set the mired color temperature for a hue bulb to a warm white
+turnon “my hue bulb” color temperature 2700
+</code>
+<code>
+-- do a short alert for a color capable device
+turnon “my color device” rgb color “FF0000” for 2
+</code>
 ===Preset Levels===
-Non-dimmable (discrete) units simply turn on and off. Different kinds of dimmable devices have widely varying behavior when receiving an ON command. Older X10 devices and some ZWave devices treat an on as a dim to 100%. They will always go to full on when receiving an ON command. Other “smart” devices will remember their last dim level and return to that when they receive an ON command. XTension supports all these types of dimmers but some setup in the unit preferences may be necessary to get them to behave as you wish. See the [[getting_started:the_unit:dimmable_types|]] page for more information.
+The behavior of the turn on command is dependent on the dimmable type setting of the unit.
+  * **Simple** a Simple unit assumes that when it is turned on that it goes to full on. A simple device when sent an on will go to 100%
+  * **Simulated** a Simulated device includes the last dim level as known by XTension. This is translated internally to a dim or set value command and will include the last dim level as well as the last color or color temperature the unit was at. This is the default for most modern device types such as ZWave and ZigBee.
+  * **Smart** a Smart device is assumed to be handling it’s own preset levels locally. XTension will send a simple On command and let the device decide what to do but will set it’s database level to the last known value. This is a special use case for “smart” X10 modules and may not apply in any sensible way to more modern devices.
 ===Notes:===