User Tools

Site Tools


current

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
current [2018/07/14 10:44] James Sentmancurrent [2023/02/25 15:22] – added beta link James Sentman
Line 1: Line 1:
-=====XTension Version 9.4.6===== +=====XTension Version 9.5.1===== 
-Released7/13/2018\\+ 
 +**There is a [[current:beta|Beta Version of 9.5.2 Available]] which is important for anyone using the disk space management features of the new video system.**\\
 \\ \\
-Download: [[http://www.machomeautomation.com/files/xtension/xtension_986.zip|XTension v9.4.6 (build 986) 7/13/2018]]\\ 
-zipfile md5 = [[tech_notes:md5|448274952c7346224c2b778594be2b81]]\\ 
  
 +Released 2/3/2023\\
 +\\
 +Download Universal Binary for all Supported OS versions; [[https://www.machomeautomation.com/files/xtension/xtension_9_5_1.dmg|XTension. v 9.5.1 (build 1069)]]\\
  
-====Change Log==== +**Minimum System Version** for this release is OSX 10.10 but not all plugins will function properly prior to 10.13Please start the necessary work to upgrade to at least 10.13 or recommended 10.15 or newerAt some point in the near future it will no longer be possible for me to support anything prior to 10.13 and the video plugins will never work prior to Catalina.
-  NEW: Lifx device support. These are excellent WiFi attached color capable light bulbs. Most of the same features as the phillips hue bulbs but they don’t require a hub. Create a new instance of the Lifx interface and all the devices on the network will magically appear in your database and give you full control over their color and color temperature. These bulbs can also be brighter than the Phillips bulbs as they come in 75 watt equivalent versions. As of this moment the driver is in beta. It does not yet poll the bulbs for local changes or for changes that you might make through their mobile apps or other interfaces. It does not support the more complex devices they sell like the panels or the tracks though that is definitely coming. It also doesn’t have any support for color loops or display presentations yet but that is also coming. +
-  NEW: Vera UI7 natively supports the standard virtual device that is commonly used in places where the vera insists on having a unit. +
-  NEW: Vera UI7 now has a device type for Scene Controller. This will support Central Scene capable dimmers like the [[supported_modules:wallmote|WallMote Quad]] and the Hank branded scene controllers. +
-  NEW: wiki article discussing the [[supported_modules:wallmote|WallMote]] scene controllers. +
-  * NEW: wiki artivle discussing the excellent [[supported_modules:hs-wd100|Home Seer HS-WD100+ dimmer]] family of devices and how to set their inner parameters with XTension. +
-  * NEW: Vera UI7 new [[dictionary:unitcontrol:setdata|setData]] command for setting parameters inside ZWave devices. This will let you easily set things like a switches ramp rate or turning it’s LED’s on and off. +
-  * NEW: Vera UI7 support for the new [[supported_modules:hs-wd200|Home Seer HS-WD200+ dimmers]] and how to control their lights individually via the above mentioned setData command. You can now control the color and flash rate of each LED on these new dimmers directly from XTension to show the state of something or flash an alert or anything you choose. The WD200 devices also support 2 new gestures. You can now trap in XTension the quadruple tap and the pentuple tap if you need that many central scene commands :)  +
-  * 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 receivedPreviously 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 displays updates for remote changes of thermostat mode and fan mode changes. Previously it failed to receive these and the mode would only update if you changed it from XTension. +
-  * 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 to the deviceThis works for any color or color temperature supported devicePreviously the web UI’s were limited to clicking on the limited pallet of choices or selecting a preset. +
-  * 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 in order to send you more info about the device. +
-  * 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 it can send you. +
-  * 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 will set a default label in the Mode and State units for the current mode and state. If you’re happy with those values you don’t have to change anything however if your thermostat supports different values or you just wish to change the wording of those you can still add an advanced label state tag to the On and Off labels of the unit to have it display what you wishYou can override the labels sent by the plugin. Previously I was sending actual values for the On and Off labels which would have overwritten your custom settings. +
-  * 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 to connect with no delay between attempts. +
-  * 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:xtension:recycleinterface|Recycle Interface]] verb. This means that it returns very quickly and the interfaces will shutdown and restart cleanly in the background.+
  
 +**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.1 Change Log:====
 +
 +  * NEW: [[supported_hardware:mqtt|MQTT Client Plugin]] for getting info from, or sharing info to, any MQTT Broker.
 +  * NEW: [[supported_hardware:mqtt:espresence|ESPresense Support]] in the new MQTT Client Plugin.
 +  * NEW: [[supported_hardware:nohassle4|Plugin for No Hassle AV 4x4 HDMI Switches]]
 +  * NEW: [[supported_hardware:nohassle8|Plugin for No Hassle AC 8x8 HDML Switches]]
 +  * NEW: [[supported_hardware:controlbywebout|Control By Web plugin]] that makes outgoing connections rather than using the inter device communications protocol. The original Control By Web plugin is unaffected and still included in the package.
 +  * NEW: If there are important messages generated during startup they will also display in a new Startup Messages window. This way problems that would otherwise be lost in a very long log output are more easy to see and then deal with. This was build first to support the checking for multiple-interface collisions see next item...
 +  * NEW: During database load any collisions in Multi-Interface setups will be logged and also written to the new Startup Messages Window. In order for multiple interfaces to work there must not be a unit actually receiving messages at the same address on the extra interfaces. This makes it easier to find this situation and fix it.
 +  * NEW: The [[:video|new Video system]] now inserts the time stamp and any other messages you add for the reason for recording to the closed captioning track of the recorded video snippet. This is superior to just overlaying the video as it does not obscure any of the frame as it can be moved around in the player or even turned off if you do not need to see this.
 +  * NEW: [[:video|new Video system]] now will display any events you sent as the reason for a recording on the original Web Interfaces which brings this into line with the way the original Video Pitcher system worked.
 +  * NEW: In the Video Encoder plugin whenever a recording is complete and post processed or encoded and ready an event is called in the plugins interface script passing you the name of the video stream it came from as well as the full path to the file so if you wish to script uploading them or doing anything else with them it is now easier to do so.
 +  * NEW: If you’re using the “live recording” option that doesn’t use the Video Encoder separate process the above event is sent to the video plugin’s interface script instead. So they can also be handled in the same way, just in a different place.
 +  * NEW: The [[supported_hardware:hubitat|hubitat plugin]] now supports getting the data from objects with the attributes of “rate”, “valve” and “totalConsumptionToday”. This was for the Moen FLO Smart Shutoff and water meter device but will work for any device that uses those keywords/topics for it’s data.
 +  * NEW: Added a “SendRaw” handler to the [[supported_hardware:arduino|Arduino plugin]] so that in addition to the regular Unit commands you can send any arbitrary data to your device as well.
 +  * FIX: Units added later to a list shared via home kit will no longer be at risk of getting a Duplicate Accessory ID error.
 +  * FIX: If you have units that are already suffering from the above problem there are [[supported_hardware:homekit|new script functions]] you can use to find and correct the errors.
 +  * FIX: Fixed an issue that would cause a slight increase in CPU usage in the MJPEG Camera plugin each time it reconnected the stream.
 +  * FIX: Fixed an issue with the Amcrest Camera API plugin that would cause it’s CPU usage to go to 100% after a stream connection was lost and restarted.
 +  * FIX: Improved the syncing of the database to the plugins fixing an issue that sometimes caused an error during the load that could have stopped any units after the error from loading at all.
 +  * FIX: The available ram that is logged when XTension is starting up was calculating incorrectly displaying what looked like just a few meg rather than the correct value. It is not logged properly and is therefore useful again.
 +  * CHANGE: Calling plugin registered scripting handlers will now generate an error in the script if you call one that does not exist or misspell it or something similar. Previously such errors were lost silently.
 +  * FIX: When doing the “log debug data” for a unit the thisUnit value is set properly letting it show up when filtering the log for output from that Unit.
 +  * FIX: Fixed an issue loading Unit Icon files that were not JPEGS. All system supported graphic types are again working.
 +  * CHANGE: When setting the enumerations for a unit value the individual comma delimited entries are now trimmed of any leading or trailing spaces when they are saved, It is common to type a list with spaces in it that you don’t actually want in the value like “one, two, three” which would have resulted in the value being “ two” now when saving the Unit the values are fixed so that the previous would become the correct “one,two,three"
 +  * FIX: Fixed a typo in the debug logging in the Phillips Hue plugin that caused a second error while trying to log useful data about a first one. The error messages are now potentially useful instead of being an error about the error handling.
 +  * CHANGE: if you select the “Show More Information” menu item from the gear menu of the Interface List window the CPU usage of each plugin process is calculated for all running plugins. This makes looking for something having a problem or stuck in a loop where it shouldn’t be easier. This is not a completely trivial extra load so the data is only gathered if you have the list window in the Show More Information state and not in the normal more compressed state.
 +  * FIX: The camera API plugins are now python compiled before adding to the application bundle during the build process. They always worked fine but they would have taken longer to load as they needed to be compiled by the python interpreter each time and the compiled data could not be saved as they are inside the signed portion of the application so doing so would break the developer signature. 
 +
 +
 +
 +-----
 +
 +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:cm19]], [[supported_hardware:cm15a]], [[supported_hardware:zwave]] or the various Smarthome X10 interfaces please download [[tech_notes:catalina|the legacy plugins package from here]] and install the ones you need via the “Install Plugin” menu item of the “Database” menu. 
 + 
 =====Previous Releases===== =====Previous Releases=====
 {{indexmenu>:current#2|js#doku}} {{indexmenu>:current#2|js#doku}}
  
-=== 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