current:beta
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
current:beta [2023/03/21 18:34] – 9.5.2 pr1 James Sentman | current:beta [2024/02/05 17:51] (current) – 9.5.5b1 James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Beta | + | =====Beta |
- | **XTension | + | |
- | Preview Release 1 of 9.5.2 is now available: [[https:// | + | This is a beta release |
- | * NEW: List Windows will show the number of units in the list, the number with errors and the number with low battery flags after the name of the list. | ||
- | * MQTT Client plugin now sends enumerated values properly as well as receives them, no matter how many, or how few, enumerated values are in the list. | ||
- | * Kasa/ | ||
- | * Weeder: If extra packing characters, or other bogus data characters are received from an IP connected chain they will be thrown out and ignored prior to processing whats left of the data. This will not get around true problems with noise on the data ground or devices resetting due to power supply issues, but if it’s a matter of the wiznet card sending packing characters above the range of printable characters then this should get rid of that, Of course if the noise generates characters within the range of the bytes that are used for normal communications this will not solve the problem either. | ||
- | ----- | + | **This version makes no changes to the format of the Database so returning to a previous version can be done simply by placing the previous version of the application back into service. The default location of the XTension |
- | **XTension | + | |
- | A third and hopefully last beta of 9.5.2 is now available: [[https:// | ||
- | * Added a slight random pause in the startup of the Video plugins as it seems that starting many of them all at once was causing some errors or hangups at the sheer number of processes being started at once. | + | If you’re not interested |
- | * There was an error case in the Video plugin where frames would be corrupt, but rather than an error I could trap and therefore realize the camera was no longer sending valid data the system would return a corrupt frame with no way to tell that an error was occurring. This version adds some, but not all, traps to places where the frames are processed in order to trap this. If a camera starts doing this while it’s being recorded or streamed they will be caught and treated like a stall if they don’t get better on their own. The stream will then restart and go back to working properly. It may not catch this condition when nobody is looking at the stream or when the stream is not being recorded as the frames are either not received or not processed when not necessary. IN which case the stream would be fixed shortly after you started using it again. | + | |
- | * Fixed a bug in the DIY interface that could keep it from reconnecting to a networked device after the device rebooted or was otherwise disconnected from the network. The interface will now reconnect properly. | + | |
- | * Added support | + | |
- | * Added specific support for Kasa Dimmers | + | |
- | * When dealing with Kasa bulbs you can now control how a bulb is treated at power off. See the Kasa documentation for more info on the “nova” effect some bulbs have and how to fix that or set the next power on preset while turning them off. | + | |
- | * The Hubitat plugin now implements sending user name and password if you have set that up on your device. | + | |
- | * The Hubitat plugin now sends more helpful error messages if the API ID or Authentication token is wrong or corrupt in the interface setup. | + | |
- | * The Hubitat will now log more useful messages when the ZigBee Radio changes status rather than logging an unknown push message error. | + | |
- | * MQTT Units are now created with a timeout of 2 minutes instead of 15 seconds to avoid having quite so many on and off for normal devices that dont transmit that rapidly. | + | |
- | * MQTT Units are now created with the “dont log new value receptions” advanced unit option set to avoid having the log filled immediately with messages from them as potentially hundreds of units turn on and off constantly until the timeouts and other things are configured properly. You can turn this logging back on if you wish once you figure out which Units are actually important to you. | + | |
- | * Added the ability to navigate through a JSON packet in the MQTT Units to find the value that is important to you removing the need for most such things to be handled in code. Any JSON packet can be parsed through this but more complex structures, or sending JSON packets to the server, might still need to be handled in code. See the MQTT Plugin documentation for more info. There is also a link to the specifics and some examples on the plugin documentation page. | + | |
- | ----- | + | ===Changes to the location of XTension’s data files=== |
- | **XTension | + | |
- | A second beta of 9.5.2 is now available. [[https:// | + | There are 2 ways that XTension can be installed. If the application is placed in the Applications folder then a folder called “XTension Support” was created in the Users Documents folder and the Database and other support |
- | This beta fixes a problem | + | The location of the XTension Support folder has become an issue with Apple’s iCloud feature of syncing your Documents folder with iCloud. |
- | If a volume | + | It is my advice |
- | ----- | + | ===Process of moving the files=== |
+ | When first run XTension will look for an XTension Support folder in your Documents folder. If it exists in that location but not already in the Application Support folder it will move it and startup normally. Giving you a startup message window telling you exactly what it did. If there is already an XTension Support folder in your Application support folder and it does not contain a database then it will be renamed and the current XTension Support folder will be moved to the new location. If it does contain a database, even if it is an old one, then it cannot move it and will startup with that database along with a message that what appears to be your current database could not be moved and you will have to resolve the conflict manually. There should not be a live database in the Application Support folder however much earlier versions of XTension did use this location and so there may be old and outdated versions of information there that you may have to remove. | ||
+ | ===Switching to Running in the Applications Folder=== | ||
+ | If you are running XTension in the legacy way of being anywhere but the Applications folder you do not have to move anything manually yet. However at some point Apple may enforce that applications have to live in the Applications folder. If you wish to make the change now you can move the XTension application into the Applications folder. Then move all the support folders and database from the folder you used to have the App in to the Documents/ | ||
- | **XTension 9.5.2 Beta 1 (2/ | + | ===Returning to a previous version=== |
+ | If you find this version to cause new problems, please do not just return to the previous version without letting me know exactly what the issue was that caused you to need to do so or it will be much less likely I can get it sorted out by the release. Without XTension running just move the XTension Support folder from the Application Support folder back to your Documents folder and then start the previous version. The Application Support folder is generally hidden from the User and may not be easily visible from the Finder. If so you can use the “Go” menu in the Finder to reveal the Library folder and inside that will be the Application Support folder. If XTension is still running you can use the Reveal Database In The Finder menu item from it’s Database menu, Then Quit XTension and do the move manually before replacing it with the previous version. | ||
- | There is a beta version available of XTension 9.5.2 | + | ====Changelog:==== |
- | Download for all supported architectures: [[https:// | + | |
- | This version contains important fixes to the new video system. This build fixes issues with the disk space management | + | * At startup if XTension finds that your database is being shared to iCloud it will open a startup messages window advising you of this and suggesting that you turn that off. This info is also saved in the database so that if someone sends me a database |
+ | * If the database has already suffered some kinds of corruption from being shared to iCloud there are many things that it can now clean up. This includes deleted units or scripts that have been replaced by an over zealous iCloud sync service. It cannot replace active files that were replaced or reverted incorrectly but this can still be a major help in getting things sorted out. | ||
+ | * The XTension Support folder is moved from the Documents Folder to the Application Support folder. Unless there is already a Database in an older version of the folder | ||
+ | * Improved script error logging. Previously errors that were generated while running handlers in a different script were sometimes not logged causing instead a generic error in the script doing the calling. They will now log more useful information for debugging purposes | ||
+ | * Quite a few major OS versions now Apple changed Applescript to be somewhat, sometimes, unpredictably threaded. This allowed the application to continue to process commands and events while another script might have still been running. This led to confusion and things no longer happening in a linear and logically consistent order. I fixed that back in the day by pausing the command queue while a script was running so that even if the app got control back no more commands would be processed until the current script being run was complete. I recently added some new RTS cameras of higher resolution to my system which is pushing my older Mini a bit and I started getting more regular strange scripting errors that rarely or never happened before. In studying the problem I realized that not all scripts are purely started by received commands or scheduled events anymore. The Idle handler and the DoLater commands use program | ||
+ | * Further new script debugging I’ve added the ability to log runtimes of individual scripts. You can turn this on in the Gear toolbar menu for any script be it an On/Off script or a Global Script. This may be useful if there is a script that sometimes seems to take a lot longer than it should be. Especially if that script is talking to an external app to wait for something. | ||
+ | * Errors that could be logged when deleting more than a single page of Units from a list is now suppressed. It was never a useful error message so no fix was necessary, it’s just confusing debug logging. | ||
+ | * Errors that would sometimes be logged when closing the Interface list window while doing CPU and Memory use displaying in the “show more information” mode are no longer logged. Again these were just over zealous debugging messages and did not indicate a real problem. | ||
+ | * Fixed the incorrect display of version information. The version logged and in the About window | ||
+ | * Made some additions | ||
+ | * Added another debug menu option to log the current state of the globals “thisUnit”, | ||
- | A minimum disk space of 100m is maintained with a default of 5gb. Depending on the number of video streams you are saving to the disk you may wish to keep the disk space free higher than 5gb so that there is enough space to process the current file and record from new ones. Generally there needs to be at least 2x the disk space available as the size of the video snippet but pushing it too close could lead to a snippet failing to be saved at all. | ||
- | Only files inside the folders you select for the video plugins are scanned and deleted if needed. No other folders on the disk are touched. This means that other things not part of the Video recording system might cause the disk to fill up, or to cause more video files to be deleted to keep the space available. | + | [[https:// |
- | There are no other changes to this build from the last release of 9.5.1, so it should not cause any new problems. It also makes no changes to the database layout or structure. If you do need to revert you should not have to revert the database to the backup that is made automatically when this build is first run, but it will be there if you need it. | ||
- | If you suspect an issue with the new disk space management or wish to see debug log output of it’s functioning and what files it chooses please go to the preferences and check the “show debug menu” checkbox. Then in the newly visible debug menu select the "Log Disk Space Management Info." When in debug mode the scan will be run every minute instead of every 5 to collect more debug data which will be written to the log in a lovely orange. You may also use the “Run DiskCheck Now” menu item to force it to run while you’re watching. Uncheck the “Log Disk Space Management Info” menu item to go back to normal functioning. Be aware that other options in the debug menu are undocumented and may cause more problems than it’s worth to play with them. Please do not use other debug menu items unless I ask you to in order to collect more info on other issues. | ||
- | -James 2/25/2023 | ||
current/beta.1679423678.txt.gz · Last modified: 2023/03/21 18:34 by James Sentman