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 [2019/11/08 15:40] – 9.4.24 James Sentman | current [2020/03/22 15:45] – 9.4.28 James Sentman | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====XTension Version 9.4.24===== | + | =====XTension Version 9.4.28===== |
| - | Released: | + | Released: |
| \\ | \\ | ||
| - | Download: [[https:// | + | Download |
| - | zipfile md5 = [[tech_notes: | + | Download for Catalina |
| - | \\ | + | |
| - | Download for Catalina: (awaiting notarization, | + | |
| - | **NOTE!** not all plugins are included in the Catalina | + | |
| \\ | \\ | ||
| + | **NOTE: the catalina download is a notarized disk image file but does not contain the entirety of the plugins as not all are updated to run on Catalina yet. See the Catalina note below or more info. Please do not use this image on a 10.14 (Mohave) or earlier version, use the zip file above.** | ||
| + | |||
| ====Important Info==== | ====Important Info==== | ||
| **Minimum System Version** for this release is OSX 10.10\\ | **Minimum System Version** for this release is OSX 10.10\\ | ||
| + | \\ | ||
| + | **Mac OSX Catalina** As of this moment I do not recommend that anyone update to OSX Catalina. Changes in Catalina have disabled several of the older plugins and the newer ones are not fully tested with it yet. As of this moment I do not recommend running Catalina on your house server. I don’t see any advantages and there are many potential issues not just with XTension. I can provide an Apple notarized DMG file of the subset of plugins that do work properly if this is something that you need. Otherwise do not update to Catalina yet for your house server.\\ | ||
| \\ | \\ | ||
| **Mac OSX Mojave** has changed the requirements for scripting of other applications. You MUST force any script to run that contacts a different application when you upgrade and click “OK” when it asks for permission or your scripts will silently fail when they run later. See the [[tech_notes: | **Mac OSX Mojave** has changed the requirements for scripting of other applications. You MUST force any script to run that contacts a different application when you upgrade and click “OK” when it asks for permission or your scripts will silently fail when they run later. See the [[tech_notes: | ||
| - | \\ | ||
| - | **Mac OSX Catalina** As of this moment I do not recommend that anyone update to OSX Catalina. I am supplying a Notarized dmg version of XTension that will run on Catalina. The regular zip file release and any previous release version will likely not run at all. Please see the [[tech_notes: | ||
| - | \\ | ||
| - | ====9.4.24 Change Log==== | ||
| - | * NEW: added “reset low battery flag” contextual menu item to the unit lists. If you have a unit that has a stuck low battery flag for whatever reason you can now reset it manually. If the low battery flag is actually coming from the interface it will reset itself as soon as the next command from the device is received though. | ||
| - | * NEW: added xtUnit class applescript parameters for the newer Group properties. You can now set the following parameters for Groups, they will have no effect if you try to use them for a non-group unit. They are read/write so you can query them or set them from another script. | ||
| - | * xtGroupBehavior | ||
| - | * xtTreatAsRadioButtons | ||
| - | * xtScriptsRunWhenAutochanged | ||
| - | * xtShowDimmableControls | ||
| - | * xtShowColorControls | ||
| - | * xtShowColorTempControls | ||
| - | * FIX: the xtUnit class property xtFlags now includes the correct battery level, if any, reported by the device. | ||
| - | * FIX: the xtUnit class property xtFlags no longer includes the no longer used “rfOK” flag. | ||
| - | * Totally rebuilt the internal handling of unit properties. They are now more abstracted so that they will be easier to use from other scripting languages once those are available. You can still store AppleScript specific parameters like lists and records but they may not be available to other scripting systems in the future. There should be no changes for how you’re using them at all. For the moment I am maintaining the data in the original format in the database so that if you need to revert to an earlier version of XTension you can do so without losing any data. After some number of releases without any bug reports on the new system I’ll remove those files. | ||
| - | * Change: Global Scripts now update their Last Activity date even if the script fails due to an error. Previously they would fail to update this if the script did not complete successfully. | ||
| - | * Change: Unit Properties are now sent through the Database Sharing plugins. The unit properties are synced in both directions. If you make a change on either side of the shared database connection the change will be sent to the other side. If you make a change on the receiver side while the connection is down or the interface is disabled then the receiver side will be overwritten by the data from the sender side when the interface reconnects. At this time the syncing of the unit properties is limited to Strings, Numbers and Dates. Applescript specific types like Lists and Records are not synced. This is possible to do so please let me know if you need this. | ||
| - | * The new RFX plugin for the older RFX and RFXe devices is no longer considered beta. I and several beta testers have been using it successfully now for months. Note that the newer devices are NOT yet supported by this plugin. Please make sure you’re connecting to one of the older protocol devices and that you select the Legacy protocol in the plugin setup dialog in XTension. The beta level support for that device will appear in the next XTension release. | ||
| - | * FIX: The previous rare but real occurance of the Vera, and potentially some other plugins become unresponsive is fixed. I was finally gifted a duplication of this problem by my own server after having been unable to duplicate it or figure out what was happening at all. It turns out to be a lower level system problem that hung up all networking for a short time. Not all plugins were affected, some seemed to recover just fine, others became suck in a hang down in the system. Since there was no error that could be trapped the only way to fix the problem was to implement a ping and restart system in XTension for the affected plugins. If a plugin of any type goes unresponsive for more than around 2 minutes XTension will quit it and start a new instance which does fix the problem. If the system does ever return a proper error from the networking level that will also result in the interface restarting to get itself running again. | ||
| + | ====9.4.28 Change Log==== | ||
| + | * NEW: The Return Of Alexa! This version has newer plugin versions that can get around the recent changes that Amazon added to their Alexa firmware. **There are several install requirements and configuration changes that are necessary before they will run.** Please have a look at the the [[supported_hardware: | ||
| + | * NEW: The first pass at a Catalina capable RFX plugin for the newer RFX devices. This plugin is in alpha at the moment and incomplete. It does not try to transmit and does not yet support the lighting device types. It is limited to receiving the receive only sensors from Oregon and others. Please do not actually convert your existing plugin to this yet as things may change. Please do disable the current plugin and create a new one using the new plugin to test it. See if the devices you have are properly received and that new units are created in XTension. If you see any errors in the log when receiving them please forward those log entries to me. If you have other problems please also email me that. I will be adding support for the lighting and other transmit capable devices soon. | ||
| + | * NEW: Added the [[supported_hardware: | ||
| + | * Icons in the Select Unit Icon window are now always presented in alphabetical order. | ||
| + | * FIX: The [[supported_hardware: | ||
| + | * FIX: The xBee plugin will not get shutdown for failing to return pings on very quite networks. Previously if you didn’t receive or send at least some command every few minutes XTension would think the interface had hung up and would restart it. | ||
| + | * FIX: Fixed a problem that cause the master log window to not be restored if you had quit the program with a log filter set to an interface or plugin instance. | ||
| + | * FIX: Fixed a timing problem with the [[supported_hardware: | ||
| + | * FIX: Another issue with shared databases if you set a unit property from the on propertyChanged event those messages could also bounce back and forth forever. This is now properly supported. | ||
| + | * FIX: Fixed a problem in the [[supported_hardware: | ||
| + | * FIX: Fixed a problem in the [[supported_hardware: | ||
| + | * FIX: In all plugin configuration and unit configuration windows and dialogs the tab order of controls will be correct, or at least sensible, regardless of the order they are created in within the plugin configuration files. Some of the plugin setup windows were actually tabbing backwards which has always driven me crazy but I’ve never gotten motivated to fix. If you see windows in XTension that still have incorrect or non-sensical tab order please let me know. | ||
| + | * FIX: Fixed a potential issue with sending emails that could cause timeouts to be logged instead of the email being sent. | ||
| + | * FIX: Fixed a minor issue where the transmitted packet count was not updated for a shared database connection. | ||
| + | * Added support for radio button groups in the plugin configuration windows. | ||
| + | * Added support for the barometer/ | ||
| + | * Changed the plugin interface for the current RFX plugin for the legacy RFX devices to not offer to receive the newer RFX device protocol. The two devices are now served by 2 separate plugin. | ||
| + | * Added the ability for a custom column in a unit list to also look into the lower level database of the unit for it’s value. You just need to use the actual database key rather than the name of a unit property. This will be of limited usefulness to the majority of you but has already come in handy for me in debugging things. | ||
current.txt · Last modified: 2024/02/05 17:53 by James Sentman