Differences

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

--- supported_hardware:wiz [2021/02/14 14:29]
James Sentman [Other Supported Functions:] added DiscoverDevices command
+++ supported_hardware:wiz [2021/02/14 17:49] (current)
James Sentman
@@ Line 10: / Line 10: @@
 ====XTension Setup:====
+{{:supported_hardware:wiz_setup.png?500 |}}
 The Wiz bulbs use a local network broadcast system to find each other and for control and so can only control devices on the same local network as XTension. Only a single instance of the plugin running is necessary to support any number of devices on the same network. No setup for the plugin is required beyond creating a new interface in XTension and selecting “Wiz Connected” from the device/plugin popup.
 Once you save and enable the plugin it will begin by doing a discovery on the local network. Any devices that are found will have a Unit in XTension created automatically for them if it doesn’t already exist. The Unit will reflect the capabilities of the device as far as dimmable or not and what color or color temperature capabilities are available.
-As of this first beta if you wish to rediscover new devices you must disable and re-enable the interface to do another discovery. Eventually a discovery will be done periodically and an interface button to discover now will be added.
+Discovered devices will initially be named with the interface name you used above and the unique MAC address of the unit. There does not appear to be a good way to get the name of the device that you configured into the Wiz system at this time. Once the Unit is created you can edit it and give it a more descriptive name. The current status and color or color temperature values will be reflected immediately in the new Unit.
-{{ :supported_hardware:wiz_list.png?400 |}}
+You can run a discovery of new devices at any time by clicking the **Discover New Devices Now** button or using the script command “discoverDevices()” as documented below.
-Discovered devices will initially be named with the interface name you used above and the unique MAC address of the unit. There does not appear to be a good way to get the name of the device that you configured into the Wiz system at this time. Once the Unit is created you can edit it and give it a more descriptive name. The current status and color or color temperature values will be reflected immediately in the new Unit.
 ----
@@ Line 59: / Line 58: @@
 </code>
-would set the bulb to run the “Party” scene at a speed of 200 and full brightness.
+would set the bulb to run the “Party” scene at a speed of 200 and full brightness. Note that the scene name is not case sensitive “party” would work as well.
+There is some oddness about how the bulbs respond to these commands that I haven’t figured out yet. When trying to just change the speed of the Party scene without changing the brightness the command is often ignored. If however you also change the brightness as well it seems to accept it. There also appear to be limits to what speeds are available at lower dimming ranges. Some experimentation may be necessary to get these bulbs to do what you desire.
+===Valid Scene Names:===
+The following are the currently valid scene names you can use as the name in the script command. The names are not case sensitive when sent through the script.
+  * Bedtime
+  * Candlelight
+  * Christmas
+  * Club
+  * Cool White (not recommended: just use the regular color temperature settings)
+  * Cozy
+  * Deepdive
+  * Fall
+  * Fireplace
+  * Focus
+  * Forest
+  * Golden White
+  * Halloween
+  * Jungle
+  * Mojito
+  * Night Light
+  * Ocean
+  * Party
+  * Pastel Colors
+  * Plantgrowth
+  * Pulse
+  * Relax
+  * Rhythm (I think this is used as part of a remote control type display and might not do anything otherwise)
+  * Romance
+  * Spring
+  * Steampunk
+  * Summer
+  * Sunset
+  * True Colors
+  * TV Time
+  * Wake up
+  * Warm White (not recommended: just use the regular color temperature settings)
 ----
@@ Line 75: / Line 112: @@
 tell xInterface “name of your wiz interface” to discoverDevices()
 </code>
+  * Reboot a device. A device can be rebooted from the script command reboot()
+<code>
+tell xUnit “name of your wiz device unit” to reboot()
+</code>
 ----
 ====Known Issues and Yet To Do:====
-  * Scenes are still a work in progress.
+  * Values often pop down one from what you set them after the next poll. For example you set the light to 100 and it resets to 99 after the next poll. This is a problem with conversion between the internal 0-255 value and XTensions 0-100 percent that is not completely sorted everywhere. This will be fixed before the release.
+  * If you are running a scene and issue a regular turnon or turn off it will reset the bulb to a non-scene regular setting but the value in XTension will not remove the name of the last scene until the next poll. This will be fixed before the non-beta release.
+  * Setting the scene to “None” does not stop the scene yet. Use a turn off or turn on to a specific color or color temperature to cancel a scene for the moment.
   * If the bulb goes offline you’ll get errors in the log about it not being available for polling rather than an error in the Unit display as is the norm. This will be fleshed out in the next version.

Mac Home Automation

User Tools

Site Tools

Differences

Page Tools