current:beta
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:beta [2023/03/21 18:45] – James Sentman | current:beta [2023/06/05 13:49] – added beta 3 James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Beta | + | =====Beta |
- | **XTension | + | |
- | Preview Release 1 of 9.5.2 is now available: [[https://machomeautomation.com/ | + | The currently available beta version |
- | * 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. | + | Beta 3 is continuing |
- | * MQTT Client plugin now sends enumerated values properly on machines that use a decimal separator other than a period. | + | |
- | * 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 | + | |
- | * Hubitat | + | |
- | * I have improved the logic in handling off messages to the hubitat as well. since this changes existing behavior i have added a checkbox in the interface setup that defaults to the new method but if that causes you any difficulty you can switch to the original method as easily as unchecking a checkbox. DO NO do this and just assume that I somehow know you’re having a problem. If you need to do this please tell me why and as much about it as you can otherwise | + | |
- | * NEW: In the Hubitat settings is a new checkbox | + | |
- | ----- | + | [[https:// |
- | **XTension | + | |
- | A third and hopefully | + | Keep in mind this is a beta build and may contain bugs or annoyances and not all expected features or changes may yet be implemented. No database changes are made so if you to have to revert to the last release version simply replace the application with the previous version and all will be well. |
- | | + | **Changelog:** |
- | | + | |
- | | + | |
- | | + | |
- | * 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. | + | |
- | ----- | + | * **Hue Plugin:** |
- | **XTension | + | * Hue Plugin: Fixed an issue where it could send continual updates for a sensor value even if the value had not changed. |
+ | | ||
+ | * **Video System:** | ||
+ | * Video Encoder Plugin: Added a checkbox so you can suppress logging of video encoding times if you wish. | ||
+ | * Video: Removed error logging for stalled streams as this would fill the log if the camera was offline for any length of time. To log this information please implement the stalled script handler in the Interface Script and write to the log whatever information is helpful. | ||
+ | * **Sysinfo Plugin:** | ||
+ | * System Info Plugin: no longer claims in it’s startup log message to be the Disk Space plugin. | ||
+ | * Fixed an incorrect default link to the boot volume so that this will work without having to edit it each time. | ||
+ | * **Internal Python:** | ||
+ | * Python: A symlink to the built in python3 version is now added to / | ||
+ | * Python: | ||
+ | * **Web Remote:** | ||
+ | * Web Remote: New documentation of the hashing of web remote links to immediately go to a specific page or view. This can be useful if you are saving specific links as iOS shortcuts, or creating a Kiosk type application. This is not a new feature, but was never properly documented. [[webremote: | ||
+ | * Web Remote: Added several new scripting commands to control sessions in the web remote. This lets you programmatically change the view on a specific device to say, a video page or a View in response to motion or other event. Additionally you can script a popup alert or timed message in any color to display on all active sessions or only on specific ones. [[webremote: | ||
+ | * Web Remote: Added support for a resource folder that will be served as regular files through the web remote built in web server. This way if custom controls or other features you are adding need to load a specific image or other support file they can do so if you put it in the resources directory inside your XTension Database. [[webremote: | ||
+ | * Note that these changes have not been rolled into the mobile web remote plugin, only the desktop version. | ||
+ | * **Plugin API:** | ||
+ | * A new key for the info.json file that will allow a plugin to receive any scripting command the user issues. This simplifies some kinds of plugin tasks at the expense that users script will not know if the command succeeded or not, all commands will just be sent and forgot. This does not affect regular using the app, only plugin developers. | ||
+ | * Added the capability for plugins to display information in new text windows and to append to or change the display of one without opening a new window each time. This mostly affects plugin developers but I used it in the new and changed show info commands in the Amcrest API plugin above. | ||
+ | * All plugins now log their version number in the startup message from the information stored in their info.json file. This will keep them from always being wrong as I forget to update it in 2 places instead of just 1. | ||
+ | * **Hubitat Plugin:** | ||
+ | * Hubitat: Added entries to the “insert” toolbar menu for the central scene Held, and Released events to make it easier to script these without having to visit the wiki to look up the specifics. | ||
+ | * Hubitat: Added support for Energy and Usage units. If a device reports these values a Unit will be created for them. | ||
+ | * Hubitat: Added support for values that come in as “STRING” rather than numerical or enumerated. This is a bit of a hack as it’s impossible to know what format these things will seem to be. First the value is scanned to see if there is a number in the first part of the string. If there is then the Unit will be dimmable and the value will be placed in the value of the Unit. for example: “3.2 Hours” would create a dimmable unit and set the value to 3.2. The Default Label and the description for the unit will be set to the string as it is sent. So even though the Unit value is 3.2, the display of the value in any XTension interfaces would be “3.2 Hours” If there is no number at the beginning of the string then the UNit will not be dimmable and it will just have it’s default label and description set to the text. You can capture the set description event in the unit’s on script to get the text and parse manually if you need to. | ||
+ | * Hubitat: Some devices from the Hubitat will now have more descriptive, | ||
+ | * Hubitat: The list of supported commands for each Unit is now saved to a [[dictionary: | ||
+ | | ||
+ | | ||
+ | * Amcrest Camera API: Added support for specific Units to link to Object Detection if your camera supports it. You can now create a Unit to get an ON when a human is detected, or when a vehical is detected and so forth. | ||
+ | * Amcrest API New Status and Display commands: | ||
+ | * setFontScale(0.1..2.0) control the size of the text displayed over the image. | ||
+ | * setChannelTitleVisible( true|false) | ||
+ | * setChannelTitleLocation( 34, 12) | ||
+ | * setChannelTitleColor( R, G, B, A) | ||
+ | * setChannelTitleBackColor( R, G, B, A) | ||
+ | * setUserDisplayVisible( index, true|false) | ||
+ | * setUserDisplayText( index, “the info to display”) | ||
+ | * setUserDisplayLocation( index, xloc, yloc) | ||
+ | * setUserDisplayColor( R, G, B, A) | ||
+ | * setUserDisplayBackColor( R, G, B, A) | ||
+ | * setLogoVisible( true|false) hide or show the Amcrest logo image overlay | ||
+ | * setLogoLocation( xLoc, yLoc) | ||
+ | * setLogoFilename( “osd.bmp”) your camera must support allowing you to change this or it will do nothing. | ||
+ | * setTimeDisplayVisible( true|false) | ||
+ | * setTimeDisplayLocation( xLoc, yLoc) | ||
+ | * setTimeDisplayColor( R, G, B, A) | ||
+ | * setTimeDisplayBackColor( R, G, B, A) | ||
+ | * setTimeDisplayFormat( “yyyy-M-dd hh:mm:ss t”) see the wiki link above for a table of valid format string entities. | ||
+ | * note that there is a limit to the number of overlays the camera can “blend” into the encoding video. Check the capabilities below to find out what the limit is for your camera. They may all be different. My doorbell cam can only do 2 at once. | ||
+ | * changed the logEvents() command to be showEvents() and it now shows the info in a window rather than just writing it to the log. | ||
+ | * changed logMotionRegions() showMotionRegions() which also shows the list in a separate window rather than just writing it to the log. | ||
+ | * showCapabilities() opens a window with most, but not all, of the capabilities of the camera listed. There are still some more to add | ||
+ | * There are a LOT of other things I can add to this plugin that could be controlled. | ||
+ | * **Scripting Dictionary: | ||
+ | * NEW: the [[dictionary: | ||
+ | * NEW: The [[dictionary: | ||
+ | * **Xtension UI:** | ||
+ | * New: Each unit will get a new Unit Property called Created with the date the unit was created. You can add this to any List view by control clicking in the headers and selecting create custom column. Then you can sort lists by the date the Unit was created and not just the last activity date. For new Units this is set as they are created and then never changed. For existing Units the date is taken from the creation date of their folder within the database. This seems to work pretty well for most units most of the time, but there may be a date in the past where you restored a database or otherwise performed an action on it that would have reset those dates. This is still the best I can do but keep in mind that older Units may not show the date they were actually created, but the last time you zipped and moved the database or something like that. | ||
- | A second beta of 9.5.2 is now available. [[https:// | ||
- | |||
- | This beta fixes a problem with the most recent release that rendered the non-scripting dictionary commands to older interfaces like the Vera unavailable. These commands now work normally again. | ||
- | |||
- | If a volume is missing or not mounted when a video plugin attempts to register it as a space managed volume, XTension will log a single error but keep trying during the disk space scans to find it and when it appears it will begin scanning it normally. If a drive is unmounted and remounted it will continue to be properly scanned by the disk space manager for video recording. | ||
- | |||
- | ----- | ||
- | |||
- | |||
- | **XTension 9.5.2 Beta 1 (2/ | ||
- | |||
- | |||
- | There is a beta version available of XTension 9.5.2 | ||
- | Download for all supported architectures: | ||
- | |||
- | 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. | ||
- | |||
- | 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. | ||
- | |||
- | 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.txt · Last modified: 2024/02/05 17:51 by James Sentman