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/17 14:13] – 9.5.2 beta 3 info James Sentman | current:beta [2024/02/05 17:51] (current) – 9.5.5b1 James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Beta | + | =====Beta |
- | **XTension 9.5.2 Beta 3 (3/ | + | |
- | A third and hopefully last beta of 9.5.2 is now available: [[https:// | + | This is a beta release |
- | * 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. | ||
- | * 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 for ramp rate to the Kasa/ | ||
- | * Added specific support for Kasa Dimmers to the Kasa/ | ||
- | * 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. | ||
- | ----- | + | **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 second beta of 9.5.2 is now available. [[https:// | ||
- | This beta fixes a problem with the most recent release that rendered | + | If you’re not interested in the history and why the support folder needs to be moved skip to the next section. |
- | If a volume is missing or not mounted when a video plugin attempts | + | ===Changes |
- | ----- | + | 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 files were placed there. You can also continue to use XTension as it was in days of old and run it from any other folder on your drive. If you do this the database and some support folders are created along side the app inside this same folder but an XTension support folder is still created in the Documents folder. |
+ | The location of the XTension Support folder has become an issue with Apple’s iCloud feature of syncing your Documents folder with iCloud. This service remains potentially a problem for many things but can and does cause corruption of the XTension database as files seem to be updated too often for it to remain in sync. It seems to restore files that were deleted as well as replacing new versions with older versions on occasion. | ||
- | **XTension | + | It is my advice to not use this iCloud feature at all as it causes the same problems with other files you may have stored in your documents folder. If you have this turned on you should turn it off immediately to avoid losing information. In the meantime moving the XTension Support folder to the Application Support folder will solve the problem for XTension |
+ | ===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. | ||
- | There is a beta version available of XTension | + | ===Switching to Running in the Applications Folder=== |
- | Download for all supported architectures: | + | If you are running |
- | This version contains important fixes to the new video system. This build fixes issues with the disk space management that could lead to the drives you’re storing video to filling up. The program now properly honors your settings in the video plugins setup pages where you set a minimum disk space to keep available on the disk. It will scan every 5 minutes and remove enough of the oldest files across all of the managed folders to bring the available space back up to your minimum setting. | + | ===Returning |
- | A minimum disk space of 100m is maintained with a default of 5gb. Depending on the number of video streams | + | If you find this version to cause new problems, please do not just return |
- | Only files inside | + | ====Changelog: |
+ | |||
+ | * 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 to debug I can check easily if this is the source of some of the problems. | ||
+ | * 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 | ||
+ | * 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 that might exist in the Application Support folder. In which case no files are moved or deleted and a message is displayed asking | ||
+ | * 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 | ||
+ | * 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 | ||
+ | * 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 | ||
+ | * 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 | ||
+ | * Made some additions and changes to the runtime debugger window | ||
+ | * Added another debug menu option | ||
+ | |||
+ | |||
+ | [[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.1679062412.txt.gz · Last modified: 2023/03/17 14:13 by James Sentman