Differences

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

--- getting_started:the_unit:dimmable_types [2016/03/14 15:10] – external edit 127.0.0.1
+++ getting_started:the_unit:dimmable_types [2023/02/13 14:52] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====Dimmable Unit Types====
-Different devices can have widely different dimming behavior. XTension supports all the different types by providing 3 kinds of dimming behavior, or in the case of some specific devices forcing the behavior to what works in order to avoid confusion. The three dimmable types were originally developed for the different kinds of X10 devices, but the logic holds and is helpful for all other device types as well. In the [[getting_started:the_unit|Unit Interface Dialog]] the dimmable type is selected from a popup menu opposite the “dimmable” checkbox. Units without the dimmable checkbox set can only be on or off, called “discrete”. When the checkbox is set you can select from 3 types of behavior: **simple**, **simulated**, and **smart**.
+The Dimmable type popup changes the behavior of a dimmable unit when using the turn on command.
 ===Simple===
-For X10 devices a simple device would be the original push button wall switch. A simple dimmable device can be dimmed, but responds to an ON command by going to full on (100%). Many ZWave devices also behave in this way. By selecting the unit dimmable type that corresponds to the actual behavior of the unit it makes sure that the value display in XTension properly corresponds to what the device is doing.
+Simple devices assume that the value goes to full on when an on command is sent. This is the default behavior for legacy X10 units as that is how they physically behave. There are also modern ZWave and UPB modules that behave the same way. If your device always goes to full on when you send the on command (and that is how you want it to behave, see simulated below) then select this unit type
 ===Smart===
-Most Zwave and Zigbee devices are Smart. When you set a dim level either at the switch manually or via a [[dictionary:unitcontrol:dim|]] command the switch itself remembers that value and will return to that value the next time it receives an ON command. Unlike simple devices the switch will not return to 100% when you turn it back on. If this is the behavior you want for any given script or event you can simply send an ON command. If you wish to know for sure what the value is going to be use a dim or brighten command. There are many kids of X10 “smart” devices as well. These devices often are 2 way sending you updates for local changes and may respond to other commands for faster dimming and more features such as the [[dictionary:unitcontrol:xpress|]] command.
+Smart devices are expected to manage their own preset levels. If you turn on a Smart device then XTension will assume it’s going to go to the last preset level that XTension knows about. It may have had it’s own internal level changed manually since then though so the XTension database may assume that the device has gone to 75% but it was changed manually at the switch to 50% and so the database may be wrong in these conditions. The database will be updated the next time the device is queried or changed via a script or direct XTension command.
-===Simulated==
+===Simulated===
-The simulated dimmable type was developed for “simple” X10 devices that suffered from the “Nova” effect, that once off they could not be brightened, upon receiving the first dim command they would jump to 100%. A simulated X10 device is never turned hard off, but dimmed to 0 when you send the off command. And an on command sends a brighten to the last known level for that device.
+Simulated devices are where things get more interesting and useful.
-By using a simulated setting for any “simple” device you can simulate this behavior for any device that doesn’t support it if you wish. You can also change the preset that XTension will use to set the value of the lamp using the [[xtension_manual:simulatedpresetdim|]] command. This sends nothing to the lamp itself, just changes the preset level in XTension that will be used when the lamp next turns on.
+If you set a device to simulated then XTension will never actually send an ON command at all but instead will substitute a dim command to the current preset level as known by XTension. You can change the preset level that XTension will send via the [[dictionary:unitcontrol:simpreset|sim preset]] verb.
+Most modern devices maintain an internal preset level that is set whenever the device changes it’s level to anything other than off. If you manually dim a ZWave device to 10% then the next time the switch it turned on manually or the next time an ON is sent from XTension it will return to that 10%. So if last night you dimmed your lights but this afternoon you want them to come on at full when XTension turns them on for you you should use a simulated device type or use the dim command rather than the turn on command. Using the sim preset verb in XTension does not send any command to the device itself and will not change the level of the device, it only affects what value is sent with the next on. For currently known units there is no way to send a preset level to a switch without changing it’s current dim level.
+In my own home I often manually brighten the bathroom lights to a low value if I am getting up early in the morning. That low level then sticks as the switches local preset and when I tap the switch later they only go on to 10% and I have to stand there and hold the paddle. To work around that at some point after everyone has had their shower and the lights have been turned off I send them a dim to 100 command and then immediately afterwards a turn off command. The ramp rate of the light combined with the fact that LED bulbs don’t turn on instantly means that the lights don’t even flicker on but now the internal preset of the switch has been set to 100% so that when I next turn them on at the switch they go to full on.
+Changing a devices value manually at the device does not update the preset level in XTension, so any other ON commands that you send to a simulated device will result in them going to the value that you have set in your scripts.
 NOTE: Though Phillips hue bulbs are technically “smart” in XTension they ignore their dimmable setting and are always treated as simulated units. In my testing with them they would often get confused about color or level values, especially in the case of a power hit or other minor such problem. This led them to often being out of sync with XTension. When using Phillips Hue bulbs and sending an ON or a dim command the current color and level information as known by XTension is always sent along with the command.
+====History====
+The 3 types of dimming devices date back to the beginnings of time and the X10 protocol. The Simulated device type was designed to work around the “Nova” feature of early X10 switches and lamp modules. You could not brighten them up from off to a desired level. If you sent them a brighten command they would “nova” to 100% and then from there you would have to send them dim commands to go down to the desired level. XTension introduced the simulated device type so that you could never turn them all the way off. If an X10 device that is set to simulated is turned off the OFF command is not actually sent but instead the device is dimmed to 0 so it appears to be off, but from this state you can say dim to 10 and it will brighten gently to 10% avoiding the “nova” affect of those early devices. Modern devices do not have the nova problem but still benefit from having different ways of handling the preset levels.