current
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
current [2018/07/14 10:44] – James Sentman | current [2023/12/19 22:15] – 9.5.4 release James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====XTension | + | =====Download |
- | Released: 7/13/2018\\ | + | |
+ | Released | ||
\\ | \\ | ||
- | Download: [[http:// | + | Download |
- | zipfile md5 = [[tech_notes: | + | |
+ | **This is an important update for NGROK users.** This updates the ngrok client to support the system changes they are making live. The older version will no longer be supported very soon. Anyone using ngrok tunnels should definitely perform this upgrade as soon as possible. | ||
- | ====Change Log==== | + | **Minimum System Version** for this release |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | * NEW: wiki artivle discussing the excellent [[supported_modules: | + | |
- | * NEW: Vera UI7 new [[dictionary: | + | |
- | * NEW: Vera UI7 support for the new [[supported_modules: | + | |
- | * FIX: Vera UI7 now properly recognizes door and motion sensors and will create units for them in XTension without you having to wait for an event to happen on them. | + | |
- | * FIX: unrecognized security devices should now automatically create a unit for their tripped state once the first change for that unit is received. Previously we were suppressing those incorrectly. This means that I don’t have to manually add every single potential type of security unit but ones I haven’t manually added will not create a unit at startup, only after a change in state has been sent. | + | |
- | * FIX: Fixed a problem with the web remote not processing the correct “state” advanced label syntax based on the value of a unit. Basically it was always treating a unit as if it were not-dimmable so you would only ever get the off state and the first on state. Now it will probably parse that state list and give you the correct label. | + | |
- | * FIX: A regression in a previous build caused the RFXt driver to launch the wrong actual plugin. Thats now fixed and the RFXt will work normally again. | + | |
- | * FIX: The “show properties” button in the toolbar of the edit unit window once again shows the properties window for the unit rather than opening up an empty window and logging an error. | + | |
- | * FIX: Vera UI7 now properly | + | |
- | * FIX: Vera UI7 I was using the wrong state variable for the energy savings mode, it should now update properly when the mode is changed locally at the thermostat or through other vera interfaces. | + | |
- | * FIX: If you’re editing a script that has an idle timer created and run it in the script editor and then click cancel rather than save the timer and script will no longer be left running in the background with no way to stop them except for quitting and restarting XTension. | + | |
- | * NEW: Web Remote and Mobile Web Remote both display the color temperature as a degrees k value like the built in control in XTension. | + | |
- | * NEW: Web Remote and Mobile Web Remote when controlling a color or color temperature unit now will show the current state of the color or temperature in a box in the upper right of the detailed unit controls just like the desktop control did. Clicking on that control will bring up a small window where you can physically type in a color’s RGB value or a color temperatures degree k value and send it specifically | + | |
- | * NEW: You can now save a preset from the mobile web remote. The previously was impossible because you could not generate a control-click to bring up the contextual menu on an iPhone. There is now a “save preset” button that brings up a list of the current presets for you to select from into which it will then save the current state of the bulb, color temperature or color as currently operating. | + | |
- | * NEW: plugins can now execute script handlers inside either it’s interface script or inside a units ON script | + | |
- | * NEW: plugins can now define script handlers and insert them into the “insert” menu when editing either the units ON script or the interface script so you don’t even have to go read the wiki to know what information | + | |
- | * NEW: Via that mechanism the new Vera UI7 plugin adds the “on central scene” handler and some documentation to that popup when you’re editing an eligable units ON script. | + | |
- | * NEW: a plugin may save to a unit a “default” label that describes the current state but without overriding the ON and OFF label of the unit if the user has set those. For example the new thermostat support | + | |
- | * FIX: using the “install plugin” menu item to install a different version of a plugin that ships inside of XTension no longer tries to remove the one that is in the application. It just puts the new one inside the plugin folder in your database where it will override the shipped version. | + | |
- | * FIX: fixed an error condition with the Shared Database sender that could have it spinning at 100% of a CPU during certain error states while it retried | + | |
- | * NEW: Vera UI7 added another script command for Update Neighbors. If a device is not responding or not reliably responding to commands you can reconfigure just the units nearby to try to create a new path. There is no interface button for this yet but you can do it via the command line by issuing something like: tell xUnit “name of a unit” to updateNeighbors() | + | |
- | * FIX: after installing a plugin via the “install plugin” menu item only interfaces that were actually enabled at the time of the install are restarted. Previously all interfaces assigned to the plugin were started up even if they were disabled at the time you installed the plugin. | + | |
- | * NEW: the install plugin now internally works the same as the new [[dictionary: | + | |
+ | **Rosetta Note:** While the entirety of the main app and all more recent plugins are Universal and run natively on Intel or Apple Silicon there are a few older plugins including the W800 and CM11 that are still Intel only. They run fine under Rosetta and you’ll never notice the difference. The only issue is that Rosetta is not included by default on the new Apple Silicon Macs. You’ll need to first run any Intel app, or do a get info on any app at all and select “open using Rosetta” then the OS will tell you that you need Rosetta and would you like to install it now. Once you complete that those plugins will run normally. | ||
- | Note: 6:30am 7/14/18 I am still plagued by the occasional version control snafu from our switch to using git recently. The first version I uploaded had the wrong builds of both the Lifx plugin and the mobile web remote plugin included in the package. The Lifx plugin wouldn’t have run at all, The mobile web remote just displayed the color controls for every unit. I’ve re-uploaded the same version with both of those things including the correct version as of 6:30am on 7/14. If you downloaded prior to that and use the mobile web remote or wanted to try the Lifx plugin please download again. Sorry about that... | + | ====9.5.4 Change Log:==== |
+ | * Fixed a problem with the Wiz plugin that would log errors as the libraries now return the name of the scene rather than it’s ID as they did previously. | ||
+ | * Fixed the error that was logged while trying to create a symlink to the internal python version if you did not have a / | ||
+ | * The python symlink is now created inside the XTension Support folder “pythonxt” and you can use that to run python scripts inside XTension or from elsewhere but using the XTension settings. It is especially useful if you are running python scripts from an async shell script in XTension as they will inherit all the path info to run properly where running the built in python may cause errors. | ||
+ | * NEW: Added an option to delay quitting. This will popup a window asking if you really meant to quit, stopping accidental shutdown of the entire program due to misplaced fingers. The window will count down for 30 seconds and then quit the app. This window does not come up if the system tells XTension to quit as if before a restart or something similar. Find the checkbox to turn it on in the Preferences. | ||
+ | * NEW: Added the option to send a value of 0 for a dimmable Unit to the On script if there is no Off script. Normally a value of 0 for any dimmable unit will be sent to the Off script rather than the On script. Unless there is no off script. This meant that previously you potentially had to duplicate some of your logic for handling values in the On and Off script. When this is turned on in the Preference, and a Unit has no Off script. The On script will be run instead with the future value set to 0. This is on by default, but if it causes you issues with some of your scripting you can turn it off in the preferences window. | ||
+ | * Fixed the incorrect link to the mailing list signup page in the purchase dialog. | ||
+ | * Removed some debug logging I failed to remove before the last release. This was in the conversion of potentially confused strings into floats and so did not affect every plugin, but might have logged confusing information occationally. | ||
+ | * There was a change in AppleScript support in OS versions from Ventura on that would actually enforce some, but not all, of the scripting dictionary flags that have never, in the entire history of the Mac, mattered. So us developers got sloppy and failed to add things like the “optional” flag to all the verbs reliably. The first I’ve found and fixed was with the Speak verb where it would tell you that the “in” parameter was required. It is no longer required. So far I have not found any other such issues and a visual search through the dictionary did not reveal any more such issues, but it’s entirely possible there are more parameters that are not properly marked as optional. If you find any such errors please let me know. | ||
+ | * The Interface list window can now be sorted by CPU Usage, Memory Usage and Process ID. This only works if you have the “show more information” option turned on in the gear menu on the window. This can be a great aide in finding the plugin process that is eating up all your CPU or memory and linking a python process shown in the Activity Monitor to the plugin it’s actually running. They all just say “python” in the monitor. But now it’s easier to find the PID number in the list if you sort by it. | ||
+ | * Updated the ngrok client version to 3.5. This is an important update if you are using this service as the old version will no longer be supported sometime in January. There were many changes to the usage of the client, and many more to the layout of the configuration file. I believe I have them all sorted out, but if you have issues let me know. All output from the client is logged during startup so you can check immediately if it thinks it started the tunnels or if it logged errors instead. | ||
+ | * I had previously hidden some of the lower level debugging aids in the contextual menus by having people hold the option key while right clicking. There is really no need for this extra step so I removed it. The Contextual menus for Units and Interfaces will have their “log debug data” and “Reveal in Finder” options at the bottom of all the contextual menus for them. This will make it easier to collect info for me if things start behaving oddly. | ||
+ | * I added the same debug logging info to the contextual menus of global scripts should it ever be necessary to get a look at that. | ||
+ | * To that debug output I added another line of info comparing the length of the Unit Address in both bytes and glyphs. This might be helpful to more easily discover if a plugin or a bug somewhere has inserted invisible characters into the Address field of a Unit causing things to get disconnected in the database and potentially making more and more units being created when there really should be only the one. | ||
+ | * There were some significant updates and improvements in the main program libraries that will make many things run faster and smoother. So far my testing of all of them work just fine. They aren’t a thing I can turn off though, they are just part of the latest compiler update. It will depend on what you’re doing, how busy your machine is and how fast it is in general whether you’ll see any difference at all. Usually the things they improved aren’t an issue until you’re doing something many times in a row. So I expect that the main improvements will be in window redrawing and things like that, but if you have a machine that is very busy it may improve that somewhat throughout. | ||
+ | |||
+ | ----- | ||
+ | |||
+ | NOTE: This disk image no longer includes the older legacy plugins that will not be updated for newer OS versions. If you still need to run the [[supported_hardware: | ||
+ | |||
=====Previous Releases===== | =====Previous Releases===== | ||
{{indexmenu>: | {{indexmenu>: | ||
- | === Older Versions === | + | |
- | [[beta|The Changelog and Download links for builds between 763 and version 9.1 can be found here]] | + |
current.txt · Last modified: 2024/02/05 17:53 by James Sentman