Mac Home Automation

User Tools

Site Tools

You are here: Macintosh Home Automation With XTension » Download XTension 9.5.4
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 [2023/02/13 14:52] – external edit 127.0.0.1current [2023/06/07 15:36] – James Sentman
Line 1: Line 1:
-=====XTension Version 9.5.1=====+=====Download XTension 9.5.2=====
  
-Released 2/3/2023\\+> There is a Beta version available: [[current:beta|]] 
 + 
 +Released 4/9/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)]]\\+Download Universal Binary for all Supported OS versions; [[https://www.machomeautomation.com/files/xtension/xtension_9_5_2.dmg|XTension. v 9.5.2 (build 1076)]]\\
  
 **Minimum System Version** for this release is OSX 10.10 but not all plugins will function properly prior to 10.13. Please start the necessary work to upgrade to at least 10.13 or recommended 10.15 or newer. At 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. **Minimum System Version** for this release is OSX 10.10 but not all plugins will function properly prior to 10.13. Please start the necessary work to upgrade to at least 10.13 or recommended 10.15 or newer. At 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.
Line 9: Line 11:
 **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. **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.
  
 +====9.5.2 Change Log:====
  
-====9.5.1 Change Log:==== +  * NEW: [[supported_hardware:sysinfo|Sysinfo Plugin]] for monitoring Disk space, Disk Usage, Network Usage and Networking Errors. 
- +  * NEW: [[supported_hardware:zadarma|Zadarma plugin]] to send SMS messages via the commercial Zadarma service. 
-  * NEW: [[supported_hardware:mqtt|MQTT Client Plugin]] for getting info from, or sharing info to, any MQTT Broker. +  * NEW: New option in the Preferences dialog to Dont Stop A Restart With "Window Has Changes" Dialog. This is not really the correct way to handle this so consider it a stop gap measure until I can properly support the saving and restoring of the window state. Previously if you had left a script window open with changes, or an Edit Unit window open with changes and the machine tried to restart automatically the “this document has changes, are you sure you wish to throw them away” message would halt the shutdown and leave XTension in a non-operating condition. With this option turned on XTension will still provide those warnings if you manually try to close a window that has changes, but if the app is being quit it will allow the changes to be lost and so not cause hangups or problems when restarting the server. If this is not how you wish it to behave then you can turn this off in the Preferences. 
-  * NEW: [[supported_hardware:mqtt:espresence|ESPresense Support]] in the new MQTT Client Plugin. +  * NEW: List windows now display the number of Units in the List as well as the number of Units in an error condition or with low battery messages. This is shown in the title of the window after the List name. 
-  * NEW: [[supported_hardware:nohassle4|Plugin for No Hassle AV 4x4 HDMI Switches]] +  * NEW: The [[supported_hardware:mqtt|MQTT plugin]] now lets you get values out of a payload that is in JSON format without having to script your way through it. You can use the new JSON Path field to give names of entries and indexes into json arrays to find the value you are looking for. This applies to all non-special device units and so once you get to the info you want any of the Units will then be able to look for numerical data, or enumerated values or just put the value into the Description at that point. This does not effect the sending of payloads. If you have to send a JSON packet you’ll still have to build that in a script for the moment and use the raw publish command. 
-  * NEW: [[supported_hardware:nohassle8|Plugin for No Hassle AC 8x8 HDML Switches]] +  * NEW: The [[supported_hardware:hubitat|Hubitat plugin]] now properly implements sending of a user/password to the hubitat if you have that option turned on in the hub. 
-  * 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: The [[supported_hardware:hubitat|Hubitat plugin]] now properly handles valve devices and controlling them via their open/close commands. 
-  * 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 TEMPORARY: I have made some changes to the standard off handling in the Hubitat that fixes some oddness with enumerated commands. I believe this works for all existing devices as well but just in case there is a new checkbox in the hubitat settings that will allow you to drop back to the old handling if it causes you any problems. Please let me know if you have to use this for any reason and the details of that otherwise I will be removing it in the next version unless I hear from people with the need to do this. 
-  * 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 [[supported_hardware:hubitat|Hubitat plugin]] has a new checkbox that will log status messages from the Hubitat. These are normally things like “the bedroom lights were turned on” but it might be useful to see these if there are issues or debugging that you’re trying to sort out. It can be a lot of extra logging that doesn’t usually contain any useful information so it is an option you have to turn on if you wish to see 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: Those same Hubitat status messages are now automatically added to a Unit property called “Status Message” and another Unit Property “Status Timestamp” will be the date/time when the current message was received. This way you can trap them in a script, or add a custom column to any List window to show them if you wish rather than just logging them. The above checkbox for logging the status messages does not have to be turned on to send this info to the Unit Properties. This is always done. 
-  * 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: The [[supported_hardware:tplink|Kasa plugin]] now properly supports in wall dimmers as well as just bulbs. 
-  * 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: Added support for Ramp Rates to the [[supported_hardware:tplink|Kasa plugin]]so you can control the dimming speed on a command by command basis if you wish. 
-  * 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: Added several options to the [[supported_hardware:tplink|Kasa plugin]] for the handling of preset values for Kasa bulbs vs dimmers. 
-  * 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: The CPU Usage figures for plugins shown in the Interface List window when “show more information” is selected now includes the CPU usage of any helper apps or sub processes that the plugin might be running. This makes them much more accurate and useful for very CPU intensive plugins such as the Video plugins or the rtlamr or other plugins that use helper apps. 
-  * 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. +  * NEW: The Interface List window also shows a percent of memory use for the plugin instance and any child processes after the CPU Usage number. 
-  * FIX: Units added later to a list shared via home kit will no longer be at risk of getting a Duplicate Accessory ID error. +  * NEW: A new option in the Interface List window lets you chose if the CPU Usage calculation is done based on 100% a single CPU core, or 100% being every CPU available in the machine. So if you have 10 cores and you chose individual then 100% would be using a full core, but per machine that would only be 10% of the overall machine load. Whichever makes more sense to you when viewing it. The numbers are usually very low and so many not show up on the graph at all unless you increase their values by setting it to per CPU. Plugins that are using GPU resources or that are using helper apps may show as using more than 100% if per CPU is selected. This is OK. 
-  * 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. +  * CHANGE: The helper app for the Video system that does the encoding is now a proper background app and so will not show up in the dock as it is running. 
-  * FIX: Fixed an issue that would cause a slight increase in CPU usage in the MJPEG Camera plugin each time it reconnected the stream. +  * CHANGE: The [[supported_hardware:mqtt|MQTT plugin]] now creates new units with a default timeout of 2 minutes rather than the original 15 seconds which caused a lot of unnecessary chattering in otherwise valid receptions. You can still adjust this to whatever value is correct for your system after the units are created. This does not change any setting you have set in existing Units created by the plugin. 
-  * 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. +  * CHANGE: The [[supported_hardware:mqtt|MQTT plugin]] now creates new units with the “do not log new value receptions” checkbox set as it is possible for this plugin to generate a truly obscene amount of logging if it’s in an area with a lot of devices. You can turn this back on for the Units you wish to watch. It will not change the setting of any already existing Units. 
-  * 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. +  * CHANGE: The [[supported_hardware:weedtech|Weeder plugin]] will filter non-ascii characters that might be received when making IP connections. This may help if there is noise on the data line that inserts random data or if an ethernet/serial device is stuck in a mode sending packing characters. If it is because of noise it will not actually solve the problem but it will give you more time to sort it out. If it’s a packing problem it will probably be OK as long as the packing character is not in the range of ascii that the weeder cards use to communicate normally. This same filtering is not yet applied to direct serial connections, please let me know if that is a thing that would help anyone. 
-  * 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. +  * The [[supported_hardware:hubitat|Hubitat plugin]] now throws more useful errors if there is a problem with the API number, or API Key or user/password so it’s easier to sort out a failing connection. Previously it would just complain that it couldn’t connect but did not elaborate. 
-  * 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. +  * The [[supported_hardware:hubitat|Hubitat plugin]] will now log Zigbee Radio status changes or errors as proper messages from the Hubitat rather than as unknown messages. 
-  * 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: Found a problem with the [[supported_hardware:tplink|Kasa plugin]] that might have caused some Units to be created with the wrong device type, or even no device type at all causing XTension to create it as if it was an old school X10 unit as in the absence of the more recent data structures it seems to regress to it’s origins. I am not certain this has fixed all the problems people were having with this and the situation that it would happen in is odd and therefore rare and difficult to duplicate. Specifically it was only a problem if the kasa dimmer type was discovered directly after a powerstrip type. 
-  * FIX: Fixed an issue loading Unit Icon files that were not JPEGS. All system supported graphic types are again working. +  * FIX: If the [[supported_hardware:mqtt|MQTT plugin]] receives messages from ESPresense devices that do not have a “distance” parameter for some reason it will just ignore that message. Previously this could lead to further updates being ignored as it threw out other updates after the error. While this will allow processing to continue I believe that this can only happen due to an error or a bug or some problem with the ESPresense device or software and this will not be able to fix that. You may lose reception entirely from that receiver, or just that beacon that it’s sending, but something deeper is causing this. At least XTension will continue to process valid packets from anywhere else. 
-  * 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: The [[supported_hardware:mqtt|MQTT plugin]] will now properly publish enumerated values on systems that use a period instead of a comma as their decimal separator. 
-  * 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. +  * FIX: Added a random pause up to 3 seconds when starting up multiple [[video:rtsp|RTSP video streams]] at the same time. On older or more resource limited machines this was causing problems if many streams tried to startup at exactly the same moment. 
-  * 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: An [[video:rtsp|RTSP video stream]] can become confused at some point and stop sending full frames from some devices. Previously the plugin would happily display and record these partial or badly corrupted frames. Under most circumstances it will now realize that they are not valid frames and restart the stream in order to recover from this problem. 
-  * 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. +  * FIX: The [[supported_hardware:diy|DIY Plugin]] will now properly recover from the loss of a network serial connection the same way that it does for a local serial connection. 
 +  * FIX: Older binary plugins such as the Vera plugin would throw errors when trying to issue some unit specific scripting commands. This was due to the changes in the previous version that allowed the scripts to throw applescript errors if you called a handler that did not exist. The older plugins were not registering their handlers in the same way and so fell afoul of this. They will now let you call any of the handlers without an error. 
 +  * FIX: Fixed some problems with the managed folder system that is used by the new video plugins for managing disk space on the recording volume. This will now properly keep the minimum disk space you have set available. If you suspect something is going wrong with this there is an option in the new Debug menu (see below) that will let you log it’s progress and calculations to the log which you can then send to me for debugging. 
 +  * FIX: The managed folder system now recovers from having a volume not present at startup, or if a volume is unmounted and then re-attached. It will let you know if the Volume is unavailable and then will begin scanning it again when it re-appears. 
 +  * DEBUG: Added a checkbox to the preferences for “show debug menu” this will reveal a debug menu where I have gathered many of the various hidden debugging options in the app for easier access when it is necessary to gather more info for me on a problem. Please do not experiment with these unless I’ve asked you to as they may generate huge amounts of log output or break other things if used incorrectly.
  
  
current.txt · Last modified: 2024/02/05 17:53 by James Sentman